Q06UDEHCPU
Q06UDEHCPU
Q06UDEHCPU
-Q03UDVCPU
-Q03UDECPU
-Q04UDVCPU
-Q04UDEHCPU
-Q06UDVCPU
-Q06UDEHCPU
-Q10UDEHCPU
-Q13UDVCPU
-Q13UDEHCPU
-Q20UDEHCPU
-Q26UDVCPU
-Q26UDEHCPU
-Q50UDEHCPU
-Q100UDEHCPU
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention
to safety to handle the product correctly.
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".
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
● Configure safety circuits external to the programmable controller to ensure that the entire system
operates safely even when a fault occurs in the external power supply or the programmable controller.
Failure to do so may result in an accident due to an incorrect output or malfunction.
(1) Configure external safety circuits, such as an emergency stop circuit, protection circuit, and
protective interlock circuit for forward/reverse operation or upper/lower limit positioning.
(2) The programmable controller stops its operation upon detection of the following status, and the
output status of the system will be as shown below.
All outputs may turn on when an error occurs in the part, such as I/O control part, where the CPU
module cannot detect any error. To ensure safety operation in such a case, provide a safety
mechanism or a fail-safe circuit external to the programmable controller. For a fail-safe circuit
example, refer to the QCPU User's Manual (Hardware Design, Maintenance and Inspection).
(3) Outputs may remain on or off due to a failure of an output module relay or transistor. Configure an
external circuit for monitoring output signals that could cause a serious accident.
1
[Design Precautions]
WARNING
● In an output module, when a load current exceeding the rated current or an overcurrent caused by a
load short-circuit flows for a long time, it may cause smoke and fire. To prevent this, configure an
external safety circuit, such as a fuse.
● Configure a circuit so that the programmable controller is turned on first and then the external power
supply.
If the external power supply is turned on first, an accident may occur due to an incorrect output or
malfunction.
● For the operating status of each station after a communication failure, refer to relevant manuals for the
network.
Incorrect output or malfunction due to a communication failure may result in an accident.
● When changing data of the running programmable controller from a peripheral connected to the CPU
module or from a personal computer connected to an intelligent function module, configure an
interlock circuit in the sequence program to ensure that the entire system will always operate safely.
For program modification and operating status change, read relevant manuals carefully and ensure
the safety before operation.
Especially, when a remote programmable controller is controlled by an external device, immediate
action cannot be taken if a problem occurs in the programmable controller due to a communication
failure.
To prevent this, configure an interlock circuit in the sequence program, and determine corrective
actions to be taken between the external device and CPU module in case of a communication failure.
[Design Precautions]
CAUTION
● Do not install the control lines or communication cables together with the main circuit lines or power
cables.
Keep a distance of 100mm or more between them.
Failure to do so may result in malfunction due to noise.
● When a device such as a lamp, heater, or solenoid valve is controlled through an output module, a
large current (approximately ten times greater than normal) may flow when the output is turned from
off to on.
Take measures such as replacing the module with one having a sufficient current rating.
● After the CPU module is powered on or is reset, the time taken to enter the RUN status varies
depending on the system configuration, parameter settings, and/or program size. Design circuits so
that the entire system will always operate safely, regardless of the time.
2
[Installation Precautions]
CAUTION
● Use the programmable controller in an environment that meets the general specifications in the
QCPU User's Manual (Hardware Design, Maintenance and Inspection).
Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the
product.
● To mount the module, while pressing the module mounting lever in the lower part of the module, fully
insert the module fixing projection(s) into the hole(s) in the base unit and press the module until it
snaps into place.
Incorrect mounting may cause malfunction, failure, or drop of the module.
When using the programmable controller in an environment of frequent vibrations, fix the module with
a screw.
Tighten the screw within the specified torque range.
Undertightening can cause drop of the screw, short circuit, or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
● When using an extension cable, connect it to the extension cable connector of the base unit securely.
Check the connection for looseness.
Poor contact may cause incorrect input or output.
● When using a memory card, fully insert it into the memory card slot.
Check that it is inserted completely.
Poor contact may cause malfunction.
● When using an SD memory card, fully insert it into the SD memory card slot.
Check that it is inserted completely.
Poor contact may cause malfunction.
● Securely insert an extended SRAM cassette into the cassette connector of a CPU module.
After insertion, close the cassette cover to prevent the cassette from coming off.
Failure to do so may cause malfunction.
● Shut off the external power supply (all phases) used in the system before mounting or removing a
module. Failure to do so may result in damage to the product.
A module can be replaced online (while power is on) on any MELSECNET/H remote I/O station or in
the system where a CPU module supporting the online module change function is used.
Note that there are restrictions on the modules that can be replaced online, and each module has its
predetermined replacement procedure.
For details, refer to the relevant sections in the QCPU User's Manual (Hardware Design, Maintenance
and Inspection) and in the manual for the corresponding module.
● Do not directly touch any conductive parts and electronic components of the module, memory card,
SD memory card, or extended SRAM cassette.
Doing so can cause malfunction or failure of the module.
● When using a Motion CPU module and modules designed for motion control, check that the
combinations of these modules are correct before applying power.
The modules may be damaged if the combination is incorrect.
For details, refer to the user's manual for the Motion CPU module.
3
[Wiring Precautions]
WARNING
● Shut off the external power supply (all phases) used in the system before installation and wiring.
Failure to do so may result in electric shock or damage to the product.
● After wiring, attach the included terminal cover to the module before turning it on for operation.
Failure to do so may result in electric shock.
[Wiring Precautions]
CAUTION
● Individually ground the FG and LG terminals of the programmable controller with a ground resistance
of 100 or less.
Failure to do so may result in electric shock or malfunction.
● Use applicable solderless terminals and tighten them within the specified torque range. If any spade
solderless terminal is used, it may be disconnected when the terminal screw comes loose, resulting in
failure.
● Check the rated voltage and terminal layout before wiring to the module, and connect the cables
correctly.
Connecting a power supply with a different voltage rating or incorrect wiring may cause a fire or
failure.
● Securely connect the connector to the module. Failure to do so may cause malfunction.
● Connectors for external connection must be crimped or pressed with the tool specified by the
manufacturer, or must be correctly soldered.
Incomplete connections could result in short circuit, fire, or malfunction.
● Do not install the control lines or communication cables together with the main circuit lines or power
cables.
Keep a distance of 100mm or more between them.
Failure to do so may result in malfunction due to noise.
● Place the cables in a duct or clamp them.
If not, dangling cable may swing or inadvertently be pulled, resulting in damage to the module or
cables or malfunction due to poor contact.
● Check the interface type and correctly connect the cable.
Incorrect wiring (connecting the cable to an incorrect interface) may cause failure of the module and
external device.
● Tighten the terminal screw within the specified torque range.
Undertightening can cause short circuit, fire, or malfunction.
Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
● Prevent foreign matter such as dust or wire chips from entering the module.
Such foreign matter can cause a fire, failure, or malfunction.
● A protective film is attached to the top of the module to prevent foreign matter, such as wire chips,
from entering the module during wiring.
Do not remove the film during wiring.
Remove it for heat dissipation before system operation.
4
[Wiring Precautions]
CAUTION
● When disconnecting the cable from the module, do not pull the cable by the cable part.
For the cable with connector, hold the connector part of the cable.
For the cable connected to the terminal block, loosen the terminal screw.
Pulling the cable connected to the module may result in malfunction or damage to the module or
cable.
● Mitsubishi programmable controllers must be installed in control panels.
Connect the main power supply to the power supply module in the control panel through a relay
terminal block.
Wiring and replacement of a power supply module must be performed by maintenance personnel who
is familiar with protection against electric shock. For wiring methods, refer to the QCPU User's Manual
(Hardware Design, Maintenance and Inspection).
5
[Startup and Maintenance Precautions]
CAUTION
● Shut off the external power supply (all phases) used in the system before mounting or removing a
module. Failure to do so may cause the module to fail or malfunction.
A module can be replaced online (while power is on) on any MELSECNET/H remote I/O station or in
the system where a CPU module supporting the online module change function is used.
Note that there are restrictions on the modules that can be replaced online, and each module has its
predetermined replacement procedure.
For details, refer to the relevant sections in the QCPU User's Manual (Hardware Design, Maintenance
and Inspection) and in the manual for the corresponding module.
● After the first use of the product, do not mount/remove the module to/from the base unit, and the
terminal block to/from the module, and do not insert/remove the extended SRAM cassette to/from the
CPU module more than 50 times (IEC 61131-2 compliant) respectively.
Exceeding the limit of 50 times may cause malfunction.
● After the first use of the product, do not insert/remove the SD memory card to/from the CPU module
more than 500 times. Exceeding the limit may cause malfunction.
● Do not drop or apply shock to the battery to be installed in the module.
Doing so may damage the battery, causing the battery fluid to leak inside the battery.
If the battery is dropped or any shock is applied to it, dispose of it without using.
● Before handling the module, touch a grounded metal object to discharge the static electricity from the
human body.
Failure to do so may cause the module to fail or malfunction.
[Disposal Precautions]
CAUTION
● When disposing of this product, treat it as industrial waste.
When disposing of batteries, separate them from other wastes according to the local regulations.
(For details of the battery directive in EU member states, refer to the QCPU User's Manual (Hardware
Design, Maintenance and Inspection).)
[Transportation Precautions]
CAUTION
● When transporting lithium batteries, follow the transportation regulations.
(For details of the regulated models, refer to the QCPU User's Manual (Hardware Design,
Maintenance and Inspection).)
6
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.
7
INTRODUCTION
This manual describes the function of the Universal model QCPU using Ethernet communication.
Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the
functions and performance of the Q series programmable controller to handle the product correctly.
When applying the program examples introduced in this manual to the actual system, ensure the applicability and
confirm that it will not cause system control problems.
Remark
This manual does not describe any functions other than the functions of CPU module using Ethernet communication.
For details of functions other than the functions of CPU module using Ethernet communication, refer to the following
manual.
QnUCPU User's Manual (Function Explanation, Program Fundamentals)
8
Memo
9
CONTENTS
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
MANUAL PAGE ORGANIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
CHAPTER 1 OVERVIEW 20
1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3.6 Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.3 Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.4 Error codes, end codes, and abnormal codes in MC protocol communication. . . . . . . . . . . . . 61
10
6.5 Execution Conditions of Predefined Protocol Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
6.6 Operation Image and Data Structure of the Predefined Protocol Function. . . . . . . . . . . . . . . . 73
6.7 Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
11
11.2.2 Clear operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
APPENDICES 187
Appendix 1 Operation Processing Time for Each Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Appendix 2 Port Numbers Used by Built-in Ethernet Port QCPU . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Appendix 3 Added and Changed Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Appendix 4 Specifications Comparison with Ethernet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
INDEX 197
12
MANUALS
To understand the main specifications, functions, and usage of the CPU module, refer to the basic manuals. Read
other manuals as well when using a different type of CPU module and its functions. The manuals related to this
product are listed below. Please place an order as needed.
: Basic manual, : Other CPU module manuals/Use them to utilize functions.
13
(3) Operating manual
14
MANUAL PAGE ORGANIZATION
In this manual, pages are organized and the symbols are used as shown below. The following page illustration is for
explanation purpose only, and is different from the actual pages.
The chapter of
the current page is shown.
shows operating
procedures.
shows mouse
operations.*1
The section of
the current page is shown.
shows reference
manuals.
shows useful
information.
Menu bar
15
Icon
Description
Universal model QCPU
Universal Icons indicate that specifications described on the page contain some precautions.
16
Pages describing instructions are organized as shown below.
The following page illustrations are for explanation purpose only, and are different from the actual pages.
Instruction name
Setting side
Descriptions of
User : Device value is set by the user.
setting data and data type
System: Device value is set by
the CPU module.
Descriptions of
control data (if any)
Detailed descriptions
of the instruction
17
• Instructions can be executed under the following conditions.
On the falling On the falling
Execution condition Any time During on During off
edge edge
Symbol No symbol
18
TERMS
Unless otherwise specified, this manual uses the following generic terms and abbreviations.
* represents the model or version.
(Example): Q33B, Q35B, Q38B, Q312B Q3B
19
CHAPTER 1 OVERVIEW
1.1 Features
The features specific to the Built-in Ethernet port QCPU are described below.
(4) Data communications using the predefined protocol ( Page 64, CHAPTER
6)
The predefined protocol function sends and receives packets predefined by using GX Works2, enabling easy
communications with external devices (such as measuring instruments and bar code readers). Protocol can be
either selected from the prepared predefined protocol library, or created and edited by users.
20
CHAPTER 1 OVERVIEW
1.1 Features
Some functions have been added by the upgrade of the serial numbers of CPU modules or the programming tool. For the list
of functions added by the upgrade, refer to Page 190, Appendix 3.
21
CHAPTER 2 COMMUNICATION SPECIFICATIONS
The following are the communication specifications of the built-in Ethernet port of the CPU module.
Item Specification
Data transfer speed 100 or 10 Mbps
Communication mode Full-duplex or half-duplex
Transmission method Base band
Transmission Maximum distance between hub
specifications 100 m
and node
Maximum 10BASE-T Cascade connection: Up to four*2
number of
nodes/connection 100BASE-TX Cascade connection: Up to two*2
*4 The ports must comply with the IEEE802.3 10BASE-T or IEEE802.3 100BASE-TX standards.
● When connected to a hub, the CPU module determines the cable used (10BASE-T or 100BASE-TX) and the
communication mode (full-duplex or half-duplex) according to the hub.
Set the hub into the half-duplex mode if the hub that does not have the auto-negotiation function.
● The operation of commercial devices used for the following applications is not guaranteed. Check the operation before
using the module.
• Internet (general public line)
(Internet-access service offered by an Internet service provider or a telecommunications carrier)
• Firewall device(s)
• Broadband router(s)
• Wireless LAN
● If Ethernet communication is performed with "Specify service process execution counts" selected for "Service processing
setting" in the PLC system tab of PLC parameter, a scan time increases by time for service processing (approximately
500ms).
To reduce it to 500ms or less, select an item other than "Specify service process execution counts".
(Example: Select "Specify service process time" and then enter a time value.)
● If broadcast storm occurs in the network, scan time may be increased.
● If the destination device of the CPU module does not respond due to power-off or other reasons, Ethernet communication
of the CPU module may delay up to 500ms.
22
CHAPTER 2 COMMUNICATION SPECIFICATIONS
Remark
TCP and UDP are defined as follows:
• TCP (Transmission Control Protocol)
In communications among programmable controllers and networked devices, this protocol establishes a
connection between port numbers of the two devices to perform reliable data communications.
2
• UDP (User Datagram Protocol)
This is a connectionless protocol and thereby its speed is faster than that of TCP. However, the reliability in data
communications is low. (Data may be lost or not be received in correct order.) Note that simultaneous broadcast is
available.
Select an appropriate protocol, considering the specifications of the external device and the characteristics of the above
protocols.
23
CHAPTER 3 CONNECTION OF PROGRAMMING
TOOLS AND GOT
This chapter explains how to connect the CPU module to a programming tool or GOT.
Ethernet
Hub
● The CPU module and programming tool can be connected directly (simple connection) through one Ethernet cable. In
direct connection, the module and the tool can communicate with each other without each other's IP address in mind.
( Page 48, CHAPTER 4)
● GOT on Ethernet can be accessed from the programming tool via the built-in Ethernet port of a CPU module.
( Page 31, Section 3.5)
Start
Connecting cables and external devices Connect cables and devices required for Ethernet
communication.
Setting the connection target Set a connection target by the programming tool.
( Page 27, Section 3.2 )
End
24
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
2.
1.
25
2. Set MELSOFT connection.
button
Item Setting
Protocol Select "TCP" or "UDP" depending on the connected device.
Open System Select "MELSOFT Connection".
After writing the parameters to the CPU module, power off and on or reset the CPU module to enable the
parameters.
26
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
1.
2.
3.
27
2. Select "PLC Module" for "PLC side I/F".
Enter the IP address or host name of the CPU module in the "PLC side I/F Detailed Setting of PLC
Module" window, as shown below.
(For the host name, enter the name set in the Microsoft® Windows® hosts file.)
28
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
In a configuration using a hub, clicking in the "PLC side I/F Detailed Setting of PLC
Module" window will start searching for CPU modules connected to the hub where the programming tool is also
connected, and display a list of them.
• CPU modules connected to cascaded hubs are also searched and a list of them is displayed.
• CPU modules connected via a router cannot be searched.
29
3.4 Communication via Routers
From the built-in Ethernet port, access is available via routers on a network such as a corporate LAN.*1
Router
Corporate
LAN
Personal
CPU module computer
*1 For some functions as shown below, communications via a router are not available.
• Searching CPU modules on the network
• Simultaneous broadcast in socket communication
For access via a router, follow the instruction in the step 1 on Page 25, Section 3.1 (1) to set the subnet mask
pattern and the default router IP address in addition to the IP address.
30
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
GOT on Ethernet can be accessed from the programming tool via the built-in Ethernet port of a CPU module. An
access via another network is also enabled.Note 3.1
CPU module
3
Ethernet
GOT
Network
GOT
31
Remark
If the MELSOFT connection extended setting is not used, an Ethernet module needs to be used to access the GOT and
modules on Ethernet from the programming tool.
Ethernet module
Ethernet
32
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
By setting the routing parameter, the following network stations other than Ethernet can also be accessed.
• CC-Link IE Controller Network
• MELSECNET/H
• CC-Link IE Field Network
• CC-Link
When relaying multiple networks, communications can be made with stations up to eight networks apart (number of
relay stations: 7).
Network No.5
(Relay station 5)
CPU
module
Network No.6
(Relay station 6)
CPU
module
Network No.7
(Relay
station 7)
CPU CPU CPU
module module module
Remark
Access from other stations using MELSOFT connection extended setting is performed using the UDP/IP protocol and data is
always communicated in binary code.
33
3.5.1 Setting method
Button
Remark
When the MELSOFT connection extended setting is used, do not overlap the network number to be set for a CPU module
with the network number of another relay network. Set a station number different from those used in the same network.
34
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
35
(a) Station No. <-> IP information setting system (conversion method)
There are four kinds of station No. <-> IP information setting system as shown below.
: Setting required, ×: Setting not required
Conversion method Net mask pattern Conversion setting
Automatic response system × ×
IP address calculation system ×
For details of each conversion method, refer to Page 39, Section 3.5.2.
Class B FF.FF.00.00H
Class C FF.FF.FF.00H
36
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
Network No.
(Relay station)
Network No.
37
(a) Setting examples
Making access from request source (network No.1) to request destination (network No.3) via network No. 2
Target Relay
[1] network No. network No. Relay station No. [1]
Request 3 1 3
source
The data is transferred to the relay station [2]
of the own network to go to the network No.3.
38
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
This section provides an overview of the processing of the conversion method that is set in "Station No. <-> IP
Information Setting".
CPU
module
Ethernet
Relay receiving station Relay sending station
CPU
module
The automatic response
system can be set.
CPU
module
Request destination station
3.5.2 Convert format between the network number/station number and IP address/port number
3.5 MELSOFT Connection Extended Setting
Relay station
When the CPU module receives other station access request message (command frame), the send source
network number, IP address, and UDP port number in the request message, are stored internally. The response
message (response) for the request message is returned to the destination IP address and UDP port number
calculated from the stored network number and station number. Therefore, by receiving the other station access
request message first, the communication partner stations can be maintained.
The maximum number of station information that can be set is 64. When more than 64 other station access
request messages are received, the CPU module starts deleting from the oldest data to store the station
information in the newly received request message. However, it is ignored if the station information is the same
as the station information already stored. *1
*1 Information from the same station is not stored twice.
39
(2) IP address calculation system
During calculation, the IP address of the partner station is obtained from the calculation equation below according
to the network number and station number, and the UDP port number predefined for the CPU module system is
used as the UDP port number of the destination.
For more information about the net mask pattern for routing other networks, refer to Page 36, Section 3.5.1 (2)
(b).
Network number
IP address of IP address of Logical Net mask Logical
= and station number
the partner station the own station product pattern sum
of the destination
When a request message (command frame) to access other station is received, the IP address is calculated from
the network number and station number of the destination in the request message, and the request message is
sent to the next station.*1
The response message (response) for the request message is returned based on the return IP address and the
stored data above.
*1 The network number and station number of the destination in the request message are stored in the CPU module.
The logical sum is calculated differently depending on the class of the own station IP address. An IP address is
calculated for each class as follows.
40
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
3.5.2 Convert format between the network number/station number and IP address/port number
3.5 MELSOFT Connection Extended Setting
Network No. and station No. Logical sum 0 2
Remark
● IP address configuration of class A
31 30 to 24 23 to 16 15 to 0
Network
Class address Host address
41
(3) Table exchange system
This method uses the network number, station number, and IP address set in the conversion table of the Station
No. <-> IP information, and uses the UDP port number predefined for the Ethernet system as the UDP port
number of the destination.
If duplicate network and station numbers are set in the conversion table, the data set with the younger registration
number is used. If all the required values are not set, communication may not be performed successfully.
When a request message (command frame) to access other station is received, the same network number and
station number are searched in the conversion table of the Station No. <-> IP information, and the request
message is sent to the partner station with the corresponding IP address.
The response message (response) for the request message is returned based on the return IP address and the
data in the conversion table above.
Network No. :2
CPU Station No. : 22
module IP Address : (192. 0. 2. 22)
Module setting details when accessing from CPU [1] to CPU [2]
Item [1] Request source
[2] [3] [4]
station *1
Network No., station
1, 12
Setting value (Decimal) number Setting not necessary Setting not necessary Setting not necessary
IP Address 192.0.1.12
Module setting details when accessing from CPU [1] to CPU [4]
[4] Request
Item [1] Request source [2] Relay receiving [3] Relay sending
destination station
station *1 station *2 station *1
*2
Network No., station
1, 12 1, 11 2, 22 2, 21
Setting value (Decimal) number
IP Address 192.0.1.12 192.0.1.11 192.0.2.22 192.0.2.21
Module setting details when accessing from CPU [2] to CPU [1]
[2] Request
Item
[1] destination station [3] [4]
*1
Network No., station
1, 11
Setting value (Decimal) number Setting not necessary Setting not necessary Setting not necessary
IP Address 192.0.1.11
42
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
Module setting details when accessing from CPU [3] to CPU [4]
Item [3] Relay sending
[1] [2] [4]
station *1
Network No., station
2, 22
Setting value (Decimal) number Setting not necessary Setting not necessary Setting not necessary
IP Address 192.0.2.22
Module setting details when accessing from CPU [4] to CPU [1]
[4] Request
Item [1] Request source [2] Relay sending [3] Relay receiving
destination station 3
station *2 station *1 station *2
*1
Network No., station
1, 12 1, 11 2, 22 2, 21
Setting value (Decimal) number
IP Address 192.0.1.12 192.0.1.11 192.0.2.22 192.0.2.21
Module setting details when accessing from CPU [4] to CPU [3]
[4] Request
Item
[1] [2] [3] destination station
*1
Network No., station
2, 21
Setting value (Decimal) number Setting not necessary Setting not necessary Setting not necessary
IP Address 192.0.2.21
*1 Indicates that the set value is for sending request messages.
*2 Indicates that the set value is for sending response messages.
3.5.2 Convert format between the network number/station number and IP address/port number
3.5 MELSOFT Connection Extended Setting
When a request message (command frame) to access other station is received, the request message is sent to
the next station obtained by the table exchange system at first.
If the IP address of the CPU module cannot be obtained by the table exchange system, the IP address is
obtained by the IP address calculation system to send the request message.
The response message (response) to the request message is returned based on the return IP address and the
data in the conversion table or the stored data.
43
3.5.3 Checking communication status
Among the errors that occurred when the MELSOFT connection extended setting is used, those arising from
communication errors are stored in the error history of Ethernet diagnostics. "MELSOFT connection" is displayed for
the connection number and open system of each error.
44
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
3.6 Precautions
3.6 Precautions
(4) Retransmission on TCP connection
If no ACK response is returned from the other end of a TCP connection, the ACK will be resent six times, starting
in 0.3 seconds after the first transmission, and then 0.6, 1.2, 2.4, 4.8, and 9.6 seconds. When no TCP ACK
response is returned within 19.2 seconds after the last retransmission, the device is regarded as faulty and the
connection is disconnected. (As a result, the connection is disconnected in total of 38.1 seconds.)
45
(5) MELSOFT connection over TCP or UDP
For TCP or UDP communications with multiple MELSOFT devices, set the same number of protocols as that of
the connected MELSOFT devices in the setting of the PLC parameter.
CPU module
Ethernet
Hub
MELSOFT device
MELSOFT device MELSOFT device
When all MELSOFT devices start communicating at the same time, devices may fail to communicate because of the
congestion of communications. In such a case, schedule the timing for when each device starts communicating so that the
communication congestion will not occur. When using GOTs, for example, set different rise time and time-out values in the
GOTs.
46
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
Ex. Relay communication cannot be performed because the MELSOFT connection extended setting is not
used in CPU No.2, which is the control CPU of the Ethernet module. Change the control CPU of the 3
Ethernet module to CPU No.1, or set the MELSOFT connection extended setting to "USE" for CPU No.2.
Programming tool
Controlled by
CPU No.2
USB
*1
Ethernet Ethernet
*1 CPU No.2 does not use the MELSOFT connection extended setting.
3.6 Precautions
47
CHAPTER 4 DIRECT CONNECTION TO
PROGRAMMING TOOL (SIMPLE
CONNECTION)
The CPU module can be directly connected to the programming tool with an Ethernet cable, without using a hub
(simple connection).
For direct connection, the IP address and host name need not be specified in the connection target setting.
(Simultaneous broadcast is used.)
CPU module
Ethernet cable
Programming tool
An Ethernet cable used for direct connection will be longer compared with the case of using a USB cable. This can cause an
unauthorized connection from a remote location.
Unauthorized connections can be prevented by selecting the following option in the Built-in Ethernet port tab of the PLC
parameter window.
48
CHAPTER 4 DIRECT CONNECTION TO PROGRAMMING TOOL (SIMPLE CONNECTION)
4
1.
2.
3.
49
4.2 Precautions
CPU module
Hub
Ethernet cable
Programming tool
• When two or more Ethernet ports are enabled in the network connections setting on the personal computer,
communication by direct connection is not possible. In the setting, leave only one Ethernet port enabled for
direct connection and disable other Ethernet ports.
• In the CPU module IP address bits, the bits corresponding to the host address of the class in the personal
computer IP address are all ON or all OFF.
Remark
● The IP address pattern for each class is as follows.
Class A: 0.x.x.x to 127.x.x.x Class B: 128.x.x.x to 191.x.x.x Class C: 192.x.x.x to 223.x.x.x
● The host address for each class is the part shown with "0".
Class A: 255. 0. 0. 0 Class B: 255.255. 0. 0 Class C: 255.255.255. 0
50
CHAPTER 5 MC PROTOCOL COMMUNICATION
The built-in Ethernet port allows MC protocol communication. From an peripheral device such as a personal computer
or HMI, device data of the CPU module can be read or written using MC protocol. Monitoring of CPU module
operation, data analysis, and production control are available on a personal computer or HMI by these device data
reading and writing.
Besides, the remote password function can prevent unauthorized access from outside of the system. ( Page 152,
CHAPTER 10)
CPU module
5
Hub
From the peripheral device such as a personal computer or HMI, only the CPU module connected can communicate using
MC protocol.
An access to a CPU on another station via CC-Link network is not allowed.
Start
Remark
Access through routers is also available. When configuring the settings for it, set the subnet mask pattern and default router
IP address. ( Page 30, Section 3.4)
51
5.1 Setting Method
3.
1.
2.
1. Select Binary or ASCII code as the communication data code used for MC protocol.
2. Select the "Enable online change (FTP, MC Protocol)" checkbox to enable data to be written to the
CPU module even in the RUN state.
52
CHAPTER 5 MC PROTOCOL COMMUNICATION
button
Item Description
Protocol Select TCP or UDP depending on the target device.
Open System Select "MC Protocol".
Host Station Port
Set the port number of the host station. (Setting range: 0401H to 1387H, 1392H to FFFEH)*1
No.
When the "Enable online change (FTP, MC protocol)" setting is disabled, if the CPU module in the RUN state receives a data
write request from the target device, data will not be written and an NAK message will be returned.
53
5.2 MC Protocol Commands
The following commands are executable for MC protocol communication of the CPU module.
*1 Devices, TS, TC, SS, SC, CS, and CC cannot be specified in units of words.
Specifying any of these for monitor registration will cause an error (4032H) at the time of monitoring execution.
*2 For monitor registration, monitoring conditions cannot be set.
*3 Do not execute monitor registration from multiple devices. If executed, the last monitor registration takes effect.
*4 Set the number of processed points so that the following condition is satisfied.
(Number of word access points) × 12 + (Number of double-word access points) × 14 1920
For bit devices, one point is regarded as 16 bits in word access and 32 bits in double-word access.
For word devices, one point is regarded as one word in word access, and two words in double-word access.
54
CHAPTER 5 MC PROTOCOL COMMUNICATION
*1 Devices such as TS, TC, CS, and CC cannot be specified in units of words. If specified, an error (4032H) occurs during
monitoring.
55
5.2.2 Available devices
The following table lists the devices available in the commands used for MC protocol communication.
Device code*1
Classification Device Device number range
ASCII Binary
Input X* 9CH The number range of a device in a CPU module, Hexadecimal
Contact TS C1H
Contact CS C4H
*1 This is a code specified in MC protocol messages. When communicating data in ASCII code, specify the code in two
characters. If the code consists of only one character, add "*" (ASCII code: 2AH) or a space (ASCII code: 20H) after the
character.
*2 Devices of DX/DY1000 or later are not available. Use X/Y devices to access devices of X/Y1000 or later.
56
CHAPTER 5 MC PROTOCOL COMMUNICATION
Device code
Classification Device Device range Device number
ASCII Binary
5820
Input (35H/38H/32H 58H/20H X0 to X7FF 0000H to 07FFH
/30H)
5920
Output (35H/39H/32H 59H/20H Y0 to Y7FF 0000H to 07FFH
/30H)
• M0 to M8191
4D20 • M9000 to M9255
• 0000H to 1FFFH
Internal relay (34H/44H/32H 4DH/20H (SM1000 to SM1255)*1
• 2328H to 2427H
/30H) Note, however, that local devices
cannot be accessed.
5
Latch relay - - Cannot be accessed.
4620
internal user
Annunciator (34H/36H/32H 46H/20H F0 to F2047 0000H to 07FFH
device
/30H)
• D0 to D6143
4420 • D9000 to D9255
• 0000H to 17FFH
Data register (34H/34H/32H 42H/20H (SD1000 to SD1255)*1
• 2328H to 2427H
/30H) Note, however, that local devices
cannot be accessed.
5720
57
Device code
Classification Device Device range Device number
ASCII Binary
5453
Contact (35H/34H/35H 54H/53H
/33H)
5443 T0 to T2047
Timer Coil (35H/34H/34H 54H/43H Note, however, that local devices 0000H to 07FFH
/33H) cannot be accessed.
544E
Current value (35H/34H/34H 54H/4EH
/45H)
Contact - -
Retentive timer Coil - - Cannot be accessed.
Current value - -
4343 C0 to C1023
Counter Coil (34H/33H/34H 43H/43H Note, however, that local devices 0000H to 03FFH
/33H) cannot be accessed.
434E
Current value (34H/33H/34H 43H/4EH
45H)
4420 • D0 to D6143
• 0000H to 17FFH
Extended data register (34H/34H/32H 42H/20H • D9000 to D9255
*1
• 2328H to 2427H
/30H) (SD1000 to SD1255)
5720
Extended link register (35H/37H/32H 57H/20H W0 to WFFF 0000H to 0FFFH
/30H)
*1 When M9000 to M9255 (D9000 to D9255) are specified, specify SM1000 to SM1255 (SD1000 to SD1255). Make sure to
check the checkbox in the "A-PLC Compatibility Setting" field in the PLC system tab of the PLC parameters.
*2 Available for the CPU modules with the following serial number (first five digits).
• QnUDE(H)CPU: "14112" or later
• QnUDVCPU: "15043" or later
58
CHAPTER 5 MC PROTOCOL COMMUNICATION
5.3 Precautions
button
A-compatible 1E frame *1
*1 Available for the QnUDE(H)CPU with a serial number (first five digits) of "13102" or later
5.3 Precautions
(4) When UDP is selected for Protocol
• If a new request message is sent to a UDP port after the previous request message is sent to the same port
and before no response is returned, the new request message will be discarded.
• Setting the same host station port number for multiple UDP connections is regarded as one setting. For
communication with multiple devices using the same host station port number, select TCP.
59
(6) Receiving a response message
The following shows an example of receive processing on the other device side.
NO
Is TCP connection open?
YES
Received data
within the time specified by NO
the monitoring timer
value?
YES
NO
Sufficient receive
data size?
YES
Processing for the response message
YES
End Error handling
For Ethernet communication, TCP socket functions are used inside personal computers.
The functions do not have boundary concept. Therefore, if the sender sent data by calling the "send" function once, the
receiver needs to call the "recv" function once or more times to read out the data. ("send" does not correspond to "recv" on
the one-to-one basis.) For this reason, the processing shown above is always required on the program of the receiving
device. Note that, if the "recv" function is used in blocking mode, data may be read by calling the function once.
60
CHAPTER 5 MC PROTOCOL COMMUNICATION
When an error occurs during MC protocol communication, an error code is sent from the CPU module to the external
device. The following table lists error codes, error descriptions, and corrective actions.
Error code
Description Corrective action
(Hexadecimal)
Refer to the following manual.
Errors detected by the CPU module
4000H to 4FFFH QCPU User's Manual(Hardware Design, Maintenance and
(Errors occurred in other than MC protocol communication)
Inspection) 5
Although online change is disabled, the connected device • Before enabling online change, write the data.
0055H
requested the RUN-state CPU module for data writing. • Change the CPU module state to STOP and write the data.
• Select Binary Code for "Communication Data Code", and restart
When "Communication Data Code" is set to ASCII Code, ASCII the CPU module.
C050 H
code data that cannot be converted to binary were received. • Correct the send data of the connected device and resend the
data.
Correct the number of read or write points, and resend the data to
C051H to C054H The number of read or write points is outside the allowable range.
the CPU module.
Correct the start address or the number of read or write points, and
C056 H The read or write request exceeds the maximum address. resend the data to the CPU module.
(The maximum address must not be exceeded.)
The request data length after ASCII-to-binary conversion does not Check and correct the text data or the request data length of the
C058 H
match the data size of the character area (a part of text data). header, and resend the data to the CPU module.
• The command and/or subcommand are specified incorrectly. • Check the request.
C059 H • The CPU module does not support the command and/or • Use commands and/or subcommands supported by the CPU
5.4 Error codes, end codes, and abnormal codes in MC protocol communication
subcommand. module.
The CPU module cannot read data from or write data to the
C05BH Check the device to be read or written.
specified device.
The request data is incorrect. (e.g. reading or writing data in units of Correct the request data and resend it to the CPU module.
C05CH
bits from or to a word device) (e.g. subcommand correction)
C05DH No monitor registration Perform monitor registration before monitoring.
• Correct the network number, PC number, request destination
module I/O number, or request destination module station
C05FH The request cannot be executed to the CPU module.
number.
• Correct the read/write request data.
The request data is incorrect. (ex. incorrect specification of data for
C060 H Correct the request data and resend it to the CPU module.
bit devices)
The request data length does not match the number of data in the Check and correct the text data or the request data length of the
C061 H
character area (a part of text data). header, and resend the data to the CPU module.
The CPU module received a request message in ASCII format
• Send a request message that matches the "Communication Data
when "Communication Data Code" is set to Binary Code, or
Code" setting.
C06FH received it in binary format when the setting is set to ASCII Code.
• Change the "Communication Data Code" setting so that it will
(This error code is only registered to the error history, and no
match the request message.
abnormal response is returned.)
The device memory extension cannot be specified for the target Read data from or write data to the device memory without
C070 H
station. specifying the extension.
• Correct the request data.
C0B5H The CPU module cannot handle the data specified.
• Stop the current request.
Correct the remote password, and unlock and lock the remote
C200 H The remote password is incorrect.
password function again.
61
Error code
Description Corrective action
(Hexadecimal)
The port used for communication is locked with the remote
password.
C201H Or, because of the remote password lock status with Unlock the remote password before communication.
"Communication Data Code" set to ASCII Code, the subcommand
and later part cannot be converted to a binary code.
The connected device is different from the one that requested for From the device that requested the unlock processing, request for
C204H
unlock processing of the remote password. lock processing of the remote password.
62
CHAPTER 5 MC PROTOCOL COMMUNICATION
When the communication data code setting is set to ASCII code in the Built-in Ethernet Correct the send data on the external
54H
port QCPU, ASCII code data that cannot be converted to binary code was received. device side.
When the setting for online change is disabled on the Built-in Ethernet port tab of PLC • Enable online change and write data.
55H parameter in GX Developer, an external device requested online change to the CPU • Change the status of the CPU module to
module. STOP and write data.
56H An external device specified the incorrect device. Specify the device correctly.
• The number of points for a command specified by an external device exceeds the
maximum number of processing points (number of points can be processed per
• Correct the number of points specified or
communication) for each processing.
the start address (start device number).
5.4 Error codes, end codes, and abnormal codes in MC protocol communication
57H • The number of points specified from the start address (start device number) exceeds
• Check the command.
the maximum address (maximum device number) for each processing.
• The length of a command message is too short to analyze.
Monitoring was requested without monitor data being registered. Register the monitor data.
The start address (start device number) of a command specified by an external device Correct the start address within the setting
exceeds the setting range. range for each processing.
The file register (R) cannot be specified. Check the device.
58H
• A word device is specified in a command for bit devices.
Correct the command or the specified
• In a command for word devices, the start number of a bit device is specified by a value
device.
other than a multiple of 16.
Identify an error location according to the
5BH The CPU module cannot process requests from an external device.
abnormal code and correct the error.
The communication target port is in the remote password locked status. Or, when the
Perform remote password unlock
C201H communication data code setting is set to ASCII code, any data of subcommands and
processing before communication.
later cannot be converted to binary code since the remote password is locked.
63
CHAPTER 6 DATA COMMUNICATIONS USING
THE PREDEFINED PROTOCOL Note 6.1
The predefined protocol function sends and receives packets predefined by using GX Works2, enabling easy
communications with external devices (such as measuring instruments and bar code readers). Protocols can be either
selected from the prepared predefined protocol library, or created and edited by users.Note 6.1
GX Works2
Sending
The predefined protocol function can only be used for the QnUDVCPU.
When using the predefined protocol function, check the versions of the CPU module and GX Works2.
( Page 190, Appendix 3)
64
CHAPTER 6 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
6.1 Specifications
6.1 Specifications
65
6.2 Setting Method
The setting required for using the predefined protocol function is described below.
1. Open the "Predefined Protocol Support Function"
window.
Select "User Protocol Library" in the "Add Protocol" window to read the protocol stored by the user. For details of the user
protocol library, refer to the following.
GX Works2 Version 1 Operating Manual (Intelligent Function Module)
66
CHAPTER 6 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
67
6. Write the protocol setting data to the CPU module.
In the "Writing Protocol Setting" window, specify the
write-target drive in the CPU module and write the
protocol setting data.*1
● To enable the written protocol setting data without powering off or resetting the CPU module, turn on SM1355
(Predefined protocol setting check request). Before enabling the protocol setting data, stop the CPU module and check
that no instruction is being executed. Depending on the on-timing of SM1355 (Predefined protocol setting check
request), the instruction being executed may end abnormally.
Item Description
Protocol Select "TCP" or "UDP".
Open System Select "Predefined Protocol".
TCP Connection When "Protocol" is "TCP", select the connection method. ( Page 77, Section 7.1)
Set the port number of the CPU module.
Host Station
Setting range: 0001H to 1387H, 1392H to FFFEH (1 to 4999, 5010 to 65534)*1
Set the start device number for storing the protocol execution status, received data verification
result, number of protocol executions, and protocol cancellation status. ( Page 70, Section
Start Device to Store
6.2 (1))
Predefined Protocol
The area of 19 words starting from the specified device is used.
Available devices: D, W, R, ZR
*1 Do not specify 1388H to 1391H (5000 to 5009) because these ports are used by the system. ( Page 189, Appendix 2)
68
CHAPTER 6 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
69
(1) Start device to store the predefined protocol operation status
In the open setting, set the start device where the predefined protocol operation status is to be stored. The
following information is stored in the area of 19 words starting from the selected device.
Start Device to Store
Predefined Protocol Name Description*1
(offset)
The execution status of the predefined protocol function is stored. (Default: 0)
• 0: Not executed
Protocol execution • 1: Waiting for data to be sent
+0
status • 2: Data being sent
• 3: Waiting for data to be received
• 5: Execution completed
The verification result of received packet No.1 is stored. (Default: 0) ( Page 70,
Received data
Section 6.2 (1) (a))
+1 verification result
• b0 to b7: Element No. where the verification result did not match
(received packet No.1)
• b8 to b15: The cause of mismatch (verification result code)
Received data
verification result
+2 to 16 The bit configuration is the same as the received packet No.1.
(received packet No.2
to 16)
The number of protocol executions is stored. (Default: 0)
Number of protocol
+17 • 0: No execution
executions
• 1 to 65535: Number of executions (The value remains the same after 65535.)
The protocol cancellation request status is stored. (Default: 0)
Protocol cancellation • 0: No cancellation requested
+18
specification • 1: Cancellation requested (set by users)
• 2: Cancellation completed (set by the system)
*1 Even after data communications by the predefined protocol function (executed by the SP.ECPRTCL instruction) is
completed, the stored values are held.
70
CHAPTER 6 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
There are three protocol communication types: "Send Only", "Receive Only", and "Send & Receive".
The packet elements include "Length", "Static data", "Non-conversion Variable", and "Non-verified Reception".
Up to 32 elements can be set in a single packet.
6
The protocol setting method and packet elements are the same as those of the Ethernet interface module, except for
some differences.
Q Corresponding Ethernet Interface Module User's Manual (Basic)
The following are the differences.
• Read the E71 (Ethernet interface module) as the CPU module in the manual.
• Buffer memory cannot be set as a data storage area for non-conversion variable.
71
6.4 Predefined Protocol Function Instructions
The predefined protocol function instructions are provided for the CPU module to use the predefined protocol function.
This section describes the predefined protocol function instructions.
Instruction Description Reference
Establishes a connection with the external device.
If an Active open is performed by the CPU module, the Page 77, Section 7.1
SP.SOCOPEN
SP.SOCOPEN instruction is used to establish a connection with Page 95, Section 7.4.1
the external device.
SP.SOCCLOSE Closes a connection with the external device. Page 99, Section 7.4.2
Page 113, Section
SP.SOCCINF Reads out connection information.
7.4.6
Changes the target of the connection for UDP/IP Page 116, Section
SP.SOCCSET
communications. 7.4.7
SP.ECPRTCL Executes the configured predefined protocol. Page 72, Section 6.4.1
If the instruction has a completion device, do not change any data (such as control data and request data) specified for the
instruction until the execution is completed.
This instruction sends and receives packets set by the predefined protocol support function of GX Works2.
Usage of the SP.ECPRTCL instruction is the same as that of the GP.ECPRTCL instruction for the Ethernet interface
module, except for some differences. For the GP.ECPRTCL instruction, refer to the following.
Q Corresponding Ethernet Interface Module User's Manual (Basic)
The following are the differences.
Item Differences
U0 (dummy) needs to be specified.
Setting data Un Since this is a dummy, no change is required when replacing from the GP.ECPRTCL
instruction of the Ethernet interface module.
The connection No. set in the "Open Setting" of the "Built-in Ethernet Port Setting" tab
Setting data n1
need to be specified.
The protocol execution status can be checked by "Start Device to Store Predefined
Protocol execution status
Protocol" in the "Open Setting" of the "Built-in Ethernet Port Setting" tab.
The pairing open setting is not available in the CPU module. The CPU module sends
Pairing open
and receives data using one connection.
Protocol execution can be cancelled by "Start Device to Store Predefined Protocol"
Cancellation of protocol execution (offset+18) set in the "Open Setting" of the "Built-in Ethernet Port Setting" tab.
( Page 70, Section 6.2 (1) )
72
CHAPTER 6 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
The predefined protocol function can be executed when the protocol setting data is enabled and SM1354 (Predefined
protocol ready) is on. The written protocol setting data will be enabled when
• the CPU module is powered on or is reset, or
• SM1355 (Predefined protocol setting check request) is turned on
SM1354 is used as an interlock signal to execute the protocol.
(2) Changing the protocol setting data without powering off or resetting the CPU
module
The protocol setting data can be changed by turning on SM1355 (Predefined protocol setting check request).
After SM1355 turns on, the following occurs.
• SM1354 (Predefined protocol ready) turns off.
• If the protocol setting data is normal, SM1354 turns on, and SM1355 turns off.
For operation image and data structure of the predefined protocol function, refer to the following. (Read the E71
(Ethernet interface module) as the CPU module.)
Q Corresponding Ethernet Interface Module User's Manual (Basic)
73
6.7 Precautions
74
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
The socket communication function allows data communications with the devices on Ethernet by TCP or UDP using
various dedicated instructions.
Sending data
SP.SOCSND instruction
Socket communication
receive area*1
Connection No.1
Program
Connection No.2
SP.SOCRCV instruction
S.SOCRCVS instruction Connection No.3
External device
Reading receive data to Receiving data
Connection No.16
*1 The area is used for storing data received from the connected open devices. 7
Remark
● For dedicated instructions used for the socket communication function, refer to: Page 94, Section 7.4
● Access through routers is also available (except for simultaneous broadcast). When configuring the settings for it, set the
subnet mask pattern and default router IP address. ( Page 30, Section 3.4)
Note 7.1
Before using the socket communication function for the QnUDE(H)CPU, check the versions of the CPU module and
programming tool. ( Page 190, Appendix 3)
75
(1) Port numbers
In socket communication, port numbers are used to identify respective communications and thereby multiple
communications are available both on TCP and UDP.
• For sending
Specify the port number of the CPU module from which data are sent, and the port number of the destination
device.
• For receiving
Specify the port number of the CPU module, and read out the data sent to the port.
CPU module
(IP address: xx.xx.xx.xx) Ethernet
Sending UDP data from port No.A of the CPU
module to port No.L of external device 1
External device 1
(IP address: yy.yy.yy.yy)
Port No.A Sending UDP data from port No.L of Port No.L
external device 1 to port No.A of the CPU
module
76
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
TCP (Transmission Control Protocol) establishes a connection to a device with a port number, and performs reliable
data communications.
To perform socket communication using TCP, confirm the following in advance.
• IP address and port number of the target device
• IP address and port number of the CPU module
• Which side will open a connection, the target device or CPU module?
(Active open or Passive open)
Type of TCP
Description
connection
Remark
The expressions of Active and Passive opens may vary according to the device.
• Active open: TCP connection initiating device, client, connecting side, etc.
• Passive open: TCP connection waiting device, server, listening side, etc.
77
(2) Program example for Active open
The following shows a communication flow of an Active open.
Start Specify the port number of the external device waiting for
TCP connection and open a connection by Active open.
Open processing:
SP.SOCOPEN instruction
NO
End
button
Item Setting
Protocol TCP
Open System Socket Communication
TCP Connection Active
Host Station Port No. 1000H (Setting range: 0001H to 1387H, 1392H to FFFEH)*1
*1 Do not specify 1388H to 1391H because these ports are used by the system. ( Page 189, Appendix 2)
78
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
79
(c) Sample program
*1
<<Fixed length mode setting>>
Normal completion
Error completion
<<Data sending>>
Setting send data length
Normal completion
Error completion
<<Data receiving>>
Receiving data
Normal completion
Error completion
Normal completion
Error completion
*1 There are two kinds of TCP receive modes: TCP standard receive mode and TCP fixed-length receive mode. For fixing
the data size, run the program enclosed by a dotted line. (It can be omitted when the data size is not fixed.)
For the TCP receive mode, refer to the section for the SP.SOCRMODE instruction. ( Page 118, Section 7.4.8)
80
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
SOCCLOSE instruction
7
81
(3) Program example for Passive open
The following shows a communication flow of a Passive open.
NO
Send or receive?
YES
button
Item Setting
Protocol TCP
Open System Socket Communication
TCP Connection Unpassive
Host Station Port No. 1000H (Setting range: 0001H to 1387H, 1392H to FFFEH)*2
82
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
83
(c) Sample program
*1
<<Fixed length mode setting>>
Normal completion
Error completion
<<Data receiving>>
Receiving data
Normal completion
Error completion
*1 There are two kinds of TCP receive modes: TCP standard receive mode and TCP fixed-length receive mode.
For fixing the data size, run the program enclosed by a dotted line. (It can be omitted when the data size is not fixed.)
For the TCP receive mode, refer to the section for the SP.SOCRMODE instruction. ( Page 118, Section 7.4.8)
*2 For acquiring information of the device connected on TCP, run the program enclosed by a dotted line. (It can be omitted
when the information acquisition is not needed.)
84
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
• When a device establishes a connection by Passive open, the IP address and port number of the
connected device can be acquired using the SP.SOCCINF instruction.
For the SP.SOCCINF instruction, refer to: Page 113, Section 7.4.6
• On TCP, one connection is established with one target device.
To communicate with multiple devices from one port number, prepare the same number of connections as
7
that of the target devices.
A connection that exceeds the preset number of connections will be disconnected immediately.
• Do not accept a connection from a device until the CPU module is placed in the wait-for-open state.
If a TCP connection request is received before entering the wait-for-open state after completion of CPU
startup, the request will be recognized as an error, and a forced close message for the connection will be
returned to the interfacing device.
In this case, wait until the CPU state is changed to the wait-for-open state and then retry the connection
85
7.2 Communication Using UDP
UDP (User Datagram Protocol) is a simple protocol that does not perform data sequencing and retransmission.
To perform socket communication using UDP, confirm the following in advance.
• IP address and port number of the target device
• IP address and port number of the CPU module
button
Item Setting
Protocol UDP
Open System Socket Communication
TCP Connection Blank
Host Station Port No. 1000H (Setting range: 0001H to 1387H and 1392H to FFFEH)*1
*1 Do not specify 1388H to 1391H because these ports are used by the system. ( Page 189, Appendix 2)
86
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
87
(c) Sample program
*1
<<Target changing>>
Changing setting of
Connection No.1
<<Data sending>>
Setting send data length
Normal completion
Error completion
<<Data receiving>> *2
Obtaining information of
target device
Receiving data
Normal completion
Error completion
*1 For changing the target device, run the program enclosed by a dotted line. (It can be omitted when the communication
target is not changed.) For details, refer to the section of the SP.SOCCSET instruction. ( Page 116, Section 7.4.7)
*2 For acquiring information of the target device connected on UDP, run the program enclosed by a dotted line. (It can be
omitted when the information acquisition is not needed.)
88
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
CPU module
(IP address: xx.xx.xx.xx, Subnet mask: 255.255.255.0)
Ethernet
Sending data from port No.A of the
Port No.A CPU module to each port No.N of all
external devices. Port No.L External device 1
(IP address: xx.xx.xx.yy)
Port No.N
External device 3
Port No.N
(IP address: xx.xx.xx.ww)
7
89
(3) Precautions
90
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
91
7.3 Precautions for the Socket Communication Function
This section provides other precautions for the socket communication function.
92
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
NO
Is TCP connection open?
YES
Receive the rest of the message. TCP connection is closed.
YES 7
Check the received data size.
NO
Sufficient receive data size?
YES
NO
Was the entire received
message processed?
YES
93
7.4 Socket Communication Function Instructions
The socket communication function instructions are provided for the CPU module to use the socket communication
function.
This section explains the socket communication function instructions.
● For configuration of data communication using the socket communication function, refer to: Page 77, Section 7.1,
Page 86, Section 7.2
● If the instruction has a completion device, do not change any data, such as control data and request data, that are
specified for the instruction until the execution of the instruction is completed.
● Do not execute any socket communication function instruction in an interrupt program.
● For error codes, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
94
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
Command
SP.SOCOPEN SP.SOCOPEN U0 S1 S2 D
S1 - - -
S2 - *1 *1 - - -
*1 (except for *1
D - - -
T, ST, and
C)
*1 File registers set for each local device or program cannot be used.
7
(1) Setting data
Setting data Description Set by*2 Data type
U0 Dummy - Character string
Start number of the device from which control data are stored User, system Device name
Start number of the device which turns on for one scan upon
D completion of the instruction System Bit
D +1 also turns on when failed.
When replacing the ZP.OPEN instruction (Ethernet module dedicated instruction), dummy argument can be used in a Built-
in Ethernet port QCPU instruction without rewriting.
95
(2) Control data
Device Item Description Setting range Set by*3
Specify which settings are used to open a
connection, parameter settings configured by a
programming tool or control data settings S2 +2
to S2 +9.
1H to FFFFFFFFH
S2 +4 Target device IP (FFFFFFFFH:
Specify the IP address of the target device.
S2 +5 address*4 Simultaneous
broadcast)
1H to FFFFH
Target device (FFFFH:
S2 +6 Specify the port number of the target device.
port number*4 Simultaneous
broadcast)
S2 +7
96
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
(3) Function
This instruction opens a connection specified in S1 .
The set values used for the open processing is selected in S2 +0.
The result of the SP.SOCOPEN instruction can be checked with the completion device, D +0 and D +1.
• Completion device D +0
Turns on in the END processing of the scan after completion of the SP.SOCOPEN instruction, and turns
off in the next END processing.
• Completion device D +1
Turns on or off according to the result of the SP.SOCOPEN instruction.
State Description
When completed Remains off.
Turns on in the END processing of the scan after the SP.SOCOPEN instruction is completed and turns off
When failed
in the next END processing.
• A connection with no parameters (no protocol is specified) can be opened. In this case, specify 8000H for
S2 +0 and configure open settings in S2 +2 to S2 +9.
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
(Error code: 4002)
• The connection number specified for S1 is other than 1 to 16.
(Error code: 4101)
• The device numbers specified for S2 and D exceed the device point range.
(Error code: 4101)
• An invalid device is specified.
(Error code: 4004)
97
(5) Program examples
• Program
Setting Execution/
completion type to 0H
Normal completion
Error completion
• Program
Setting Execution/
completion type to 8000H
Setting Application area
to 200H
(TCP/IP, Active open)
Setting port No. of host
station to 4096
Normal completion
Error completion
98
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
Command
SP.SOCCLOSE SP.SOCCLOSE U0 S1 S2 D
S1 - - -
S2 - *1 *1 - - -
*1 (except for *1
D - - -
T, ST, and
C)
*1 File registers set for each local device or program cannot be used.
7
(1) Setting data
Setting data Description Set by*2 Data type
U0 Dummy - Character string
When replacing the ZP.CLOSE instruction (Ethernet module dedicated instruction), dummy argument can be used in a Built-
in Ethernet port QCPU instruction without rewriting.
99
(3) Function
This instruction closes a connection specified in S1 . (Disconnection of a connection)
The result of the SP.SOCCLOSE instruction can be checked with the completion device, D +0 and D +1.
• Completion device D +0
Turns on in the END processing of a scan after completion of the SP.SOCCLOSE instruction, and turns off in
the next END processing.
• Completion device D +1
Turns on or off according to the result of the SP.SOCCLOSE instruction.
State Description
When completed Remains off.
Turns on in the END processing of a scan after completion of the SP.SOCCLOSE instruction, and turns
When failed
off in the next END processing.
SP.SOCCLOSE instruction
ON
OFF
Completion device D +0
ON When failed
OFF
Completion device D +1
Connection 1 scan when
close normally completed
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
(Error code: 4002)
• The connection number specified for S1 is other than 1 to 16.
(Error code: 4101)
• The device numbers specified for S2 and D exceed the device point range.
(Error code: 4101)
• An invalid device is specified.
(Error code: 4004)
Remark
Do not use Passive open for execution of the SP.SOCCLOSE instruction. Doing so will turn off the Open completion signal
and Open request signal of the connection and cause close processing, which disables data transfer.
100
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
• Program
Setting SP.SOCCLOSE
executing flag
Normal completion
Error completion
7
Resetting SP.SOCCLOSE
executing flag
101
7.4.3 Reading out received data in the END processing
(SP.SOCRCV)
Command
SP.SOCRCV SP.SOCRCV U0 S1 S2 D1 D2
S1 - - -
S2 - *1 *1 - - -
D1 - *1 *1 - - -
*1 (except for *1
D2 - - -
T, ST, and
C)
*1 File registers set for each local device or program cannot be used.
When replacing the ZP.BUFRCV instruction (Ethernet module dedicated instruction), dummy argument can be used in a
Built-in Ethernet port QCPU instruction without rewriting.
102
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
● Receive data size is 2046 bytes by default. To receive data over 2046 bytes, change the receive data size with the
SP.SOCRMODE instruction.
7
● When the SP.SOCRCV instruction is executed, data are read from Socket communication receive data area at END
processing. Therefore, executing the SP.SOCRCV instruction will increase the scan time.
● If the CPU module receives odd-byte data, invalid data is stored to the high byte of the device where the last received
data is stored.
103
(3) Function
This instruction reads out received data of the connection specified in S1 from the Socket communication receive
data area in the END processing after execution of the SP.SOCRCV instruction.
CPU module
Receive data
D1 +0 length
Socket communication
D1 +1 Receive data receive data area
D1 +2 Receive data Connection
No. specified by S1 External device
SP.SOCRCV Receiving
(Reading receive data)
D1 +n Receive data
The result of the SP.SOCRCV instruction can be checked with the completion device D2 +0 and D2 +1.
• Completion device D2 +0
Turns on in the END processing of the scan after completion of the SP.SOCRCV instruction, and turns off in
the next END processing.
• Completion device D2 +1
The following figure shows the timing of reception processing with the SP.SOCRCV instruction.
Data
Open transmission Data read
processing processing processing
ON
Open completion OFF
signal (SD1282, n) END END END
processing processing processing
Sequence program
ON
Reception status OFF
signal (SD1286, n) SP.SOCRCV instruction execution
SP.SOCRCV
instruction 1 scan
ON
Completion
D2 OFF
device
Abnormal termination
ON
Completion
D2 +1 OFF
device
Data
Data reception
read
ACK processing
(TCP only)
104
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
(Error code: 4002)
• The connection number specified for S1 is other than 1 to 16.
(Error code: 4101)
• The received data size exceeds the size of the receive data storage device.
(Error code: 4101)
• The device numbers specified for S2 , D1 , and D2 exceed the device point range.
(Error code: 4101)
• An invalid device is specified.
(Error code: 4004)
Reading receive
data of Connection
No.1
Normal completion
Error completion
● To avoid receiving large amounts of data, the volume of received data can be limited by setting the receive data size
using the SP.SOCRMODE instruction.
● Consecutively sent data can be consecutively read out by connecting the completion device of the SP.SOCRCV
instruction to the execution command at the normally closed contact.
105
7.4.4 Reading out received data during instruction execution
(S.SOCRCVS)
Command
S.SOCRCVS S.SOCRCVS U0 S D
S - - -
D - - - -
When replacing the Z.BUFRCVS instruction (Ethernet module dedicated instruction), dummy argument can be used in a
Built-in Ethernet port QCPU instruction without rewriting.
106
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
● Receive data size is 2046 bytes by default. To receive data over 2046 bytes, change the receive data size with the
SP.SOCRMODE instruction.
● If the CPU module receives odd-byte data, invalid data is stored to the high byte of the device where the last received
data is stored.
(3) Function
This instruction reads out received data of the connection specified in S from the Socket communication receive
data area.
CPU module
Receive data
D +0 length
Socket communication
D +1 Receive data receive data area
D +2 Receive data Connection
No. specified by S External device
S.SOCRCV Receiving
(Reading receive data)
D +n Receive data
7
The following figure shows the timing of reception processing with the S.SOCRCVS instruction.
Data
Open reception Data read
processing processing processing
ON
Reception status OFF
signal (SD1286, n) S.SOCRCVS instruction
execution
S.SOCRCVS
instruction
Data
read
processing
Data reception
107
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
(Error code: 4002)
• The connection number specified for S is other than 1 to 16.
(Error code: 4101)
• The received data size exceeds the size of the receive data storage device.
(Error code: 4101)
• The device number specified for D exceeds the device point range.
(Error code: 4101)
• An invalid device is specified.
(Error code: 4004)
(5) Precaution
Do not use both this and SP.SOCRCV instructions when reading out receive data of the same connection.
• Program
Reading receive
data of Connection
No.1
● To avoid receiving large amounts of data, the volume of received data can be limited by setting the receive data size
using the SP.SOCRMODE instruction.
● Data reception can be speeded up by placing a receive processing program at the beginning of multiple programs.
108
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
Command
SP.SOCSND SP.SOCSND U0 S1 S2 S3 D
S1 - - -
S2 - *1 *1 - - -
S3 - - - -
*1 (except for *1
D - - -
T, ST, and
C)
7
*1 File registers set for each local device or program cannot be used.
S2 Start number of the device where control data are specified System
Device name
S3 Start number of the device from which send data are stored User
Start number of the device which turns on for one scan upon
D completion of the instruction System Bit
D +1 also turns on when failed.
When replacing the ZP.BUFSND instruction (Ethernet module dedicated instruction), dummy argument can be used in a
Built-in Ethernet port QCPU instruction without rewriting.
109
(2) Control data
Device Item Description Setting range Set by*3
S2 +0 System area - - -
S3 +0 Send data length The length of send data is specified (in bytes). 1 to 10238*4
S3 +1
User
to Send data Send data are specified. -
S3 +n
For TCP, set the send data length within the maximum window size of the target device (receive buffer of TCP). Data whose
size exceeds the maximum window size cannot be sent.
110
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
(3) Function
This instruction sends data set in S1 to the target device of the connection specified by S3 .
CPU module
Send data
S3 +0 length
S3 +1 Send data
S3 +n Send data
The result of the SP.SOCSND instruction can be checked with the completion device, D +0 and D +1.
• Completion device D +0
Turns on in the END processing of the scan after completion of the SP.SOCSND instruction, and turns off in
the next END processing.
• Completion device D +1
Turns on or off according to the result of the SP.SOCSND instruction.
State Description
7
When completed Remains off.
Turns on in the END processing of the scan after completion of the SP.SOCSND instruction, and turns off
When failed
in the next END processing.
The following figure shows the timing of reception processing with the SP.SOCRCV instruction.
ON
Open completion OFF
signal (SD1282, n) END END END
processing processing processing
Sequence program
SP.SOCSND instruction execution
SP.SOCSND
instruction 1 scan
ON
Completion D OFF
device Abnormal termination
ON
Completion D +1 OFF
device Data
transmission
processing *1 Data transmission may continue
even though the completion
transmission
Data
*1
111
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
(Error code: 4002)
• The connection number specified for S1 is other than 1 to 16.
(Error code: 4101)
• The device numbers specified for S2 , S3 , and D exceed the device point range.
(Error code: 4101)
• An invalid device is specified.
(Error code: 4004)
• Program
Sending data to
Connection No.1
Normal completion
Error completion
112
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
Command
SP.SOCCINF SP.SOCCINF U0 S1 S2 D
S1 - - -
S2 - - - -
D - - - -
S2 Start number of the device from which control data are stored
Start number of the device from which connection information System Device name
D
is stored
113
(2) Control data
Device Item Description Setting range Set by*2
S2 +0 System area - - -
1H to 1387H
Host station port
D +3 Port number of the host station is stored. 1392H to FFFEH
number
*3 *4
System
b15 b14 b13 to b10 b9 b8 b7 to b0
D +4 [3] 0 [2] [1] 0
114
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
(3) Function
This instruction reads out connection information specified in S1 .
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
(Error code: 4002)
• The connection number specified for S1 is other than 1 to 16.
(Error code: 4101)
• The device numbers specified for S2 and D exceed the device point range.
(Error code: 4101)
• An invalid device is specified.
(Error code: 4004)
• Program
115
7.4.7 Changing the target of a connection (UDP/IP) (SP.SOCCSET)
Command
SP.SOCCSET SP.SOCCSET U0 S1 S2
S1 - - -
S2 - - - -
S2 Start number of the device from which control data are stored User, System Device name
1H to FFFFFFFFH
S2 +2 Target device IP (FFFFFFFFH:
IP address of the target device is specified.
S2 +3 address Simultaneous
broadcast)
User
1H to FFFFH
Target device (FFFFH:
S2 +4 Port number of the target device is specified.
port number Simultaneous
broadcast)
116
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
(3) Function
This instruction changes the IP address and port number of the target device of which connection is specified in
S1 .
● The target device can be changed without closing the connection by using the SP.SOCCSET instruction.
● The set values take effect at the following SP.SOCCSET instruction execution timing:
• When data exist in the socket communication receive data area: After execution of the SP.SOCRCV or
S.SOCRCVS instruction, only once after execution of the SP.SOCCSET instruction
• When no data exists in the socket communication receive data area: After execution of the SP.SOCCSET
instruction
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
7
(Error code: 4002)
• The connection number specified for S1 is other than 1 to 16.
(Error code: 4101)
• The device number specified for S2 exceeds the device point range.
(Error code: 4101)
• An invalid device is specified.
(5) Precaution
Do not change the target device using the SP.SOCCSET instruction during execution of the SP.SOCSND
instruction.
• Program
Changing setting of
Connection No.1
117
7.4.8 Changing the receive mode of a connection (SP.SOCRMODE)
Command
SP.SOCRMODE SP.SOCRMODE U0 S1 S2
S1 - - -
S2 - - - -
S2 Start number of the device from which control data are stored User, System Device name
118
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
(3) Function
This instruction changes the TCP receive mode and receive data size of the connection specified in S1 . The
mode is changed as specified in S2 +2. (This instruction is invalid for UDP connections.)
SP.SOCRCV or SP.SOCRCV or
Reading receive data S.SOCRCVS S.SOCRCVS
instruction instruction
Socket communication Data stored Data reading Data stored Data reading
receive data area (300 bytes) (200 bytes)
ON
SD1286 OFF
Data reception
(500 bytes) 7
(b) TCP fixed-length receive mode
When data are received, they are stored in the Socket communication receive data area, and SD1286
(Receive state signal) turns on. However, if the size of the data does not reach the specified receive data size,
SD1286 does not turn on.
Data reception is repeated and once the data size reaches to the specified size, SD1286 turns on.
SP.SOCRCV or
Reading receive data S.SOCRCVS
instruction
119
● Effective use of devices
Devices can be effectively used by setting the receive data size to less than 1024 words while the default size of the
receive data storing devices for the SP.SOCRCV and S.SOCRCVS instructions is 1024 words.
● Prevention of receive data fragmentation
Data from the connected device may be fragmented depending on the line type. To prevent this, the receive data size can
be specified in the TCP fixed-length receive mode.
● Prevention of receive data binding
Separately sent data may be combined depending on the interfacing device due to a delay in receive processing of the
program.
To prevent this, the receive data size can be specified in the TCP fixed-length receive mode.
Remark
The set values will take effect at the following timing of the SP.SOCRMODE instruction execution.
• Before opening: Values take effect after opening a connection.
• When there are data in the Socket communication receive data area:
Values take effect after execution of the SP.SOCRCV or S.SOCRCVS instruction once after the S.SOCRMODE
instruction.
• When there is no data in the Socket communication receive data area:
Values take effect after the SP.SOCRMODE instruction is executed.
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
(Error code: 4002)
• The connection number specified for S1 is other than 1 to 16.
(Error code: 4101)
• The device number specified for S2 exceeds the device point range.
(Error code: 4101)
• Invalid device is specified.
(Error code: 4004)
Remark
Even when the Receive state signal is not on in the TCP fixed-length receive mode, the data received at the point can be
read out with the SP.SOCRDATA instruction. This allows you to check whether the data sent from the connected device is
adequate in size.
120
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
• Program
121
7.4.9 Socket communication receive data read (S(P).SOCRDATA)
Command
S.SOCRDATA S.SOCRDATA U0 S1 S2 D n
Command
SP.SOCRDATA SP.SOCRDATA U0 S1 S2 D n
S1 - - -
S2 - - - -
D - - - -
n - -
S2 Start number of the device from which control data are stored
User Device name
D Start number of the device where read data are stored
122
CHAPTER 7 SOCKET COMMUNICATION FUNCTION
(3) Function
This instruction reads out the data of the amount specified for n from the Socket communication receive data
area of which connection is specified in S1 , and stores them in the device specified in D or higher. No processing
is performed when the number of read data (n) is 0.
● Data of the receive data length can be read out by setting the number of read data to one word.
This allows change of the device storing receive data, upon execution of the SP.SOCRCV or S.SOCRCVS instruction.
● In the following order, based on the data currently received, the size of the data received the next time can be specified.
1. Check the data currently received using the S(P).SOCRDATA instruction.
2. Specify the size of the data to be received the next time using the SP.SOCRMODE instruction.
3. Read out the data currently received using the SP.SOCRCV or S.SOCRCVS instruction.
Remark
● Even if the S(P).SOCRDATA instruction is executed, the next receive data will not be stored in the Socket communication
receive data area because the area is not cleared and the Receive state signal does not change.
● To update the receive data, read out the data using the SP.SOCRCV or S.SOCRCVS instruction.
7
(4) Error
A detection of an operation error turns on the Error flag (SM0) and a corresponding error code is stored in SD0
when:
• The instruction is executed in the QnUDE(H)CPU with a serial number (first five digits) of "11011" or earlier
or a CPU module other than the Built-in Ethernet port QCPU.
123
(5) Program example
When M4000 is turned on, the receive data length of connection No.1 is read out.
• Devices used
Device number Application
SD1282 Open completion signal
SD1286 Receive state signal
D400 S.SOCRDATA instruction control data
D4000 Storage location where data are read out
K1 Number of read data (one word)
• Program
Reading receive data
length of Connection
No.1
124
CHAPTER 8 TIME SETTING FUNCTION (SNTP CLIENT)
The CPU module collects time information from a time information server on LAN, and automatically sets its own time.
With this time setting function, the CPU module queries the server for time information at the specified timing, and can
set the time information sent from the server as its own clock data.
Time query
LAN
CPU module
Setting server time in the CPU module
8
Ethernet
Personal computer
● Confirm the connection of the hub or the interfacing device in advance when setting time at the timing of CPU module
power-on or reset.
● The time setting results can be checked with the special register (SD1270 to SD1275).
● During execution of the time setting function, other time setting operations are ignored.
Remark
Access through routers is also available. When configuring the settings for it, set the subnet mask pattern and default router
IP address. ( Page 30, Section 3.4)
125
8.1 Setting Method
Configure the time settings in the Built-in Ethernet port tab of the PLC parameter window.
button
Execution Interval*2 Select this when executing the time setting function at fixed time intervals. 1 to 1440 (min.)
Select this when executing the time setting function at a specified time (in
Execution Time*2 00:00 to 23:30
increments of 30 minutes).
126
CHAPTER 8 TIME SETTING FUNCTION (SNTP CLIENT)
8.2 Precautions
8.2 Precautions
127
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
The CPU module supports the server function for FTP (File Transfer Protocol) which is a protocol designed for file
transfer to or from the connected device.
The device with the FTP client function can directly access any files located in the CPU module.
Parameters
Programs Storage files
Data
Read
Write
Ethernet
The following operations can be performed between the connected device with the FTP client function and the CPU
module.
In a multiple CPU system, only the CPU module connected with an Ethernet cable can transfer files.
Remark
Access through routers is also available. When configuring the settings for it, set the subnet mask and default router IP
address. ( Page 30, Section 3.4 )
128
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
3.
1.
2.
129
3. Configure the FTP settings.
Item Description
FTP Select "Used".
Set a log-in name used for file transfer (login) request from an external device.
Password
[Default value]
• QnUDVCPU: "MELSEC"
• QnUDE(H)CPU: "QNUDECPU"
Set a time for monitoring command input performed by the CPU module. When no command is input within the set
Command Input
period of time, the FTP connection is disconnected. (Setting range : 1 to 32767 ( × 500ms))
Monitoring Timer
Set a time value larger than the time required for file transfer.
130
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
Start
Is the FTP NO
communication port subject
to remote password
check?
YES
(quote password-unlock
Unlock the remote password. "remote password" <ret>)
No file conversion is notified. (binary <ret>) No file conversion is notified. (binary <ret>)
Disconnect from
the CPU module. (bye <ret>)
Check the file list. (dir <ret> Check the file list. (dir <ret> or
or ls <ret>) ls <ret>)
End
NO Is File NO
password 32 set for the Can it be overwritten?
target file?
YES YES
(quote passwd-rd
Enter a file password. NO Is File
"read password" <ret>) password 32 set for the
target file?
Read the file. (get "file name" <ret>) YES
(quote passwd-wr
Enter a file password.
"write password" <ret>)
(delete "file name" <ret> or
Delete or rename the file. rename "current file name"
"new file name" <ret>)
131
(b) For the QnUDE(H)CPU
Start
NO Is the FTP
communication port subject
to remote password
check?
YES
132
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
Ex. Start up the FTP from the MS-DOS prompt of Microsoft® Windows®.
1.
2.
3.
4.
When terminating the operation, lock the unlocked remote password using the following command.
(quote password-lock <ret>)
If the FTP communication port is specified as a remote password check target, any other commands cannot be used until
the remote password is unlocked.
133
9.2 Files Transferable Using FTP
The following table lists the files that can be transferred using the file transfer function.
:Available, × :N/A
Program SD
Standard Standard SRAM Flash
memory ATA card memory File name or
File type RAM ROM*4 card card
*2*3 card*4 extension
Drive 0 Drive 3 Drive 4 Drive 1 Drive 2
Parameter × × × × × × PARAM.QPA
Program × × × × × × .QPG
Source information × × × × × × × *5
*1 The SP.FWRITE or SP.FREAD instruction in the program will write or read the file respectively.
For details, refer to the following manual.
MELSEC-Q/L Programming Manual (Common Instruction)
*2 Files can be written to the program memory only when the CPU module is in the STOP state.
*3 Write destination is the program cache memory.
The user should back up files using the "pm-write" command as required. ( Page 138, Section 9.4.1)
134
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
135
9.3 Files That Can Be Deleted Using FTP
The following table lists the files that can be deleted using the file transfer function.
: Deletable, : Not deletable only in RUN state, ×: Not deletable, -: Not writable
Program SD
Standard Standard SRAM Flash
memory ATA card memory File name or
File type *2*3
RAM ROM*4 card card
card*4 extension
Drive 0 Drive 3 Drive 4 Drive 1 Drive 2
Parameter *6 PARAM.QPA
Program *6 .QPG
Source information *5
LOGCOM.QLG,
Data logging setting file - - - - - LOG01.QLG to
LOG10.QLG
136
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
*1 The SP.FWRITE or SP.FREAD instruction in the program will write or read the file respectively.
For details, refer to the following manual.
MELSEC-Q/L Programming Manual (Common Instruction)
9
*2 Files can be written to the program memory only when the CPU module is in the STOP state.
*3 Write destination is the program cache memory.
The user should back up files using the "pm-write" command as required. ( Page 138, Section 9.4.1)
*4 The following number of files, which can be written using FTP, can be stored.
[Maximum number of files storable on the drive - 1]
*5 Except for the High-speed Universal model QCPU, file names are SRCINF1M.CAB and SRCINF2M.CAB for Simple
projects (with labels), and SRCINF1I.CAB and SRCINF2I.CAB for Structured projects.
For the High-speed Universal model QCPU, file names are SRCINF1M.C32 and SRCINF2M.C32 for Simple projects
(with labels), and SRCINF1I.C32 and SRCINF2I.C32 for Structured projects.
*6 For the QnUDE(H)CPU, this file cannot be stored.
*7 The file name stored differs depending on the module connected.
When the online change settings is disabled in the "Built-in Ethernet Port Setting" tab of PLC Parameter, deleting a file in
RUN state will cause an error.
137
9.4 FTP Commands
: Available, × : N/A
CPU module state Remote password
RUN
Command Function Write Write Unlocked Locked
STOP
enabled disabled *2 *2
*1 *1
*6
delete Deletes a file in the CPU module.*4 × ×
dir *4 ×
Displays file information of the CPU module.
*6 *4 ×
get Reads a file from the CPU module.
ls *4 ×
Displays file names of the files stored in the CPU module.
*6 *4 × ×
mdelete Deletes file(s) stored in the CPU module.
user Inputs the user name and password of the CPU module.
*1 Whether the online change settings is enabled or not is indicated in the "Built-in Ethernet Port" tab in the PLC Parameter
window.
*2 These indicate whether the remote password can be used or not when the FTP communication port is specified as a
remote password check target in the remote password setting. For remote passwords, refer to: Page 152,
CHAPTER 10
*3 On the next page, subcommands available with the "quote" command are shown.
*4 Each of these commands can include a folder name in the file specification.
*5 This command is set automatically in the CPU module. Therefore, a file transfer is coded in binary regardless of the
"Communication Data Code" of the "Built-in Ethernet Port Setting" in PLC Parameter.
*6 The command cannot be used for access control target files in the file access control by security key.
138
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
The following table lists the subcommands available with the command, "quote".
: Available, × : N/A 9
CPU module state Remote password
RUN
Subcommand Function
STOP Write Write Unlocked Locked
enabled disabled
*1 Even if the subcommand is executed, the remote password remains locked with no error occurred.
*2 This command can include a folder name in the file specification.
*3 The subcommand cannot be used for the QnUDVCPU.
*4 The subcommand cannot be used for the QnUDE(H)CPU.
*5 The subcommand cannot be used for access control target files in the file access control by security key.
139
9.4.2 How to specify an FTP command
This section explains how to specify a file with an FTP command on the FTP client (connected device), which is
supported by the CPU module.
The part enclosed with brackets in the specification format can be omitted.
140
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
Note that some FTP commands may not function as described in this manual, depending on the FTP application used on the
FTP client side.
Check the functions and operation methods, referring to the manual(s) for the FTP client.
●binary
[Function] Notifies the FTP server of file transfer without conversion.
Neither return codes nor kanji codes are converted.
This command is set automatically in the CPU module.
[Specification format] binary (abbreviated to "bin")
●bye
[Function] Disconnects the line to the FTP server, and terminates the FTP session.
[Specification format] bye
[Identical command] quit
●close
●delete
[Function] Deletes a file stored in the CPU module.
[Specification format] delete "file path name"
[Example] When deleting a file stored in an SD memory card:
delete 2:\MAINSEQ1.USR
[Similar command] mdelete
●dir
[Function] Displays the names, creation dates, and sizes of the files stored in the CPU module.
[Specification format] dir [drive name:\]
[Example] When displaying the detailed information of the files stored in an SD memory card:
dir 2:\
[Similar command] ls
141
●get
[Function] Reads a file from the CPU module.
[Specification format] get "source file path name" [destination file path name]
[Example 1] When reading a file stored in the standard RAM and saving it under the same file name:
get 3:\MAINSEQ1.QDR
[Example 2] When reading a file stored in the standard RAM and saving it under a different file name:
get 3:\SEQ1BAK.QDR \SEQ\SEQ10LD.QDR
[Note] • When no destination file path name (FTP client side) is specified, the file is saved in the
FTP client using the same source file name (CPU module side).
• The transfer destination is on the current directory where FTP is started up and
connected to the server.
●ls
[Function] Displays the names of the files stored in the CPU module.
[Specification format] Is [drive name:\]
[Example] When displaying the names of the files stored in an SD memory card:
ls 2:\
[Similar command] dir
●mdelete
[Function] Deletes a file stored in the CPU module.
To delete multiple files, specify the file name and extension within the file path name using
a wild card character (* or ?).
[Specification format] mdelete "file path name" (abbreviated to "mdel")
[Example] When deleting all the files whose extensions are "QPG" from the program memory:
mdelete 0:\*.QPG
[Similar command] delete
●mdir
[Function] Saves detailed information (file names, creation dates, and sizes) of the files stored in the
CPU module as log data into a file on the FTP client side.
[Specification format] mdir "source drive name" :\"destination file path name"
[Example] When saving detailed information of the files stored in an SD memory card into the
S990901.LOG file:
mdir 2:\ S990901.LOG
[Note] • Type "\" immediately after the source drive name.
• Specify a source drive name when specifying a destination file path name (FTP client
side).
• Without a destination file path name, the file is saved using a file name determined by
the FTP application on the FTP client side.
• The transfer destination is on the current directory where FTP is started up and
connected to the server.
[Similar command] mls
142
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
●mget
[Function] Reads out a file from the CPU module. 9
To read out multiple files, specify the file name and extension within the file path name
using a wild card (* and/or ?).
When reading multiple files, reception is checked for each file transfer.
[Specification format] mget "file path name"
[Example] When reading all the files whose extensions are "USR" among the files stored in an SD
memory card:
mget 2:\*.USR
[Note] The file read out is saved on the FTP client side under the same file name.
The storage destination is on the current directory where FTP is started up and connected
to the server.
●mls
[Function] Stores the names of the files in the CPU module as log data into a file on the FTP client
side.
[Specification format] mls "source drive name":\"destination file path name"
[Example] When storing the names of the files in an SD memory card into the S990901F.LOG file:
mls 2:\ S990901F.LOG
[Note] • Type "\" immediately after the source drive name.
• Specify a source drive name when specifying a destination file path name (FTP client
side).
• Without a destination file path name, the file is stored using a file name determined by
the FTP application on the FTP client side.
• The transfer destination is on the current directory where FTP is started up and
connected to the server.
[Similar command] mdir
●open
[Function] Connects to the FTP server by specifying the host name or IP address and port number of
the FTP server.
[Specification format] open "host name" [port number]
open "IP address" [port number]
• Host name: Host name set in the Microsoft® Windows® hosts file
• IP address: CPU module IP address
• Port number: Port number to be used
[Example 1] When connecting to the FTP server by specifying a host name:
open HOST
[Example 2] When connecting to the FTP server by specifying an IP address:
open 192.0.1.254
[Note] Connection is also possible by specifying an IP address at startup of FTP.
143
●put
[Function] Writes a file to the CPU module.
[Specification format] put "source file path name" [destination file path name]
[Example 1] When writing the MAINSEQ1.QDR file to the standard RAM with the same file name:
put MAINSEQ1.QDR 3:\MAINSEQ1.QDR
[Example 2] When writing the MAINSEQ.QDR file to the standard RAM with a different file name:
put MAINSEQ.QDR 3:\MAINSEQ1.QDR
[Note] • If no directory is specified for the source file path name (FTP client side), the file on the
current directory where FTP is started up and connected to the server is written.
• When no destination file path name (FTP server side) is specified, the file is saved in the
memory in which current parameter files are stored.
●pwd
[Function] Displays the current directory name of the CPU module.
[Specification format] pwd
[Note] "\" is displayed as the execution result of the "pwd" command.
●quit
[Function] Disconnects the line from the FTP server and terminates the FTP session.
[Specification format] quit
[Identical command] bye
●quote
[Function] Sends an FTP server subcommand (a subcommand dedicated to CPU modules).
[Specification format] quote
[Example] quote password-lock
[Note] Only CPU module dedicated subcommands can be specified. Refer to (2).
●rename
[Function] Renames a CPU module file.
[Specification format] rename "old file path name" "new file path name" (abbreviated to "ren")
[Example] When renaming a file stored in the standard RAM:
rename 3:\MAINSEQ1.QDR 3:\SEQ1OLD.QDR
[Note] Either of the following response codes is displayed upon completion.
350 Need more info.
250 Rename successful.
●user
[Function] Inputs the user name and password of the connected FTP server.
[Specification format] user "user name" [FTP password]
• User name: Login name set with a CPU module parameter
• FTP password: FTP password set with a CPU module parameter
[Example 1] When specifying a user name:
user CPU
[Example 2] When specifying a user name and password:
user CPU CPU
144
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
●change
[Function] Displays or changes the attribute of a file stored in the CPU module.
[Specification format 1] When displaying the file attribute:
quote change "file path name"
Either of the following is displayed as an execution result upon completion.
• When the specified file is read-only: ----- R
• When the specified file is writable and readable: ----- W
[Specification format 2] When changing the file attribute:
quote change "file path name" "attribute"
Use either of the following to specify the attribute.
• To change it to a read-only file: r
• To change it to a writable and readable file: w
[Example 1] When displaying the attribute of the file stored in the standard RAM:
quote change 3:\MAINSEQ1.QDR
[Example 2] When changing the attribute of the file stored in the standard RAM:
quote change 3:\MAINSEQ1.QDR r
●keyword-set
[Function] Sets a file password registered in the file transfer target file into the Built-in Ethernet port
QCPU.*1
Or, displays/clears the password set for FTP settings in parameter.
[Specification format] quote keyword-set [File password]
• File password :Specify the file password registered in the Built-in Ethernet port QCPU file.
To clear the set file password, specify "****".
*1 : This command is used only when a file password is registered in the file transfer target file. The QnUDE(H)CPU checks
a file password when a specified file is accessed.
145
●password-unlock
[Function] Specify the remote password set in the CPU module to unlock the password.*2
[Specification format] quote password-unlock [remote password]
• Remote password: Specify the remote password set with a parameter for the CPU
module.
The following is displayed as an execution result upon completion.
200 Command Okey
The following is displayed if the entered remote password does not match the setting.
556 Password Error
The following is displayed if another command is requested before unlock processing of
the remote password.
555 Password Locked
[Example] When specifying a remote password (1234):
quote password-unlock 1234
[Note] • The remote password is locked when you log in if the remote password check is enabled
for the FTP communication port.
• By executing this command before various FTP operations, the password is unlocked,
allowing file operations of the CPU module.
• Unlock processing will be completed if the remote password is unlocked when the
remote password check is disabled for the FTP communication port.
*2 Use this command only when the FTP communication port is specified as a remote password check target.
●password-lock
*3 Use this command only when the FTP communication port is specified as a remote password check target.
146
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
●run
9
[Function] Changes the CPU module state to RUN. (Remote RUN.)
At this time, device memory clear can be specified.
[Specification format] quote run [mode [clear mode]]
• Mode: Specify whether to force remote RUN or not.
0: Normal RUN (default)
1: Forced RUN
• Clear mode:
Specify the CPU module device memory clear (initialization) processing performed when
the operation starts by executing remote RUN.
0 : Do not clear device (default)
1 : Clear other than the latch range
2 : Clear all including the latch range
The following message is displayed as an execution result upon completion.
200 Command successful
[Example 1] When executing remote RUN, with "Normal RUN" and "Do not clear device" specified:
quote run
[Example 2] When executing remote RUN, with "Forced RUN" and "Do not clear device" specified:
quote run 1
[Example 3] When executing remote RUN, with "Forced RUN" and "Clear other than the latch range":
specified
quote run 1 1
[Note] • Forced RUN should be used only to force remote RUN to the CPU module from another
device when a device that executed remote STOP to the CPU module have a problem
and cannot perform remote RUN.
With Normal RUN, the CPU module state cannot be changed from STOP/PAUSE to RUN
if the previous state is set by a different device.
• Specify the clear mode at the start of an operation, according to the system arrangement.
After completing the specified clear processing, the CPU module runs in accordance with
●status
[Function] Displays information of the CPU module operation.
This command is used to check the information on the CPU module operation before
transferring a file to the CPU module.
[Specification format] quote status
One of the following is displayed as an execution result upon completion.
• When the CPU module is in RUN state: "RUN"
• When the CPU module is in STOP state: "STOP"
• When the CPU module is in PAUSE state: "PAUSE"
●stop
[Function] Changes the CPU module state to STOP (remote STOP).
[Specification format] quote stop
The following message is displayed as an execution result upon completion.
200 Command successful
[Note] Before writing data to the program memory, set the CPU module into the STOP state using
this command.
147
●pm-write
[Function] Transfers program cache memory to the program memory.
[Specification format] quote pm-write
The following message is displayed as an execution result upon completion.
200 Command successful
[Note] Before writing data, set the CPU module to STOP.
●passwd-rd
[Function] Set the read password (file password 32) that has been registered in a target file to transfer
in the CPU module.
Displays and clears the read password that has been set in the CPU module.
Use this command only when a read password has been registered in the target file to
transfer.
The CPU module checks a password when a specified file is accessed.
[Specification format 1] When setting a read password in the CPU module
quote passwd-rd "read password"
The following message is displayed as an execution result at the normal end.
• 200 Command successful
[Specification format 2] When displaying the read password that has been set in the CPU module
quote passwd-rd
Any of the following is displayed as an execution result at the normal end.
• When the command is executed with a read password set: 200 Read-password is "read
password."
• When the command is executed with no read passwords set: 200 Read-password is not
set.
[Specification format 3] When clearing the read password that has been set in the CPU module
quote passwd-rd c or quote passwd-rd C
The following message is displayed as an execution result at the normal end.
• 200 Command successful
[Note] • A read password can be set for the CPU module.
When the target file to transfer is changed, re-set a read password for a new target file if
the read password has been registered in the new file.
• Re-set a read password before accessing the target file to transfer because the
password that has been set using the command is initialized or cleared upon login to the
CPU module.
148
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
●passwd-wr
9
[Function] Sets the write password (file password 32) that has been registered in a target file to
transfer in the CPU module.
Displays and clears the write password that has been set in the CPU module.
Use this command only when a write password has been registered in the target file to
transfer.
The CPU module checks a password when a specified file is accessed.
[Specification format 1] When setting a write password in the CPU module
quote passwd-wr "write password"
The following message is displayed as an execution result at the normal end.
• 200 Command successful
[Specification format 2] When displaying the write password that has been set in the CPU module
quote passwd-wr
Any of the following messages is displayed as an execution result at the normal end.
• When the command is executed with a write password set: 200 Write-password is "write
password."
• When the command is executed with no write passwords set: 200 Write-password is not
set.
[Specification format 3] When clearing the write password that has been set in the CPU module
quote passwd-wr c or quote passwd-wr C
The following message is displayed as an execution result at the normal end.
• 200 Command successful
[Note] • A write password can be set for the CPU module.
When the target file to transfer is changed, re-set a write password for a new target file if
the write password has been registered in the new file.
• Re-set a write password before accessing the target file to transfer because the
password that has been set using the command is initialized or cleared upon login to the
CPU module.
149
9.5 Precautions
150
CHAPTER 9 FILE TRANSFER FUNCTION (FTP)
9.5 Precautions
1. Read out the parameters from the CPU module to the programming tool.
2. In the FTP Parameter Setting window, click the "Default" button to return all the FTP parameters to
default values.
button
151
CHAPTER 10 REMOTE PASSWORD
A remote password is checked when a connection is requested for the following.
• Communication using a programming tool
• Communication using MC protocol
• File transfer (FTP)
The remote password function is one of the preventive methods against unauthorized access (e.g. destruction of data and
programs) from external devices.
However, this function cannot completely prevent unauthorized access.
Other preventive measures should be taken at users’ discretion if security of the programmable controller system needs to
be maintained against unauthorized access from external devices. We cannot be held responsibility for any problems
caused by unauthorized access.
152
CHAPTER 10 REMOTE PASSWORD
Communication is performed in the order described below when a remote password is set for the CPU module.
10
(1) Allowing access (unlock processing)
On a communication device such as a personal computer, unlock the remote password set for the CPU module.
If it is not unlocked, an error will occur on the connected device because the CPU module will prohibit any
access.
Enable/
153
10.2 Remote Password Setting
Password Select a CPU model to enable the remote password for the built-in
Ethernet Built-in
Active Model Name Ethernet port of the CPU module.
CPU
Module Only one CPU model is selectable.
Setting Condition Click this to display the "Remote Password Detail Setting" window. -
Select one of them when the remote password is to be enabled for
User
the built-in Ethernet port.
Connection Connection 1 to 16
(Setting of an unused connection or MELSOFT connection is
No.*5
ignored.)
154
CHAPTER 10 REMOTE PASSWORD
*1 One-byte alphanumeric and special characters can be used for remote password entry.
(Case-sensitive)
*2 To enable the remote password for the port for which the open system is set to "MELSOFT Connection" in PLC
Parameter, select the following checkbox.
When Protocol is set to "TCP" "MELSOFT Transmission Port (TCP/IP)".
When Protocol is set to "UDP" "MELSOFT Transmission Port (UDP/IP)".
When MELSOFT connection extended setting is used "MELSOFT Transmission Port (UDP/IP)".
10
*3 When connecting the CPU module and a GOT via Ethernet, do not select "MELSOFT Transmission Port (UDP/IP)".
*4 Select this checkbox to enable the remote password for the CPU module that is directly connected to the programming
tool using the built-in Ethernet port. ( Page 48, CHAPTER 4)
*5 User connection is for users for communications such as MC protocol communications and communications using fixed
buffers.
*6 System connection is used by the system for communications such as FTP communications and MELSOFT
communications (TCP/IP, UDP/IP).
155
10.3 Precautions
1)
2) Ethernet
3)
Enable/ 4)
Disable
Remote password
check
No remote password
parameter
Remote password
parameter
No.1 No.2
156
CHAPTER 10 REMOTE PASSWORD
(4) Operation performed when CPU modules are set as relay stations
The following shows the accessibility when CPU modules are set as relay stations in the MELSOFT connection
extended setting.
10
Programming tool
Ethernet Ethernet
While a remote password is set for all CPU modules, the remote password set for CPU module [1] can be
unlocked so that the relay station CPU modules can be accessed without password checking.
10.3 Precautions
157
10.4 Detection of Unauthorized Access and Actions
When the remote password mismatch count reaches the upper limit in unlock processing, "REMOTE PASS FAIL"
(error code: 2700) is detected.
If this occurs, unauthorized access from the outside of the system can be considered as a cause of the error.
1. Monitor the Remote password count (SD979 to SD999) and identify the connection of which
remote mismatch count has reached the upper limit in unlock processing.
2. Stop the communication by disabling the connection as shown below.
• Select the connection in the "Ethernet diagnostics" window, and force it to be deactivated.
( GX Works2 Version 1 Operating Manual (Common))
• Turn on the force deactivation flag of the connection in the special register (SD1276, SD1277).
If the error is detected due to frequent incorrect typing by authorized users, prevent this by the following operations.
• Enable "Clear Mismatch Count when Remote Password Matches" in the "Remote Password Detail Setting"
window.
• Clear the accumulated count of remote password mismatches using the special relay (SM1273).
158
CHAPTER 11 IP ADDRESS CHANGE FUNCTION
The IP address of a built-in Ethernet port can be changed without changing the built-in Ethernet port settings of PLC
parameters, by storing the values in special relays and special registers.
11
2) Store the IP address of the special register (SD)
to the IP address storage area (flash ROM) by
turning the special relay (SM) on.
1) Store the IP address in the special IP address storage area
register (SD) by the device write Special register (SD) (flash ROM)
operation.
SD1292
IP address IP address
SD1293
GOT 3) Power off and 4) Operate with the IP address stored in the
then off or reset IP address storage area (flash ROM).
the CPU module.
This function can also be used by changing values for special relay and special register from GOT. For details of the special
relay and special register used for this function, refer to the lists of the special relay and special register in the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
Note 11.1
To use the IP address change function for the QnUDE(H)CPU, check the version of the CPU module. ( Page 190,
Appendix 3)
159
11.1 IP Address of the Built-in Ethernet Port
For IP address of the built-in Ethernet port, a value of the built-in Ethernet port setting of the PLC Parameter is set at
the initial processing of the CPU module. When this function is used, the value stored in the IP address storage area
(flash ROM) will be set to the IP address of the built-in Ethernet port which is set during the initial processing of the
CPU module, instead of the value set in the parameter.
Parameter file
Built-in Ethernet port
Built-in Ethernet port setting
IP address 192.168.3.39 IP address 192.168.3.39
Subnet mask pattern 255.255.255.0 Subnet mask pattern 255.255.255.0
Default router IP address 192.168.3.254 Default router IP address 192.168.3.254
IP address 192.168.3.40
The IP address in the IP address
storage area (flash ROM) is set. Subnet mask pattern 255.255.255.0
Default router IP address 192.168.3.254
(1) Write and clear operation to the IP address storage area (flash ROM)
Write a value of IP address to the IP address storage area (flash ROM). The special relay and special register are
used to perform the write and clear operations.
(2) Execution timing of writing to and clearing the IP address storage area (flash
ROM)
Write and clear processing are executed in the END processing. Therefore, the scan time is increased during
execution.
160
CHAPTER 11 IP ADDRESS CHANGE FUNCTION
This operation can be performed by storing the IP address to be changed in SD1292 to SD1297 and turning off and on
SM1292 (IP address storage area write request). 11
(1) Operating procedure
The following shows the write operation flow.
Store the value to be changed in (Example) When storing the IP address (192.168.3.40 (C0A80328H)) to
SD1292 to SD1297 SD1292 and SD1293
• IP address
1) Convert the IP address to be changed from decimal (192.168.3.40) to
• Subnet mask pattern
hexadecimal (C0A80328H).
• Default router IP address
2) Store the IP address converted to hexadecimal in the SD.
Execute writing to the IP address storage * Store the subnet mask pattern and default router IP address in the same way.
area (flash ROM).
Setting the IP address of the built-in Ethernet port Setting the IP address of the built-in Ethernet port
Set values in the IP address storage area Set values in the built-in Ethernet port on the
(flash ROM) to the IP address of the built-in PLC parameter to the IP address of the built-in
Ethernet port Ethernet port
• IP address • IP address
• Subnet mask pattern • Subnet mask pattern
• Default router IP address • Default router IP address
161
(2) Operations of special relay and special register
The following shows the operations of special relay and special register during the operation of writing to the IP
address storage area (flash ROM).
(a) Operations of special relay and special register during the operation of writing to
the IP address storage area (flash ROM)
Write request ON
(SM1292) OFF
(b) Operations of special relay and special register when the operation of writing to the
IP address storage area (flash ROM) failed
Write request ON
(SM1292) OFF
(3) Cause of failure to write to the IP address storage area (flash ROM)
If the processing of writing to the IP address storage area (flash ROM) is not completed, the error cause is stored
in SD1298 (IP address storage area write error factor).
162
CHAPTER 11 IP ADDRESS CHANGE FUNCTION
D108 to D111*1 Default router IP address to be changed M102 Abnormal write completion indication
SD1292 to SD1297 IP address setting SD1298 IP address storage area write error factor
SM1292 IP address storage area write request D100 Write error factor display
*1 Set as follows.
Example When setting the IP address 192.168.3.40 in D100 to D103
D100 40
D101 3
D102 168
D103 192
Write start
Write complete
163
11.2.2 Clear operation
This operation can be performed by turning off and on SM1295 (IP address storage area clear request).
164
CHAPTER 11 IP ADDRESS CHANGE FUNCTION
(a) Operations of special relay and special register during the operation of clearing the
IP address storage area (flash ROM)
11
Clear start Clear complete
END END END END
processing processing processing processing
Clear request ON
(SM1295) OFF
(b) Operations of special relay and special register when the operation of clearing the
IP address storage area (flash ROM) failed
Clear request ON
(SM1295) OFF
(3) Cause of failure to clear the IP address storage area (flash ROM)
If the processing of clearing the IP address storage area (flash ROM) is not completed, the error cause is stored
in SD1299 (IP address storage area clear error factor).
165
(4) Program example
The following shows a program example of clearing the IP address storage area (flash ROM).
Clear start
Clear complete
166
CHAPTER 11 IP ADDRESS CHANGE FUNCTION
*1 Stored as follows.
Example When IP address is 192.168.3.39 (C0A80327H)
11.4 Precautions
167
(4) Functions that cannot be performed during write processing and clear
processing
The following functions cannot be executed during the write or clear processing to the IP address storage area.
Do not execute the functions before the processing is completed. Doing so may cause an error.
If operation of writing to or clearing the IP address storage area (flash ROM) is executed during the execution of
the following functions, the write or clear operation is processed as an error.
• Online Program Change
• Export to ROM format
• Write to PLC (flash ROM)
• CPU module data backup/restoration function
168
CHAPTER 12 IP PACKET TRANSFER FUNCTION
Communications can be performed with a device which supports the following IP addresses, which have been
specified via a CC-Link IE Controller Network module or CC-Link IE Field Network module, using a protocol such as
the FTP or HTTP via a built-in Ethernet port from an Ethernet device such as a personal computer.
• External devices on CC-Link IE Controller Network or CC-Link IE Field Network
• External devices on the Ethernet network, which are connected through the built-in Ethernet portsNote 12.1
12
Ethernet device (source)
IP packet transfer
Network No.2
CC-Link IE Field Network
IP packet transfer
Network No.3
CC-Link IE
Field Network
IP packet transfer
Check the versions of the CPU module and GX Works2 when using the IP packet transfer function for the
QnUDE(H)CPU. ( Page 190, Appendix 3)
169
(1) How to use
For the settings of IP packet transfer function or how to use the function, refer to the following.
Manual for the CC-link IE Controller Network module used
Manual for the CC-link IE Field Network module used
(2) Precautions
• The data that are communicated using the IP packet transfer function are communicated separately by the
following processing.
• Service processing by a sequence scan of a CPU module
• Link scan on CC-Link IE Controller Network
• Link scan on CC-Link IE Field Network
The above processing causes communication speeds to be slower than Ethernet lines. Manuals for the CC-
Link IE Controller Network module or CC-Link IE Field Network module describe targeted communication
speeds when the IP packet transfer function is used.
• Broadcast communication and multicast communication cannot be performed with the IP packet transfer
function. Perform unicast communication (communication with one request destination specified).
• If the application time-out of the request source device occurs due to a heavy communication load on the
path that an IP packet takes, measure the response time using the ping command from the request source
device and adjust the application timeout time.
• Data size must be within 1460 bytes when the ping command is used.
• UDP provides less reliable data communications compared with TCP and thus data may be lost or arrive out
of order. Use TCP communications if a problem occurs with the UDP communications.
170
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
Dedicated instructions allow the CPU module on the host station to read/write device data from/to the CPU module on
another station.Note 13.1
Programming
13
Ethernet
Device Device
D50 D500
This section describes the instructions associated with reading/writing device data from/to the CPU module on another
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
station by specifying an IP address.
The SP.READ/SP.WRITE instructions cannot be used in an interrupt program or fixed scan execution type program.
Reading/writing device data from/to the CPU module on another station by specifying an IP address is available with
QnUDVCPU only.
Before reading/writing device data from/to the CPU module on another station by specifying an IP address is used, check
the versions of the CPU modules (i.e., the CPU modules of the host and other stations) and the versions of the
programming tools. ( Page 190, Appendix 3)
171
(2) Applicable devices
The following table lists the devices whose data can be read from and written to a target CPU module using the
SP.READ/SP.WRITE instructions:
Category Type Device name Requirements for configuration
• The digit specification range must be 16
bits.
Bit device X, Y, M, L, B, F, SB
Internal user device • The bit device number must be a multiple
of 16 (10H).
Word device SD -
Program
Program
D0 D0
Data register
D9999
Data register Access is possible.
D19999
172
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
(a) Channels
A channel is an area in the CPU module that contains the data handled by the SP.READ/SP.WRITE
instructions. Using multiple channels allows the CPU module on the host station to access the CPU modules of
multiple other stations simultaneously or read/write data at the same time from/to the same CPU module on
another station. 13
(b) Maximum available number of channels
The system provides eight channels that can be used along with the SP.READ/SP.WRITE instructions. Using
these eight channels allows the host station to execute eight SP.READ/SP.WRITE instructions simultaneously.
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
SP.WRITE Channel 2 CPU module 2
on another station
on another station
173
13.1.1 Reading device data (SP.READ)
Command S2
S1 D1 D2
SP.READ SP.READ U0 or
" S2 "
S1 - *1 *1 *1 - - -
S2 - *1*2 *1 *1 - *3 -
D1 - *1 *1 *1 - - -
D2 *1 *1 *1 - - - -
*1 Local devices and the file registers set for individual programs cannot be used.
*2 Word devices T, C, D, W, ST, SD, and SW can be specified.
*3 For information on string data specified with S2 , refer to Page 172, Section 13.1 (2).
S1 Start device that contains control data. User, system Device name
When specifying the start device by the device specification method, ensure that the CPU module device on another station
from which to read data is within the range of devices available to the CPU module on the host station.
(The start device S2 of the CPU module on another station from which to read data) + (number of reads - 1)
≤(the end device number of the CPU module on the host station (the end device number of the CPU module on the host
station that has the same device name as S2 ))
174
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
b15 b14 to b9 b8 b7 b6 to b1 b0
S1 +0 1 0 [2] [1] 0 1
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
(1) When the instruction is executed
Length of the
Specifies the length of the data to be read.
S1 +9 data to be 1 to 960 User
1 to 960 (words)
read
175
Device Item Description Setting range Set by*1
● The read data storage device D1 requires a contiguous area as large as the length of the data to be read (specified with
S1 +9) (up to 960 words).
● The number of resends ( S1 +7) must be set whenever the instruction is executed.
(3) Function
This function reads the specified device data from the CPU module on another station specified with the IP
address setting in the control data. When the function finished reading the device data, the completion device
specified with D2 turns on.
The completion status of the SP.READ instruction can be checked using the completion devices D2 +0 and D2 +1.
• Completion device D2 +0
Turns on at the time of the END processing for the scan in which the SP.READ instruction completes and
turns off at the time of the next END processing.
• Completion status indication device D2 +1
Turns on or off depending on the status after the completion of the SP.READ instruction.
State Description
Normal completion Remains off.
Turns on at the time of the END processing for the scan in which the SP.READ instruction completes
Error completion
and turns off at the time of the next END processing.
176
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
The following are the timing charts for the SP.READ instruction:
• Normal completion
READ
ON
OFF OFF
Read command
ON
Completion device
CPU module OFF OFF
(Device specified in D2 )
on the host station
1 scan
Completion status OFF
indication device
(Device of D2 +1)
Read data storage device
(Device specified in D1 )
100 13
• Error completion
READ
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
ON
OFF OFF
Completion device ON
CPU module (Device specified in D2 ) OFF OFF
on the host station
Completion status ON
indication device
(Device of D2 +1) OFF OFF
1 scan
Completion status
(Device of S1 +1) Error code
Target error
177
(4) Error
(a) An operation error occurs, the error flag (SM0) turns on, and the error code is stored
in SD0 in the following cases:
(b) The completion device ( D2 )+1 turns on and the error code is stored in the completion
status area ( S1 )+1 in the following cases:
• The CPU module device on another station specified by the CPU module on the host station does not exist
or the device number is outside the range.
(Error code: 4031H)
• The IP address specified does not exist in the target.
(Error code: 4181H)
• The IP address specified is not supported by the SP.READ instruction.
(Error code: 4182H)
• No cable connection is detected through the built-in Ethernet port.
(Error code: 41ADH)
178
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
13
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
Station by Specifying an IP Address
179
13.1.2 Writing device data (SP.WRITE)
Command D1
S1 S2 D2
SP.WRITE SP.WRITE U0 or
" D1 "
S1 - *1 *1 *1 - - -
S2 - *1*2 *1 *1 - - -
D1 - - *3 -
D2 *1 *1 *1 - - - -
*1 Local devices and the file registers set for individual programs cannot be used.
*2 Word devices T, C, D, W, ST, SD, and SW can be specified.
*3 For information on string data specified with S2 , refer to Page 172, Section 13.1 (2).
S1 Start device that contains control data. User, system Device name
When specifying the start device by the device specification method, ensure that the CPU module on another station to
which to write data is within the range of devices available to the CPU module on the host station.
(The start device S2 of the CPU module on another station to which to write data) + (number of writes - 1)
≤(the end device number of the CPU module on the host station (the end device number of the CPU module device on the
host station that has the same device name as S2 ))
180
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
b15 b14 to b9 b8 b7 b6 to b1 b0
1 0 [3] [2] 0 [1]
Completed
Execution
Target 8000H
source
8001H
1: With arrival confirmation
Instruction The instruction completes after writing the data to the
8080H
8081H
13
S1 +0 execution other station's CPU module. User
8100H
type
8101H
Completed 8180H
Execution Target 8181H
source
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
Completion
S1 +1 0: Normal completion - System
status
181
Device Item Description Setting range Set by*1
Specifies the monitoring If the arrival monitoring time
time allowed before the setting is set to 1s with
completion of the S1 +0: 1 to 16383
processing. If the 1 to 16383: Monitoring time
processing does not (set in units of 1 second)
complete within the
Arrival monitoring time, the system
monitoring resends data until it User
S1 +8
reaches the number of If the arrival monitoring time
time
resends specified with setting is set to 100ms with
S1 +7. S1 +0: 1 to 65535
(This setting takes effect 1 to 65535: Monitoring time
(set in units of 0.1 second)
when S1 +0 is configured to
set the execution type to "1:
With arrival confirmation.")
Length of the
Specifies the length of the data to be written.
S1 +9 data to be 1 to 960 User
1 to 960 (words)
written
● The write data storage device S2 requires a contiguous area as large as the length of the data to be written (specified
with S1 +9) (up to 960 words).
● The number of resends ( S1 +7) must be set whenever the instruction is executed.
182
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
(3) Function
This function writes the data to the specified device of the CPU module on another station specified with the IP
address setting in the control data. When the function finished writing the device data, the completion device
specified with D2 turns on.
The completion status of the SP.WRITE instruction can be checked using the completion devices D2 +0 and
D2 +1.
• Completion device D2 +0
Turns on at the time of the END processing for the scan in which the SP.WRITE instruction completes and
turns off at the time of the next END processing.
• Completion status indication device D2 +1
Turns on or off depending on the status after the completion of the SP.WRITE instruction. 13
State Description
Normal completion Remains off.
Turns on at the time of the END processing for the scan in which the SP.WRITE instruction completes
Error completion
and turns off at the time of the next END processing.
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
Station by Specifying an IP Address
183
The following are the timing charts for the SP.WRITE instruction:
• Normal completion
WRITE
ON
Write command OFF OFF
Completion device ON
CPU module (Device specified in D2 ) OFF OFF
on the host station
Completion status 1 scan
indication device
(Device of D2 +1) OFF
• Error completion
WRITE
ON
OFF OFF
Write command
ON
Completion device
CPU module
(Device specified in D2 ) OFF OFF
on the host station
ON
Completion status indication OFF OFF
device (Device of D2 +1) 1 scan
Completion status
Error code
(Device of S1 +1)
Target error
184
CHAPTER 13 READING/WRITING DEVICE DATA FROM/TO THE CPU MODULE ON ANOTHER STATION BY SPECIFYING AN IP
ADDRESS
(4) Error
(a) An operation error occurs, the error flag (SM0) turns on, and the error code is stored
in SD0 in the following cases:
(b) The completion device ( D2 )+1 turns on and the error code is stored in the completion
status area ( S1 )+1 in the following cases:
• The CPU module device on another station specified by the CPU module on the host station does not exist
or the device number is outside the range.
(Error code: 4031H)
13.1 Instructions Associated with Reading/Writing Device Data from/to the CPU Module on Another
• The IP address specified does not exist in the target.
185
(5) Sample program
This sample program writes the data stored in devices D50 to D53 of the CPU module on the host station to the
devices D300 to D303 of the CPU module identified by an IP address of 192.168.20.4.
186
APPENDICES
APPENDICES
Appendix 1 Operation Processing Time for Each
Instruction
The following table lists the processing time of instructions described in this manual.
For details on the processing time, refer to the following.
MELSEC-Q/L Programming Manual (Common Instruction)
Processing time(µs)
Type Instruction Condition QnUDVCPU QnUDE(H)CPU
Minimum Maximum Minimum Maximum
Active 14.900 34.800 18.500 40.900
SP.SOCOPEN
TCP Unpassive 14.900 32.500 18.400 40.900 A
Fullpassive 14.900 32.400 18.400 40.900
UDP 14.900 34.600 18.400 40.900
From the host CPU 14.600 34.100 18.500 40.100
TCP
SP.SOCCLOSE From the connected device 14.600 34.000 18.500 40.000
UDP 14.600 33.400 18.900 40.100
Minimum data volume (1 byte) 6.400 25.000 17.000 39.100
TCP Maximum data volume (2046 bytes) 6.300 24.900 17.500 39.100
Maximum data volume (10238 bytes) 6.200 24.700 17.500 39.100
SP.SOCRCV
Minimum data volume (1 byte) 6.200 25.000 17.100 39.100
Instructions for TCP Maximum data volume (2046 bytes) 37.900 66.700 243.400 259.100
the socket Maximum data volume (10238 bytes) 149.100 190.400 1168.600 1185.300
S.SOCRCVS
communication Minimum data volume (1 byte) 14.200 36.500 12.800 30.100
function UDP Maximum data volume (2046 bytes) 38.100 69.100 243.400 259.100
Maximum data volume (10238 bytes) 153.800 191.800 1167.600 1185.300
Minimum data volume (1 byte) 11.700 34.500 18.900 43.100
TCP Maximum data volume (2046 bytes) 41.100 75.900 290.000 313.700
Maximum data volume (10238 bytes) 177.600 235.800 1367.600 1407.300
SP.SOCSND
Minimum data volume (1 byte) 11.400 35.400 18.900 43.100
UDP Maximum data volume (2046 bytes) 41.800 76.800 290.000 313.700
Maximum data volume (10238 bytes) 189.800 235.900 1367.600 1407.300
SP.SOCCINF - 4.900 20.800 12.700 32.200
SP.SOCCSET - 4.200 19.200 10.700 29.200
Standard mode Fixed-length mode 8.500 19.400 9.700 27.200
SP.SOCRMODE
Fixed-length mode Standard mode 8.300 19.400 9.700 27.200
Minimum data volume (1 word) 4.400 19.200 9.700 27.200
SP.SOCRDATA Maximum data volume (1024 words) 28.100 51.800 241.700 258.200
Maximum data volume (5120 words) 144.200 173.800 1168.600 1184.300
187
Processing time(µs)
Type Instruction Condition QnUDVCPU QnUDE(H)CPU
Minimum Maximum Minimum Maximum
Instruction for
the predefined
SP.ECPRTCL - 15.900 50.300 - -
protocol
function
Number of processing points = 1 word 43.10 48.60 - -
Device SP.READ
Number of processing points = 960 words 43.10 48.60 - -
read/write
Number of processing points = 1 word 43.10 48.20 - -
instructions SP.WRITE
Number of processing points = 960 words 66.70 71.90 - -
188
APPENDICES
Do not specify the following port numbers, because these numbers are used by the system.
189
Appendix 3 Added and Changed Functions
The following table lists added or modified functions in the CPU module and programming tool for built-in Ethernet port
communications and the corresponding serial numbers of CPU modules and software versions of GX Works2
software.
×: Not available, -: A function not related to the programming tool
The first five The corresponding version of the
Corresponding
digits of the programming tool
Added function function
corresponding
version GX Works2 GX Developer
serial number
Socket communication function ( Page 75, CHAPTER 7) "11012" or later 1.11M or later 8.78G or later
Predefined protocol function ( Page 64, CHAPTER 6) "15103" or later 1.501X or later ×
*1 This function cannot be used for some models. For the availability of the function, refer to each reference.
*2 For the versions of the intelligent function modules that support the function, refer to the manual for the intelligent
function module used.
*3 Available for the CPU modules with the following serial number (first five digits).
• QnUDE(H)CPU: "14112" or later
• QnUDVCPU: "15043" or later
190
APPENDICES
MC protocol QnA-
Reading/Writing
data in device
Reads/writes data (device) in the CPU module from/to an
*1*8
A
external device.
communication compatible memory
3E frame Reads/writes data (file) in the CPU module from/to an
Other ×
external device.
• Reads/writes data in the CPU module from/to an
A-compatible 1E frame external device. *11
Ethernet (V2.0) Sends data using the frame format selected for the
Send frame setting
IEEE802.3 Ethernet header of the data link layer. ×
191
Availability
Built-in
Item Description
Ethernet port QJ71E71-100
QCPU
Checks the connection status of an external device by
sending a Ping message (ICMP Echo) to an external
Check with Ping ("Use the Ping") ×
device. Closes the corresponding connection if no
Alive check function response message is received.
(alive check of an
external device) Checks the connection status of an external device by
Check with KeepAlive ("Use the sending an ACK message, which notifies an open status of *4
KeepAlive") the connection opened using the TCP protocol to an
external device.
Enables data communications using two connections with
Pairing open opening of one port, by pairing the receiving connection ×
with the sending connection.
Enables communications without performing open/close
Communication using automatic open UDP port setting processing after the station, in which an Ethernet module is ×
mounted, is started up.
Prevents unauthorized access to the CPU module by users
Remote password check
in remote locations.
Enables simultaneous broadcast to all Ethernet module
mounted stations within the same Ethernet network, when *10
Simultaneous broadcast
fixed buffer communications are performed without
procedure on the condition that UDP/IP is used.
Enables the connection to a MELSOFT product (such as a
Connection to MELSOFT products or GOT
programming tool and MX Component) or GOT
Finds the CPU modules connected to the same hub as GX
Find CPU function ×
Developer, and displays a list.
Collects time information from the time information server
Time setting function (SNTP client) ×
and sets time in the CPU module automatically.
Connection which is used by user during communications
using the MC protocol or the fixed buffer.
User connection Can be used as MELSOFT communication port of system
connection by setting parameters.
Up to 16 connections can be used.
HTTP port ×
192
APPENDICES
Availability
Built-in
Item Description
Ethernet port QJ71E71-100
QCPU
Enables the Ethernet module to send/receive data to/from
an external device by using the protocol for the external
Data communications using the predefined protocol device. The external device side protocol can be easily *11
Remark
For Ethernet modules, refer to the following.
Q Corresponding Ethernet Interface Module User's Manual (Basic)
193
(2) Differences on MC protocol functions between the Built-in Ethernet port QCPU
and Ethernet module
Consequence of a
Built-in Ethernet port
Item QJ71E71-100 communication with the Action
QCPU
Built-in Ethernet port QCPU
Data sending method is Perform the
Data sending method on TCP when the Data sending method is
selectable. If the response message size procedure described
response message size exceeds 1460 fixed to "Enable TCP
(Default: "Disable TCP exceeds 1460 bytes, the message in Page 60, Section
bytes Maximum Segment Size
Maximum Segment split by the external device may not 5.3 (6) so that the
(TCP Maximum Segment Size Option Option transmission" and
Size Option be read correctly. external device can
transmission) cannot be changed.
transmission") process split data.
Retry
1 to 16383.5 seconds. communication from
Fixed to one second. If each part of the split request
(Default: 30 seconds) the external device.
Wait time for receiving entire message (A request message is message is not sent within one
(The time value can be If a communication
(from the first message to the last discarded if the next part second, a response message is
changed in "Response timeout frequently
message) when a request message is of the split message not returned and a communication
monitoring timer" under occurs, reduce the
split and sent cannot be received within timeout occurs in the external
"Timer setting" of GX load of the external
one second.) device.
Developer.) device or Ethernet
network.
Check that the
external device
receives a response
Even when one When one connection If request messages are
message before
connection receives another request consecutively sent to one
sending next
Operation when request messages are consecutively receives message before connection, response messages
request message.
consecutively sent to one connection request messages, responding a request are not returned and a
(Do not
each request message message, the second communication timeout may occur
consecutively send
can be processed. message is discarded. in the external device.
request messages
from the external
device.)
194
APPENDICES
Consequence of a
Built-in Ethernet port communication with
Item QJ71E71-100 Action
QCPU the Built-in Ethernet
port QCPU
ZP.OPEN SP.SOCOPEN
ZP.CLOSE SP.SOCCLOSE
Instruction name ZP.BUFRCV SP.SOCRCV - Replace the instruction name.
Z.BUFRCVS S.SOCRCVS
ZP.BUFSND SP.SOCSND
When sending or receiving Set only one connection by parameter.
When sending or receiving
data using one When connection No. of the instruction is
Pairing open not data using one
connection, two - the same as the second connection No. of
necessary connection, paring setting
connections are occupied paring open, replace it with the first
is not used.
by the paring open setting. connection No.
Select whether UDP and
Automation of UDP
TCP-Full/Unpassive open
UDP and TCP-
A
is performed by the initial Delete the instructions for open and close
and TCP- Full/Unpassive open is -
timing setting parameter for UDP and TCP-Full/Unpassive.
Full/Unpassive open automatically performed.
automatically or by an
instruction.
When communications with
Data sending
the QJ71E71-100 are used
method on TCP Select whether to enable
for a CPU module which
when the message TCP Maximum Segment
performs TCP
size exceeds 1460 Size Option transmission "Enable TCP Maximum Perform the procedure indicated in Page 93,
communications with an
bytes in the buffer memory. Segment Size Option Section 7.3 (7) so that the external device
external device with the
(TCP Maximum (Default: "Disable TCP transmission" can process split data.
message size over 1460
Segment Size Maximum Segment Size
bytes, the external device
Option Option transmission")
may not correctly read split
195
Memo
196
INDEX
A L
Active open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Lock processing . . . . . . . . . . . . . . . . . . . . . . . . . 153
ls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
B
M
binary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Built-in Ethernet port QCPU . . . . . . . . . . . . . . . . . . 19 MC protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
bye . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 mdelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
mdir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
mget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
C
mls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 mput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 N
CPU module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
CPU-module-dedicated subcommands . . . . . . . . . 145 NAK message . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
D O
Data communication frame . . . . . . . . . . . . . . . . . . 59 open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 I
delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
P
Direct connection . . . . . . . . . . . . . . . . . . . . . . . . . 48
Passive open . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
E password-lock . . . . . . . . . . . . . . . . . . . . . . . . . . 146
password-unlock . . . . . . . . . . . . . . . . . . . . . . . . 146
Ethernet cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 pm-write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Ethernet communication . . . . . . . . . . . . . . . . . . . . 24 put . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
pwd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
F
Q
File transfer function . . . . . . . . . . . . . . . . . . . . . . 128
FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Q series . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
FTP commands . . . . . . . . . . . . . . . . . . . . . . . . . 138 QnUDE(H)CPU . . . . . . . . . . . . . . . . . . . . . . . . . . 19
FTP server support commands . . . . . . . . . . . . . . . 141 QnUDVCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Fullpassive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
quote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
G
R
get. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
GOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19,24 recv function . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
GX Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
ret . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
H
run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
High-speed Universal model QCPU . . . . . . . . . . . . 19
Host name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 S
Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Searching CPU modules . . . . . . . . . . . . . . . . . . . . 29
Simple connection . . . . . . . . . . . . . . . . . . . . . . . . 48
I
Simultaneous broadcast . . . . . . . . . . . . . . . . . . . . 89
IP packet transfer function . . . . . . . . . . . . . . . . . . 169 SNTP client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Socket communication function instructions . . . . . . . 94
status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
K stop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Subcommand . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
KeepAlive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
keyword-set . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
197
T
TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
TCP fixed-length receive mode . . . . . . . . . . . . . . 119
TCP socket functions . . . . . . . . . . . . . . . . . . . . . . 60
TCP standard receive mode . . . . . . . . . . . . . . . . 119
Time setting function . . . . . . . . . . . . . . . . . . . . . 125
U
UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Universal model QCPU . . . . . . . . . . . . . . . . . . . . . 19
Unlock processing . . . . . . . . . . . . . . . . . . . . . . . 153
Unpassive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
W
Wild card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
198
INSTRUCTION INDEX
S
S.SOCRCVS . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
S(P).SOCRDATA . . . . . . . . . . . . . . . . . . . . . . . . 122
SP.ECPRTCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
SP.SOCCINF . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
SP.SOCCLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . 99
SP.SOCCSET . . . . . . . . . . . . . . . . . . . . . . . . . . 116
SP.SOCOPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
SP.SOCRCV . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
SP.SOCRMODE . . . . . . . . . . . . . . . . . . . . . . . . . 118
SP.SOCSND . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
199
Memo
200
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print date *Manual number Revision
December 2008 SH(NA)-080811ENG-A First edition
March 2009 SH(NA)-080811ENG-B Revisions involving function addition to the Built-in Ethernet port QCPU (support for the
serial number (first five digits) of "11012" and later)
Correction
SAFETY PRECAUTIONS, MANUAL PAGE ORGANIZATION,
GENERIC TERMS AND ABBREVIATIONS, Section 1.1, CHAPTER 2, 3 , Appendix 1
Addition
Section 3.4, CHAPTER 4, Appendix 2, 3
Change of section No.
Section 3.4 Section 3.5, Section 3.5 Section 3.6,
Section 3.6 Section 3.7
April 2010 SH(NA)-080811ENG-C Revisions involving function addition to the Built-in Ethernet port QCPU (support for the
serial number (first five digits) of "11082" and later)
Model addition
Q50UDEHCPU, Q100UDEHCPU
Correction
SAFETY PRECAUTIONS, MANUAL PAGE ORGANIZATION,
GENERIC TERMS AND ABBREVIATIONS, Section 1.1, CHAPTER 2, CHAPTER 3,
Section 3.1.2, 3.1.4, 3.1.5, 3.2, 3.2.1, 3.2.2, 3.3, 3.3.3, 3.3.4, 3.3.5, 3.4, 3.4.1, 3.4.2,
3.4.3, 3.5, 3.5.1, 3.5.2, 3.6, 3.6.1, 3.6.2, 3.6.3, 3.6.5, 3.6.6, 3.7.2, CHAPTER 4,
Section 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, Appendix 1, Appendix 2, Appendix 3
Addition
Section 3.1.3, 3.8, 3.8.1, 3.8.2, 3.8.3, 3.8.4
August 2010 SH(NA)-080811ENG-D Revision on the new functions of the Universal model QCPU with a serial number (first 5
digits) of "12052" or later
Correction
SAFETY PRECAUTIONS, CHAPTER 2, Section 3.6.2, 3.6.6, 4.3, 4.4, 4.5, 4.8, 4.9,
Appendix 1, Appendix 2
July 2011 SH(NA)-080811ENG-E
Correction
SAFETY PRECAUTIONS, CHAPTER 2, Section 3.3.1, 3.3.3, 3.4.1, 3.4.2, 3.4.3, 4.1,
4.6, Appendix 1
Addition
Appendix 4
October 2011 SH(NA)-080811ENG-F Revision on the new functions of the Universal model QCPU with a serial number (first
five digits) of "13102" or later
Correction
MANUAL PAGE ORGANIZATION, Section 3.1.1, 3.1.2, 3.1.4, 3.2.1, 3.3.2, 3.3.3, 3.3.4,
3.3.5, 3.4.1, 3.4.2, 3.6.4, 3.7.4, 3.8, CHAPTER 4, Appendix 1, Appendix 2
February 2012 SH(NA)-080811ENG-G Revision on the new functions of the Universal model QCPU with a serial number (first 5
digits) of "14022" or later
Correction
Section 1.1, CHAPTER 3, Section 3.3.5, Appendix 1, Appendix 2, Appendix 4
Addition
Section 3.9
201
Print date *Manual number Revision
February 2013 SH(NA)-080811ENG-I Overall revision due to addition of the Universal model QCPU and the changed manual
layout
Model addition
Q03UDVCPU, Q04UDVCPU, Q06UDVCPU, Q13UDVCPU, Q26UDVCPU
September 2013 SH(NA)-080811ENG-J Revision on the new functions of the Universal model QCPU with a serial number (first 5
digits) of "15043" or later
Correction
Section 5.2.2, 8.1, 8.2, 8.4.1, Appendix 3
January 2014 SH(NA)-080811ENG-K Revision on the new functions of the Universal model QCPU with a serial number (first
five digits) of "15103" or later
Partial correction
Section 1.1, Chapter 2, Section 7.3, 7.4.1, 9.2, 9.3, Chapter 10, Section 11.4, Appendix
1, Appendix 3, Appendix 4
Addition
Chapter 6
March 2015 SH(NA)-080811ENG-N Revision on the functions for High-speed Universal model QCPU with a serial number
(first 5 digits) of "17012" or later
Partial correction
Section 7.4.2, 7.4.4, 9.2, 11.3
June 2015 SH(NA)-080811ENG-O Revision on the functions for High-speed Universal model QCPU with a serial number
(first 5 digits) of "17052" or later
Partial correction
Section 1.1, CHAPTER 3, Section 3.6, CHAPTER 4, Section 10.2, 10.3, Appendix 2, 3,
4
Addition
Section 3.5
December 2015 SH(NA)-080811ENG-P Revision on the functions for High-speed Universal model QCPU with a serial number
(first 5 digits) of "17103" or later
Partial correction
Section 9.2, 9.3, CHAPTER 11
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses.
Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may
occur as a result of using the contents noted in this manual.
© 2008 MITSUBISHI ELECTRIC CORPORATION
202
WARRANTY
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product
within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service
Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at
the customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing
on-site that involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and
the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of repair
parts shall not exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc., which
follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels on the
product.
(2) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused
by the user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions
or structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary by
industry standards, had been provided.
4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the
instruction manual had been correctly serviced or replaced.
5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force
majeure such as earthquakes, lightning, wind and water damage.
6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi.
7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA
Center may differ.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation to:
(1) Damages caused by any cause found not to be the responsibility of Mitsubishi.
(2) Loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products.
(3) Special damages and secondary damages whether foreseeable or not, compensation for accidents, and
compensation for damages to products other than Mitsubishi products.
(4) Replacement by the user, maintenance of on-site equipment, start-up test run and other tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
203
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or
other countries.
Ethernet is a registered trademark of Fuji Xerox Corporation in Japan.
The SD and SDHC logos are trademarks of SD-3C, LLC.
The company names, system names and product names mentioned in this manual are either registered trademarks or
trademarks of their respective companies.
In some cases, trademark symbols such as '™' or '®' are not specified in this manual.
204 SH(NA)-080811ENG-P
SH(NA)-080811ENG-P(1512)MEE
MODEL: QNUDEHCPU-U-ET-E
MODEL CODE: 13JZ29
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.