MX Component For Android Ver1 - Reference Manual SH (NA) - 081498-B (10.15)

MX Component for Android Version 1
Reference Manual
-SW1DNC-ACTAND-B
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual carefully and pay full attention to safety to handle the product correctly.
The precautions given in this manual are concerned with this product only. For the safety precautions for the programmable
controller system, refer to the user's manual for the CPU module used and the system manual, (MELSEC iQ-R Module
Configuration Manual, QCPU User's Manual(Hardware Design, Maintenance and Inspection), MELSEC-L CPU Module
User's Manual (Hardware Design, Maintenance and Inspection)).
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".
Indicates that incorrect handling may cause hazardous conditions, resulting in

WARNING death or severe injury.
Indicates that incorrect handling may cause hazardous conditions, resulting in

CAUTION minor or moderate injury or property damage.
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious
consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.
[Design Precautions]
WARNING
When data change or status control are performed from a device such as a tablet to a running
programmable controller CPU, create an interlock circuit outside the programmable controller to
ensure that the whole system always operates safely.
Since a wireless LAN is used for communication, the communication may not be performed properly
depending on the environment. Ensure the communication method other than using this product for
the situation when the wireless LAN communication cannot be established.
[Startup and Maintenance Precautions]

CAUTION
The online operations performed from a device such as a tablet to a running CPU module have to be
executed after the manual has been carefully read and the safety has been ensured.
Improper operation may damage machines or cause accidents.
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
INTRODUCTION
Thank you for purchasing the Mitsubishi FA software, MELSOFT series.
This manual is designate for users to understand operations of MX Component for Android.
Before using this product, please read this manual carefully, and develop familiarity with the functions and performance of MX
Component for Android to handle the product correctly.
3
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
CHAPTER 1 OVERVIEW 7
1.1 What Is MX Component for Android? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Main Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
CHAPTER 2 SYSTEM CONFIGURATION 9

2.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Usable CPU modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Accessible Ethernet modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
CHAPTER 3 USAGE 14
3.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Creating Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.4 Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.5 Communication method (open method) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
CHAPTER 4 ACCESSIBLE DEVICES 20

4.1 Accessible Device List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Programmable controller CPU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
C Controller module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Motion CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.2 Considerations for Devices and Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Consideration for bit devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Considerations for using labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
CHAPTER 5 METHODS 27
5.1 Method List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
5.2 Details of Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
MELMxCommunication class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
MELMxOpenSettings class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
MELMxLabel class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
MELMxErrorCode class. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3 Considerations for Using Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.4 Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Created application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Sample method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
4
CHAPTER 6 TROUBLESHOOTING 59
6.1 Error Processing and Corrective Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
6.2 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
APPENDIX 64
Appendix 1 Added and Changed Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
METHOD INDEX 66
CONTENTS
REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
5
RELEVANT MANUALS
Manual name [manual number] Description Available form
MX Component for Android Version 1 Reference Manual Explains the system configuration, operation methods, e-Manual
[SH-081498ENG] (this manual) and methods of MX Component for Android. EPUB
PDF
e-Manual refers to the Mitsubishi FA electronic book manuals that can be browsed using a dedicated tool.
e-Manual has the following features:
Required information can be cross-searched in multiple manuals.
Other manuals can be accessed from the links in the manual.
The hardware specifications of each part can be found from the product figures.
Pages that users often browse can be bookmarked.
TERMS
Unless otherwise specified, this manual uses the following terms.
Term Description
CW Configurator A generic product name for model name, SWnDND-RCCPU ('n' indicates its version.)
C Controller module A generic term for MELSEC iQ-R series C Controller module and Q series C Controller module
Setting/monitoring tools for the C A generic product name for model names, SW4PVC-CCPU or SW3PVC-CCPU
Controller module
Ethernet module A generic term for MELSEC iQ-R series-compatible EN71, Q series-compatible E71, and L series-compatible E71
Built-in Ethernet CPU A generic term for CPU modules with Ethernet ports
FX5CPU A generic term for FX5UCPU and FX5UCCPU
GX Works2 A generic product name for model names, SWnDNC-GXW2 ('n' indicates its version.)
GX Works3 A generic product name for model names, SWnDND-GXW3 ('n' indicates its version.)
LCPU A generic term for L02SCPU, L02SCPU-P, L02CPU, L02CPU-P, L06CPU, L06CPU-P, L26CPU, L26CPU-P, L26CPU-
BT, and L26CPU-PBT
L series-compatible E71 LJ71E71-100
MELSEC iQ-R series CPU module A generic term for MELSEC iQ-R series programmable controller CPU, C Controller module, and motion CPU
MELSEC iQ-R series C Controller R12CCPU-V
module
MELSEC iQ-R series motion CPU A generic term for R16MTCPU and R32MTCPU
MELSEC iQ-R series-compatible RJ71EN71 (when using the Ethernet function)
EN71
MX Component for Android A generic product name for model names, SWnDNC-ACTAND-B ('n' indicates its version.)
QCPU A generic term for Q00JCPU, Q00UJCPU, Q00CPU, Q00UCPU, Q01CPU, Q01UCPU, Q02CPU, Q02HCPU,
Q02PHCPU, Q02UCPU, Q03UDCPU, Q03UDECPU, Q03UDVCPU, Q04UDHCPU, Q04UDEHCPU, Q04UDVCPU,
Q06HCPU, Q06PHCPU, Q06UDHCPU, Q06UDEHCPU, Q06UDVCPU, Q10UDHCPU, Q10UDEHCPU, Q12HCPU,
Q12PHCPU, Q12PRHCPU, Q13UDHCPU, Q13UDEHCPU, Q13UDVCPU, Q20UDHCPU, Q20UDEHCPU, Q25HCPU,
Q25PHCPU, Q25PRHCPU, Q26UDHCPU, Q26UDEHCPU, Q26UDVCPU, Q50UDEHCPU, and Q100UDEHCPU
Q series CPU A generic term for Q series programmable controller CPU, C Controller module, and motion CPU
Q series C Controller module A generic term for Q12DCCPU-V, Q24DHCCPU-V, and Q24DHCCPU-LS
Q series motion CPU A generic term for Q172DCPU, Q173DCPU, Q172DSCPU, and Q173DSCPU
Q series-compatible E71 A generic term for QJ71E71-100, QJ71E71-B5, and QJ71E71-B2
RCPU A generic term for RnCPU and RnENCPU
RnCPU A generic term for R04CPU, R08CPU, R16CPU, R32CPU, and R120CPU
RnENCPU A generic term for R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, and R120ENCPU
Programmable controller CPU A generic term for RCPU, FX5CPU, QCPU, and LCPU
Motion CPU A generic term for MELSEC iQ-R series motion CPU and Q series motion CPU
Universal model QCPU A generic term for Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q03UDVCPU, Q03UDECPU,
Q04UDHCPU, Q04UDVCPU, Q04UDPVCPU, Q04UDEHCPU, Q06UDHCPU, Q06UDVCPU, Q06UDPVCPU,
Q06UDEHCPU, Q10UDHCPU, Q10UDEHCPU, Q13UDHCPU, Q13UDVCPU, Q13UDPVCPU, Q13UDEHCPU,
Q20UDHCPU, Q20UDEHCPU, Q26UDHCPU, Q26UDVCPU, Q26UDPVCPU, Q26UDEHCPU, Q50UDEHCPU, and
Q100UDEHCPU
6
1 OVERVIEW
1
This chapter explains the features of MX Component for Android.
1.1 What Is MX Component for Android?

MX Component for Android is the library for reading and writing values of devices and labels in the programmable controller
from a tablet.
This product can be used when creating a user program to communicate with a programmable controller from Android OS.
Wireless communication performs between a device such as a tablet and wireless LAN router, and Ethernet communication
performs to access a programmable controller.
When creating an application, the time for creating a program to communicate with a programmable controller can be
shortened by using MX Component for Android.
This product can also be used for the static library of Java.
Writing
Tablet Device/Label
(AndroidTM OS)
Reading
Wireless LAN router Programmable Controller
1.2 Main Functions

MX Component for Android has the following main functions.
Creation of tablet applications

An application for a tablet to read or write devices and labels in a programmable controller can be created easily without
knowing a communication method with the programmable controller.
Programming by using labels (RCPU only)

Devices in a programmable controller can be accessed by using labels*1 when the communication target is RCPU. Therefore,
a program is easy to see and recreation of an application is not required even after the device configuration is changed.
*1 Labels selected in "Access from External Device" in the global editor of GX Works3 can be used.
Creation of safe applications for security

A safe application for security can be created by using this library since the remote password is encrypted*1 when
communicating with a programmable controller in which the remote password has been set.
*1 The remote password is encrypted in the following cases only.
When accessing MELSEC iQ-R series programmable controller
When accessing Q series CPU or LCPU via Ethernet module
Sample program
An application can be created by using the provided sample program as a reference. The sample program also is helpful to
see how to use the library or correct an error etc.
1 OVERVIEW
1.1 What Is MX Component for Android? 7
MEMO
1 OVERVIEW
8 1.2 Main Functions
2 SYSTEM CONFIGURATION
This chapter explains the system configuration of MX Component for Android.
2.1 System Configuration 2

The following shows system configurations for development and operation.
For development
Development personal computer

(Windows OS) Wireless LAN router Programmable controller
Install the created application.

Built-in Ethernet CPU/
Ethernet module
Tablet
(AndroidTM OS)
For operation
Wireless LAN router Programmable controller

Tablet
(AndroidTM OS)
Built-in Ethernet CPU/
Ethernet module
Hub Hub
Considerations
Access route
A tablet can be accessed the module which is directly connected with a wireless LAN router. Other stations via Ethernet
module cannot be accessed.
2.1 System Configuration 9
2.2 Device Configuration
The following shows usable CPU modules and accessible modules.
Usable CPU modules

Series Module Module name Remarks
MELSEC iQ-R series Programmable controller R04CPU, R04ENCPU, R08CPU, R08ENCPU,
CPU R16CPU, R16ENCPU, R32CPU, R32ENCPU,
R120CPU, R120ENCPU
C Controller module R12CCPU-V The Ethernet port of a C Controller module cannot be
used to access.
Use the Ethernet port of a programmable controller
CPU or an Ethernet module.
Motion CPU R16MTCPU, R32MTCPU The PERIPHERAL I/F connector cannot be used to
access.
Use the Ethernet port of a programmable controller
CPU or an Ethernet module.
FX5CPU*1 Programmable controller FX5UCPU, FX5UCCPU
CPU
Q series Programmable controller Q00JCPU, Q00UJCPU, Q00CPU, Q00UCPU, An Ethernet module is required.
CPU Q01CPU, Q01UCPU, Q02CPU, Q02HCPU,
Q02PHCPU, Q02UCPU, Q03UDCPU,
Q04UDHCPU, Q06HCPU, Q06PHCPU,
Q06UDHCPU, Q10UDHCPU, Q12HCPU,
Q12PHCPU, Q12PRHCPU, Q13UDHCPU,
Q20UDHCPU, Q25HCPU, Q25PHCPU,
Q25PRHCPU, Q26UDHCPU
Q03UDECPU, Q03UDVCPU, Q04UDEHCPU, The Ethernet port of a programmable controller CPU
Q04UDVCPU, Q06UDEHCPU, Q06UDVCPU, cannot be used to specify other stations.
Q10UDEHCPU, Q13UDEHCPU, An Ethernet module is required when specifying other
Q13UDVCPU, Q20UDEHCPU, CPUs.
Q26UDEHCPU, Q26UDVCPU,
Q50UDEHCPU, Q100UDEHCPU
C Controller module Q12DCCPU-V, Q24DHCCPU-V, Q24DHCCPU- The Ethernet port of a C Controller module cannot be
LS used to specify other stations.
An Ethernet module is required when specifying other
CPUs.
Motion CPU Q172DCPU, Q173DCPU, Q172DSCPU, The PERIPHERAL I/F connector cannot be used to
Q173DSCPU access.
The Ethernet port of a programmable controller CPU
cannot be used to access a motion CPU.
An Ethernet module is required when accessing a
motion CPU.
LCPU Programmable controller L02SCPU, L02SCPU-P An Ethernet module is required.
CPU
L02CPU, L02CPU-P, L06CPU, L06CPU-P,
L26CPU, L26CPU-P, L26CPU-BT, L26CPU-
PBT
*1 Use the firmware version '05' or later.
10 2.2 Device Configuration
Accessible Ethernet modules
An Ethernet module is required to communicate with a CPU module which has no Ethernet port.
Series Module name
*1
MELSEC iQ-R series RJ71EN71
Q series*2 QJ71E71-100, QJ71E71-B5, QJ71E71-B2 2
L series*3 LJ71E71-100
*1 Use the firmware version '02' or later.

*2 Use the first five digits of the serial number are '15042' and function version is 'D' or later.
*3 Use the first five digits of the serial number are '15042' and function version is 'A' or later.
2.2 Device Configuration 11
2.3 Operating Environment
The following shows the operating environment of MX Component for Android.
Development environment
Item Description
Personal computer *1
Personal computer on which Windows OS operates
Operating system Microsoft Windows 8.1 Operating System (Japanese/English)
Microsoft Windows 8.1 Pro Operating System (Japanese/English)
Microsoft Windows 7 Professional Operating System (Japanese/English) (32-bit version/64-bit version)
Development environment*2 and Development application Eclipse Kepler Service Release '2' or later
language
Development language Java

Software Java Platform, Standard Edition 7 Development Kit ('JDK 7u60' or later)*3
*1 CPU modules, required memory, and HDD free capacity need to follow the recommended specifications of the operating system,
development environment and language.
*2 Operations by using the simulator included in the development environment are not guaranteed.
*3 Download JDK from ORACLE website.
Operating environment
Item Description
Smartphone and tablet Smartphones and tablets on which AndroidOS operates (Module types that can perform the wireless LAN
communication)
Operating system Android OS 4.2, 4.3, 4.4
Only ARM is supported. ('x86' is not supported.)
When using Android OS 4.4.2, only 'Dalvik VM' is supported. ('ART VM' is not supported.)
12 2.3 Operating Environment
2.4 Considerations
The following shows the considerations for using MX Component for Android.
Considerations for programming and each setting

2
Electric interruption and a noise affection
Some packets may be lost due to the electric interruption or noise affection during communication with a wireless LAN. When
creating a user program, create it to include the retransmission processing and reopen processing of the line according to the
system.
Erroneous data reception at timeout

An erroneous data reception may be caused if timeout has occurred while the Ethernet port of FX5CPU or QCPU is
connecting. Create a program to include the reopen processing of the line.
Functions and applications that disconnect Wi-Fi communication automatically

When any of the following functions or applications are enabled on a device such as a tablet, packets may be lost and timeout
error may occur due to the disconnection of Wi-Fi communication.
If timeout error has occurred, perform the close processing, then perform the reopen processing again. In another way, use
after disabling the functions and applications.
Battery saving function of Wi-Fi setting*1
Auto connection/disconnection functions of Wi-Fi network*1
Auto disconnection applications of Wi-Fi communication
*1 Depending on the device that is used, the setting method is different; "Wi-Fi Advanced" "Wi-Fi optimization" or "Wi-Fi Advanced"
"Wi-Fi timer".
Wireless LAN switching

On the communication with a wireless LAN, some packets may be lost and timeout error may occur due to the wireless LAN
switching*1. In the environment that a wireless LAN is switched, create a program to include the retransmission processing
and reopen processing of the line according to the system.
*1 Wireless LAN roaming, hand-over, and disconnection etc.
Considerations for Android specification

If a device such as a table is in sleep status or an application is running as a background task, Ethernet communication of
application that uses this product may be disconnected. In this case, perform the reopen processing as necessary.
This product is the communication library to perform the Ethernet communication. In operating systems, there are some
essential items and recommendations related to the tasks for communication. Create a program by following them.
Example: Thread the communication processing and perform it in a background.
Considerations for using this product with other products

For the connection setting between a device such as a tablet and wireless LAN, set a protocol that encrypts data for the
connection settings such as WPA2.
An illegal data access may occur if a protocol that does not encrypt data is selected for the connection settings.
Select a much safer security setting between a device such as a tablet and wireless LAN.
2.4 Considerations 13
3 USAGE
This chapter explains how to use MX Component for Android.
3.1 Installation
The following shows the procedure to use this library on the development environment of Android application (Eclipse).
Importing the library (so file)

Operating procedure
1. Create a new project by using Eclipse.
2. Copy the following files and folder from the CD-ROM, which is provided with this product, to "jni" folder in the project
created newly.
"libs" folder
"libinterface.so.X.XX" file*1
"libMXComponent.so.X.XX" file*1
"libSupport.so.X.XX" file*1
*1 'X.XX' after the file extension "so" indicates the number of its version.
Example: libSupport.so.1.01
3 USAGE
14 3.1 Installation
3.2 Creating Projects
When creating a project, the following are required; importing the library, setting the permission, and reading the library
Importing the library

This library can be imported as the following package name.
jp.co.melco.mxcomponent
Setting the permission for the socket communication

Add the following statement in the "AndroidManifest.xml" to use the socket communication.
<uses-permission android:name="android.permission.INTERNET"></uses-permission>
3 USAGE
3.2 Creating Projects 15
Reading the library
This library is a shared library. Create a program to read the library by using Eclipse.
3.3 Update
To download the update version of MX Component for Android, please consult your local Mitsubishi representative.
Operating procedure
1. Delete the files and folder of this library from the "jni" folder in which this library has been copied when installing.
2. Copy the following files and folder that are in the downloaded folder to the "jni" folder.
"libs" folder
"libinterface.so.X.XX" file*1
"libMXComponent.so.X.XX" file*1
"libSupport.so.X.XX" file*1
*1 'X.XX' after the file extension "so" indicates the number of its version.
Example: libSupport.so.1.01
3. Check that all files and folder are copied and the file version are updated.
Checking the version of MX Component for Android

The version of this library can be checked with the numbers after the file extension "so".
Ex.
The version of "libSupport.so.1.01" is '1.01'.
3.4 Uninstallation
Delete the files and folder copied when installing them.
3 USAGE
16 3.3 Update
3.5 Communication method (open method)
To communicate with a tablet, set the parameters of the Ethernet communication.
Set the parameters on the following setting screens.
Connection target Parameter setting Setting screen
RCPU MELSOFT connection Page 18 GX Works3 Module Parameter
MELSEC iQ-R series-compatible EN71 MELSOFT connection Page 18 GX Works3 Module Parameter (Ethernet)
FX5CPU
QCPU (Built-in Ethernet port)
SLMP
MC protocol
Page 18 GX Works3 Module Parameter
Page 19 GX Works2 PLC Parameter
3
Q series-compatible E71 MELSOFT connection Page 19 GX Works2 Network Parameter Ethernet/CC IE Field
Q series C Controller module MC protocol Page 19 Setting/monitoring tools for the C Controller module CCPU
Parameter (SW4PVC-CCPU)
LCPU (Built-in Ethernet port CPU) MC protocol Page 19 GX Works2 PLC Parameter
L series-compatible E71 MELSOFT connection Page 19 GX Works2 Network Parameter Ethernet/CC IE Field
Precautions
To communicate with a CPU module which has no Ethernet port, set the parameters of Ethernet communication to the
Ethernet module.
The parameters of Ethernet communication in the motion CPU are same in the multiple CPU system. For the combination
of CPU modules that can be used in a multiple CPU system configuration, refer to the manuals of each module.
Settings for RnENCPU are different depending on the Ethernet ports used.
A port of CPU part: The settings when the connection target is RCPU
A port of network part: The settings when the connection target is MELSEC iQ-R series-compatible EN71
3 USAGE
3.5 Communication method (open method) 17
Setting screen
For details on the settings, refer to the manual of each module.
GX Works3 Module Parameter
GX Works3 Module Parameter (Ethernet)
3 USAGE
18 3.5 Communication method (open method)
GX Works2 PLC Parameter
GX Works2 Network Parameter Ethernet/CC IE Field
Setting/monitoring tools for the C Controller module CCPU Parameter (SW4PVC-CCPU)

<Q24DHCCPU-V/-LS> <Q12DCCPU-V>
3 USAGE
3.5 Communication method (open method) 19
4 ACCESSIBLE DEVICES
This chapter explains the accessible devices with this library.
4.1 Accessible Device List

The following table shows the applicable devices for reading/writing devices of this library.
Programmable controller CPU

: Accessible, : Not accessible
Category Device name*1,*2 Symbol Type Notation Access target*3
RCPU FX5CPU QCPU/
LCPU
System device Special relay SM Bit Decimal
Special register SD Word Decimal
User device Input X Bit Hexadecimal
Octal
Output Y Hexadecimal
Octal
Internal relay M Decimal
Latch relay L Decimal
Annunciator F Decimal
Edge relay V Decimal
Link relay B Hexadecimal
Data register D Word Decimal
Link register W Hexadecimal
Timer (T) Contact TS Bit Decimal
Coil TC Decimal
Current value TN Word Decimal
Long timer (LT) Contact LTS Bit Decimal
Coil LTC Decimal
Current value LTN Double Word Decimal
Retentive timer Contact STS Bit Decimal
(ST)
SS Decimal
Coil STC Decimal
Current value STN Word Decimal
SN Decimal
Long retentive Contact LSTS Bit Decimal
timer (LST) Coil LSTC Decimal
Current value LSTN Double Word Decimal
Counter (C) Contact CS Bit Decimal
Coil CC Decimal
Current value CN Word Decimal
Long counter (LC) Contact LCS Bit Decimal
Coil LCC Decimal
Current value LCN Double Word Decimal
Link special relay SB Bit Hexadecimal
Link special register SW Word Hexadecimal
Step relay S Bit Decimal
Direct access input DX Hexadecimal
Direct access output DY Hexadecimal
20 4.1 Accessible Device List
RCPU FX5CPU QCPU/
LCPU
Index register Z Word Decimal
LZ Double Word Decimal
File register*4,*5 R Word Decimal
ZR Decimal
Extended data register D Word Decimal *6
Extended link register W Word Hexadecimal *6
*7,*8
Link direct device Link input J\X Bit Hexadecimal
Link output J\Y Hexadecimal
Link relay J\B Hexadecimal
Link special relay J\SB Hexadecimal 4
Link register J\W Word Hexadecimal
Link special register J\SW Hexadecimal
Module access device*7 Module access device U\G*9 Word Decimal
CPU buffer memory CPU buffer memory access device U3E\G Word Decimal
access device*7 Fixed cycle communication area U3E\HG Decimal
access device
Module refresh register Module refresh register RD Word Decimal
*1 Local devices can not be accessed.

*2 Digit specification, bit specification, and index modification specification are not available.
*3 Even if the accessibility of device is accessible () in the table, some of them may not be accessible () due to the restrictions of
methods. For details, refer to the considerations of each method.
*4 When the file register consists of multiple blocks, use the device codes in the sequential number access method.
*5 In GX Works3, specify "Use Common File Register in All Programs" in the CPU parameter. In GX Works2, specify "Use the following
file" in the PLC parameter.
*6 Only universal model QCPU and LCPU support the devices.
*7 Some methods are restricted since the devices are classified as the device extension specification.
*8 For the link direct devices (J), specify a network number in hexadecimal.
*9 For the module access device (U\G), specify the I/O number of the target module.
Example: U20\G1000 (when the I/O number is '200H' and the address is '1000'.)
4.1 Accessible Device List 21
C Controller module
Numbers in the access target column indicate the CPU modules: (1) MELSEC iQ-R series C Controller module, (2) Q series
C Controller module
Category Device*1,*2 Symbol Type Notation Access target*3
(1) (2)
System device Special relay*4 SM Bit Decimal
Special register*4 SD Word Decimal
Internal relay*4 M Decimal
Data register*4 D Word Decimal
File register ZR Word Decimal
Link direct device Link input J\X Bit Hexadecimal
Link output J\Y Hexadecimal
Link relay J\B Hexadecimal
Link special relay J\SB Hexadecimal
Link register J\W Word Hexadecimal
Link special register J\SW Hexadecimal
Module access device Module access device U\G Word Decimal
CPU buffer memory access CPU buffer memory access device U3E\G Word Decimal
device Fixed cycle communication area access U3E\HG Decimal
device

*4 The Q12DCCPU-V of which the first five digits of the serial number are '12042' is accessible.
22 4.1 Accessible Device List
Motion CPU
Numbers in the access target column indicate the CPU modules: (1) MELSEC iQ-R series motion CPU, (2) Q series motion
CPU
(1) (2)
System device Link special relay SM Bit Decimal
Special register SD Word Decimal
Internal relay M Decimal 4
Annunciator F Decimal
Data register D Word Decimal
Motion register # Decimal
Module access device*4 Module access device U\G*5 Word Decimal
CPU buffer memory access CPU buffer memory access device U3E\G Word Decimal
device*4 Fixed cycle communication area access U3E\HG Decimal
device

*4 Some methods are restricted since the devices are classified as the device extension specification.
*5 For the module access device (U\G), specify the I/O number of the target module.
Example: U20\G1000 (when the I/O number is '200H' and the address is '1000'.)
4.1 Accessible Device List 23
4.2 Considerations for Devices and Labels
The following shows the considerations for using devices and labels.
Consideration for bit devices

The place of memory need to be considered when reading/writing bit devices in batches. Bit devices are stored in word units
in the memory. Note these points when obtaining/setting bit values of target devices.
The byte-order of Android is the big endian.
Ex.
When reading a point (one word) from M0
Upper byte Lower byte
M7 M6 M5 M4 M3 M2 M1 M0 M15 M14 M13 M12 M11 M10 M9 M8
1 byte 1 byte
The bit devices are stored in order from upper bytes.
Considerations for using labels
Data type of label

The following shows the variable types in this library (Java) corresponding to the data type of labels.
Labels of which data types are timer, retentive timer, counter, long timer, long retentive timer, or long counter are treated as
the structure type. For details, refer to the following section.
Page 26 Data type of label treated as the structure type
Data type of label Variable type in this library (Java) Definition name
Bit Boolean MEL_MX_LABEL_DATATYPE_BIT
Word [Signed] Integer MEL_MX_LABEL_DATATYPE_WORD
Word [Unsigned]/Bit String [16-bit] Integer MEL_MX_LABEL_DATATYPE_UNSIGNED_WORD
Double Word [Signed] Long MEL_MX_LABEL_DATATYPE_DOUBLE_WORD
Double Word [Unsigned]/Bit String [32-bit] Long MEL_MX_LABEL_DATATYPE_UNSIGNED_DOUBLE_WO
RD
FLOAT (Single Precision) Float MEL_MX_LABEL_DATATYPE_FLOAT_SINGLE
FLOAT (Double Precision) Double MEL_MX_LABEL_DATATYPE_FLOAT_DOUBLE
String (32) String MEL_MX_LABEL_DATATYPE_STRING_ASCII
String [Unicode] (32) String MEL_MX_LABEL_DATATYPE_STRING_UNICODE
Time Long MEL_MX_LABEL_DATATYPE_TIME
24 4.2 Considerations for Devices and Labels
Specification methods of label name
Specify the registered label names in a CPU module when reading/writing the labels.
The applicable labels are as shown below.
Simple data type

Specify the data types described in the following section.
Page 24 Data type of label
Array type
Up to three dimensions of array type labels can be specified.
Specify a label name and indexes of the array element (decimal).
For the data type of array type labels, only the simple data type can be specified.
4
Ex.
When specifying up to three dimensions: Label1[10,10,10]
Structure type
Specify the structure type labels.
Specify all elements by connecting each element name of the structure with the period.
For the last element, the simple data type or array type can only be specified.
The whole structure cannot be specified by specifying the structure name only.
Ex.
Applicable: stLabel1.stLabel2.bMember1 (The simple data type label is specified for the last element.)
Inapplicable: stLabel1.stLabel2 (The structure type label is specified for the last element.)
Precautions
If the specific conditions of label name length are not satisfied, the label may not be specified. For details on the conditions,
refer to each method (considerations).
Digit specification, bit specification, and index modification specification are not available. Inapplicable label names are as
follows;
Label type Specification example
Bit specification of labels Label.3
Digit specification of labels K4Label
Specification of index modification LabelZ0
Specification of multiple CPU No.2 U3E1\Label
The alias name cannot be specified.
4.2 Considerations for Devices and Labels 25
Data type of label treated as the structure type
Labels of the following data types are treated as the structure type that includes a contact, coil, and current value for its
elements. Note the specification method of label names when reading/writing the labels.
Timer
Retentive timer
Counter
Long timer
Long retentive timer
Long counter
Ex.
When reading the current value of the label name 'TimerLabel' in which the long retentive timer is assigned, specify the data
type as follows;
TimerLabel.N
The following shows the members of data type handled as the structure type.
Data name Member name Data type
Contact S Bit
Coil C Bit
Current value N Timer, retentive timer, counter: Word (Unsigned)
Long timer, long retentive timer, long counter: Double Word (Unsigned)
26 4.2 Considerations for Devices and Labels
5 METHODS
This chapter explains the procedure and functions of methods provided by the library.
Procedure for using methods

The following flow chart shows the basic order when reading and writing devices/labels by using methods of MX Component
for Android.
Start
MELMXOpenSettings
Set the parameters.
MELMXCommunication
5
Execute open method.
Failed
Check return values.
Success
Read/Write data.
Target for reading/writing: Labels

Devices/Labels
Devices
MELMXLabel
Set the parameters.
MELMXCommunication MELMXCommunication
Call readDeviceBlock method, Call readArrayLabel method,

writeDeviceRandom method. writeLabelRandom method.
Failed
Check return values.
Success Not Time-out

Check error codes.
Time-out
MELMXCommunication
Execute close method. Refer to the error code list.
End
To use the methods in a program, open the communication line at the beginning of the program, and close it at the end of the
program.
5 METHODS
27
5.1 Method List
The following table shows the method list.
Class Method Function Reference
MELMxCommunication MELMxCommunication Constructor Page 29 MELMxComminication (Constructor)
open To open the communication line Page 29 open (To open the communication line)
close To close the communication line Page 30 close (To close the communication line)
readDeviceBlock To read the devices in batch Page 31 readDeviceBlock (To read the devices in
batch)
writeDeviceBlock To write the devices in batch Page 32 writeDeviceBlock (To write devices in
batch)
readDeviceRandom To read the devices randomly Page 33 readDeviceRandom (To read devices
randomly)
writeDeviceRandom To write the devices randomly Page 34 writeDeviceRandom (To write devices
randomly)
readArrayLabel To read the data by specifying the array type Page 35 readArrayLabel (To read the data by
label specifying the array type label)
writeArrayLabel To write the data by specifying the array type Page 35 writeArrayLabel (To write the data by
label specifying the array type label)
readLabelRandom To read the data by specifying multiple labels Page 36 readLabelRandom (To read the data by
specifying multiple labels)
writeLabelRandom To write the data by specifying multiple Page 36 writeLabelRandom (To write the data by
labels specifying multiple labels)
MELMxLabel MELMxLabel Constructor Page 41 MELMxLabel (Constructor)
getValues To obtain the label data Page 41 getValues (To obtain the label data)
getName To obtain the label name Page 41 getName (To obtain the label name)
getDataType To obtain the data type of label Page 42 getDataType (To obtain the data type of
label)
setBitLabel To set the label data of Bit type Page 42 setBitLabel (To set the label data of Bit
type)
setWordLabel To set the label data of Word (Signed) Page 42 setWordLabel (To set the label data of
Word (Signed))
setUnsignedWordLabel To set the label data of Word (Unsigned) Page 43 setUnsignedWordLabel (To set the label
data of Word (Unsigned))
setDoubleWordLabel To set the label data of Double Word Page 43 setDoubleWordLabel (To set the label
(Signed) data of Double Word (Signed))
setUnsignedDoubleWordLabel To set the label data of Double Word Page 43 setUnsignedDoubleWordLabel (To set
(Unsigned) the label data of Double Word (Unsigned))
setFloatSingleLabel To set the label data of FLOAT (Single Page 44 setFloatSingleLabel (To set the label data
Precision) of FLOAT (Single Precision))
setFloatDoubleLabel To set the label data of FLOAT (Double Page 44 setFloatDoubleLabel (To set the label
Precision) data of FLOAT (Double Precision))
setAsciiStringLabel To set the label data of ASCII character Page 44 setAsciiStringLabel (To set the label data
string of ASCII character string)
setUnicodeStringLabel To set the label data of Unicode character Page 45 setUnicodeStringLabel (To set the label
string data of Unicode character string)
setTimeLabel To set the label data of Time Page 45 setTimeLabel (To set the label data of
Time)
5 METHODS
28 5.1 Method List
5.2 Details of Methods
The following shows the details of each method.
MELMxCommunication class
It is the class to access a CPU module for reading/writing data.
Create multiple instances as necessary when performing communication with multiple CPU modules.
Details of methods
MELMxComminication (Constructor)
MELSEC iQ-R series CPU FX5CPU Q series CPU LCPU

Item Description
Class name MELMxCommunication
5
Method definition void MELMxCommuinication()
Argument None
Return value None
Function It is the constructor of this class.
Up to 10 instances can be created for this class. The operation is not guaranteed if 11 or more instances are created.
Reference None
Considerations None
open (To open the communication line)


Item Description
Method definition int open(
MELMxOpenSettings openSettings,
String remotePassword
)
Argument [in]openSettings Specify the instance of MELMxOpenSettings class that stores the setting values for connection.
For details, refer to the following section.
Page 37 MELMxOpenSettings class
[in]remotePassword Specify a password to unlock the remote password.
Specify 'null' when any remote password has not been set in the module.
For 'null', the unlock processing of remote password is not executed.
Return value MX_SUCCESS: Succeed
Except for MX_SUCCESS: Failed (Page 59 Error Code List)
Function Opens the communication line.
The communication with one CPU module is enabled per one instance. When performing communication with multiple CPU
modules, create multiple instances as necessary.
Multiple Ethernet modules or built-in Ethernet CPUs are required when simultaneously accessing a CPU module by using
multiple instances with TCP/IP. One port is required for one instance. The communication between one port and two or more
instances cannot be performed.
Reference close()
Considerations Remote password
A remote password is unlocked in the open method, and it is locked again when the close method is called.
The operation related to the remote password is the same as that for Ethernet modules and built-in Ethernet CPU.
When 'null' is specified to 'remotePassword' (argument) even if a remote password has been set to the Ethernet module or
built-in Ethernet CPU, an error will be detected with the method to read/write devices and labels (without the open method).
5 METHODS
5.2 Details of Methods 29
close (To close the communication line)

Item Description
Method definition int close()
Argument None
Function Disconnects the communication.
Reference open()
Considerations While the close method is executing, if the disconnection request of TCP connection has not reached to the CPU module or
Ethernet module due to the disconnection of the Ethernet cable on the CPU module or Ethernet module side, or the power of
the wireless router OFF. The connection of the CPU module or Ethernet module side is retained.
Wait until the connection is disconnected.
Time until the connections to each connected module are disconnected

Connected module Check item
RCPU GX Works3: Module Parameter [Application Settings] [Timer Settings for Data
Communication]
MELSEC iQ-R series-compatible EN71
FX5CPU
QCPU (Built-in Ethernet port) Inapplicable (Timeout value of KeepAlive: 45 seconds)
LCPU (Built-in Ethernet port)
Q series-compatible E71 GX Works2: Network Parameter Ethernet/CC IE Field Network Type: Ethernet [Initial
Settings] Timer Settings
L series-compatible E71
Q series C Controller module Inapplicable (Timeout value of KeepAlive: 30 seconds)
5 METHODS
30 5.2 Details of Methods
readDeviceBlock (To read the devices in batch)

Item Description
Method definition int readDeviceBlock(
String deviceName,
int size,
int[] readDatas
)
Argument [in]deviceName Specify the device names which include the start reading device number.
[in]size Specify a number of read points .
Up to 960 points can be read.
[out]readDatas The read device values are stored.
Function
Use when reading sequential device values.
5
Reads device values for the number of points specified to 'size' (argument) from the device specified to 'deviceName'
(argument), and stores them to 'readDatas' (argument) in batch.
Device specification Example: Read the data for three points (three words) from M0
method deviceName="M0", size=3
(when specifying bit Data storage example (one element of an array: 32-bit)
devices) readDatas[0]: M0 to M15
readDatas[1]: M16 to M31
readDatas[2]: M32 to M47
Since the data of bit device is stored in the elements of an array (32-bit) by word unit, the upper
2-bytes are padded with '0'.
The data storage example of bit devices are different depending on the environment. For
details, refer to the following section.
Page 24 Consideration for bit devices
Device specification Example: Read the data for three points from D0
method deviceName="D0", size=3
(when specifying word Data storage example (one element of an array: 32-bit)
devices) readDatas[0]: D0
readDatas[1]: D1
readDatas[2]: D2
Since the data is stored in the elements of an array (32-bit), the upper 2-bytes are padded with
'0'.
Reference open(), close(), writeDeviceBlock()
Considerations Device name The following device names cannot be specified. An error occurs if specified.
Long timer: LTN (Current value)
Long retentive timer: LSTN (Current value)
Long counter: LCN (Current value)
Index register: LZ
Device extension The devices used the extension specification cannot be specified. (Example: 'U3E1\G0' cannot
specification be specified.)
Number of read points The maximum number of read points are within the range that satisfies the following formula.
Start reading device number + number of read points end device number
Bit device specification Only the multiples of 16 can be specified for the device number when specifying bit devices.
Specify the number of elements equal or greater than that specified to 'size' (argument) for 'readDatas' (argument).
5 METHODS
writeDeviceBlock (To write devices in batch)

Item Description
Method definition int writeDeviceBlock(
String deviceName,
int size,
int[] writeDatas
)
Argument [in]deviceName Specify the device names that include the start writing device number.
[in]size Specify the number of write points
Up to 960 points can be written.
[in]writeDatas Specify the array of device values to be written.
Function Use when writing sequential device values.
Writes device values for the number of points specified to 'size (argument) from the device specified to 'deviceName'
(argument) in batch.
Specify the device value, which is to be written, to 'writeDatas' (argument)
Device specification Example: Write the data for three points (three words) from M0
method deviceName="M0", size=3
(when specifying bit Data storage example (one element of an array: 32-bit)
devices) writeDatas[0]: M0 to M15
writeDatas[1]: M16 to M31
writeDatas[2]: M32 to M47
Since the data of bit device is stored in the elements in an array (32-bit) by word unit, the upper
2-bytes are padded with '0'.
The data storage example of bit devices are different depending on the environment. For
details, refer to the following section.
Page 24 Consideration for bit devices
Device specification Example: Write the data for three points from D0
method deviceName="D0", size=3
(when specifying word Data storage example (one element of an array: 32-bit)
devices) writeDatas[0]: D0
writeDatas[1]: D1
writeDatas[2]: D2
Since the data is stored in the elements of an array (32-bit), the upper 2-bytes are padded with
'0'.
Reference open(), close(), readDeviceBlock()
Considerations Device name The following device names cannot be specified. An error occurs if specified.
Long timer: LTN (Current value)
Long retentive timer: LSTN (Current value)
Long counter: LCN (Current value)
Index register: LZ
Device extension The devices used the extension specification cannot be specified. ('U3E1\G0' is not acceptable.)
specification
Number of write points The maximum number of write points are within the range that satisfies the following formula.
Start writing device number + number of write points end device number
Bit device specification Only the multiples of 16 can be specified for the device number when specifying bit devices.
Specify the number of elements equal or greater than that specified to 'size' (argument) for 'writeDatas' (argument).
5 METHODS
readDeviceRandom (To read devices randomly)

Item Description
Method definition int readDeviceRandom(
String[] deviceNames,
int[] readDatas
)
Argument [in]deviceNames Specify the device name, which includes device number, in an array.
Processes the number of elements of the array as the number of read point. Therefore,
specifying the number of read points with an argument is not required.
Up to 96 points can be read.
[out]readDatas The read device values are stored.
Function Use when reading values by specifying multiple devices individually. 5
Reads device values from the multiple devices specified to 'deviceNames' (argument), and stores them to each element of
'readDatas' (argument).
Device specification Example: Read the device values of M0, D10, and LZ20
method deviceNames="M0", "D10", "LZ20"
Data storage example (one element of an array: 32-bit)
readDatas[0]: M0 (ON/OFF is judged in bit 0.)
readDatas[1]: D10
readDatas[2]: LZ20
Reference open(), close(), writeDeviceRandom()
Considerations Devices and the devices used the extension specification cannot be specified together. (Example: 'U3E1\G0' and 'D0' are
not acceptable to specify together.) When specifying the device used the extension specification, specify the devices only to
'deviceNames' (argument).
Specify the number of elements equal or greater than that of read points to 'readDatas' (argument).
5 METHODS
writeDeviceRandom (To write devices randomly)

Item Description
Method definition int writeDeviceRandom(
String[] deviceNames,
int[] writeDatas
)
Argument [in]deviceNames Specify the device name, which includes device number, in an array.
Processes the number of elements of the array as the number of write points. Therefore,
specifying the number of write points with an argument is not required.
The maximum number of write points is as follows:
RCPU: 68 points
QCPU/LCPU/FX5CPU: 80 points
[in]writeDatas Specify the device value to be written.
Function Use when writing by specifying multiple devices individually.
Writes device values to the multiple device specified to 'deviceNames' (argument).
Specify the device value, which is to be written, to each element of 'writeDatas'.
Device specification Example: Write the device values of M0, D10, and LZ20
method deviceNames="M0", "D10", "LZ20"
Data storage example (one element of an array: 32-bit)
writeDatas[0]: M0 (ON/OFF is judged in bit 0.)
writeDatas[1]: D10
writeDatas[2]: LZ20
Reference open(), close(), readDeviceRandom()
Considerations Devices and the devices used the extension specification cannot be specified together. (Example: 'U3E1\G0' and 'D0' are
not acceptable to specify together.) When specifying the device used the extension specification, specify the devices only to
'deviceNames' (argument).
Specify the number of elements equal or greater than that of write points to 'writeDatas' (argument).
When bit devices and word devices (including double word devices) are specified together, they are processed as respective
packets. Therefore, the timing for writing the bit devices and word devices are different.
When bit devices and word devices (including double word devices) are specified together, the bit devices are written after
writing the word devices. Therefore, the writing of bit devices may fail even if the word devices successfully are written. If the
error occurs in this method, write them again after checking the error content.
5 METHODS
readArrayLabel (To read the data by specifying the array type label)

Item Description
Method definition int readArrayLabel(
MELMxLabel label
)
Argument [in/out]label Specify the MELMxLabel object in which the array type label to be read has been set.
For the MELMxLabel object, set the label name, character string length stored in the label (when
the data type is the string type only), and number of pieces of data by using the method for the
label data setting in advance.
After this method succeeded, the read label data is stored.
Function Use when reading label data of array type.
Reads the array type label data specified to 'label' (argument) for the number of array elements. 5
The read label data is stored to 'label' (argument).
Reference open(), close(), writeArrayLabel()
Considerations The array type label of the following data types cannot be specified;
Timer, retentive timer, counter, long timer, long retentive timer, long counter
Up to three dimensions of arrays can be specified . (Note that two-dimensional arrays and three-dimensional arrays, of
which data types are bit, cannot be specified with this method.)
An error occurs if the data size to be read exceeds 1914 bytes. Specify the size 1914 bytes or less.
Specify the character string length for the label name up to 1906 bytes.
4-byte characters of Unicode (Example: (U+20089)) are treated as 2 bytes and 2 characters.
The simple type label data can be read as the array type label of which the number of element is one. (Example: Label[0])
writeArrayLabel (To write the data by specifying the array type label)

Item Description
Method definition int writeArrayLabel(
MELMxLabel label
)
Argument [in]label Specify the MELMxLabel object in which the array type label to be written has been set.
For the MELMxLabel object, set the label name, character string length stored in the label (when
the data type is the string type only), label data, and number of pieces of data by using the
method for the label data setting in advance.
Function Use when writing label data of array type.
Writes the array type label data specified to 'label' (argument) for the number of array elements.
Specify the label data to be written to 'label' (argument).
Reference open(), close(), readArrayLabel()
Considerations The array type label of the following data types cannot be specified;Timer, retentive timer, counter, long timer, long retentive
timer, long counter
Up to three dimensions of arrays can be specified . (Note that two-dimensional arrays and three-dimensional arrays, of
which data types are bit, cannot be specified with this method.)
The total number of the character string length and data to be written for specifying label names is up to 1906 bytes.
The simple type label data can be written as the array type label of which the number of element is one. (Example: Label[0])
5 METHODS
readLabelRandom (To read the data by specifying multiple labels)

Item Description
Method definition int readLabelRandom(
MELMxLabel[] labels
)
Argument [in/out]labels Specify multiple MELMxLabel objects, in which the labels to be read have been set, in an array.
For each MELMxLabel object, set the label name, character string length stored in the label
(when the data type is the string type only), and number of pieces of data by using the method for
the label data setting in advance.
After this method succeeded, the read label data is stored.
Function Use when reading the following label data.
Simple type label
Simple type label of structure elements
Reads the data from the label specified to 'labels' (argument).
The read label data is stored in each element of 'labels' (argument).
Reference open(), close(), writeLabelRandom()
Considerations The size of the label data to be read needs to satisfy the following condition formula.
Total number of (the size of read data + 2) 1912
The total length of label names needs to satisfy the following condition formula.
Total number of (the length of label name 2 + 2) 1910
writeLabelRandom (To write the data by specifying multiple labels)


Item Description
Method definition int writeLabelRandom(
MELMxLabel[] labels
)
Argument [in]labels Specify multiple MELMxLabel objects, in which the labels to be written have been set, in an array.
For each MELMxLabel object, set the label name, character string length stored in the label
(when the data type is the string type only), label data, and number of pieces of data by using the
method for the label data setting in advance.
Function Use when writing the following label data.
Simple type label
Simple type label of structure elements
Writes the data to the label specified to 'labels' (argument).
Specify the label data to be written to each element of 'labels' (argument).
Reference open(), close(), readLabelRandom()
Considerations The total length of label names needs to specify the following condition formula.
Total number of (the length of label name 2 + the size of write data + 4) 1910
5 METHODS
MELMxOpenSettings class
It is the class to manage the following parameters when communicating.
The parameters can access directly as "Public field".
Details of fields
Field name Data type Description Default value Reference
unitType Integer Specify the connected module of communication target. UNIT_RETHER (1002H) Page 38 unitType
ioNumber long Specify the start I/O No. in the CPU module of access target. 3FFH
Single CPU system
Host CPU: 3FFH
Multiple CPU system*1CPU No.1: 3E0H, CPU No.2: 3E1H,
CPU No.3: 3E2H, CPU No.4: 3E3H
cpuType Integer Specify the CPU module of access target. CPU_R04CPU (1001H) Page 38 cpuType
protocolType Integer Specify the communication protocol. PROTOCOL_TCPIP Page 40 protocolType
(05H)
hostAddress String Specify the host name (IP address) of connection target. 1.1.1.1
5
Only IPv4 is supported.
portNumber Integer Specify the port number of devices such as a tablet. 0H
destinationPortNumber Integer Specify the port number of connection target module. 5002
When using the SLMP/MC protocol, specify the same port
number set to the connection target module.
When using the MELSOFT connection, specify the port
number as described in the following section.
Page 40 destinationPortNumber
timeOut Integer Specify the timeout time (ms) for communication between the 10000 (2710H)
CPU module and a device such as a tablet.
cpuTimeOut Integer Set the CPU monitoring timer. (Units: 250 ms) 40
Example: 2500 ms for 10
The available range is 0 to FFFFH. Set '0' if the value that is
outside of range has been set.
When specifying '0', it will be an infinity wait.
Fix '0' for FX5CPU.
*1 In Q series, the Ethernet port of a CPU cannot be used to specify other stations. Use an Ethernet module when specifying other CPUs.
5 METHODS
unitType
Connected module Definition name Value (Hexadecimal)
RCPU UNIT_RETHER 1002H
FX5CPU UNIT_FETHER 2001H
QCPU UNIT_QNETHER 2CH
LCPU (Built-in Ethernet port) UNIT_LNETHER 52H
MELSEC iQ-R series-compatible EN71 UNIT_RJ71EN71 1001H
Q series-compatible E71 UNIT_QJ71E71 1AH
L series-compatible E71 UNIT_LJ71E71 5CH
Q series C Controller module UNIT_QCCPUETHER 0800H
cpuType
MELSEC iQ-R series CPU
Applicable CPU module Definition name Value (Hexadecimal)
R04CPU CPU_R04CPU 1001H
R04ENCPU CPU_R04ENCPU 1008H
R08ENCPU CPU_R08ENCPU 1009H
R16ENCPU CPU_R16ENCPU 100AH
R32ENCPU CPU_R32ENCPU 100BH
R120ENCPU CPU_R120ENCPU 100CH
R12CCPU_V CPU_R12CCPU_V 1021H
R16MTCPU CPU_R16MTCPU 1011H
R32MTCPU CPU_R32MTCPU 1012H
FX5CPU
FX5UCPU CPU_FX5UCPU 210H
FX5UCCPU CPU_FX5UCCPU 210H
5 METHODS
Q series CPU
Q00JCPU CPU_Q00JCPU 30H
Q00UJCPU CPU_Q00UJCPU 80H
Q00CPU CPU_Q00CPU 31H
Q00UCPU CPU_Q00UCPU 81H
Q01CPU CPU_Q01CPU 32H
Q02(H)CPU CPU_Q02CPU 22H
Q06HCPU CPU_Q06CPU 23H
Q02PHCPU CPU_Q02PHCPU 45H
Q25PHCPU CPU_Q25PHCPU 42H 5
Q12PRHCPU CPU_Q12PRHCPU 43H
Q25PRHCPU CPU_Q25PRHCPU 44H
Q03UDCPU CPU_Q03UDCPU 70H
Q04UDHCPU CPU_Q04UDHCPU 71H
Q03UDECPU CPU_Q03UDECPU 90H
Q04UDEHCPU CPU_Q04UDEHCPU 91H
Q100UDEHCPU CPU_Q100UDEHCPU 9AH
Q03UDVCPU CPU_Q03UDVCPU D1H
Q12DCCPU-V CPU_Q12DC_V 58H
Q24DHCCPU-V CPU_Q24DHC_V 59H
Q24DHCCPU-LS CPU_Q24DHC_LS 5BH
Q172DCPU CPU_Q172DCPU 625H
Q173DCPU CPU_Q173DCPU 626H
Q172DSCPU CPU_Q172DSCPU 62AH
Q173DSCPU CPU_Q173DSCPU 62BH
5 METHODS
LCPU
L02SCPU CPU_L02SCPU A3H
L02SCPU-P CPU_L02SCPU A3H
L02CPU CPU_L02CPU A1H
L02CPU-P CPU_L02CPU A1H
L26CPU-BT CPU_L26CPUBT A2H
L26CPU-PBT CPU_L26CPUBT A2H
protocolType
Applicable protocol Definition name Value (Hexadecimal)
TCP/IP PROTOCOL_TCPIP 05H
destinationPortNumber
Connected module TCP/IP
RCPU 5007
MELSEC iQ-R series-compatible EN71 5002
Q series-compatible E71 5002
L series-compatible E71 5002
5 METHODS
MELMxLabel class
It is the class to manage the label data for label names.
Use this class when using the methods for reading/writing of labels (readArrayLabel/writeArrayLabel/readLabelRandom/
writeLabelRandom of MELMxCommunication class).
Details of methods
MELMxLabel (Constructor)
Item Description
Class name MELMxLabel
Method definition void MELMxLabel()
Argument None
Return value None
Function It is the constructor of this class.
The default value of label name is null character.
Set "MEL_MX_LABEL_DATATYPE_BIT" for the default value of data type, and set "false" for the default value of value.
5
The default value of points is 1 point.
The default value of the string data length for a label, of which data type is 'string [32] or 'string' [Unicode] (32), is 32 characters.
Reference None
Considerations None
getValues (To obtain the label data)

Item Description
Method definition Object[] getValues()
Argument None
Return value Label data
Function Obtains the label data that is managed in the instances of this class.
Use this class to obtain the label data which was read with 'readLabelRandom'. (Page 36 readLabelRandom (To read
the data by specifying multiple labels))
The obtained data is the 'Object' instance.
Before using the data, convert them to the variables that match with the data type obtained by the method for obtaining data
types (getDataType).(Page 42 getDataType (To obtain the data type of label))
For details on the type of variable, refer to the following section.
Reference None
Considerations If 4-byte characters of Unicode (Example: (U+20089)) are included when the label data is the Unicode character string,
they are treated as 2 bytes and 2 characters.
getName (To obtain the label name)

Item Description
Method definition String getName()
Argument None
Return value Label name
Function Obtains the label names specified with the methods of label data settings.
Reference MELMxLabel()
Considerations When 4-byte characters of Unicode (Example: (U+20089)) are included in the label name, they are treated as 2 bytes and
2 characters.
5 METHODS
getDataType (To obtain the data type of label)
Item Description
Method definition int getDataType()
Argument None
Return value Data type of label
Function Obtains the data type of the label.
For details on the types of variables, refer to the following section.
Reference None
Considerations None
setBitLabel (To set the label data of Bit type)

Item Description
Method definition void setBitLabel(
String name,
Boolean[] values,
int size
)
Argument [in]name Specify a label name.
[in]values Specify the label data.
[in]size Specify the number of pieces of label data.
For the simple type label, specify '1'.
For the array type label, specify the number of elements.
Return value None
Function Set the label name, type, and label data to be managed in the instance of this class.
Use this method when using the label of which the data type is Bit. (Page 24 Data type of label)
Reference getValues()
Considerations None
setWordLabel (To set the label data of Word (Signed))

Item Description
Method definition void setWordLabel(
String name,
Integer[] values,
int size
)
Return value None
Use this method when using the label of which the data type is Word (Signed). (Page 24 Data type of label)
Considerations None
5 METHODS
setUnsignedWordLabel (To set the label data of Word (Unsigned))
Item Description
Method definition void setUnsignedWordLabel(
String name,
Integer[] values,
int size
)
Return value None
Use this method when using the label of which the data type is Word (Unsigned). (Page 24 Data type of label)
Reference getValues() 5
Considerations None
setDoubleWordLabel (To set the label data of Double Word (Signed))

Item Description
Method definition void setDoubleWordLabel(
String name,
Long[] values,
int size
)
Return value None
Use this method when using the label of which the data type is Double Word (Signed). (Page 24 Data type of label)
Considerations None
setUnsignedDoubleWordLabel (To set the label data of Double Word (Unsigned))

Item Description
Method definition void setUnsignedDoubleWordLabel(
String name,
Long values,
int size
)
Return value None
Use this method when using the label of which the data type is Double Word (Unsigned). (Page 24 Data type of label)
Considerations None
5 METHODS
setFloatSingleLabel (To set the label data of FLOAT (Single Precision))
Item Description
Method definition void setFloatSingleLabel(
String name,
Float[] values,
int size
)
Return value None
Use this method when using the label of which the data type is FLOAT (Single Precision). (Page 24 Data type of label)
Considerations None
setFloatDoubleLabel (To set the label data of FLOAT (Double Precision))

Item Description
Method definition void setFloatDoubleLabel(
String name,
Double[] values,
int size
)
Return value None
Use this method when using the label of which the data type is FLOAT (Double Precision). (Page 24 Data type of label)
Considerations None
setAsciiStringLabel (To set the label data of ASCII character string)

Item Description
Method definition void setAsciiStringLabel(
String name,
Long length,
String[] values,
int size
)
[in]length Specify the character string length to be stored in the label.
Return value None
Use this method when using the label of which the data type is String [32]. (Page 24 Data type of label)
Considerations None
5 METHODS
setUnicodeStringLabel (To set the label data of Unicode character string)
Item Description
Method definition void setUnicodeStringLabel(
String name,
Long length,
String[] values,
int size
)
[in]length Specify the character string length to be stored in the label.
Return value None
Use this method when using the label of which the data type is String [Unicode] (32). (Page 24 Data type of label)
5
Considerations When 4-byte characters of Unicode (Example: (U+20089)) are included in the label name and label data, they are treated
as 2 bytes and 2 characters.
setTimeLabel (To set the label data of Time)

Item Description
Method definition void setTimeLabel(
String name,
Long[] values,
int size
)
Return value None
Use this method when using the label of which the data type is Time. (Page 24 Data type of label)
Considerations None
MELMxErrorCode class
It is the class which retains error codes in this library.
The error codes are retained in 'public static const' field.
For details on error codes, refer to the following section.
Page 59 Error codes returned by MX Component library
5.3 Considerations for Using Methods

When the remote password has been set, unlock the password (open method) before communicating.
The remote password is locked when the communication is completed (close method).
5 METHODS
5.3 Considerations for Using Methods 45
5.4 Sample Program
This section explains the sample program in the CD-ROM provided with this product.
Sample programs are different depending on the CPU series. Use the sample program according to the CPU module to be
accessed.
Folder name Description
SampleProject iQ-F PLC Sample for the MELSEC iQ-F series FX5CPU
iQ-R PLC&Motion Sample for MELSEC iQ-R series programmable controller CPU and motion CPU.
C_Controller Sample for the MELSEC iQ-R series C Controller module
Q PLC&Motion Sample for Q series/L series programmable controller CPU and motion CPU.
C_Controller Sample for the Q series C Controller module
Created application
The following shows an example of the screen when the application created by using sample program is operated with a
tablet.
The methods are executed by tapping the buttons on the left side of the screen. After execution, the result is displayed on the
right side of the screen.
When the processing succeeds, "SUCCESS" and the value of execution result are displayed. If the processing fails, the error
code appears.
Reading and writing

devices/labels
The following table shows the processing corresponding to the each button on the screen above.
Button name Processing
Open Page 49 execOpen
Close Page 50 execClose
ReadDeviceBlock Page 51 execReadDeviceBlock
WriteDeviceBlock Page 52 execWriteDeviceBlock
ReadDeviceRandom Page 53 execReadDeviceRandom
WriteDeviceRandom Page 54 execWriteDeviceRandom
ReadArrayLabel Page 55 execReadArrayLabel
WriteArrayLabel Page 56 execWriteArrayLabel
ReadLabelRandom Page 57 execReadLabelRandom
WriteLabelRandom Page 58 execWriteLabelRandom
5 METHODS
46 5.4 Sample Program
Operation for application
The following shows the basic operation for communication.
Operating procedure
1. Start the application.
2. Tap the [Open] button.
3. Tap the button for reading and writing of devices/labels.
4. Tap the [Close] button.

If tap the [ClearRecord] button, the execution result is cleared.
Operation environment
The sample program is created to operate in the following environment.
Folder name Item Description System configuration 5
iQ-F PLC CPU FX5UCPU (Host CPU) Page 48 iQ-F PLC
IP address 192.168.2.100
Port (Ethernet port direct connection) 5014
iQ-R PLC&Motion CPU R16CPU (Host CPU), R16MTCPU (CPU No.2) Page 48 iQ-R
PLC&Motion
IP address 192.168.2.100
C_Controller CPU R16CPU (Host CPU), R12CCPU-V (CPU No.2) Page 48 iQ-R
C_Controller
IP address 192.168.2.100
Q PLC&Motion CPU Q20UDEHCPU (Host CPU), Q172DSCPU Page 48 Q
(CPU No.2) PLC&Motion
IP address 192.168.2.100
C_Controller CPU Q12DCCPU-V (Host CPU) Page 48 Q
C_Controller
IP address 192.168.2.100
5 METHODS
5.4 Sample Program 47
System configuration
The sample programs are created to operate in the following system configuration.
iQ-F PLC
Wireless LAN router FX5CPU
Tablet
(AndroidTM OS)
Hub
iQ-R PLC&Motion
Wireless LAN router R16CPU, R16MTCPU
Tablet
(AndroidTM OS)
Hub
iQ-R C_Controller
Wireless LAN router R16CPU, R12CCPU-V
Tablet
(AndroidTM OS)
Hub
Q PLC&Motion
Wireless LAN router Q20UDEHCPU, Q172DSCPU
Tablet
(AndroidTM OS)
Hub
Q C_Controller
Wireless LAN router Q12DCCPU-V
Tablet
(AndroidTM OS)
Hub
For the communication method (open method), refer to the following section.
Page 17 Communication method (open method)
5 METHODS
Sample method
The methods explained in this section are written in the following file.
Storage folder: SampleProject (folder for each series) (folder for each module) src jp co melco
mxcomponentsample
File name: MXComponentManager.java
Processing corresponding to each button

The following shows the processing corresponding to the buttons.
execOpen
The following processing are executed by tapping the [Open] button.
The open method of MELMxCommunication class is executed in the background.
When counting the elapsed time and if it is over the specified timeout period, a timeout error is returned.
5 METHODS
execClose
The following processing are executed by tapping the [Close] button.
The close method of MELMxCommunication class is executed in the background.
5 METHODS
execReadDeviceBlock
The following processing are executed by tapping the [ReadDeviceBlock] button.
Read the values from the device 'D100' of the opened connection target, and display the values.
5 METHODS
execWriteDeviceBlock
The following processing are executed by tapping the [WriteDeviceBlock] button.
Write the random values from 0 to 99 to the device 'D100' of the opened connection target.
5 METHODS
execReadDeviceRandom
The following processing are executed by tapping the [ReadDeviceRandom] button.
Read the values from the device 'D100', 'M0', and 'LZ0' of the opened connection target, and display the values.
For bit devices, the execution result is displayed in ON/OFF.
5 METHODS
execWriteDeviceRandom
The following processing are executed by tapping the [WriteDeviceRandom] button.
Write the random values to the device 'D100', 'M0', and 'LZ0' of the opened connection target.
For bit devices, the execution result is displayed in ON/OFF.
5 METHODS
execReadArrayLabel
The following processing are executed by tapping the [ReadArrayLabel] button.
Read the values from the wLabel[0]*1 of the opened connection target, and display the values.
*1 'wLabel' is the array type label of Word type.
5 METHODS
execWriteArrayLabel
The following processing are executed by tapping the [WriteArrayLabel] button.
Write the random values from 0 to 99 to the wLabel[0]*1 of the opened connection target.
*1 'wLabel' is the array type label of Word type.
5 METHODS
execReadLabelRandom
The following processing are executed by tapping the [ReadLabelRandom] button.
Read the values from the wLabel[0], bLabel[0], and sLabel[0]*1 of the opened connection target, and display the values.
*1 'wLabel' is the array type label of word type. 'bLabel' is the array type label of bit type. 'sLabel' is the array type label of string type.
5 METHODS
execWriteLabelRandom
The following processing are executed by tapping the [WriteLabelRandom] button.
Write the random values to the wLabel[0], bLabel[0], and sLabel[0]*1 of the opened connection target.
*1 'wLabel' is the array type label of word type. 'bLabel' is the array type label of bit type. 'sLabel' is the array type label of string type.
5 METHODS
6 TROUBLESHOOTING
This chapter explains the contents of error codes and corrective actions.
6.1 Error Processing and Corrective Actions

An error code is returned to an abnormal processing.
For error codes and corrective actions, refer to the following section.
Page 59 Error Code List
6.2 Error Code List

This section shows the error codes and corrective actions.
Error codes returned by CPU module/module

The lower 4 digits of error codes indicate the error code for CPU modules/modules.
For details, refer to the manual for each module. 6
0x01090000 to 0x0109FFFF: FX5CPU
0x010A0000 to 0x010AFFFF: MELSEC iQ-R series CPU, Q series CPU, and LCPU
0x010C0000 to 0x010CFFFF: MELSEC iQ-R series-compatible EN71, Q series-compatible E71, L series-compatible E71
Error codes returned by MX Component library

0xF0000000 to 0xF1FFFFFF, 0xFE000001 to 0xFE00FFFF: MX Component for Android library itself
0x01800000 to 0x0180FFFF, 0x01900000 to 0x0190FFFF: EasySocket Communication
Error code Error description Corrective action
0x00000000 Normal completion
0x01800001 No command error Check if the CPU module or module supports the function.
The specified CPU module or module does
not support the corresponding function.
0x01800003 Memory securing error End other running applications, and then restart the application which is created by
using MX Component for Android.
Restart the device such as a tablet.
0x01800004 Load error Check if the specified unitType, cpuType, and protocolType match the system
configuration used.
End other running applications, and then restart the application which is created by
If the error occurs again even after taking the corrective actions mentioned above,
please consult your local Mitsubishi representative.
0x01801002 Multi-line open error End other running applications, and then restart the application which is created by
0x01801003 Open not yet executed using MX Component for Android.
0x01801006 Specified module error Check if the specified unitType matches the system configuration used.
0x01801007 Specified CPU error Check if the specified cpuType matches the system configuration used.
0x01801009 Setting file open failed End other running applications, and then restart the application which is created by
Reinstall MX Component library.
6 TROUBLESHOOTING
6.1 Error Processing and Corrective Actions 59
0x0180100B Protocol type error Check if the specified protocolType matches the system configuration used.
The specified protocol is incorrect. End other running applications, and then restart the application which is created by
0x01802001 Device error Review the device name.
The device character string specified in the
method is an incorrect device character
string.
0x01802002 Device number error Review the device number.
The device character string number specified
in the method is an incorrect device number.
0x01802005 Size error Check the number of points specified in the method.
The number of points specified in the method Review the system such as the CPU module settings, Ethernet module settings, and
is incorrect. cable condition.
Check the communication status between the device such as a tablet and the wireless
LAN router.
0x01802007 Receive data error Review the system such as the CPU module settings, Ethernet module settings, and
The received data is abnormal. cable condition.
LAN router.
0x01802079 'null' specification error Specify the correct value to the argument.
'null' is specified to the argument.
0x01808001 Multiple open error Execute any methods except for the open method.
The open method was executed when it has End other running applications, and then restart the application which is created by
been already opened. using MX Component for Android.
0x01808007 Socket object generation error Check if the application which uses the same port number is running.
The generation of the Socket object failed. Change the value specified to PortNumber and retry.
0x01808008 Port connection error Review the values specified to PortNumber and hostAddress.
Establishment of connection failed. The Review the system such as the CPU module settings, Ethernet module settings, and
connection target does not respond. cable condition.
0x01808101 Multiple close error End other running applications, and then restart the application which is created by
0x01808201 Send error Review the system such as the CPU module settings, Ethernet module settings, and
Data send failed. cable condition.
LAN router.
Retry the method.
0x01808301 Receive error Review the system such as the CPU module settings, Ethernet module settings, and
Data receive failed. cable condition.
Review the value specified to timeOut.
LAN router.
Retry the method.
6 TROUBLESHOOTING
60 6.2 Error Code List
0x01808404 Open not yet executed Execute the open method.
0x0180840B Time-out error Review the system such as the CPU module settings, Ethernet module settings, and
Data could not be received before the cable condition.
timeout period had elapsed. Review the value specified to timeOut.
LAN router.
Retry the method.
Execute the close processing at once, then execute the open method again.
Disable the battery saving functions of Wi-Fi settings (depending on the device to be
used, the display is different such as "Wi-Fi Advanced" "Wi-Fi optimization" or "Wi-Fi
Advanced" "Wi-Fi timer").
Disable the auto connect/disconnect functions for Wi-Fi network (depending on the
device to be used, the display is different such as "Wi-Fi Advanced" "Wi-Fi
optimization" or "Wi-Fi Advanced" "Wi-Fi timer").
End the auto disconnect applications for Wi-Fi communication.
0x01902001 Extended device mixed error When using an extended device, specify only the extended device.
Both extended devices and devices are
specified.
6
0x01902801 Label data incorrect error Check the number of label data of the arguments.
The specified label data to the arguments are
incorrect.
0x01902802 Label name length error Specify the label name or the total number of label names within the applicable length.
Label name length or total number of label
name length exceeds the applicable length.
0x01902803 Label data size error Specify the data size of the label within the applicable range.
The data size of the label exceeds the
applicable size.
0x01902804 Label name length and label data size error Specify the total size of label name length and label data within the applicable size.
The total size of label name length and label
data exceeds the applicable size.
0x01902805 Label data incorrect error Specify the data type supported the label.
The type of the specified label is unknown.
0x01903801 Data type mismatch error Specify the correct label data type ((that matches the one in the CPU module) and
The data type of specified label mismatches execute the method again.
the one set to the CPU module.
0x01904001 Remote password length error MELSEC iQ-R series CPU, FX5CPU:
The remote password length is not 4 bytes or Set the remote password length between 6 to 32 bytes.
exceeds 32 bytes. Q series CPU, LCPU:
Set the remote password length to 4 bytes.
0x01904002 Port number error Specify the correct portNumber and destinationPortNumber.
The port number is wrong.
0x01905001 The send error of the remote password lock The close processing has been completed. Execute the open method again as
has occurred in the close processing at the necessary.
setting of the remote password.
0x0190FFFF Exception occurrence error in the operating End other running applications, and then restart the application which is created by
environment using MX Component for Android.
An exception error has occurred in the Restart the device such as a tablet.
running device. Reinstall MX Component library.
0xF0000001 No-license error MX Component for Android is used without the license. Install the license of MX
Component for Android duly.
0xF0000003 Already open error Execute the close processing at once, then execute the open method again.
The open method was executed when it has
been already opened.
0xF0000004 Not yet open error After executing the open method, execute the corresponding method.
The open method has not been executed.
6 TROUBLESHOOTING
6.2 Error Code List 61
0xF1000002 Start I/O No. error Check the value of start I/O number to be specified to the method.
The value of specified start I/O number is Review the system such as the CPU module settings, multiple CPU system settings,
incorrect. No matching start I/O number exist. and cable condition.
0xF1000005 Size error Check the size specified in the method.
The size specified to the read/write method is
abnormal. The 'first read/write number + size'
exceeds the device or buffer area.
0xFE003001 Label name length error Specify the label name or the total number of label names within the applicable length.
Label name length or total number of label
name length exceeds the applicable length.
0xFE003002 Label data size error Specify the data size of the label data within the applicable range.
The data size of the label exceeds the
applicable size.
0xFE003003 Label name length and label data size error Specify the total size of label name length and label data within the applicable size.
The total size of label name length and label
data exceeds the applicable size.
0xFE003004 Label data type error Change the data type of the label to the supported data type.
The data type of the label is unsupported. If the error occurs again even after taking the corrective actions mentioned above,
0xFE004001 'null' is specified. Specify the correct value to the argument.
'null' is specified to the argument.
6 TROUBLESHOOTING
62 6.2 Error Code List
MEMO
6 TROUBLESHOOTING
6.2 Error Code List 63
APPENDIX
Appendix 1 Added and Changed Functions
The following table shows the added or changed functions, and the applicable software version of MX Component for
Android.
Added/changed contents Applicable software version
Supported by the following modules. 1.01B or later
C Controller module (R12CCPU-V, Q12DCCPU-V, Q24DHCCPU-V, and Q24DHCCPU-LS)
Motion CPU (R16MTCPU, R32MTCPU, Q172DCPU, Q173DCPU, Q172DSCPU, and Q173DSCPU)
RnENCPU (R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, and R120ENCPU)
The multiple CPU system is supported.
APPENDICES APPENDIX
64 Appendix 1 Added and Changed Functions
MEMO
A
APPENDICES APPENDIX
Appendix 1 Added and Changed Functions 65
METHOD INDEX
C
close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
G
getDataType. . . . . . . . . . . . . . . . . . . . . . . . . . . 42
getName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
getValues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
M
MELMxComminication . . . . . . . . . . . . . . . . . . . . 29
MELMxLabel . . . . . . . . . . . . . . . . . . . . . . . . . . 41
O
open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
R
readArrayLabel . . . . ..................... 35
readDeviceBlock . . . ..................... 31
readDeviceRandom ..................... 33
readLabelRandom . ..................... 36
S
setAsciiStringLabel . . . . . . . . . ............. 44
setBitLabel . . . . . . . . . . . . . . . ............. 42
setDoubleWordLabel . . . . . . . . ............. 43
setFloatDoubleLabel . . . . . . . . ............. 44
setFloatSingleLabel . . . . . . . . . ............. 44
setTimeLabel . . . . . . . . . . . . . ............. 45
setUnicodeStringLabel. . . . . . . ............. 45
setUnsignedDoubleWordLabel . ............. 43
setUnsignedWordLabel . . . . . . ............. 43
setWordLabel . . . . . . . . . . . . . ............. 42
W
writeArrayLabel . . . . ..................... 35
writeDeviceBlock . . ..................... 32
writeDeviceRandom ..................... 34
writeLabelRandom . ..................... 36
66
MEMO
67
REVISIONS
*The manual number is given on the bottom left of the back cover.
Revision date *Manual number Description
February 2015 SH(NA)-081498ENG-A First edition
October 2015 SH(NA)-081498ENG-B Added or modified parts
TERMS, Section 2.1, Section 2.2, Section 2.4, Chapter 3, Section 4.1, Section 5.2, Section 5.4,
Section 6.2, Appendix 1
Japanese manual number: SH-081496-B

This manual confers no industrial property rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held
responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.
2015 MITSUBISHI ELECTRIC CORPORATION
68
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 of damages caused by any cause
found not to be the responsibility of Mitsubishi, loss in opportunity, lost profits incurred to the user by Failures of
Mitsubishi products, special damages and secondary damages whether foreseeable or not, compensation for accidents,
and compensation for damages to products other than Mitsubishi products, 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.
69
TRADEMARKS
Microsoft, Windows, Windows Vista, Windows NT, Windows XP, Windows Server, Visio, Excel, PowerPoint, Visual Basic,
Visual C++, and Access are either registered trademarks or trademarks of Microsoft Corporation in the United States, Japan,
and other countries.
Intel, Pentium, and Celeron are either registered trademarks or trademarks of Intel Corporation in the United States and other
countries.
Ethernet is a trademark of Xerox Corp.
Android is either a registered trademark or a trademark of Google Inc.
ARM is either a registered trademark or a trademark of ARM Ltd. in the United States and other countries.
Eclipse is either a registered trademark or a trademark of Eclipse Foundation, Inc. in the United States and other countries.
Java is a registered trademark of Oracle Corporation and its affiliated companies.
All other company names and product names used in this manual are either trademarks or registered trademarks of their
respective companies.
70
SH(NA)-081498ENG-B(1510)
MODEL:MXC-AND1-R-E
HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN
NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN
When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.
Specifications subject to change without notice.

MX Component For Android Ver1 - Reference Manual SH (NA) - 081498-B (10.15)

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

MX Component For Android Ver1 - Reference Manual SH (NA) - 081498-B (10.15)

Transféré par

Droits d'auteur :

Formats disponibles

MX Component for Android Version 1

Indicates that incorrect handling may cause hazardous conditions, resulting in

Indicates that incorrect handling may cause hazardous conditions, resulting in

[Startup and Maintenance Precautions]

CHAPTER 2 SYSTEM CONFIGURATION 9

CHAPTER 4 ACCESSIBLE DEVICES 20

1.1 What Is MX Component for Android?

Wireless LAN router Programmable Controller

1.2 Main Functions

Creation of tablet applications

Programming by using labels (RCPU only)

Creation of safe applications for security

2.1 System Configuration 2

Development personal computer

Install the created application.

Wireless LAN router Programmable controller

Usable CPU modules

*1 Use the firmware version '05' or later.

*1 Use the firmware version '02' or later.

Considerations for programming and each setting

Erroneous data reception at timeout

Functions and applications that disconnect Wi-Fi communication automatically

Wireless LAN switching

Considerations for Android specification

Considerations for using this product with other products

Importing the library (so file)

Importing the library

Setting the permission for the socket communication

Checking the version of MX Component for Android

GX Works3 Module Parameter

GX Works3 Module Parameter (Ethernet)

GX Works2 Network Parameter Ethernet/CC IE Field

Setting/monitoring tools for the C Controller module CCPU Parameter (SW4PVC-CCPU)

4.1 Accessible Device List

Programmable controller CPU

*1 Local devices can not be accessed.

*1 Local devices can not be accessed.

*1 Local devices can not be accessed.

Consideration for bit devices

Upper byte Lower byte

M7 M6 M5 M4 M3 M2 M1 M0 M15 M14 M13 M12 M11 M10 M9 M8

The bit devices are stored in order from upper bytes.

Considerations for using labels

Data type of label

Simple data type

The alias name cannot be specified.

Procedure for using methods

Set the parameters.

Target for reading/writing: Labels

Set the parameters.

Call readDeviceBlock method, Call readArrayLabel method,

Success Not Time-out

Execute close method. Refer to the error code list.

open (To open the communication line)

Time until the connections to each connected module are disconnected

writeLabelRandom (To write the data by specifying multiple labels)

getValues (To obtain the label data)

getName (To obtain the label name)

setBitLabel (To set the label data of Bit type)

setWordLabel (To set the label data of Word (Signed))

setDoubleWordLabel (To set the label data of Double Word (Signed))

setUnsignedDoubleWordLabel (To set the label data of Double Word (Unsigned))

setFloatDoubleLabel (To set the label data of FLOAT (Double Precision))