advertisement
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".
WARNING
CAUTION
Indicates that incorrect handling may cause hazardous conditions, resulting in death or severe injury.
Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage.
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to serious consequences.
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) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting operations (such as forward/reverse rotations or upper/lower limit positioning) must be configured external to the programmable controller.
(2) Machine OPR (Original Point Return) of the positioning function is controlled by two kinds of data: an OPR direction and an OPR speed. Deceleration starts when the near-point watchdog signal turns on. If an incorrect OPR direction is set, motion control may continue without deceleration. To prevent machine damage caused by this, configure an interlock circuit external to the programmable controller.
(3) When the CPU module detects an error during control by the positioning function, the motion slows down and stops.
1
[Design Precautions]
WARNING
(4) When the programmable controller detects an abnormal condition, it stops the operation and all outputs are:
• Turned off if the overcurrent or overvoltage protection of the power supply module is activated.
• Held or turned off according to the parameter setting if the self-diagnostic function of the CPU module detects an error such as a watchdog timer error.
Also, all outputs may be turned on if an error occurs in a part, such as an 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 "General Safety Requirements" in the MELSEC-L CPU
Module User's Manual (Hardware Design, Maintenance and Inspection).
(5) Outputs may remain on or off due to a failure of a component such as a transistor in an output circuit. Configure an external circuit for monitoring output signals that could cause a serious accident.
● In an output circuit, 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.
● Configure a circuit so that the external power supply is turned off first and then the programmable controller. If the programmable controller is turned off 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 each network. Incorrect output or malfunction due to a communication failure may result in an accident.
● When changing data from a peripheral device connected to the CPU module to the running programmable controller, configure an interlock circuit in the program to ensure that the entire system will always operate safely. For other controls to a running programmable controller (such as program modification or operating status change), read relevant manuals carefully and ensure the safety before the operation. Especially, in the case of a control from an external device to a remote programmable controller, immediate action cannot be taken for a problem on the programmable controller due to a communication failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions to be taken between the external device and CPU module in case of a communication failure.
● An absolute position restoration by the positioning function may turn off the servo-on signal (servo off) for approximately 20ms, and the motor may run unexpectedly. If this causes a problem, provide an electromagnetic brake to lock the motor during absolute position restoration.
2
[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.
● During control of an inductive load such as a lamp, heater, or solenoid valve, a large current
(approximately ten times greater than normal) may flow when the output is turned from off to on.
Therefore, use a module that has 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.
[Installation Precautions]
WARNING
● 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 electric shock or cause the module to fail or malfunction.
3
[Installation Precautions]
CAUTION
● Use the programmable controller in an environment that meets the general specifications in the
MELSEC-L CPU Module 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 interconnect modules, engage the respective connectors and securely lock the module joint levers until they click. Incorrect interconnection may cause malfunction, failure, or drop of the module.
● Do not directly touch any conductive parts and electronic components of the module. Doing so can cause malfunction or failure of the module.
● Securely connect an extension cable to the connectors of a branch module and an extension module. After connections, check that the cable 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.
● Do not directly touch any conductive parts and electronic components of the module or SD memory card. Doing so can cause malfunction or failure of the module.
[Wiring Precautions]
WARNING
● Shut off the external power supply (all phases) used in the system before wiring. Failure to do so may result in electric shock or cause the module to fail or malfunction.
● After installation and wiring, attach the included terminal cover to the module before turning it on for operation. Failure to do so may result in electric shock.
4
[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 a terminal block 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.
● Connectors for external devices must be crimped or pressed with the tool specified by the manufacturer, or must be correctly soldered. Incomplete connections may cause short circuit, fire, or malfunction.
● Securely connect the connector to the module.
● Do not install the control lines or communication cables together with the main circuit lines or power cables. 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 block 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, fire, or malfunction.
● 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.
● 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.
● To use the high-speed counter function, ground the shield cable on the encoder side (relay box).
Always ground the FG and LG terminals to the protective ground conductor. Failure to do so may cause malfunction.
● 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 qualified maintenance personnel with knowledge of protection against electric shock. For wiring methods, refer to the
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection).
5
[Startup and Maintenance Precautions]
WARNING
● Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction.
● Correctly connect the battery connector. Do not charge, disassemble, heat, short-circuit, solder, or throw the battery into the fire. Also, do not expose it to liquid or strong shock.
Doing so will cause the battery to produce heat, explode, ignite, or leak, resulting in injury and fire.
● Shut off the external power supply (all phases) used in the system before cleaning the module or retightening the terminal block screws. Failure to do so may result in electric shock.
[Startup and Maintenance Precautions]
CAUTION
● Before performing online operations (especially, program modification, forced output, and operating status change) for the running CPU module from the peripheral device connected, read relevant manuals carefully and ensure the safety. Improper operation may damage machines or cause accidents.
● Do not disassemble or modify the modules. Doing so may cause failure, malfunction, injury, or a fire.
● Use any radio communication device such as a cellular phone or PHS (Personal Handy-phone
System) more than 25cm away in all directions from the programmable controller. 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 cause the module to fail or malfunction.
● Tighten the terminal block screw within the specified torque range. Undertightening can cause drop of the component or wire, short circuit, or malfunction. Overtightening can damage the screw and/or module, resulting in drop, short circuit, or malfunction.
● After the first use of the product (module, display unit, and terminal block), do not connect/disconnect the product more than 50 times (in accordance with IEC 61131-2). Exceeding the limit may cause malfunction.
● After the first use of the SD memory card, do not insert/remove the memory card 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 conducting object such as a grounded metal to discharge the static electricity from the human body. Failure to do so may cause the module to fail or malfunction.
● Before testing the operation by the positioning function, set a low speed value for the speed limit parameter so that the operation can be stopped immediately upon occurrence of a hazardous condition.
6
[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 on battery regulations in EU member states, refer to the MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection).)
[Transportation Precautions]
CAUTION
● When transporting lithium batteries, follow the transportation regulations. (For details on the regulated models, refer to the MELSEC-L CPU Module User's Manual (Hardware Design,
Maintenance and Inspection).)
7
8
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.
INTRODUCTION
Thank you for purchasing the Mitsubishi MELSEC-L series programmable controllers.
This manual describes the functions of the CPU module and programming necessary for Ethernet communication.
Before using the product, please read this manual and the relevant manuals carefully and develop familiarity with the functions and performance of the MELSEC-L 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.
Please make sure that the end users read this manual.
Relevant CPU modules:
LCPU
CPU module Model
L02CPU, L02CPU-P, L06CPU, L26CPU, L26CPU-BT, and L26CPU-PBT
Remark
● This manual describes only the functions of CPU module using Ethernet communication.
For other CPU module functions, refer to the following.
MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)
MELSEC-L CPU Module User's Manual (Built-In I/O Function)
QnUDVCPU/LCPU User's Manual (Data Logging Function)
● The L02SCPU does not support the built-in Ethernet function.
9
RELEVANT MANUALS
(1) CPU module user's manual
Manual name
<manual number (model code)>
MELSEC-L CPU Module User's Manual
(Hardware Design, Maintenance and Inspection)
Description
Specifications of the CPU modules, power supply modules, display unit, branch module, extension module, SD memory cards, and batteries, information on how to establish a system, maintenance and inspection, and troubleshooting <SH-080890ENG, 13JZ36>
MELSEC-L CPU Module User's Manual
(Function Explanation, Program Fundamentals)
<SH-080889ENG, 13JZ35>
MELSEC-L CPU Module User's Manual (Built-In I/O Function)
Functions and devices of the CPU module, and programming
<SH-080892ENG, 13JZ38>
QnUDVCPU/LCPU User's Manual (Data Logging Function)
<SH-080893ENG, 13JZ39>
The general-purpose I/O function, interrupt input function, pulse catch function, positioning function, and high-speed counter function of the
CPU module
The data logging function of the CPU module
(2) Programming manual
Manual name
<manual number (model code)>
MELSEC-Q/L Programming Manual (Common Instruction)
<SH-080809ENG, 13JW10>
Description
Detailed description and usage of instructions used in programs
(3) Operating manual
Manual name
<manual number (model code)>
GX Works2 Version 1 Operating Manual (Common)
<SH-080779ENG, 13JU63>
GX Developer Version 8 Operating Manual
<SH-080373E, 13JU41>
Description
System configuration, parameter settings, and online operations
(common to Simple project and Structured project) of GX Works2
Operating methods of GX Developer, such as programming, printing, monitoring, and debugging
(4) I/O module and intelligent function module manua
Manual name
<manual number (model code)>
MELSEC-Q/L MELSEC Communication Protocol Reference Manual
<SH-080008, 13JF89>
Description
Details of MELSEC communication protocol (MC protocol) that is used for data communication between a target device and a CPU module
10
Memo
11
CONTENTS
CHAPTER 1 OVERVIEW 18
CHAPTER 2 COMMUNICATION SPECIFICATIONS 20
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT 22
23
25
27
28
29
CHAPTER 4 DIRECT CONNECTION TO PROGRAMMING TOOL
(SIMPLE CONNECTION) 31
32
33
CHAPTER 5 MC PROTOCOL COMMUNICATION 34
35
37
37
38
39
41
12
CHAPTER 6 SOCKET COMMUNICATION FUNCTION 42
44
53
59
61
62
67
Reading out received data in the END processing (SP.SOCRCV) . . . . . . . . . . . . . . . . . . . .
70
Reading out received data during instruction execution (S.SOCRCVS) . . . . . . . . . . . . . . . .
74
77
81
84
Changing the receive mode of a connection (SP.SOCRMODE) . . . . . . . . . . . . . . . . . . . . . .
86
89
CHAPTER 7 TIME SETTING FUNCTION (SNTP CLIENT) 91
92
93
CHAPTER 8 FILE TRANSFER FUNCTION (FTP) 94
95
99
100
101
101
103
104
112
CHAPTER 9 REMOTE PASSWORD 114
115
116
119
120
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION 121
122
133
134
134
136
CHAPTER 11 IP PACKET TRANSFER FUNCTION 138
APPENDICES 140
140
141
141
142
144
INDEX 149
INSTRUCTION INDEX 151
13
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.
"" is used for screen names and items.
shows operating procedures.
shows mouse operations.
*1
[ ] is used for items in the menu bar and the project window.
The chapter of the current page is shown.
The section of the current page is shown.
operating examples.
shows reference manuals.
shows reference pages.
shows notes that requires attention.
shows useful information.
*1 The mouse operation example is provided below. (For GX Works2)
Menu bar
Ex.
[Online] [Write to PLC...]
Select [Online] on the menu bar, and then select [Write to PLC...].
A window selected in the view selection area is displayed.
Ex.
Project window
[PLC Parameter]
[Parameter]
Select [Project] from the view selection area to open the Project window.
In the Project window, expand [Parameter] and select [PLC Parameter].
View selection area
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
Execution condition of the instruction
Structure of the instruction in the ladder mode
shows the devices
applicable to the instruction
Descriptions of setting data and data type
Setting side
User : Device value is set by the user.
System: Device value is set by
the CPU module.
Descriptions of control data (if any)
Detailed descriptions of the instruction
Conditions for the error and error codes
For the errors not described in this manual, refer to the following.
MELSEC-Q/L Programming
Manual (Common Instruction)
Simple program example(s) and descriptions of the devices used
15
16
*2
*3
• Instructions can be executed under the following conditions.
Execution condition Any time During on
On the falling edge
Symbol No symbol
• The following devices can be used.
Setting data
Internal device
(system, user)
Bit Word
File register
Link direct device
J\
Bit Word
Intelligent function module
U\G
During off
Index register
Zn
Applicable device
*1
X,Y,M,L,S
M,F,B,SB,F
X,FY
*2
T,ST,C,D,W,
SD,SW,FD,
@
R,ZR U
\G
Z
*1 For details on each device, refer to the following
MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)
FX and FY can be used for bit data only, and FD for word data only.
In the "Constant" and "Others" columns, a device(s) that can be set for each instruction is shown.
On the falling edge
Con stant
*3
Other
*3
K, H,
E, $
P,I,J,U,D
X,DY,N,B
L,TR,BL\
S,V
• The following data types can be used.
Data type
Bit
BIN 16-bit
BIN 32-bit
BCD 4-digit
BCD 8-digit
Real number
Character string
Device name
Description
Bit data or the start number of bit data
16-bit binary data or the start number of word device
32-bit binary data or the start number of double-word device
Four-digit binary-coded decimal data
Eight-digit binary-coded decimal data
Floating-point data
Character string data
Device name data
TERMS
Unless otherwise specified, this manual uses the following terms.
CPU module
Power supply module
Branch module
Extension module
END cover
Display unit
Term
SD memory card
Extension cable
Built-in Ethernet port LCPU
LCPU
Programming tool
GX Works2
GX Developer
MC protocol
FTP
SNTP
Description
The abbreviation for the MELSEC-L series CPU module
The abbreviation for the MELSEC-L series power supply module
The abbreviation for the MELSEC-L series branch module
The abbreviation for the MELSEC-L series extension module
A cover to be attached to the right side of the rightmost MELSEC-L series module
A liquid crystal display to be attached to the CPU module
Secure Digital Memory Card, which is a flash memory device. The L1MEM-2GBSD and L1MEM-4GBSD are available.
The abbreviation for the MELSEC-L series extension cable
A generic term for the L02CPU, L02CPU-P, L06CPU, L26CPU, L26CPU-BT, and L26CPU-PBT
Another term for the MELSEC-L series CPU module
A generic term for GX Works2 and GX Developer
The product name of the software package for the MELSEC programmable controllers
The abbreviation for the MELSEC communication protocol, a protocol to access a CPU module from a target device in the Ethernet or serial communication
The abbreviation for File Transfer Protocol, which is a standard network protocol used to exchange files
The abbreviation for Simple Network Time Protocol, which is a protocol for synchronizing the clocks of computer systems over a TCP/IP based network
17
CHAPTER 1
OVERVIEW
The following describes the built-in Ethernet function of the CPU module.
(1) Connection of programming tools and GOTs (
Page 22, CHAPTER 3)
• By using a hub, the CPU module can be connected to multiple programming tools and GOTs.
Up to 16 external devices can be connected to a single CPU module at the same time.
• When CPU modules and a programming tool are connected to the same hub, these CPU modules can be searched from the programming tool. Displayed search results include IP addresses so that any of them can be specified.
• MELSOFT connection allows access through routers in an environment such as a corporate LAN.
(2) Direct connection to a programming tool (simple connection)
(
Page 31, CHAPTER 4)
The CPU module can be directly connected to a programming tool with a single Ethernet cable only, without using a hub (simple connection).
For direct connection, the IP address and host name need not be specified in the transfer setup.
(3) MC protocol communication (
Page 34, CHAPTER 5)
From an external device such as a personal computer or HMI, device data of the CPU module can be read or written, and this allows CPU module operation monitoring, data analysis, and production control.
(4) Socket communication function (
Page 42, CHAPTER 6)
By using instructions dedicated to socket communication, any data can be transferred from and to the external devices connected through Ethernet using TCP or UDP.
(5) Time setting function (SNTP client) (
Page 91, CHAPTER 7)
• Automatic time setting of the CPU module can reduce the maintenance cost for time setting.
• By sharing the same clock data among CPU modules connected to Ethernet via their built-in Ethernet ports, the order of errors between processes can be traced, facilitating problem solving.
• Since the automatic time setting is enabled upon power-on of the CPU module, operations can be started based on accurate clock data.
(6) File transfer function (FTP) (
Page 94, CHAPTER 8)
Each of the files stored in the CPU module can be read or written from the interfacing device with the FTP client function, and a large amount of data can be easily transferred.
(7) Remote password (
Page 114, CHAPTER 9)
Remote password setting can prevent unauthorized access from the outside and enhance the security of the system.
(8) Simple PLC communication function (
Page 121, CHAPTER 10)
Device data can be communicated between the CPU modules connected with Ethernet cable without programming.
18
CHAPTER 1 OVERVIEW
(9) IP packet transfer function (
Page 138, CHAPTER 11)
Communications can be performed with a device which supports the following IP addresses, which have been specified via a 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 Field Network
• External devices on the Ethernet network, which are connected through the built-in Ethernet ports
1
19
CHAPTER 2
COMMUNICATION SPECIFICATIONS
The following are the communication specifications of the built-in Ethernet port of the CPU module.
Item Specification
Transmission specifications
Data transfer speed
Communication mode
Transmission method
Maximum distance between hub and node
Maximum number of nodes/ connection
TCP/IP
10BASE-T
100BASE-TX
100 or 10 Mbps
Full-duplex or half-duplex
Base band
100 m
Cascade connection: Up to four
*2
Cascade connection: Up to two
*2
Number of connections
Connection cable
*1
UDP/IP
10BASE-T
100BASE-TX
Total of 16 for socket communications, MELSOFT connections, and MC protocol.
One for FTP
Ethernet cable of category 3 or higher (STP/UTP cable)
*3
Ethernet cable of category 5 or higher (STP cable)
*1 Straight cables can be used.
When the CPU module is directly connected to GOT with Ethernet cable, a cross cable of Category 5e or lower can also be used.
*2 This number applies when a repeater hub is used.
When using a switching hub, check the number of cascaded stages with the manufacturer of the hub to be used.
*3 Use of STP cables is recommended in an environment with noise.
Hubs with 10BASE-T or 100BASE-TX ports
*4
can be used.
Up to 16 external devices can access one CPU module at the same time.
*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.
20
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.
• 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.
2
21
CHAPTER 3
CONNECTION OF PROGRAMMING
TOOLS AND GOT
This chapter explains how to connect the CPU module to a programming tool or GOT.
CPU module CPU module
Ethernet
Hub
Programming tool
Programming tool
To start Ethernet communication, perform the following steps.
Start
Setting parameters
GOT
Configure PLC parameters by the programming tool.
Writing to the CPU module
Write the configured parameters to the CPU module.
Power it on again or reset it for the parameters to take effect.
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.
End
For the GOT setting, refer to the following manual.
GOT1000 Series Connection Manual (Mitsubishi Products)
22
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
3.1
Setting for the CPU Module
(1) PLC parameter setting
Select the "Built-in Ethernet Port Setting" tab and set the parameters.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
3
2.
1.
1.
Set the IP address of the CPU module.
2.
Set MELSOFT connection.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
[Open Setting]
Protocol
Item
Open System
Setting
Select "TCP" or "UDP" depending on the connected device.
Select "MELSOFT Connection".
23
24
(2) Writing to the CPU module
From the "Write to PLC" screen, write the parameter settings to the CPU module.
[Online] [Write to PLC]
After writing the parameters to the CPU module, power off and on or reset the CPU module to enable the parameters.
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
3.2
Setting for the Programming Tool
Configure the settings in the "Transfer Setup" dialog box.
Connection Destination window [Connection1]
3
1.
2.
3.
1.
Select "Ethernet Board" for "PC side I/F".
In the "PC side IF Ethernet Board Setting" dialog box, select a "TCP" or "UDP" protocol. Select the same protocol as the one set in the Open Setting dialog box. (
25
26
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" dialog box, as shown below.
(For the host name, enter the name set in the Microsoft
®
Windows
®
hosts file.)
3.
Set "Other Station Setting".
Select an item appropriate to the operating environment.
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
3.3
Searching CPU Modules on the Network
In a configuration using a hub, clicking in the "PLC side I/F Detailed Setting of PLC
Module" dialog box will start searching for CPU modules connected to the hub where the programming tool is also connected, and display a list of them.
3
Clicking this button will automatically enter the
IP address of the CPU module.
• 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.
• Some CPU modules connected via wireless LAN may not be found since Ethernet communication may not be stable due to packet loss.
• If multiple CPU modules with the same IP address are found in the list, check the IP address parameters for the CPU modules. Starting communication with the IP address duplicated will cause a communication error.
• Appropriate CPU modules may not be found if a heavy load for service processing is applied.
Increase the response waiting time value in the "Find CPU (Built-in Ethernet port)" dialog box, or the service processing time value in the Service processing setting tab of PLC parameter.
• By selecting the option shown below in the Built-in Ethernet port tab of PLC parameter, the Find CPU function can be disabled and the system does not respond to a search request on the network.
27
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
Factory
Control room
Personal computer
*1
CPU module
The following functions do not support the communication via routers.
• Searching CPU modules on the network
• Simultaneous broadcast in socket communication
the default router IP address in addition to the IP address.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
Set the subnet mask pattern and default router IP address.
28
CHAPTER 3 CONNECTION OF PROGRAMMING TOOLS AND GOT
3.5
Precautions
(1) IP address duplication
Check that the IP address is not duplicated when configuring a network or connecting a new device to a network.
If the IP address is duplicated, a device may communicate with the wrong device.
Check for the IP address duplication in the following ways.
• Check for the IP address duplication with the find CPU function.
• Disconnect the device from the line and send ping to the IP address of the disconnected device.
Having a response means the IP address duplication.
(2) KeepAlive check
When the protocol is set to TCP, KeepAlive check is performed. (Checking for a response to a KeepAlive ACK message)
An alive check message is sent five seconds after reception of the last message from the connected device to check if the device returns a response or not. If no response is received, the alive check message will be resent at intervals of five seconds. When no response is received for 45 seconds, the connected device is regarded as non-existent and the connection is disconnected. If the connected device does not support the TCP KeepAlive function, the connection may be disconnected.
(3) Connections exceeding the setting
Do not exceed the number of connections set for the open settings parameters. Establishing too many TCP connections from a personal computer may cause the following states, depending on the application.
• Time before timeout error detection is increased.
• An unexpected timeout error occurs in any of the communicating devices.
(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.)
3
29
30
(5) MELSOFT connection over UDP
For UDP communications with multiple MELSOFT devices, set the same number of connections as that of the connected MELSOFT devices on the screen displayed from PLC parameter.
CPU module
Ethernet
Hub
MELSOFT device
MELSOFT device
MELSOFT device
Set the same number of protocols as that of
MELSOFT devices.
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.
(6) Sampling trace
When the function has been executed using the programming tool via a built-in Ethernet port, stop the function before powering off or resetting the CPU module.
(7) Remote STOP or remote PAUSE
When remote STOP or remote PAUSE has been executed using the programming tool via a built-in Ethernet port, perform the following operations before powering off or resetting the CPU module.
• Remote RUN
• Remote RESET
CHAPTER 4 DIRECT CONNECTION TO PROGRAMMING TOOL (SIMPLE CONNECTION)
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
4
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 dialog box.
31
4.1
Setting Method
Set the items on the Transfer Setup screen.
Connection Destination window [Connection1]
2.
3.
1.
1.
Select "Ethernet Board" for "PC side I/F".
2.
Select "PLC Module" for "PLC side I/F".
In the "PLC side IF Detailed Setting of PLC Module" dialog box, select the Ethernet Port Direct
Connection checkbox as shown below.
32
3.
Complete setting of "Other Station Setting".
Select an item appropriate to the operating environment.
CHAPTER 4 DIRECT CONNECTION TO PROGRAMMING TOOL (SIMPLE CONNECTION)
4.2
Precautions
(1) Connection to LAN line
When connecting the CPU module to a LAN line, do not set direct connection. Doing so will apply a load to the
LAN line and adversely affect communications with other external devices.
(2) Indirect connection
• Do not set up direct connection when a CPU module is connected to an external device in a one-to-one basis using a hub as shown below.
CPU module
4
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.
(3) Conditions that disallow direct connection
When any of the following conditions is met, communication by direct connection may not be available. In that case, check the setting of the CPU module and/or personal computer.
• In the CPU module IP address bits, the bits corresponding to "0" in the personal computer subnet mask are all ON or all OFF.
Ex.
CPU module IP address
Personal computer IP address
Personal computer subnet mask
:
:
:
64.
64.
255.
64.
64.
255.
255.
1.
0.
255
1
0
• 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.
Ex.
CPU module IP address
Personal computer IP address
Personal computer subnet mask
:
:
:
64.
192.
255.
64.
168.
0.
255.
0.
0.
255
1
0
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
33
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.
CPU module
GOT
Hub
Communication using MC protocol
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.
To start MC protocol communication, perform the following steps.
Start
Connecting cables and external devices
Connect cables and devices required for MC protocol communication.
Setting parameters
Configure PLC parameters by the programming tool.
Writing to the CPU module
End
Write the configured parameters to the CPU module.
Power it on again or reset it for the parameters to take effect.
MC protocol communication is available.
For the MC protocol communication, refer to the following manual.
MELSEC-Q/L MELSEC Communication Protocol Reference Manual
Remark
Access through routers is also available. When configuring the settings for it, set the subnet mask pattern and default router
IP address. (
34
CHAPTER 5 MC PROTOCOL COMMUNICATION
5.1
Setting Method
Setting for communication using the MC protocol is described below.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
3.
5
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.
35
36
3.
Set connections used for MC protocol communication.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting] button
Item
Protocol
Open System
Host Station Port
No.
*1
Description
Select TCP or UDP depending on the target device.
Select "MC Protocol".
Set the port number of the host station. (Setting range: 0401
H
to 1387
H
, 1392
H
to FFFE
H
*1
Do not specify 1388
H
to 1391
H
because these ports are used by the system. (
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.
CHAPTER 5 MC PROTOCOL COMMUNICATION
5.2
MC Protocol Commands
5.2.1
Command list
Device memory
The following commands are executable for MC protocol communication of the CPU module.
Remote password
Function
Batch read
In units of bits
1401
(0001)
Batch write
In units of words
1401
(0000)
Random read *2
Test
(Random write)
Monitor registration
*2*3*4
In units of words
0801
(0000)
Monitor
Unlock
Lock
In units of bits
In units of bits
Command
(Subcomm and)*1
0401
(0001)
In units of words
0401
(0000)
In units of words
0403
(0000)
1402
(0001)
In units of words
*2
1402
(0000)
In units of words
0802
(0000)
1630
(0000)
1631
(0000)
Description
Number of processed points
: Available,
×: N/A
CPU module state
STOP
RUN
Write enabled
Write disabled
Reads bit devices in units of one point.
Reads bit devices in units of 16 points.
Reads word devices in units of one point.
Writes bit devices in units of one point.
Writes bit devices in units of 16 points.
Writes word devices in units of one point.
Reads bit devices in units of 16 or 32 points by randomly specifying the target.
Reads word devices in units of one or two points by randomly specifying the target.
Sets or resets bit devices in units of one point by randomly specifying the target.
Sets or resets bit devices in units of 16 or 32 points by randomly specifying the target.
Writes word devices in units of one or two points by randomly specifying the target.
Registers bit devices to be monitored in units of 16 or 32 points.
Registers word devices to be monitored in units of one or two points.
ASCII: 3584 points
BIN: 7168 points
960 words
(15360 points)
960 points
ASCII: 3584 points
BIN: 7168 points
960 words
(15360 points)
960 points
192 points
188 points
*5
192 points
Monitors the devices registered.
Number of registered points
Specifies a remote password to unlock the locked state.
Specifies a remote password to lock the unlocked state.
-
-
×
×
*1 These commands are for QnA-compatible 3E frames.
*2 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 (4032
H
) at the time of monitoring execution.
*3 For monitor registration, monitoring conditions cannot be set.
*4 Do not execute monitor registration from multiple devices. If executed, the last monitor registration takes effect.
*5 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.
5
37
5.2.2
Available devices
The following table
lists the devices available in the commands used for MC protocol communication.
Classification
Internal user device
Internal system device
Input
Output
Internal relay
Latch relay
Annunciator
Edge relay
Link relay
Data register
Link register
Timer
Retentive timer
Counter
Link special relay
Link special register
Step relay
Device
Special register
Contact
Coil
X*
Y*
M*
L*
F*
V*
B*
D*
W*
TS
TC
Current value TN
Contact
Coil
SS
Device code
*1
ASCII Binary
SC
Current value SN
Contact
Coil
CS
CC
Current value CN
Direct input
*2
Direct output
*2
Function input
Function output
Function register
Special relay
SB
SW
S*
DX
DY
SM
SD
-
-
-
A8
H
B4
H
C1
H
C0
H
C2
H
C7
H
C6
H
C8
H
9C
H
9D
H
90
H
92
H
93
H
94
H
A0
H
B5
H
98
H
A2
H
A3
H
C4
H
C3
H
C5
H
A1
H
91
H
A9
H
-
-
-
The number range of a device in a CPU module, which is accessed to, can be specified.
The number range of a device in a CPU module, which is accessed to, can be specified.
Note that the access to a local device is not possible.
The number range of a device in a CPU module, which is accessed to, can be specified.
Cannot be accessed.
Device number range
The number range of a device in a CPU module, which is accessed to, can be specified.
Hexadecimal
Hexadecimal
Decimal
Decimal
Decimal
Decimal
Hexadecimal
Decimal
Hexadecimal
Decimal
Decimal
Decimal
Hexadecimal
Hexadecimal
Decimal
Hexadecimal
Hexadecimal
-
-
-
Decimal
Decimal
Index register Z*
CC
H
The number range of a device in a CPU module, which is accessed to, can be specified.
Note that the access to a local device is not possible.
Decimal
File register
Extended data register
Extended link register
*1
*2
R*
ZR
D*
W*
AF
H
B0
H
A8
H
B4
H
The number range of a device in a CPU module, which is accessed to, can be specified.
Decimal
Decimal
Decimal
Hexadecimal
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: 2A
H
) or a space (ASCII code: 20
H
) after the character.
For the L02CPU and L02CPU-P, devices of DX/DY400 or later number cannot be used. Use X/Y devices to access devices of X/Y400 or later. For the L06CPU, L26CPU, L26CPU-BT and L26CPU-PBT, devices of DX/DY1000 or later number cannot be used. Use X/Y devices to access devices of X/Y1000 or later.
38
CHAPTER 5 MC PROTOCOL COMMUNICATION
5.3
Precautions
(1) Number of devices
Only the external devices whose open system is set to "MC Protocol" can be connected concurrently using MC protocol.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting] button
(2) Data communication frame
The QnA-compatible 3E frames only are applicable to CPU modules.
(3) Access range
• Only the connected CPU module can be accessed. Accessing another module will cause an error.
• Accessing another station on a network such as CC-Link is not allowed via the connected CPU module.
(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.
(5) File access during MC communication
The CPU module will perform file access processing prior to Ethernet communication processing. Because of this, processing of the MC protocol function may be delayed if a file is accessed by FTP or a programming tool during use of the MC protocol function.
When accessing a file while response time monitoring is performed on the connected device with the MC protocol function, add the time required for file access to the monitoring time.
5
39
40
(6) Receiving a response message
The following shows an example of receive processing on the other device side.
Communication processing on the other device side
Request message, send processing
Response message, receive processing
Is TCP connection open?
NO
YES
Received data within the time specified by the monitoring timer value?
YES
NO
Check the received data size.
NO
Sufficient receive data size?
YES
Processing for the response message
Was the entire received message processed?
YES
End
NO
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.
CHAPTER 5 MC PROTOCOL COMMUNICATION
5.4
Error Codes for 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
(Hexadecimal)
Description Corrective action
4000
C051
H
to 4FFF
0055
C050
H
H
H
to C054
C056
C058
C059
C05B
C05C
C05D
C05F
H
H
H
H
H
H
H
H
H
Errors detected by the CPU module
(Errors occurred in other than MC protocol communication)
Although online change is disabled, the connected device requested the RUN-state CPU module for data writing.
When "Communication Data Code" is set to ASCII Code, ASCII code data that cannot be converted to binary were received.
The number of read or write points is outside the allowable range.
The read or write request exceeds the maximum address.
The request data length after ASCII-to-binary conversion does not match the data size of the character area (a part of text data).
• The command and/or subcommand are specified incorrectly.
• The CPU module does not support the command and/or subcommand.
The CPU module cannot read data from or write data to the specified device.
The request data is incorrect. (e.g. reading or writing data in units of bits from or to a word device)
No monitor registration
The request cannot be executed to the CPU module.
Refer to the following manual.
MELSEC-L CPU Module User's Manual (Hardware Design,
Maintenance and Inspection)
• Before enabling online change, write the data.
• Change the CPU module state to STOP and write the data.
• Select Binary Code for "Communication Data Code", and restart the CPU module.
• 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 the CPU module.
Correct the start address or the number of read or write points, and resend the data to the CPU module.
(The maximum address must not be exceeded.)
Check and correct the text data or the request data length of the header, and resend the data to the CPU module.
• Check the request.
• Use commands and/or subcommands supported by the CPU module.
Check the device to be read or written.
Correct the request data and resend it to the CPU module.
(e.g. subcommand correction)
Perform monitor registration before monitoring.
• Correct the network number, PC number, request destination module I/O number, or request destination module station number.
• Correct the read/write request data.
C060
C061
C06F
C070
H
H
H
H
The request data is incorrect. (ex. incorrect specification of data for bit devices)
The request data length does not match the number of data in the character area (a part of text data).
The CPU module received a request message in ASCII format when "Communication Data Code" is set to Binary Code, or received it in binary format when the setting is set to ASCII Code.
(This error code is only registered to the error history, and no abnormal response is returned.)
The device memory extension cannot be specified for the target station.
Correct the request data and resend it to the CPU module.
Check and correct the text data or the request data length of the header, and resend the data to the CPU module.
• Send a request message that matches the "Communication Data
Code" setting.
• Change the "Communication Data Code" setting so that it will match the request message.
C0B5
C200
H
H
The CPU module cannot handle the data specified.
The remote password is incorrect.
Read data from or write data to the device memory without specifying the extension.
• Correct the request data.
• Stop the current request.
Correct the remote password, and unlock and lock the remote password function again.
C201
C204
H
H
The port used for communication is locked with the remote password.
Or, because of the remote password lock status with
"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 unlock processing of the remote password.
Unlock the remote password before communication.
From the device that requested the unlock processing, request for lock processing of the remote password.
5
41
CHAPTER 6
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
Program
SP.SOCSND instruction
SP.SOCRCV instruction
S.SOCRCVS instruction
Reading receive data
Socket communication receive area*
1
Connection No.1
Connection No.2
Connection No.3
to
Connection No.16
Receiving data
External device
*1 The area is used for storing data received from the connected open devices.
Remark
● For dedicated instructions used for the socket communication function, refer to:
● 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. (
42
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(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 external device 1 to port No.A of the CPU module
Port No.L
Sending data via TCP connection
Port No.B
Sending data via TCP connection
Port No.M
Sending UDP data from port No.C of the CPU module to port No.N of external device 3
External device 2
(IP address: zz.zz.zz.zz)
External device 3
(IP address: ww.ww.ww.ww)
Port No.C
Sending UDP data from port No.N of external device 3 to port No.C of the CPU module
Port No.N
6
43
6.1
Communication Using TCP
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)
(1) TCP connection
There are two types of open operation for TCP connection: Active open and Passive open.
Firstly, the device waiting for a TCP connection performs a Passive open at the specified port.
The other device performs an Active open by specifying the port number of the device which is waiting in Passive open state.
Through the above process, a TCP connection is established and communication is available.
(a) Active open
Active open is a TCP connection method, which actively opens a connection to the device that is passively waiting for a TCP connection.
(b) Passive open
The following two types of Passive open methods are available for TCP connection.
TCP connection method
Unpassive
Fullpassive
Description
Allows a connection regardless of the IP address and port number of the connected device.
(The IP address and port number of the device connected can be acquired using the
SP.SOCCINF instruction.)
Allows a connection to the device only when the specified IP address and port number are met.
A connection made by another device that does not have the specified IP address and port number is automatically disconnected before communication.
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.
44
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(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
Was data transfer completed?
NO
Send by the SP.SOCSND instruction, or receive by the
SP.SOCRCV or
S.SOCRCVS instruction.
YES (Completed, or disconnected by the external device.)
Close processing:
SP.SOCCLOSE instruction
End
(a) Parameter setting
The following parameters are set for the sample program.
Project window
[Parameter] [PLC Parameter] [Built-in Ethernet Port Setting] button
6
*1
Item
Protocol
Open System
TCP Connection
Host Station Port No.
Destination IP Address
Destination Port No.
Setting
TCP
Socket Communication
Active
1000
H
(Setting range: 0001
H
to 1387
H
, 1392
H
to FFFE
H
)
*1
192.168.3.40 (Setting range: 0.0.0.1 to 223.255.255.254)
1000
H
(Setting range: 0001
H
to FFFE
H
)
Do not specify 1388
H
to 1391
H
because these ports are used by the system. (
45
46
(b) Devices used in the program
The following table lists the device numbers and applications used in the sample program.
Device number
M1000
D100 to D109
M100 and M101
M1002
M1003
M3000
D3000 and D3001
M300 and M301
D300 to D303
M3002
M3003
M4000
M4001
SD1282
SD1284
SD1286
SD1288
D200 and D201
M200 and M201
M4002
M4003
M4004
D400 to D403
D5000 and D5001
M500 and M501
D500 and higher
M5002
M5003
Application
Open direction
SP.SOCOPEN instruction control data
SP.SOCOPEN instruction completion device
Normal open indication
Open error indication
Send direction
SP.SOCSND instruction control data
SP.SOCSND instruction completion device
Send data length and send data (6 bytes of 12
H,
34
H,
56
H,
78
H,
9A
H
, and BC
H
)
Normal send indication
Send error indication
Close direction
Disconnection by the other device
Open completion signal
Open request signal
Receive state signal
Connection state signal
SP.SOCCLOSE instruction control data
SP.SOCCLOSE instruction completion device
Normal close indication
Close error indication
Closing flag
SP.SOCRMODE instruction control data
SP.SOCRCV instruction control data
SP.SOCRCV instruction completion device
Receive data length and receive data
Normal receive indication
Receive error indication
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(c) Sample program
<<Fixed length mode setting>>
<<Connection No.1 open processing (Active)>>
<<Data sending>>
<<Data receiving>>
<<Connection No.1 close processing>>
*
1
Setting TCP receive mode to 1
Setting receive data size to 6
Changing TCP receive mode of
Connection No.1
Setting Execution/completion type to 0
Connection No.1 open
Normal completion
Error completion
Setting send data length
Setting send data
Sending data to Connection No.1
Normal completion
Error completion
Receiving data
Normal completion
Error completion
Processing for disconnection by the target
Connection No.1 close
Setting closing flag
Normal completion
Error completion
Resetting closing flag
*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. (
6
47
48
(d) Precaution for Active open communication
Configure an interlock circuit using the Open completion signal (SD1282) and Open request signal (SD1284) in the program.
The following chart shows on/off timings of the Open completion signal and Open request signal.
<When disconnected by the CPU module>
TCP disconnection completed upon response from the external device
Open completion signal
ON
(SD1282)
OFF
Open request signal
(SD1284)
ON
OFF
TCP disconnection request from the CPU module
SOCOPEN instruction
SOCCLOSE instruction
<When disconnected by the external device>
TCP disconnection request from the external device
TCP disconnection completed upon response from the CPU module
SOCCLOSE instruction
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(3) Program example for Passive open
The following shows a communication flow of a Passive open.
Start Waiting for TCP connection in
Passive open state.
Send or receive?
YES
Send by the SP.SOCSND instruction, or receive by the SP.SOCRCV or
S.SOCRCVS instruction.
NO
(a) Parameter setting
The following parameters are set for the sample program.
Project window
[Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
button
6
*1
*2
Item
Protocol
Open System
TCP Connection
Host Station Port No.
Destination IP Address
Destination Port No.
Setting
TCP
Socket Communication
Unpassive
1000
H
(Setting range: 0001
H
to 1387
H
, 1392
H
to FFFE
H
)
*2
Blank
*1
(Setting range: 0.0.0.1 to 223.255.255.254)
Blank
*1
(Setting range: 0001
H
to FFFE
H
)
When "Fullpassive" is selected for "TCP Connection", a value must be set.
Do not specify 1388
H
to 1391
H
because these ports are used by the system. (
49
50
(b) Devices used in the program
The following table lists the device numbers and applications used in the sample program.
Device number
M3000
D3000 and D3001
M300 and M301
D300 to D303
M3002
M3003
D400 to D403
SD1282
SD1286
D5000 and D5001
M500 and M501
D500 and higher
M5002
M5003
D6000 and D6001
D6010 to D6014
Application
Send direction
SP.SOCSND instruction control data
SP.SOCSND instruction completion device
Send data length and send data (6 bytes of 12
H,
34
H,
56
H,
78
H,
9A
H
, and BC
H
)
Normal send indication
Send error indication
SP.SOCRMODE instruction control data
Open completion signal
Receive state signal
SP.SOCRCV instruction control data
SP.SOCRCV instruction completion device
Receive data length and receive data
Normal receive indication
Receive error indication
SP.SOCCINF instruction control data
SP.SOCCINF instruction completion device
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(c) Sample program
<<Fixed length mode setting>>
<<Target checking>>
<<Data sending>>
<<Data receiving>>
*
1
Setting TCP receive mode to 1
Setting receive data size to 6
Changing TCP receive mode of
Connection 1
*
2
Obtaining information of connected device
Setting send data length
Setting send data
Sending data to Connection No.1
Normal completion
Error completion
Receiving data
Normal completion
Error completion
*1
*2
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. (
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.)
6
51
52
(d) Precaution for Passive open communication
• Configure an interlock circuit using the Open completion signal (SD1282) and Open request signal
(SD1284) in the program.
The following chart shows on/off timings of the Open completion signal and Open request signal.
TCP disconnection completed by the external device
Open completion signal
(SD1282)
ON
OFF
Open request signal
(SD1284)
ON
OFF
Always on
TCP connection completed by the external device
• 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:
• 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 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 from the device.
• Do not execute the SP.SOCCLOSE instruction in a program.
Doing so will disable data transfer since the Open completion signal and Open request signal of the corresponding connection turn off for close processing.
To reopen a closed connection, execute the SP.SOCOPEN instruction.
For the SP.SOCOPEN instruction, refer to:
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
6.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
(1) Program example
This section provides a program example for communication using UDP.
(a) Parameter setting
The following parameters are set for the sample program.
Project window
[Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
button
6
*1
Item
Protocol
Open System
TCP Connection
Host Station Port No.
Destination IP Address
Destination Port No.
Setting
UDP
Socket Communication
Blank
1000
H
(Setting range: 0001
H
to 1387
H and 1392
H
to FFFE
H
)
*1
192.168.3.40 (Setting range: 0.0.0.1 to 223.255.255.254/255.255.255.255)
1000
H
(Setting range: 0001
H
to FFFE
H
/FFFF
H
)
Do not specify 1388
H
to 1391
H
because these ports are used by the system. (
53
54
(b) Devices used in the program
The following table lists the device numbers and applications used in the sample program.
Device number
M3000
D3000 and D3001
M300 and M301
D300 and D303
M3002
M3003
D5000 to D5001
M500 to M501
SD1282
SD1286
SD1288
M3001
D500 and higher
M5002
M5003
D400 to D404
D450 to D451
D460 to D464
Application
Send direction
SP.SOCSND instruction control data
SP.SOCSND instruction completion device
Send data length and send data (6 bytes of 12
H
, 34
H
, 56
H
, 78
H
, 9A
H
, and BC
H
)
Normal send indication
Send error indication
SP.SOCRCV instruction control data
SP.SOCRCV instruction completion device
Open completion signal
Receive state signal
Connection state signal
Target change direction
Receive data length and receive data
Normal receive indication
Receive error indication
SP.SOCCSET instruction control data
SP.SOCCINF instruction control data
SP.SOCCINF instruction connection information
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(c) Sample program
<<Target changing>>
<<Data sending>>
<<Data receiving>>
*
1
Setting target IP address
Setting target port No.
Changing setting of
Connection No.1
Setting send data length
Setting send data
Sending data to Connection No.1
Normal completion
Error completion
*
2
Obtaining information of target device
Receiving data
Normal completion
Error completion
*1
*2
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. (
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.)
6
55
(2) Simultaneous broadcast
For simultaneous broadcast using UDP, set the parameters as follows.
• Destination IP Address: FF.FF.FF.FF
H
• Destination Port No.: FFFF
H
CPU module
(IP address: xx.xx.xx.xx, Subnet mask: 255.255.255.0)
Ethernet
Port No.A
Sending data from port No.A of the
CPU module to each port No.N of all external devices.
Port No.L
Port No.N
External device 1
(IP address: xx.xx.xx.yy)
Port No.M
Port No.N
External device 2
(IP address: xx.xx.xx.zz)
External device 3
(IP address: xx.xx.xx.ww)
Port No.N
Destination IP Address Destination Port No.
Other than FF.FF.FF.FF
Other than FF.FF.FF.FF
FF.FF.FF.FF
FF.FF.FF.FF
H
H
H
H
Other than FFFF
FFFF
Other than FFFF
FFFF
H
H
H
H
Receiving
Receives only the data sent from the specified IP address and port No. among the entire data sent to the host station port No.
Sending
Sends data from the host station port No. to the specified IP address and port
No.
Receives the data sent from all ports of the specified
IP address among the entire data sent to the host station port No.
Receives the data sent from the specified port No. of all the IP addresses among the entire data sent to the host station port No.
Receives all data that have sent to the host station port No.
N/A
Sends data to the port No. specified in the settings for simultaneous broadcast.
N/A
56
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(3) Precautions
(a) Use of UDP
Data may be lost, or may arrive out of order.
Consider the application of TCP if any problem is expected.
(b) Sending and receiving data
Data sending process may be terminated even if the communication line between the CPU module and target device is not connected due to a reason such as cable disconnection.
To avoid this, it is recommended to provide communication procedures at the user’s discretion.
(c) Changing the target
Use the SP.SOCCSET instruction to change the target device.
For the SP.SOCCSET instruction, refer to:
(d) Open completion signal and Open request signal
Once UDP is selected for a connection, the Open completion signal and Open request signal of the connection are always on.
(e) SP.SOCCLOSE instruction
Do not execute the SP.SOCCLOSE instruction in the program.
Doing so will disable data transfer since the Open completion signal and Open request signal of the corresponding connection turn off for close processing.
To reopen the closed connection, execute the SP.SOCOPEN instruction.
For the SP.SOCOPEN instruction, refer to:
(f) Simultaneous broadcast targets
With simultaneous broadcast, data can be sent to the devices which are connected to the same hub of the
CPU module, and to those connected to the cascaded hub(s).
Data cannot be received from the devices connected through routers.
(g) Receiving data using simultaneous broadcast
When data are received through a connection of simultaneous broadcast, the IP address and port number of the sender can be acquired by the SP.SOCCINF instruction.
For the SP.SOCCINF instruction, refer to:
(h) Connection of simultaneous broadcast
Data cannot be sent when FFFF
H
is specified for the port number of the transmission target.
To send data, specify a value other than FFFF
H.
6
57
58
(i) Destination IP address of the message transferred by simultaneous broadcast
Use a CPU module IP address of which all the bits corresponding to the host address are on.
When the subnet musk pattern is specified, apply the pattern before using the above mentioned IP address.
Ex.
168.
3.
39
IP address of the CPU module side
Subnet mask pattern
IP address of simultaneous broadcast
:
:
:
64.
None
64.
255.
255.
255
Ex.
IP address of the CPU module side
Subnet mask pattern
IP address of simultaneous broadcast
:
:
:
64.
255.
64.
168.
255.
168.
3.
255.
3.
39
0
255
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
6.3
Precautions for the Socket Communication Function
This section provides other precautions for the socket communication function.
(1) Port number
Host station port number, 0001
H
to 03FF
H
, are assigned for reserved port numbers (WELL KNOWN PORT
NUMBERS) and F000
H
to FFFE
H
are for other communication functions. Therefore, using 0400
H
to 1387
H
and
1392
H
to EFFF
H
is recommended.
Do not specify 1388
H
to 1391
H
because these ports are used by the system. (
Do not specify 0014
H
and 0015
H
for the socket communication function when using the FTP function.
Do not specify 007B
H for the socket communication function when using the time setting function (SNTP).
Do not specify F000
H
to FFFE
H
for the socket communication function when using the data logging file transfer function.
(2) Reading out received data
Read out received data when the Receive state signal (SD1286) has turned on.
Communication via the built-in Ethernet port may be affected if a considerable amount of received data have not been read out for a long time.
(3) Conditions for closing
In TCP communications, even if no close request is sent from the connected device, the Open completion signal will turn off to close the connection in the following cases.
• Alive check is timed out.
• Forced close is received from the connected device.
(4) Elements for TCP connection
The following four elements control TCP connections, and only one connection can be established with a unique setting for these elements. To use multiple TCP connections at the same time, at least one of the four elements must be different.
• IP address of the CPU module
• Port number of the CPU module
• IP address of the target device
• Port number of the target device
(5) Reestablishment of the same connection
Allow eight seconds or more before reestablishing a connection of the same target IP address, the same host station port number, and the same target port number after closing it.
If the reestablishment is time-critical, it is recommended to change the host station port number on the Active open side.
(6) Precautions for file access during communication
The CPU module will perform file access processing prior to Ethernet communication processing. Because of this, processing of the socket communication function may be delayed if a file is accessed by FTP or a programming tool during the processing.
When accessing a file while response time monitoring is performed on the connected device with the socket communication function, add the time required for file access to the monitoring time.
6
59
60
(7) Checking receive data length
Since no delimiter is provided for TCP communication data, on the receiving end, separate data blocks that are sent continuously may be combined, or data sent all at once may be segmented.
The receive data length must be confirmed on the receiving side as necessary.
When data are received on the CPU side and the data length is determined, the fixed-length mode is recommended.
When receiving data on the target device side, confirm the receive data length as shown below.
Receive processing on the other device side
Received message, receive processing
Is TCP connection open?
NO
Receive the rest of the message.
YES
Received data within the time specified by the monitoring timer value?
NO
YES
Check the received data size.
NO
Sufficient receive data size?
YES
Processing for the received message
Was the entire received message processed?
YES
End
NO
TCP connection is closed.
Error handling
(8) If an error (error code: 41A0
H
) has occurred
In TCP communications, if an error (error code: 41A0
H
) occurs at the sender, part of send data may have been sent. Therefore, if the data are sent again after the error (error code: 41A0
H
), close the connection to discard the data. Then open a connection again, and send the data again.
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
6.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.
The following is a list of the instructions.
Instruction
SP.SOCOPEN
SP.SOCCLOSE
SP.SOCRCV
S.SOCRCVS
SP.SOCSND
SP.SOCCINF
SP.SOCCSET
SP.SOCRMODE
S(P).SOCRDATA
Description
Establishes a connection.
Closes a connection.
Reads out received data (in END processing).
Reads out received data (upon instruction execution).
Sends data.
Reads out connection information.
Changes the target of the connection for UDP/IP communication.
Changes receive mode of the connection.
Reads out data from the socket communication receive data area.
Reference
6
● For configuration of data communication using the socket communication function, refer to:
● 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.
MELSEC-Q/L Programming Manual (Common Instruction)
61
6.4.1
Establishing a connection (SP.SOCOPEN)
SP.SOCOPEN
Command
SP.SOCOPEN
U0 S1 S2 D
*1
Setting data
S1
S2
D
Internal device
Bit Word
-
-
*1
*1
-
R, ZR
*1
*1
Bit
J\
Word
File registers set for each local device or program cannot be used.
-
-
-
U\G
Zn
Constant
K, H
Others
-
-
-
-
-
(1) Setting data
Setting data
U0
S1
S2
D
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which control data are stored
Start number of the device which turns on for one scan upon completion of the instruction
D
+1 also turns on when failed.
*2
Set by
*2
-
User
User, system
System
The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCOPEN instruction.
System: The CPU module stores the execution result of the SP.SOCOPEN instruction.
Data type
Character string
BIN 16-bit
Device name
Bit
62
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(2) Control data
Device Item Description
Specify which settings are used to open a connection, parameter settings configured by a programming tool or control data settings
S2
+2
Setting range
Set by
*3
S2
S2
+0
+1
Execution/ completion type
Completion status
0000
H
:
Connection is opened according to the settings set in "Open settings" of PLC parameter.
8000
H
:
Connection is opened according to the values specified for control data
S2
+2 to
S2
+9.
Completion status is stored
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
0000
8000
-
H
H
User
System
*3
*4
*5
S2
S2
S2
S2
S2
+2
+3
+4
+5
+6
Application setting area
S2 +2 b15 b14 b13
[3] to
0 b10 b9 b8 b7
[2] [1] to
0
[1] Communication method (protocol)
0: TCP/IP
1: UDP/IP
[2] Socket communication procedure
1: Nonprocedural (fixed)
[3] Open system
00: Active open or UDP/IP
10: Unpassive open
11: Fullpassive open
Host station port number
Specify the port number of the host station.
b0
Target device IP address
*4
Target device port number
*4
Specify the IP address of the target device.
Specify the port number of the target device.
-
1
H
to 1387
H
1392
H
to FFFE
H
1
H
to FFFFFFFF
H
(FFFFFFFF
H
:
Simultaneous broadcast)
1
H
to FFFF
H
(FFFF
H
:
Simultaneous broadcast)
User
S2
+7 to
S2
+9
Use prohibited System
The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCOPEN instruction.
System: The CPU module stores the execution result of the SP.SOCOPEN instruction.
For the Unpassive open, the IP address and port number of the target device are ignored.
Because host station port numbers, 0001
H
to 03FF
H
, are assigned for generally reserved port numbers (WELL KNOWN
PORT NUMBERS) and F000
H
to FFFE
H
are used for other communication functions, using 0400
H
to 1387
H
and 1392
H to EFFF
H
is recommended. Do not specify 1388
H
to 1391H because these ports are used by the system. (
6
63
64
(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.
When failed
Turns on in the END processing of the scan after the SP.SOCOPEN instruction is completed and turns off in the next END processing.
END processing END processing END processing
Program
SP.SOCOPEN instruction executed
SP.SOCOPEN instruction
ON
OFF
Completion device D +0
ON
When failed
OFF
Completion device D +1
Connection open
1 scan when normally completed
• A connection with no parameters (no protocol is specified) can be opened. In this case, specify 8000
H
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 connection number specified for
S1
is other than 1 to 16.
• The device numbers specified for
S2
and
D
exceed the device point range.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4101)
(Error code: 4004)
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(5) Program examples
(a) Opening a connection using parameter settings
When M1000 is turned on, connection No.1 is opened using the parameters set in "Open settings" of PLC parameter.
• Devices used
Device number Application
SD1282
SD1284
SD1288
D100
M100
Open completion signal
Open request signal
Connection state signal
SP.SOCOPEN instruction control data
SP.SOCOPEN instruction completion device
• Program
Setting Execution/ completion type to 0
H
Connection No.1 open
Normal completion
Error completion
6
65
66
(b) Opening a connection using control data settings
When M1000 is turned on, connection No.1 is opened using control data.
• Devices used
Device number
SD1282
SD1284
SD1288
D100
M100
Open completion signal
Application
Open request signal
Connection state signal
SP.SOCOPEN instruction control data
SP.SOCOPEN instruction completion device
• Program
Setting Execution/ completion type to 8000
H
Setting Application area to 200
H
(TCP/IP, Active open)
Setting port No. of host station to 4096
Setting target IP address to 10.97.79.14
Setting port No. of target device to 4096
Connection No.1 open
Normal completion
Error completion
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
6.4.2
Disconnecting a connection (SP.SOCCLOSE)
SP.SOCCLOSE
Command
SP.SOCCLOSE
U0 S1 S2 D
*1
Setting data
S1
S2
Internal device
Bit Word
-
*1
-
*1
-
R, ZR
*1
*1
Bit
J\
Word
D
File registers set for each local device or program cannot be used.
-
-
-
U\G
Zn
Constant
K, H
Others
-
-
-
-
(1) Setting data
Setting data
U0
S1
S2
D
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which control data are stored
Start number of the device which turns on for one scan upon completion of the instruction
D
+1 also turns on when failed.
*2
Set by
*2
-
User
System
The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCCLOSE instruction.
System: The CPU module stores the execution result of the SP.SOCCLOSE instruction.
(2) Control data
*3
Device
S2
+0
S2
+1
Item
System area
Completion status
Description
-
Completion status is stored
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
Setting range
The "Set by" column indicates the following.
System: The CPU module stores the execution result of the SP.SOCCLOSE instruction.
-
-
Data type
Character string
BIN 16-bit
Device name
Bit
Set by
*3
-
System
6
67
68
(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
When completed
Remains off.
Description
When failed
Turns on in the END processing of a scan after completion of the SP.SOCCLOSE instruction, and turns off in the next END processing.
END processing END processing END processing
Program
SP.SOCCLOSE instruction executed
SP.SOCCLOSE instruction
Completion device D +0
OFF
Completion device D +1
OFF
ON
ON
When failed
Connection close
1 scan when 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 connection number specified for
S1
is other than 1 to 16.
• The device numbers specified for
S2
and
D
exceed the device point range.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4101)
(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.
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(5) Program example
When M2000 is turned on or when the connected device disconnects connection No.1, connection No.1 is disconnected by the following program.
• Devices used
Device number
SD1282
SD1284
D200
M200
• Program
Application
Open completion signal
Open request signal
SP.SOCCLOSE instruction control data
SP.SOCCLOSE instruction completion device
Processing for disconnection of
Connection No.1by the target
Connection No.1 close
Setting SP.SOCCLOSE executing flag
Normal completion
Error completion
Resetting SP.SOCCLOSE executing flag
6
69
6.4.3
Reading out received data in the END processing (SP.SOCRCV)
70
SP.SOCRCV
Command
SP.SOCRCV
U0
S1 S2 D1 D2
*1
Setting data
S1
S2
D1
Internal device
Bit Word
-
-
*1
-
*1
*1
-
R, ZR
*1
*1
*1
Bit
J\
Word
-
-
-
-
U\G
D2
File registers set for each local device or program cannot be used.
Zn
Constant
K, H
Others
-
-
-
-
-
-
(1) Setting data
Setting data
U0
S1
S2
D1
D2
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which control data are specified
Start number of the device from which receive data are stored
Start number of the device which turns on for one scan upon completion of the instruction
D2
+1 also turns on when failed.
*2 The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCRCV instruction.
System: The CPU module stores the execution result of the SP.SOCRCV instruction.
Set by
*2
-
User
System
(2) Control data
*3
Device
S2
+0
S2
D1
+1
+0
D1
+1 to
D1
+n
Item
System area
Completion status
Receive data length
Receive data
Description
-
Completion status is stored.
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
The length of the data which were read out from the Socket communication receive data area is stored (in bytes).
The data which were read out from the Socket communication receive data area are stored in order.
Setting range
-
The "Set by" column indicates the following.
System: The CPU module stores the execution result of the SP.SOCRCV instruction.
-
0 to 2046
-
Data type
Character string
BIN 16-bit
Device name
Bit
Set by
*3
-
System
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
● 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.
(3) Function
data area in the END processing after execution of the SP.SOCRCV instruction.
CPU module
D1 +0
Receive data length
Receive data
D1 +1
D1 +2 Receive data
Socket communication receive data area
Connection
No. specified by S1
SP.SOCRCV
(Reading receive data)
Receiving
External device
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.
6
71
72
• Completion device
D2
+1
Turns on or off according to the result of the SP.SOCRCV instruction.
State
When completed
When failed
Description
Remains off
Turns on in the END processing of the scan after completion of the SP.SOCRCV instruction, and turns off in the next END processing.
The following figure shows the timing of reception processing with the SP.SOCRCV instruction.
Open completion signal (SD1282, n)
ON
OFF
Sequence program
Reception status signal (SD1286, n)
SP.SOCRCV instruction
Completion
D2 device
ON
OFF
Completion device
D2
+1
ON
OFF
Open processing
Data transmission processing
END processing
Data read processing
END processing
END processing
SP.SOCRCV instruction execution
1 scan
Abnormal termination
ACK
(TCP only)
Data read processing
CHAPTER 6 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 connection number specified for
S1
is other than 1 to 16.
• The received data size exceeds the size of the receive data storage device.
(Error code: 4101)
(Error code: 4101)
• The device numbers specified for
S2
,
D1
, and
D2
exceed the device point range.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4004)
(5) Program example
When M5000 is turned on, data received from the connected device are read out.
• Devices used
Device number
SD1282
SD1286
D5000
D500
M500
Application
Open completion signal
Receive state signal
SP.SOCRCV instruction control data
Receive data length and receive data storage location
SP.SOCRCV instruction completion device
• Program
Reading receive data of Connection
No.1
Normal completion
Error completion
6
● 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.
73
6.4.4
Reading out received data during instruction execution
(S.SOCRCVS)
Command
S.SOCRCVS
S.SOCRCVS
U0
S D
Setting data
S
D
Internal device
Bit Word
-
-
R, ZR
Bit
J\
Word
-
-
U\G
Zn
Constant
K, H
Others
-
-
(1) Setting data
Setting data
U0
S
D
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which received data are stored
*1 The "Set by" column indicates the following.
User: The data must be set before executing the S.SOCRCVS instruction.
System: The CPU module stores the execution result of the S.SOCRCVS instruction.
Set by
*1
-
User
System
(2) Control data
Device
*2
D
+0
D
+1
to
D
+n
Item
Receive data length
Receive data
Description
The length of the data which were read out from the Socket communication receive data area is stored (in bytes).
The data which were read out from the Socket communication receive data area are stored in ascending order of addresses.
Setting range
The "Set by" column indicates the following.
System: The CPU module stores the execution result of the S.SOCRCVS instruction.
0 to 2046
-
Data type
Character string
BIN 16-bit
Device name
Set by
*2
System
When odd-byte data are received, an invalid byte is inserted to the upper byte of the device that stores the last receive data.
74
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(3) Function
This instruction reads out received data of the connection specified in
S
from the Socket communication receive data area.
D +0
Receive data length
Receive data
D +1
D +2
Receive data
CPU module
Socket communication receive data area
Connection
No. specified by S
S.SOCRCV
(Reading receive data)
Receiving
External device
D +n
Receive data
The following figure shows the timing of reception processing with the S.SOCRCVS instruction.
Open processing
Data reception processing
Data read processing
ON
OFF
END processing
END processing
Open completion signal (SD1282, n)
Sequence program
Reception status signal (SD1286, n)
S.SOCRCVS instruction
S.SOCRCVS instruction execution
Data read processing
ACK (TCP only)
6
(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 connection number specified for
S
is other than 1 to 16.
• The received data size exceeds the size of the receive data storage device.
• The device number specified for
D
exceeds the device point range.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4101)
(Error code: 4101)
(Error code: 4004)
75
76
(5) Precaution
Do not use both this and SP.SOCRCV instructions when reading out receive data of the same connection.
(6) Program example
When M5000 is turned on, data received from the connected device are read out.
• Devices used
Device number
SD1282
SD1286
D5000
Application
Open completion signal
Receive state signal
Receive data length and receive data storage location
• 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.
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
6.4.5
Sending data (SP.SOCSND)
SP.SOCSND
Command
SP.SOCSND
U0 S1
S2
S3
D
*1
Setting data
S1
S2
S3
Internal device
Bit Word
-
-
*1
-
*1 -
R, ZR
*1
Bit
J\
Word
D
*1
File registers set for each local device or program cannot be used.
-
-
-
-
U\G
Zn
Constant
K, H
Others
-
-
-
-
-
-
(1) Setting data
Setting data
U0
S1
S2
S3
D
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device where control data are specified
Start number of the device from which send data are stored
Start number of the device which turns on for one scan upon completion of the instruction
D
+1 also turns on when failed.
*2 The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCSND instruction.
System: The CPU module stores the execution result of the SP.SOCSND instruction.
Set by
*2
-
User
System
User
System
Data type
Character string
BIN 16-bit
Device name
Bit
6
77
78
(2) Control data
Device
S2
+0
S2
+1
S3
+0
Item Description
System area
Completion status
-
Completion status is stored.
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
Send data length The length of send data is specified (in bytes).
S3
+1 to
S3
+n
Send data Send data are specified.
*3 The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCSND instruction.
System: The CPU module stores the execution result of the SP.SOCSND instruction.
Setting range
-
-
1 to 2046
-
Set by
*3
-
System
User
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.
(3) Function
This instruction sends data set in
S1
to the target device of the connection specified by
S3
.
S3 +0
S3 +1
S3 +2
CPU module
Send data length
Send data
Send data
External device
SP.SOCSND
(Sending 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
When completed Remains off.
When failed
Turns on in the END processing of the scan after completion of the SP.SOCSND instruction, and turns off in the next END processing.
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
The following figure shows the timing of reception processing with the SP.SOCRCV instruction.
<Transmission control method>
Open processing
Data transmission processing
Open completion signal (SD1282, n)
ON
OFF
END processing
Sequence program
END processing
END processing
SP.SOCSND instruction execution
SP.SOCSND instruction
Completion device
D
Completion device
D +1
ON
OFF
ON
OFF
Data transmission processing
1 scan
Abnormal termination
*1 Data transmission may continue
even though the completion
device turns on.
ACK (TCP only)
*
1
(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 connection number specified for
S1
is other than 1 to 16.
• The device numbers specified for
S2
,
S3
, and
D exceed the device point range.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4101)
(Error code: 4004)
6
79
80
(5) Program example
When M3000 is turned on, data (1234, 5678, and 8901) are sent to the target device using the socket communication function.
• Devices used
Device number
SD1282
D3000
D300
M300
Application
Open completion signal
SP.SOCSND instruction control data
Send data length and send data storage location
SP.SOCSND instruction completion device
• Program
Setting send data length
Setting send data
Sending data to
Connection No.1
Normal completion
Error completion
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
6.4.6
Reading out connection information (SP.SOCCINF)
SP.SOCCINF
Command
SP.SOCCINF
U0 S1 S2 D
Setting data
S1
S2
D
Internal device
Bit Word
-
-
-
R, ZR
Bit
J\
Word
-
-
-
U\G
Zn
Constant
K, H
Others
-
-
-
-
-
6
(1) Setting data
Setting data
U0
S1
S2
D
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which control data are stored
Start number of the device from which connection information is stored
*1 The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCCINF instruction.
System: The CPU module stores the execution result of the SP.SOCCINF instruction.
Set by
*1
-
User
System
Data type
Character string
BIN 16-bit
Device name
81
82
(2) Control data
*2
*3
Device
S2
+0
S2
+1
Item
System area
Completion status
Description
-
Completion status is stored.
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
Setting range
-
-
Set by
-
*2
D
D
D
D
+0
+1
+2
+3
Target device IP address
Target device port number
Host station port number
IP address of the target device is stored.
Port number of the target device is stored.
Port number of the host station is stored.
1
H
to FFFFFFFF
H
0
H
: No target
(FFFFFFFF
H
:
Simultaneous broadcast)
1
H
to FFFF
H
(FFFF
H
:
Simultaneous broadcast)
1
H
to 1387
H
1392
H
to FFFE
H
*3
System
D
+4
Application setting area
D +4 b15 b14 b13
[3] to
0 b10 b9 b8 b7
[2] [1] to
0
[1] Communication method (protocol)
0: TCP/IP
1: UDP/IP
[2] Socket communication procedure
1: Nonprocedural (fixed)
[3] Open system
00: Active open or UDP/IP
10: Unpassive open
11: Fullpassive open b0
-
The "Set by" column indicates the following.
System: The CPU module stores the execution result of the SP.SOCCINF instruction.
Using 0400
H
to 1387
H
and 1392
H
to EFFF
H
is recommended because the host station port numbers, 0001
H
to 03FF
H
, are assigned for generally reserved port numbers (WELL KNOWN PORT NUMBERS), and F000
H
to FFFE
H
are used for other communication functions. Do not specify 1388
H
to 1391
H
because these ports are used by the system.
(
(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 connection number specified for
S1
is other than 1 to 16.
• The device numbers specified for
S2
and
D
exceed the device point range.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4101)
(Error code: 4004)
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(5) Program example
When M5000 is turned on, connection information of connection No.1 is read out.
• Devices used
Device number
D500
D5000
Application
SP.SOCSND instruction control data
Storage location of connection information
• Program
Reading connection information of
Connection No.1
6
83
6.4.7
Changing the target of a connection (UDP/IP) (SP.SOCCSET)
Command
SP.SOCCSET
SP.SOCCSET
U0 S1 S2
Setting data
S1
S2
Internal device
Bit Word
-
-
R, ZR
Bit
J\
Word
-
-
U\G
Zn
Constant
K, H
-
Others
-
-
(1) Setting data
Setting data
U0
S1
S2
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which control data are stored
*1 The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCCSET instruction.
System: The CPU module stores the execution result of the SP.SOCCSET instruction.
Set by
*1
-
User
User, System
(2) Control data
*2
Device
S2
+0
S2
+1
Item
System area
Completion status
Description
-
Completion status is stored.
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
Setting range
-
-
S2
S2
S2
+2
+3
+4
Target device IP address
Target device port number
IP address of the target device is specified.
Port number of the target device is specified.
The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCCSET instruction.
System: The CPU module stores execution result of the SP.SOCCSET instruction.
1
H
to FFFFFFFF
H
(FFFFFFFF
H
:
Simultaneous broadcast)
1
H
to FFFF
H
(FFFF
H
:
Simultaneous broadcast)
Data type
Character string
BIN 16-bit
Device name
Set by
*2
-
System
User
84
CHAPTER 6 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
.
(Note that this instruction is available only for UDP/IP communications.)
● 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 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.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4004)
(5) Precaution
Do not change the target device using the SP.SOCCSET instruction during execution of the SP.SOCSND instruction.
(6) Program example
When M4000 is turned on, the connection destination (IP address and port number of the target device) of connection No.1, which is open, is changed.
• Devices used
Device number
SD1282
D400
Application
Open completion signal
SP.SOCCSET instruction control data
• Program
Setting target IP address to
10.97.85.222
Setting port No. of target device to 8193
Changing setting of
Connection No.1
6
85
6.4.8
Changing the receive mode of a connection (SP.SOCRMODE)
Command
SP.SOCRMODE
SP.SOCRMODE
U0 S1 S2
Setting data
S1
S2
Internal device
Bit Word
-
-
R, ZR
Bit
J\
Word
-
-
U\G
Zn
Constant
K, H
-
Others
-
-
(1) Setting data
Setting data
U0
S1
S2
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which control data are stored
*1
Set by
*1
-
User
User, System
The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCRMODE instruction.
System: The CPU module stores the execution result of the SP.SOCRMODE instruction.
Data type
Character string
BIN 16-bit
Device name
(2) Control data
Device
S2
+0
S2
+1
S2
+2
S2
+3
Item
System area
Completion status
TCP receive mode
*2
Receive data size
Description
-
Completion status is stored.
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
TCP receive mode is stored.
0: TCP standard receive mode
1: TCP fixed-length receive mode
Receive data size in the socket communication is stored (in bytes).
*2
*3
Setting range
-
-
0 or 1
1 to 2046
Invalid for connections in UDP communications.
The "Set by" column indicates the following.
User: The data must be set before executing the SP.SOCRMODE instruction.
System: The CPU module stores the execution result of the SP.SOCRMODE instruction.
Set by
*3
-
System
User
(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.)
86
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
(a) TCP standard receive mode
When data are received, they are stored in the Socket communication receive data area, and SD1286 turns on.
If data are received exceeding the specified receive data size, the excess data are read out the next time.
Reading receive data
SP.SOCRCV or
S.SOCRCVS instruction
Data reading
SP.SOCRCV or
S.SOCRCVS instruction
Data reading
Socket communication receive data area
Data stored
(300 bytes)
Data stored
(200 bytes)
SD1286
ON
OFF
Data reception
(500 bytes)
(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.
If data are received exceeding the specified receive data size, the excess data are read out the next time.
6
Reading receive data
Socket communication receive data area
SD1286
Data stored
(200 bytes)
ON
OFF
Data reception
(200 bytes)
Data cannot be read out because the receive data size is not reached.
Data stored
(300 bytes)
SP.SOCRCV or
S.SOCRCVS instruction
Data reading
The remaining 100 bytes will be stored at the next data reception (200 bytes).
Data reception
(200 bytes)
● 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.
87
88
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 connection number specified for
S1
is other than 1 to 16.
• The device number specified for
S2
exceeds the device point range.
• Invalid device is specified.
(Error code: 4101)
(Error code: 4101)
(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.
(5) Program example
When M4000 is turned on, connection No.1 is set to the TCP fixed-length receive mode and the receive data size is set to 256 bytes.
After execution of the instruction and when the receive data size of connection No.1 reaches 256 bytes, the
Receive state signal is turned on.
• Device used
D400
Device number Application
SP.SOCRMODE instruction control data
• Program
Setting TCP receive mode to 1
Setting receive data size to 256
Changing receive mode of
Connection No.1
CHAPTER 6 SOCKET COMMUNICATION FUNCTION
6.4.9
Socket communication receive data read (S(P).SOCRDATA)
S.SOCRDATA
SP.SOCRDATA
Command
Command
S.SOCRDATA
U0 S1 S2 D n
SP.SOCRDATA
U0 S1 S2 D n
Setting data
S1
S2
D n
-
-
-
Internal device
Bit Word
-
R, ZR
Bit
J\
Word
-
-
-
-
U\G
Zn
Constant
K, H
Others
-
-
-
-
-
6
(1) Setting data
Setting data
U0
S1
S2
D n
Description
Dummy
Connection number (Setting range: 1 to 16)
Start number of the device from which control data are stored
Start number of the device where read data are stored
Number of read data (1 to 1024 words)
*1 The "Set by" column indicates the following.
User: The data must be set before executing the S(P).SOCRDATA instruction.
Set by
*1
-
User
Data type
Character string
BIN 16-bit
Device name
BIN 16-bit
(2) Control data
*2
Device
S2
+0
S2
+1
Item
System area
Completion status
Description
-
Completion status is stored.
0000
H
: Completed
Other than 0000
H
: Failed (Error code)
Setting range
The "Set by" column indicates the following.
System: The CPU module stores the execution result of the S(P).SOCRDATA instruction.
-
-
Set by
*2
-
System
(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 , and stores them in the device specified in
D
or higher. No processing is performed when the number of read data (n) is 0.
89
90
● 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.
(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 connection number specified for
S1
is other than 1 to 16.
(Error code: 4101)
• The device numbers specified for
S2
ÅC
D
, and n1 exceed the device point range.
• An invalid device is specified.
(Error code: 4101)
(Error code: 4004)
(5) Program example
When M4000 is turned on, the receive data length of connection No.1 is read out.
• Devices used
Device number
SD1282
SD1286
D400
D4000
K1
Application
Open completion signal
Receive state signal
S.SOCRDATA instruction control data
Storage location where data are read out
Number of read data (one word)
• Program
Reading receive data length of Connection
No.1
CHAPTER 7 TIME SETTING FUNCTION (SNTP CLIENT)
CHAPTER 7
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.
The time setting can performed at the following timing.
• When the programmable controller is powered off and then on, or is reset
• At the specified time intervals (Execution interval)
• At the specified clock time (Execution time)
• According to the special relay state
*1
*1 Time is set when SM1270 is turned on for one scan.
Time query
CPU module
LAN
Setting server time in the CPU module
7
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. (
91
7.1
Setting Method
Configure the time settings in the Built-in Ethernet port tab of the PLC parameter dialog box.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting] button
Item
SNTP Function Setting
SNTP Server IP Address
Time Zone
Execute time setting at turn ON/ reset
At Error Occurrence
Execution Interval
*1
Execution Time
*1
Description
Select whether to use this function or not.
Specify the IP address of the SNTP server.
Setting range
Used or Not used
0.0.0.1 to
223.255.255.254
(GMT-12:00 to
GMT+13:00)
Specify a time zone in which the time is to be synchronized. Japan
Standard Time "GMT+9:00".is set by default.
Select whether to execute the time setting function upon power-on or reset of the CPU module.
Select whether to stop or continue the time setting when an error is detected upon power-on or reset of the CPU module.
-
Continue or Stop
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 increments of 30 minutes)
00:00 to 23:30
*1 Either of these two options must be selected.
92
CHAPTER 7 TIME SETTING FUNCTION (SNTP CLIENT)
7.2
Precautions
(1) Communication timeout
A communication timeout occurs when 20 seconds have elapsed without receiving any response after sending a time query.
At the time of a communication timeout, the value in SD1270 is FFFF
H
.
(2) Delay resulted from the time required for communication
A delay occurs and affects the set time as a result of the time spent for communication with the SNTP server computer. For a high-accuracy time setting, specify an SNTP server computer that is networked as close to the
CPU module as possible.
7
93
CHAPTER 8
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.
CPU module (FTP server) Target device (FTP client)
Parameters
Programs
Data
Storage files
Read
Write
Ethernet
The following operations can be performed between the connected device with the FTP client function and the CPU module.
(a) Reading files from the CPU module (download)
The files in the CPU module can be stored in the connected device.
(b) Writing files to the CPU module (upload)
The files stored in the connected device can be registered to the CPU module.
(c) Browsing the names of the files in the CPU module
The files registered to the CPU module can be checked from the connected device.
Remark
Access through routers is also available. When configuring the settings for it, set the subnet mask and default router IP address. (
94
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
8.1
Setting for FTP Communication
(1) Operation on the CPU module side
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
3.
1.
2.
1.
Set the IP address of the CPU module.
2.
Select "Enable online change (FTP, MC Protocol)" when data need to be written even while the
CPU module is in RUN state.
8
95
96
3.
Configure the FTP settings.
Item
FTP
Login Name
Password
Command Input
Monitoring Timer
Description
Select "Used".
Set a log-in name used for file transfer (login) request from an external device. The default value is "MELSEC".
Set an FTP password used for file transfer request from an external device. To change the password, enter both the current password and a new password for confirmation. The default value is "MELSEC".
Set a time for monitoring command input performed by the CPU module. When no command is input within the set period of time, the FTP connection is disconnected. (Setting range : 1 to 32767 ( × 500ms))
Set a time value larger than the time required for file transfer.
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
(2) Operation on the connected device (FTP client) side
The following describes the procedure and processing on the connected device side, which is required for using the FTP server function of the CPU module.
Various FTP commands and how to enter each of them are also shown.
(<ret> indicates an input of the CR, Enter, or Return key.)
Start
Start the FTP client.
(ftp <ret>)
Login to the CPU module (open "CPU module's IP address" <ret>)
Is the
FTP communication port subject to remote password check?
YES
NO
Unlock the remote password.
(quote password-unlock
"remote password" <ret>)
Is file transfer completed?
NO
Write files to the FTP server?
NO
File reading
YES
YES
No file conversion is notified.
(binary <ret>)
Check the file list.
(dir <ret>
or ls <ret>)
NO
Does the read target file exist?
YES
NO
Is File password 32 set for the target file?
YES
Enter a file password.
(quote passwd-rd
"read password" <ret>)
Read the file.
(get "file name" <ret>)
File writing
No file conversion is notified.
(binary <ret>)
Check the file list.
(dir <ret> or ls <ret>)
NO
Does the write target file exist?
YES
Can it be overwritten?
NO
YES
NO
Is File password 32 set for the target file?
YES
Enter a file password.
Delete or rename the file.
(quote passwd-wr
"write password" <ret>)
(delete "file name" <ret> or rename "current file name"
"new file name" <ret>)
Write the file.
(put "file name" <ret>)
NO
Is remote password enabled for FTP?
YES
Lock the remote password.
(quote password-lock
<ret>)
Disconnect from the CPU module.
(bye <ret>)
End
8
97
98
1.
2.
3.
4.
(a) Logging in to the CPU module
The following explains the operation flow from starting an FTP session until log-in to the CPU module.
®
Windows
®
.
1.
Start an FTP session. (FTP <ret>)
2.
Open a connection to the FTP server (open "IP address of the CPU module" <ret>)
3.
Specify the login name (Login name <ret>)
4.
Specify the password (Password <ret>)
(b) Locking and unlocking a remote password
If the FTP communication port is specified as a remote password check target in the remote password settings, unlock the remote password using the following command.
(quote password-unlock "Remote password" <ret>)
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.
(c) Entering file password 32
When file password 32 (write or read password) is set for the target file, the password must be entered with the following command before accessing the file.
• Write password (quote passwd-wr "write password" <ret>)
• Read password (quote passwd-rd "read password" <ret>)
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
8.2
Files Transferable Using FTP
The following table lists the files that can be transferred using the file transfer function.
:Available,
×
:N/A
File type
Parameter
Intelligent function module parameter
Program
Device comment
Device initial value
File register
Local device
Sampling trace file
Programmable controller user data
*1
Source information
Drive heading
Device data storage file
Module error log file
Boot setting file
Remote password
Latch data backup file
Backup data file
Data logging setting file
Program memory
*2 *3
Drive 0
×
×
×
×
×
×
×
×
×
×
×
×
×
Standard
RAM
Drive 3
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
Standard
ROM
Drive 4
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
*4
SD memory card
*4
Drive 2
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
×
File name or extension
PARAM.QPA
IPARAM.QPA
.QPG
.QCD
.QDI
.QDR
.QDL
.QTD
Any file name
*5
QN.DAT
DEVSTORE.QST
IERRLOG.QIE
AUTOEXEC.QBT
00000000.QTM
LCHDAT00.QBP
MEMBKUP0.QBP
LOGCOM.QLG,
LOG01.QLG to LOG10.QLG
.CSV
MENUDEF.QDF
Data logging file
Menu definition file
×
×
×
×
×
× ×
*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. (
*4 The following number of files can be stored using FTP.
*5
[Maximum number of files storable on the drive - 1]
File names are SRCINF1M.C32, SRCINF2M.C32 for Simple projects (with labels), and SRCINF1I.C32, SRCINF2I.C32 for Structured projects.
8
99
8.3
Files That Can Be Deleted Using FTP
The following table lists the files that can be deleted using the file transfer function.
File type
Parameter
Intelligent function module parameter
Program
Device comment
Device initial value
File register
Local device
Sampling trace file
Programmable controller user data
*1
Source information
Drive heading
Device data storage file
Module error log file
Boot setting file
Remote password
Latch data backup file
Backup data file
Data logging setting file
Program memory
*2*3
Drive 0
: Deletable, : Not deletable only in RUN state, ×: Not deletable, -: Not writable
Standard
RAM
Drive 3
Standard
ROM
*4
Drive 4
SD memory card
*4
Drive 2
File name or extension
PARAM.QPA
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
×
-
-
-
-
-
-
-
-
-
-
-
-
-
IPARAM.QPA
.QPG
.QCD
.QDI
.QDR
.QDL
.QTD
Any file name
*5
QN.DAT
DEVSTORE.QST
IERRLOG.QIE
AUTOEXEC.QBT
00000000.QTM
LCHDAT00.QBP
MEMBKUP0.QBP
LOGCOM.QLG,
LOG01.QLG to LOG10.QLG
.CSV
MENUDEF.QDF
Data logging file
Menu definition file
*1
*2
*3
*4
*5
-
-
-
-
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)
Files can be written to the program memory only when the CPU module is in the STOP state.
Write destination is the program cache memory.
The user should back up files using the "pm-write" command as required. (
The following number of files, which can be written using FTP, can be stored.
[Maximum number of files storable on the drive - 1]
File names are SRCINF1M.C32, SRCINF2M.C32 for Simple projects (with labels), and SRCINF1I.C32, SRCINF2I.C32 for Structured projects.
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.
100
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
8.4
FTP Commands
8.4.1
List of FTP commands
close delete mdir mget mls mput open dir get ls mdelete put pwd
Command
binary
*5 bye quit quote rename user
Function
STOP
CPU module state
RUN
Write enabled
*1
Write disabled
*1
: Available, × : N/A
Remote password
Unlocked
*2
Locked
*2
Notifies the FTP server of file transfer without conversion.
Disconnects the line to the FTP server and terminates the session.
Disconnects the line to the FTP server.
Deletes a file in the CPU module.
*4
Displays file information of the CPU module.
*4
Reads a file from the CPU module.
*4
Displays file names of the files stored in the CPU module.
*4
Deletes file(s) stored in the CPU module.
*4
Stores file information of the CPU module into a file.
*4
Reads file(s) from the CPU module.
*4
Stores CPU module’s file names into a file.
*4
Writes file(s) to the CPU module.
Connects to the FTP server.
Writes a file to the CPU module.
Displays the current directory of the CPU module.
Disconnects the line to the FTP server and terminates the connection.
Sends an FTP server subcommand.
*3
Changes a CPU module file name.
*4
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 dialog box.
*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:
*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.
×
×
×
×
×
×
×
×
×
8
101
The following table lists the subcommands available with the command, "quote".
Subcommand Function
Displays or changes the CPU module file attribute.
*2
Locks an unlocked remote password.
Unlocks an locked remote password.
Displays the operation information of the CPU module.
Changes the CPU module state to RUN.
Changes the CPU module state to STOP.
Writes data to the program memory.
Sets, displays, or clears file password 32 (read password).
Sets, displays, or clears file password 32 (write password).
STOP
CPU module state
RUN
Write enabled
Write disabled
× change password-lock password-unlock status run stop pm-write passwd-rd passwd-wr
× ×
*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.
: Available, × : N/A
Remote password
Unlocked Locked
×
×
*1
×
×
×
×
×
×
102
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
8.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.
(1) File specification
A file can be specified for an FTP command on the FTP client side as follows:
• For CPU modules, each file is specified using a drive name and a file name.
*2
• When specifying a file in the CPU module using the FTP function, specify the target file in the following order.
[Specification format]
Drive name:\Folder name
*1
\File name.Extension
[Example] 3:\MAINSEQ1.QDR (other than drive 2)
2:\LOGGING\LOG01\00000001\LOG01_00000001.CSV (drive 2)
[Specification details] Refer to (a) and (b) below.
*1
*2
Only for a file in drive 2, the folder name can be specified.
Use "\" as a delimiter.
(a) Drive name (drive No.)
Specify the drive name of the file transfer target memory.
For the CPU module’s memories and drive names, refer to:
(b) Folder name, file name, and extension
• Specify a folder name and a file name according to the rules described in the following manual.
MELSEC-L CPU Module User’s Manual (Function Explanation, Program Fundamentals)
• Set an extension predetermined by the CPU module.
• For an FTP command which can be used for multiple files, specify the file name and extension using a wild card character (* or ?).
*:
?:
Indicates all files having any characters (including no character) from the position where "*" is used.
Indicates all files having any characters (including no character) at the position where "?" is used.
(Multiple "?" can be used.)
Some FTP clients have other restrictions on the characters that can be used for file names.
8
The part enclosed with brackets in the specification format can be omitted.
103
8.4.3
Details of FTP commands
Details of the FTP commands on the FTP client side, which are supported by the CPU module, and how to use each of them are described below.
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.
(1) FTP server support commands
● binary
[Function]
[Specification format]
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.
binary (abbreviated to "bin")
● bye
[Function]
[Specification format]
[Identical command]
● close
[Function]
[Specification format]
● delete
[Function]
[Specification format]
[Example]
[Similar command]
Disconnects the line to the FTP server, and terminates the FTP session.
bye quit
Disconnects the line to the FTP server.
close
Deletes a file stored in the CPU module.
delete "file path name"
When deleting a file stored in an SD memory card: delete 2:\MAINSEQ1.USR
mdelete
● dir
[Function]
[Specification format]
[Example]
[Similar command]
Displays the names, creation dates, and sizes of the files stored in the CPU module.
dir [drive name:\]
When displaying the detailed information of the files stored in an SD memory card: dir 2:\ ls
104
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
● get
[Function]
[Specification format]
[Example 1]
[Example 2]
[Note]
Reads a file from the CPU module.
get "source file path name" [destination file path name]
When reading a file stored in the standard RAM and saving it under the same file name: get 3:\MAINSEQ1.QDR
When reading a file stored in the standard RAM and saving it under a different file name: get 3:\SEQ1BAK.QDR \SEQ\SEQ10LD.QDR
• 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]
[Specification format]
[Example]
[Similar command]
● mdelete
[Function]
Displays the names of the files stored in the CPU module.
Is [drive name:\]
When displaying the names of the files stored in an SD memory card: ls 2:\ dir
[Specification format]
[Example]
[Similar command]
● mdir
[Function]
[Specification format]
[Example]
[Note]
[Similar command]
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 ?).
mdelete "file path name" (abbreviated to "mdel" )
When deleting all the files whose extensions are "QPG" from the program memory: mdelete 0:\*.QPG
delete
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.
mdir "source drive name" :\"destination file path name"
When saving detailed information of the files stored in an SD memory card into the
S990901.LOG file: mdir 2:\ S990901.LOG
• 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.
mls
8
105
106
● mget
[Function]
[Specification format]
[Example]
[Note]
Reads out a file from the CPU module.
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.
mget "file path name"
When reading all the files whose extensions are "USR" among the files stored in an SD memory card: mget 2:\*.USR
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]
[Specification format]
[Example]
[Note]
Stores the names of the files in the CPU module as log data into a file on the FTP client side.
mls "source drive name":\"destination file path name"
When storing the names of the files in an SD memory card into the S990901F.LOG file: mls 2:\ S990901F.LOG
• 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.
mdir [Similar command]
● mput
[Function]
[Specification format]
[Example]
[Note]
Writes a file to the CPU module.
To write multiple files, specify the file name and extension within the file path name using a wild card (* or ?).
When writing multiple files, transmission is checked for each file transfer.
mput "source file path name"
When writing all the files whose extensions are "USR": mput *.USR
The storage destination file name is the same as that on the FTP client side.
The transfer destination is the memory in which current parameter files are stored.
● open
[Function]
[Specification format]
[Example 1]
[Example 2]
[Note]
Connects to the FTP server by specifying the host name or IP address and port number of the FTP server.
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
When connecting to the FTP server by specifying a host name: open HOST
When connecting to the FTP server by specifying an IP address: open 192.0.1.254
Connection is also possible by specifying an IP address at startup of FTP.
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
● put
[Function]
[Specification format]
[Example 1]
[Example 2]
[Note]
Writes a file to the CPU module.
put "source file path name" [destination file path name]
When writing the MAINSEQ1.QDR file to the standard RAM with the same file name: put MAINSEQ1.QDR 3:\MAINSEQ1.QDR
When writing the MAINSEQ.QDR file to the standard RAM with a different file name: put MAINSEQ.QDR 3:\MAINSEQ1.QDR
• 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]
[Specification format]
[Note]
● quit
[Function]
[Specification format]
[Identical command]
● quote
[Function]
[Specification format]
[Example]
[Note]
Displays the current directory name of the CPU module.
pwd
"\" is displayed as the execution result of the "pwd" command.
Disconnects the line from the FTP server and terminates the FTP session.
quit bye
Sends an FTP server subcommand (a subcommand dedicated to CPU modules).
quote quote password-lock
Only CPU module dedicated subcommands can be specified. Refer to Page 108, Section
● rename
[Function]
[Specification format]
[Example]
[Note]
Renames a CPU module file.
rename "old file path name" "new file path name" (abbreviated to "ren")
When renaming a file stored in the standard RAM: rename 3:\MAINSEQ1.QDR 3:\SEQ1OLD.QDR
Either of the following response codes is displayed upon completion.
350 Need more info.
250 Rename successful.
● user
[Function]
[Specification format]
[Example 1]
[Example 2]
Inputs the user name and password of the connected FTP server.
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
When specifying a user name: user CPU
When specifying a user name and password: user CPU CPU
8
107
108
(2) CPU-module-dedicated subcommands
The CPU-module-dedicated subcommands affixed to an FTP command, "quote," are described below.
● change
[Function]
[Specification format 1]
[Specification format 2]
[Example 1]
[Example 2]
Displays or changes the attribute of a file stored in the CPU module.
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
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
When displaying the attribute of the file stored in the standard RAM: quote change 3:\MAINSEQ1.QDR
When changing the attribute of the file stored in the standard RAM: quote change 3:\MAINSEQ1.QDR r
● password-unlock
[Function]
[Specification format]
[Example]
[Note]
Specify the remote password set in the CPU module to unlock the password.
*2 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
When specifying a remote password (1234): quote password-unlock 1234
• 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.
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
● password-lock
[Function]
[Specification format]
[Example]
Locks the remote password set in the CPU module.
*3 quote password-lock
The following is displayed as an execution result upon completion.
200 Command Okey
When locking the remote password: quote password-lock
*3 Use this command only when the FTP communication port is specified as a remote password check target.
● run
[Function]
[Specification format]
[Example 1]
[Example 2]
[Example 3]
[Note]
Changes the CPU module state to RUN. (Remote RUN.)
At this time, device memory clear can be specified.
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
When executing remote RUN, with "Normal RUN" and "Do not clear device" specified: quote run
When executing remote RUN, with "Forced RUN" and "Do not clear device" specified: quote run 1
When executing remote RUN, with "Forced RUN" and "Clear other than the latch range": specified quote run 1 1
• 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 the PLC parameter settings ("Initial Device value" setting on the PLC file tab).
● status
[Function]
[Specification format]
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.
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"
8
109
110
● stop
[Function]
[Specification format]
[Note]
Changes the CPU module state to STOP (remote STOP).
quote stop
The following message is displayed as an execution result upon completion.
200 Command successful
Before writing data to the program memory, set the CPU module into the STOP state using this command.
● pm-write
[Function]
[Specification format]
Transfers program cache memory to the program memory.
quote pm-write
The following message is displayed as an execution result upon completion.
200 Command successful
Before writing data, set the CPU module to STOP.
[Note]
● passwd-rd
[Function]
[Specification format]
[Example 1]
[Example 2]
[Example 3]
[Note]
Sets, displays, and clears the read password (file password 32) that is registered to the file transfer target.
With this command, the CPU module checks the read password when access is made to the transfer target file.
quote passwd-rd [read password]
Any of the following is displayed as an execution result upon completion.
• When setting a read password: 200 Command successful
• When displaying a read password: 200 Read-password is [read password]
• When clearing a read password: 200 Command successful
• When attempting to display a read password with no read password set: 200 Readpassword is not set.
When setting a read password (ABCD1234@efgh): quote passwd-rd ABCD1234@efgh
When displaying a read password that is currently set to FTP: quote passwd-rd
When clearing a read password that is currently set to FTP: quote passwd-rd c, or quote passwd-rd C
• One read password can be set to FTP of the CPU module.
When the transfer target file is changed, if a read password is preset for the new target file, set the read password of the target file again.
• When the CPU module is logged in, the read password is cleared.
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
● passwd-wr
[Function]
[Specification format]
[Example 1]
[Example 2]
[Example 3]
[Note]
Sets, displays, and clears the write password (file password 32) that is registered to the file transfer target.
With this command, the CPU module checks the write password when access is made to the transfer target file.
quote passwd-wr [write password]
Any of the following is displayed as an execution result upon completion.
• When setting a write password: 200 Command successful
• When displaying a write password: 200 Write-password is [write password]
• When clearing a write password: 200 Command successful
• When attempting to display a write password with no write password set:
200 Write-password is not set.
When setting a write password (1234@ABCDefgh): quote passwd-wr 1234@ABCDefgh
When displaying a write password that is currently set to FTP: quote passwd-wr
When clearing a write password that is currently set to FTP: quote passwd-wr c, or quote passwd-wr C
• One write password can be set to FTP of the CPU module.
When the transfer target file is changed, if a write password is preset for the new target file, set the write password of the target file again.
• When the CPU module is logged in, the write password is cleared.
8
111
8.5
Precautions
(1) FTP clients
• Some FTP clients may have FTP command specifications different from those described in this manual. In such a case, check the functions and operation methods, referring to the manuals for the FTP client.
• An FTP operation from Microsoft
®
Internet Explorer is not allowed. If it is attempted, an error will occur in
Internet Explorer.
(2) CPU module side processing
• Files only in the drives of the host station CPU module can be accessed.
• During file access, do not power off the CPU module, reset the CPU module, or remove an SD memory card.
Doing so may corrupt the file. Stop accessing to an SD memory card, and then power off the CPU module, reset the CPU module, or remove an SD memory card. All of SD memory card operations can be disabled by SM606 (SD memory card forced disable instruction). For the forced disablement of SD card, refer to the following.
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)
• During file access, do not operate the file from a peripheral such as a programming tool. (Also do not perform online operations such as online change, scam time measurement, registration of the step number set for a monitoring condition). If the file is operated during operation of the FTP function, an error may occur in the peripheral. Perform the processing suspended due to an error again after performing the FTP function.
• If an access is attempted from an FTP client during backup or restoration for the CPU module change function using an SD memory card, an error will occur.
Reexecute it after completion of the backup or restoration.
An error will also occur if backup or restoration is performed during access from an FTP client.
In that case, reexecute it after disconnecting the FTP client.
(3) Communication processing
• If a timeout error occurs during file transfer, the TCP connection will be closed (disconnected). To restart the file transfer, log in to the CPU module once again from the FTP client.
• For each FTP connection, the existence of the target device is checked. For details, refer to:
• The processing time for file transfer depends on the factors such as the Ethernet line congestion, the number of connections simultaneously used (communication processing of other connections), and the system configuration.
• Only one FTP client can log in to a CPU module at the same time. If another FTP client attempts to connect to a CPU module that is already in the logged-in state, the connection cannot be established, resulting in an error.
• An attempt to execute another communication (MELSOFT connection or MC protocol) using UDP during file transfer using FTP may cause an error such as a timeout error.
Execute it after completion of the file transfer, or use TCP.
112
CHAPTER 8 FILE TRANSFER FUNCTION (FTP)
(4) File writing
• An existing file cannot be overwritten and saved.
Either delete a file with the file delete command (delete or mdelete) or rename the file with the file rename command (rename), and then write the file.
• Writing is not allowed to read-only files and files locked by a function other than FTP. If attempted, a write error occurs.
• File transfer (writing a file) cannot be executed when the SD memory card is write-protected. If attempted, a write error occurs.
• When a file is written, a temporary file (FTP_I***.TMP) is created automatically. This file is renamed to the destination file name upon completion. However, if power failure or reset of the CPU module occurs during the file writing, this temporary file may remain. If this occurs, delete the temporary file.
• Before writing or deleting data to the file register in the standard RAM, set the CPU module to STOP.
• When the file register in the standard RAM is set as an auto refresh device, do not perform any writing or deletion to the corresponding drive.
• When writing a large file to an SD memory card, set the CPU module to STOP. If writing is performed in the
RUN state, a communication error may occur.
(5) File deletion
• The timing for deleting files must be determined by the user, considering the overall system including the
CPU module and programming tool.
• A file cannot be deleted if the SD memory card is write-protected. If attempted, an error occurs.
(6) Password for FTP
When you forgot the FTP password, set the FTP parameters again by the following steps.
1.
Read out the parameters from the CPU module to the programming tool.
2.
In the FTP Parameter Setting dialog box, click the "Default" button to return all the FTP parameters to default values.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting] button
3.
Configure the FTP parameter settings again.
4.
Write the parameters to the CPU module from the "Write to PLC" screen.
[Online] [Write to PLC]
5.
Power off and then on or reset the CPU module to enable the parameters.
8
113
CHAPTER 9
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.
[Examples of measures against unauthorized access]
• Install a firewall.
• Set up a personal computer as a relay station, and control the relay of communication data using an application program.
• Set up an external device that can control access rights as a relay station.
For devices that can control access rights, please consult your network service provider or networking equipment vendors.
114
CHAPTER 9 REMOTE PASSWORD
9.1
Communication Using Remote Password
Communication is performed in the order described below when a remote password is set for the CPU module.
(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.
(2) Access processing
Access the CPU module after completion of the remote password unlock processing.
(3) Prohibiting access (lock processing)
When terminating access from the personal computer, lock the remote password to prohibit an access from any other personal computers.
[Accessing the host CPU]
(a) Unlocking
(c) locking
Ethernet
(b) Access
9
Enable/
Disable
Remote password check
Remote password parameter
[Accessing a CPU on another station]
(a) Unlocking
(c) locking
(b) Access
Ethernet
Enable/
Disable
CC-Link
Remote password check
Remote password parameter
115
9.2
Remote Password Setting
(1) Setting a remote password
Set a remote password and a target connection in the programming tool, and write the data to the CPU module.
Project window [Parameter] [Remote Password]
Password Setting
Password
Active
Module
Setting
Model Name
Condition
Item
User
Connection
No.
*5
Connection 1 to 16
System
Connection
*6
MELSOFT Transmission Port (TCP/IP)
*2
MELSOFT Transmission Port (UDP/IP)
*2 *3
FTP Transmission Port (TCP/IP)
Direct Connection of MELSOFT
Regard as Error when Remote Password Mismatch Count
Reaches Upper Limit
Upper Limit of Mismatch
Clear Mismatch Count when Remote Password Matches
Description
Enter a remote password to be set for the CPU module.
*1
Select a CPU model to enable the remote password for the built-in
Ethernet port of the CPU module.
Only one CPU model is selectable.
Click this to display the "Remote Password Detail Setting" dialog box.
Select one of them when the remote password is to be enabled for the built-in Ethernet port.
(Setting of an unused connection or MELSOFT connection is ignored.)
Setting range
Up to four characters
Ethernet Built-in
CPU
-
Select one of them when the remote password is to be enabled for the built-in Ethernet port.
Select the checkboxes appropriate to the target connection.
(
Select this when enabling this operation.
(Useful for detecting unauthorized access)
Specify the maximum number of mismatches.
Select the checkbox when this operation is to be performed.
1 to 65535
-
116
CHAPTER 9 REMOTE PASSWORD
*5
*6
*1
*2
*3
*4
One-byte alphanumeric and special characters can be used for remote password entry. (Case-sensitive)
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 connecting the CPU module and a GOT via Ethernet, do not select "MELSOFT Transmission Port (UDP/IP)".
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. (
User connection is for users for communications such as MC protocol communications and communications using fixed buffers.
System connection is used by the system for communications such as FTP communications and MELSOFT communications (TCP/IP, UDP/IP).
(2) Writing to the CPU module
Write the remote password to the CPU module from the "Write to PLC" screen.
[Online] [Write to PLC]
After writing the parameters to the CPU module, power off and then on or reset the CPU module to enable the parameters.
(3) Unlocking or locking the remote password
The remote password is unlocked or locked from an external device such as a personal computer, as described below.
(a) When using MELSOFT connection
Enter a remote password in the following dialog box that appears during communication.
When the remote password is entered, the programming tool performs unlock processing and then accesses the CPU module
9
(b) When using MC protocol
Use commands dedicated to MC protocol. (
(c) When using the FTP function
Use the "password-lock" and "password-unlock" commands. (
117
118
(d) When using the simple PLC communication function
Unlock the remote password in the "Destination Setting List" dialog box of Simple PLC Communication Setting.
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting] [Simple
PLC Communication Setting] [Destination Setting List]
CHAPTER 9 REMOTE PASSWORD
9.3
Precautions
(1) When a remote password is set for UDP connections
• Determine a target device before data communication. (The communication target needs to be determined because, after unlocking of the remote password, communication is available with any other devices.)
• At the end of data communication, always lock the remote password.
(If the lock processing is not performed, the unlock state is held until a timeout occurs. No communication for
10 minutes causes a timeout, and the CPU module automatically performs lock processing.)
To prevent unauthorized access using the remote password setting, it is recommended to set all connection protocols to TCP/IP and disable direct connection with the parameter.
(2) When a TCP/IP connection is closed before lock processing
The CPU module automatically performs lock processing.
9
119
9.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.
Take the following actions as needed.
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" dialog box, and force it to be deactivated.
( GX Works2 Version 1 Operating Manual (Common))
[Diagnostics] [Ethernet Diagnostics] "Status of Each Connection"
120
• Turn on the force deactivation flag of the connection in the special register (SD1276, SD1277).
3.
Clear the "REMOTE PASS FAIL" error (error code: 2700).
The remote password count (SD979 to SD999) is also cleared.
4.
Inform your system administrator that the number of unlock processing failures exceeded the limit, and take appropriate actions.
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" dialog box.
• Clear the accumulated count of remote password mismatches using the special relay (SM1273).
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
CHAPTER 10
SIMPLE PLC COMMUNICATION
FUNCTION
The simple PLC communication function allows data communications between specified devices at the specified timing just by doing simple settings from a programming tool. Specify one device (transmission source) to one device
(transmission destination). The communications are performed between the specified devices.
The communications using this function are not possible when a stop error occurs in the CPU module where the parameters are set.
Note10.1
10
Hub
Set the parameters.
Device data are communicated between the CPU modules in which parameters are not set. (In this case, the CPU module in which parameters are set relays the device data.)
Ethernet
Built-in Ethernet port LCPU
Built-in Ethernet port QCPU Q/L series CPU module
+ Ethernet module
A series CPU module
+ Ethernet module
The communications using this function are possible only for the CPU modules connected with Ethernet cable. The following communications are not possible.
• Communication with a CPU module on other stations via CC-Link network.
• Communication with a CPU module except the connected Built-in Ethernet port QCPU when multiple CPU system is configured.
• Communication with a CPU module that does not control the connected Ethernet module when multiple CPU system is configured.
Remark
● The communications can be performed only with a Mitsubishi programmable controller. The communications with the programmable controllers manufactured by other companies are not possible. (
Page 125, Section 10.1 (3) (b))
● Access via routers is also possible. For the access, set the subnet mask pattern and the default router IP address. (
Note10.1
LCPU
Check the versions of the CPU module and GX Works2 when using the simple PLC communication function.
(
121
10.1
Setting Method
To use this function, configure the settings in "Simple PLC Communication Setting". Up to 64 devices can be set in
"Simple PLC Communication Setting".
Project window [Parameter] [PLC Parameter] [Built-in Ethernet Port Setting]
[Base Setting]
[Extended Setting]
122
Simple PLC Communication Setting consists of Base Setting (essential) and Extended Setting (optional). To switch the dialog boxes, use the / button on the top right of the dialog box.
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(1) Communication Pattern
Select it from the following items.
Read
Write
Transfer
*1
Setting item Description
Read the data of the specified destination device (transmission source) to the specified device of the host station (transmission destination).
Write the data of the specified device of the host station (transmission source) to the specified destination device (transmission destination).
Read the data of the specified destination device (transmission source) and write it to another specified destination device (transmission destination).
*1
The device data is not reflected in the CPU module where the parameters are set (the CPU module that relays the data).
(2) Communication Setting: Execution Interval (ms)/Request Contact
Select the communication timing from the following items.
Setting item
Fixed Interval
Description
Data are communicated between the devices at a specified execution interval.
Setting range
-
Execu-tion
Interval
On Request
*1
Execution interval is set.
10ms to 65535ms (1ms unit)
Request
Contact
*1
Data are communicated between the devices only when requested.
Data are communicated at the rising (OFF to ON) of the device that is specified as Request Contact. The ON/OFF status of Request Contact is confirmed in the END processing.
X, M, B
-
Request Contact cannot be specified overlapped with the following devices.
• Request Contact Device to Stop Fixed Interval Communication
• Execution Status Flag Device
• Source device when the host station is a transmission destination device
• Request Contact Device to Stop Fixed Interval Communication that is used for other setting No.
• Execution Status Flag Device that is used for other setting No.
• Source device when the host station is a transmission destination device, which is used for other setting No.
10
● Actual time of execution interval may be longer than the value of the setting because the time is affected by the specified devices or Ethernet line congestion. For the preventive measures, refer to the troubleshooting described in the following manual.
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)
● If latency time is set, data communication is started after the latency time has passed. (
123
(3) Register Destination
(a) Setting of devices for communications
Set the devices for both transmission source and transmission destination. Up to 64 devices can be registered.
This setting also can be done in "Destination Setting List" dialog box that will open by clicking button in "Simple PLC Communication Setting" dialog box. Use Destination Setting List dialog box as well to change the setting information.
124
Setting item
IP Address/Port No. Input
Format
Description
Select the input format of IP address and port No. DEC/HEX
Setting range
Module Type
IP Address
Port No.
Network No.
Station No.
Remote Password
Host Station Port No.
Host Station No.
*1
Select the device for communications.
Set the IP address of the device.
Set the port No. of the device.
Set the network No. of the device (host station).
Set the station No. of the device.
If a remote password is set for the destination device, the communication is possible by entering the password.
Set the port No. of the host station.
Set the station No. of the host station.
*1
Page 125, Section 10.1 (3) (b)
0.0.0.1 to 223.255.255.254
0401
H
to 1387
H
, 1392
H
to FFFE
H
1 to 239
1 to 64
4 characters or less (one-byte alphanumeric and special characters)
0401
H
1 to 64
to 1387
H
, 1392
H
to EFFF
H
Set the station number not to overlap the numbers set for other devices on the same Ethernet network (such as Ethernet module, programming tool, and GOT).
If the L/Q/QnA series modules are used for the simple PLC communication, F000
H
to FFFE
H
is automatically selected for the port No. of the host station. Therefore, when using the simple PLC communication function, do not set F000
H
to FFFE
H to Host Station Port No. for the establishing a connection instruction (SP.SOCOPEN) of the socket communication function.
If F000
H
to FFFE
H
is set, the instruction may not be completed properly.
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(b) Model Type List
The following table shows the communication devices and specifications applicable to each model.
Communication specification
Model Type Device for communications
MELSEC-Q/L (Built-in Ethernet
Function)
Built-in Ethernet port QCPU
Built-in Ethernet port LCPU
Basic model QCPU + Ethernet module
High Performance model QCPU + Ethernet module
MELSEC-Q/L (Ethernet Module) Process CPU + Ethernet module
Universal model QCPU + Ethernet module
Built-in Ethernet port LCPU + Ethernet module
MELSEC-QnA (Ethernet Module) QnACPU + Ethernet module
ACPU + Ethernet module
MELSEC-A (Ethernet Module)
High Performance model QCPU (A mode) + Ethernet module
(c) Setting for each device for communications
The settings vary depending on the device for communications.
MELSOFT connection
MC protocol Acompatible 1E frame
(binary code communication)
: Setting is required. : Setting is required if the password is set for destination device for communications. ×: Setting is not required.
Setting item
Device for communications
IP Address Network No.
Station No.
Port No.
Remote
Password
MELSEC-Q/L (Built-in Ethernet
Function)
× × ×
MELSEC-Q/L (Ethernet Module)
*1*2 *1*2
×
MELSEC-QnA (Ethernet Module)
MELSEC-A (Ethernet Module)
*1*2
×
*1*2
×
×
*1
×
×
*1
*2
Setting of the host station is required.
For the "MELSEC-Q/L (Ethernet Module)" and "MELSEC-QnA (Ethernet Module)," settings of these items in "Simple
CPU Communication Setting" are required because these modules perform communication processing using the network No. and station No.
Router
Data flow
Hub
Hub
Ethernet
10
Network No. 1
Station No. 1
Network No. 1
Station No. 2
The settings must be configured in simple PLC communication setting.
Network No. 1
Station No. 1
Network No. 1
Station No. 2
The settings must be configured in simple PLC communication setting.
125
(4)
Settings for destination devices for communications
If following devices are used as the destination devices for communications, the settings of these devices are also required.
Destination device for communications
Parameters
Necessary setting
Programming tool
DIP switch on the front of the module
MELSEC-Q/L
(Built-in Ethernet
Function)
MELSEC-Q/L
(Ethernet Module)
MELSEC-QnA
(Ethernet Module)
MELSEC-A
(Ethernet
Module)
*5
*1
*2
*3
*4
*5
Set the following items (for the numbers of the devices) in "Open
Setting".
*1
• Protocol: "UDP"
• Open System: "MELSOFT
Connection"
Set the following items from the
Ethernet setting of Network
Parameter.
• "Send Frame Setting" of "Operation
Setting": "Ethernet(V2.0)"
• "Station No.<->IP Information
System" of "Station No.<->IP
Information": "Automatic Response
System"
---
---
---
---
Set the following items from the
Ethernet setting of Network
Parameter.
• "Send Frame Setting" of "Operation
Setting": "Ethernet (V2.0)"
• "Station No.<->IP Information
System" of "Station No.<->IP
Information": "Automatic Response
System"
---
• Create an initial processing program and turn off the bits (6 and
7) in the special function setting area (address: 4(4
H
)) of buffer memory.
• Turn on the bit 15 in the exchange instruction area during STOP
(address: 103(67
H
)) of buffer memory.
*4
• Create an initial processing program and do the settings as shown below.
• Set the IP address and the port
No. by referring (3) in this section.
• Set "UDP" for the communication method.
• Turn on the bit 15 in the exchange instruction area during STOP
(address: 496(1F0
H
)) of buffer memory, and the bits corresponding to the connection
No. used for bits 0 to 7.
*4
Set the following items.
• SW3 (Automatic start up mode setting): ON setting): ON
*3
• SW7 (CPU exchange timing
*2
Set the following items.
• SW2 (Data code setting): OFF
• SW7 (CPU exchange timing setting): ON
*2
The module has the setting by default to communicate with one device whose protocol is "UDP".
To execute the simple PLC communication function when the CPU module (destination device for communications) is in
RUN state, turn on this switch.
If Ethernet module is in Automatic startup mode, turn on this switch.
To execute the simple PLC communication function when the CPU module (destination device for communications) is in
STOP state or in stop error state, turn on the bits.
The module cannot communicate regardless of the setting if a stop error occurs in it.
126
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(5) Available devices
The devices that can be specified as transmission source and transmission destination vary depending on the destination device for communications. Both a bit device and a word device can be set for the same setting No.
Set the total points of setting No.1 to No.64 (up to 4096 words
*1
) for the device points.
*1 The maximum number that can be set for each setting No. is 512 words. (Maximum points of a word device: 256 points
+ Maximum points of a bit device: 4096 points)
Destination device for communications
Type
Available device
*2
MELSEC-Q/L (Built-in Ethernet Function),
MELSEC-Q/L (Ethernet Module)
MELSEC-QnA (Ethernet Module)
MELSEC-A (Ethernet Module)
*2
*3
*4
Bit device
Word device
Bit device
Word device
Bit device
Word device
X, Y, M, L, B, SB, SM
D, D (extended data register)
*3
, W, W (extended link register)
*3
, R, ZR, SW, SD
X, Y, M, L, B, SB, SM
D, W, R, ZR, SW, SD
X, Y, M
*4
D, W, R
, B
The size of a bit device and a word device can be specified in units of 16 points and one point respectively. Use 0 or multiples of 16 to specify the device number of a bit device.
The devices are compatible with the following modules:
• Universal model QCPU whose serial number (first five digits) is "09042" or later (except the Q00UJCPU)
• Built-in Ethernet port LCPU
Use "M9000 + multiples of 16" when specifying the device of M9000 or later.
10
● Do not write any data to the special relay and the special register that are set on the system side. Doing so may cause a system failure or communication failure.
● For I/O processing when X and Y are specified as transmission destination, refer to the following:
MELSEC-L CPU Module User’s Manual (Function Explanation, Program Fundamentals)
127
(a) Timing of write or read of the device data
The data of a bit device and a word device set for each setting No. are communicated in the END processing.
*1
Even so, depending on the destination device for communications, data communications for one setting may not be done completely, resulting in data inconsistency.
Destination device for communications
Bit device
Device data
Word device
Data of a bit device and a word device are guaranteed to be communicated by setting unit.
Data inconsistency for one setting
MELSEC-Q/L
(Built-in Ethernet Function)
MELSEC-Q/L
(Ethernet Module)
MELSEC-QnA
(Ethernet Module)
MELSEC-A
(Ethernet Module)
*1
*2
*3
*5
Data of a bit device are guaranteed to be communicated by setting unit.
Within the setting range, data of a bit device are guaranteed to be communicated in units of 32 bits (2 words).
Data of a word device are guaranteed to be communicated by setting unit.
Within the setting range, data of a word device are guaranteed to be communicated in units of 2 words.
Data inconsistency of a bit device and a word device is the same level because the data of both devices are communicated at the same timing.
If both a bit device and a word device are set for the same setting No., the level of data inconsistency of both devices may be different because the data of each device is communicated at different timing.
*2
• If both a bit device and a word device are set for the same setting No., the level of data inconsistency of both devices may be different because the data of each device is communicated at different timing.
*2
• If the data of 32 bits (2 words) or larger is communicated, data inconsistency might differ in units of 32 bits (2 words).
*3
If the COM instruction is used, the data are written or read not only in the END processing but also during sequence scan (at the execution of the COM instruction).
The order of the write and read is shown below.
• When "Write" is set for Communication Pattern: A word device comes first, then a bit device.
• When "Read" is set for Communication Pattern: A bit device comes first, then a word device.
• When "Transfer" is set for Communication Pattern: The host station reads the data of transmission source in order of a bit device and a word device, and writes them to transmission destination in order of a word device and a bit device.
Because the write and read is performed from the data with smaller device number, use the device with the largest No. to secure the data.
128
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(6) Request Contact Device to Stop Fixed Interval Communication
Select the device from X, M, B and specify it as Request Contact Device to Stop Fixed Interval Communication
*1
If "Fixed Interval" is set for Communication Setting, the communications for the specified setting No. temporarily stop when Request Contact Device to Stop Fixed Interval Communication turns on. The communications re-start when Request Contact Device to Stop Fixed Interval Communication turns off. The ON/OFF status is confirmed in the END processing. This stop request is enabled when the communication status is "Communicating" or "Error".
*1 Request Contact Device to Stop Fixed Interval Communication cannot be specified overlapped with the following devices.
• Request Contact
• Execution Status Flag Device
• Source device when the host station is a transmission destination device
• Request Contact that is used for other setting No.
• Execution Status Flag Device that is used for other setting No.
• Source device when the host station is a transmission destination device, which is used for other setting No.
10
● When communications are stopped by the request to stop fixed interval communication, the data communications at a specified execution interval, which is performed when "Fixed Interval" is set for Communication Setting, is ignored.
● The stop time by the request to stop fixed interval communication is not counted as Execution Interval (Current Value).
● If the communications are stopped by the request to stop fixed interval communication during retry of communication, the retry count is reset to 0.
(7) Execution Status Flag Device
Select the device from X, M, B and specify it as a device to store the execution status.
*1
The ON/OFF status below indicate the execution status.
• ON: Communicating (the state of "Status" being "3H")
• OFF: Communication Stop
*1 Execution Status Flag Device cannot be specified overlapped with the following devices.
• Request Contact
• Request Contact Device to Stop Fixed Interval Communication
• Source device when the host station is a transmission destination device
• Request Contact that is used for other setting No.
• Request Contact Device to Stop Fixed Interval Communication that is used for other setting No.
• Execution Status Flag Device that is used for other setting No.
• Source device when the host station is a destination device, which is used for other setting No.
For examples of how to use this device, refer to:
129
130
(8) Status Save Destination Device
Select the device from D, D (extended data register), W, W (extended link register), R, ZR and specify it as a device to store the communication status.
*1
The values listed below indicate the communication status.
1
H
2
H
3
H
Item
Communication
Status
Setting and description
Communication
Setting
Description
Preparing
Waiting for the
Request
Communica-ting
Fixed Interval is set.
On Request is set.
Only On Request is set.
Fixed Interval is set.
On Request is set.
4
H
Communica-tion
Stop
Only Fixed Interval is set.
Error Code No. The corresponding error code is stored.
When waiting for the latency time to pass
Or during the time until communications start after the CPU module is powered off and on or reset
When waiting for the latency time to pass
Or during the time until communications start after the CPU module is powered off and on or reset (including the waiting time of check if the hub is connected or not)
When waiting for the communication request by Request
Contact
When device data communications at a specified execution interval are possible
When device data are communicated according to the states of
Request Contact
When the simple PLC communication function is stopped by the request to stop fixed interval communication
*1 Status Save Destination Device cannot be specified overlapped with the following devices.
• Status Save Destination Device
• Execution Interval (Current Value) Save Destination Device
• Source device when the host station is a transmission destination device
• Status Save Destination Device that is used for other setting No.
• Execution Interval (Current Value) Save Destination Device that is used for other setting No.
• Source device when the host station is a transmission destination device, which is used for other setting No.
For examples of how to use this device, refer to:
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(9) Execution Interval (Current Value) Save Destination Device
Select the device from D, D (extended data register), W, W (extended link register), R, ZR and specify it as a device to store Execution Interval (Current Value).
*1
*1
Item
Execution Interval (Current
Value)
Description
If "Fixed Interval" is set for Communication Setting, the actual execution interval of the communications is stored. If the communications have never been performed properly, "0" is stored.
Execution Interval (Current Value) Save Destination Device cannot be specified overlapped with the following devices.
• Status Save Destination Device
• Execution Interval (Current Value) Save Destination Device
• Source device when the host station is a transmission destination device
• Status Save Destination Device that is used for other setting No.
• Execution Interval (Current Value) Save Destination Device that is used for other setting No.
• Source device when the host station is a transmission destination device, which is used for other setting No.
10
For examples of how to use this device, refer to:
131
132
(10)Time-out period and Retry count
*1
*2
Setting item
Time-out Period
Retry Count
Description
Set the time interval until an error is detected or the retry of communication is performed when the destination device for communications does not respond or communications fail.
Set the number of communication retry to be performed when the destination device for communications does not respond or communications fail.
0 to 255
*2
Setting range
10ms to 65535ms (1ms unit)
*1
When the destination device for communications is "MELSEC-A (Ethernet Module)", the value is fixed at 65535ms.
When the destination device for communications is "MELSEC-A (Ethernet Module)", the value is fixed at 0.
Ex.
Error detection timing when 2 is set for Retry Count
Interval
Communication error at the previous time
Communication error at the previous time
Retry of communication, first time
Communication error at the previous time
Retry of communication, second time
Error detection time-out period time-out period time-out period
The error is detected if the destination device does not respond or communications fail by when the following time has passed:
(Retry Count + 1) × Time-out Period
(a) Precautions for retry of communication
• Communications at a specified execution interval (when "Fixed Interval" is set for Communication Setting) or communications according to the ON status of Request Contact (when "On Request" is set for
Communication Setting) are ignored during retry of communication because that period is regarded as Timeout Period.
• During retry of communication, the data at the time of communication error is sent to the destination device
(for writing of device data) and the data at the time of the retry of communication is received (for reading of device data).
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(11)Comment
Comment can be set by entering up to 32 one-byte characters (16 double-byte characters).
(12)Latency Time
By setting the latency time, the start timing in the communications can be switched in the following cases.
• To prevent an error due to the overlap of the start timing in the communications
• To start communications after the destination device is ready for the communications
During the latency time, "Preparing" is indicated in Communication Status.
Setting item
Latency Time
Description
Set the time required to start communications after completion of the CPU module startup.
Setting range
0s to 255s (1s unit)
Communications at a specified execution interval (when "Fixed Interval" is set for Communication Setting) or communications at the rising (OFF to ON) of Request Contact (when "On Request" is set for Communication Setting) are ignored during the latency time.
10.2
Program to check communications
This section shows the program used to check communications when "On Request" is set for Communication Setting.
(1) Devices used for the program
Device number
M0
M100
M200
D1000
(2) Program example
Application
Request Contact for setting No.1
Execution Status Flag Device for setting No.1
Flag to check if Request Contact turns on (when Status is "Communicating")
Status Save Destination Device for setting No.1
Processing if communications were not performed with
"On Request" set
Perform processing for no communications.
Processing when communications were completed with "On Request" set
Perform processing for successful communications.
Processing if communications failed with "On Request" set
Perform processing for communication failure.
10
133
10.3
Diagnostics
The communication status of the simple PLC communication function can be checked in "Simple PLC Communication
Status" tab of the "Ethernet Diagnostics" dialog box.
[Diagnostics] [Ethernet Diagnostics]
For detail on Ethernet diagnostics, refer to the following.
GX Works2 Version 1 Operating Manual (Common)
10.4
Errors related to the simple PLC communication function
If an error related to this function occurs, it is not regarded as a diagnostic error in the CPU module. Instead the simple
PLC communication status (the corresponding error code) is stored.
(1) Errors caused by the operation status of the CPU module or the operations of each function
The errors are not stored in the history of Ethernet diagnostics.
Error code
4900
4901
4902
4903
H
H
H
H
Error item
Other errors
Error timing Description Corrective action
When the parameters are written from the
"Write to PLC" window
After the values in "Device" of PLC
Parameter of the CPU module, where the simple PLC communication function had been set, were changed, the parameters were written to the CPU module from the
"Write to PLC" window.
Power off and on the CPU module. Or reset the CPU module.
If an error related to the simple PLC communication function occurs (at corresponding setting
No.)
If an error related to the simple PLC communication function occurs (at the other setting No.)
If a stop error occurs
The file register used for the simple PLC communication function became out of range due to the block number change of the file register.
Correct the device number of the file register. And power off and on the CPU module or reset the module.
The communication was stopped because an error occurred at the other setting No., for which the same destination device of the corresponding setting No. had been set.
The communication was stopped because a stop error occurred in the CPU module where the simple PLC communication function had been set.
Remove the error cause.
Power off and on the CPU module. Or reset the CPU module.
134
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(2) Errors caused by communication failure
The errors are stored in the history of Ethernet diagnostics. The error codes to be stored are the same as those of communication related errors. For error descriptions and the corrective actions, refer to the following.
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)
(3) Operations after the error
After the occurrence of the error, if the conditions are restored for proper communications, data communications are re-started at the following timing.
• When "Fixed Interval" is set for Communication Setting: At the timing of the execution interval
• When "On Request" is set for Communication Setting: At the rising (OFF to ON) of Request Contact
10
135
10.5
Precautions
This section provides precautions for the simple PLC communication function.
(1) The timing when the settings are enabled
The settings for this function are enabled at the following timing.
• When powering off and on the CPU module
• When resetting the CPU module
Even if the values of the settings are changed and the CPU module state is changed from STOP to RUN during execution of this function, the CPU module keeps operating with the previous settings. If the device setting of PLC parameter is changed and the parameters are written from the "Write to PLC" window, though, an error (error code: 4900
H
) is detected while the parameters are being written.
(2) Communications with other CPU modules
The communications are possible only between the CPU modules connected with Ethernet cable.
(Communications with the other CPU modules cannot be performed through the CPU module connected with
Ethernet cable.)
(3) Device data
If the COM instruction is used, not only the data in the END processing but also the data during sequence scan
(at the execution of the COM instruction) are subjected to communications. Therefore, if you want to use exact data in the END processing for the program, conduct following operations.
[Transmission source] For the program, use a different device from the one specified for this function. At the end of the program (just before the END), reflect the data of that device to the one specified for this function.
[Transmission destination] At the beginning of the program, reflect the data of the device specified for this function to the other device, and use that device for the program.
(4) Incomplete data reception and timeout
Because the load of Ethernet communication becomes heavy during the simple PLC communication, if the other communication (MELSOFT connection or MC protocol) is simultaneously performed by using protocol UDP, the data reception of UDP may not be completed, resulting in a timeout error. Therefore, to perform other communications during the simple PLC communication, the communication using TCP is recommended. Also conduct following operations to reduce Ethernet communication load.
• Increase the execution interval of the simple PLC communication.
• Reduce the number of device points for communication.
(5) Communication stop
For a certain setting No., if the device is waiting for the response of the destination device due to power off of the module, cable disconnection, or power off of the hub, communications for the other setting No. might be stopped for 1000ms.
136
CHAPTER 10 SIMPLE PLC COMMUNICATION FUNCTION
(6) Errors at the destination device
If an error related to this function occurs, following errors might be detected at the destination device.
• When the destination device is Q/L series: Remote password mismatch error
• When the destination device is A series: Device number specification error
Also, an error might be detected depending on the settings of the destination device or the conditions of Ethernet communication.
10
137
CHAPTER 11
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 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 Field Network
• External devices on the Ethernet network, which are connected through the built-in Ethernet ports
Ethernet device (source)
Network No.1
Ethernet
Network No.2
Network No.3
IP packet transfer
CC-Link IE Field Network
IP packet transfer
CC-Link IE Field Network
IP packet transfer
Ethernet Network No.4
: Access path from an Ethernet device (source)
to an Ethernet device (destination)
Ethernet device (destination)
This function is supported only by GX Works2. (It is not supported by GX Developer.)
Note11.1
138
Note11.1
LCPU
Check the versions of the CPU module and GX Works2 when using the IP packet transfer function.
(
CHAPTER 11 IP PACKET TRANSFER FUNCTION
(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 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 Field Network
The above processing causes communication speeds to be slower than Ethernet lines. Manuals for the
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.
11
139
APPENDICES
Appendix 1
Operation Processing Time for Each
Instruction
The table below indicates the operation processing times required for the instructions introduced in this manual.
For details on the processing time, refer to the following.
MELSEC-Q/L Programming Manual (Common Instruction)
Type Instruction Condition L02CPU, L02CPU-P
Minimum
Processing time (µs)
Maximum
L06CPU, L26CPU, L26CPU-BT,
L26CPU-PBT
Minimum Maximum
Instructions for the socket communication function
SP.SOCOPEN
SP.SOCCLOSE
SP.SOCRCV
S.SOCRCVS
SP.SOCSND
SP.SOCCINF
SP.SOCCSET
SP.SOCRMODE
SP.SOCRDATA
TCP
Active
Unpassive
Fullpassive
UDP
TCP
From the host
CPU
From the connected device
UDP
TCP
1 byte
2046 bytes
UDP
1 byte
2046 bytes
1 byte
TCP
2046 bytes
1 byte
UDP
2046 bytes
1 byte
TCP
2046 bytes
1 byte
UDP
2046 bytes
-
-
Standard mode
Fixed-length mode
Fixed-length mode
Standard mode
1 word
5120 words
27.20
18.90
16.90
16.30
504.30
16.30
504.30
45.70
379.70
45.70
379.70
17.10
13.30
16.00
13.00
500.00
58.90
56.60
50.70
46.30
532.60
46.30
532.60
61.30
395.30
61.30
395.30
43.70
42.90
39.60
35.60
521.60
23.50
16.60
15.40
16.00
394.20
16.00
394.20
36.60
267.60
36.60
267.60
14.70
12.70
13.70
11.30
389.70
45.50
43.80
39.20
29.30
26.10
404.30
35.20
413.20
35.20
413.20
48.20
278.20
48.20
278.20
32.30
31.40
140
APPENDICES
Appendix 2
Port Numbers Used by Built-in Ethernet Port
LCPU
Do not specify the following port numbers, because these numbers are used by the system.
Port number
1388
H
(5000)
1389
H
(5001)
138A
H
(5002)
138B
H
(5003) to 138D
H
(5005)
138E
H
(5006)
138F
H
(5007)
1390
H
(5008)
1391
H
(5009)
Application
For future extension (For Q series Ethernet modules, this port number is used for "Auto Open UDP Port".)
For future extension (For Q series Ethernet modules, this port number is used for "over UDP/IP and Ethernet module".)
For future extension (For Q series Ethernet modules, this port number is used for "over TCP/IP and Ethernet module".)
For future extension
MELSOFT communication port (over UDP/IP and CPU module)
MELSOFT communication port (over TCP/IP and CPU module)
MELSOFT direct connection port (over CPU module)
For future extension
Appendix 3
Added and Changed Functions
The following table shows the built-in Ethernet function, which is changed or added to the CPU module and GX
Works2, as well as the serial No. and software version of the CPU module and GX Works 2 that support the function.
Added function
Serial No. (first 5 digits) of CPU module
GX Works2 version Reference
*1
*2
Simple PLC communication function
*1
IP packet transfer function
*1 *2
"13042" or later
"14112" or later
1.62Q or later
1.98C or later
This function cannot be used for some models. For the availability of the function, refer to each reference.
For the versions of the intelligent function modules that support the function, refer to the manual for the intelligent function module used.
A
141
Appendix 4
Performance List of Simple PLC
Communication Function
This section shows the performance of the execution interval (simple PLC communication function). The execution interval varies depending on the number of settings, the number of communication points, the scan time of the CPU module. The interval is also affected by the execution conditions of other functions or Ethernet communication condition.
(1) Condition 1
• Communication Setting: "Fixed Interval"
• Destination device: "MELSEC-Q/L (Built-in Ethernet Function)" = L26CPU-BT
• Sequence scan time (host station): 1ms (the period before the execution of simple PLC communication function)
• Sequence scan time (destination device): 1ms (The destination device means both the transmission source and transmission destination for data transfer.)
• Device data: Bit device = M, Word device = D
• Number of settings: The number of destination devices (Double the number for data transfer.)
• The retry of communication is not performed.
CPU module
Communication
Pattern
Number of communication points for one setting
Processing time by the number of settings (unit: ms)
1 8 16
10.0
18.1
30.7
L02CPU,
L02CPU-P
L06CPU,
L26CPU,
L26CPU-BT,
L26CPU-PBT
*1
Read
Write
Transfer
Read
Write
Transfer
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
Number of points for each device (bit device and word device)
10.0
10.0
10.0
10.0
12.0
14.0
14.0
20.0
10.0
10.0
10.0
10.0
10.0
12.0
14.0
14.0
20.0
18.2
37.8
18.2
18.3
39.2
27.3
27.3
58.0
18.1
18.2
37.8
18.2
18.3
39.2
27.3
27.3
58.0
31.0
-
31.0
31.1
-
48.6
48.6
-
30.7
31.0
-
31.0
31.1
-
48.6
48.6
-
142
APPENDICES
(2) Condition 2
• Communication Setting: "Fixed Interval"
• Destination device: "MELSEC-Q/L (Built-in Ethernet Function)" = L26CPU-BT
• Sequence scan time (host station): 10ms (the period before the execution of simple PLC communication function)
• Sequence scan time (destination device): 1ms (The destination device means both the transmission source and transmission destination for data transfer.)
• Device data: Bit device = M, Word device = D
• Number of settings: The number of destination devices (Double the number for data transfer.)
• The retry of communication is not performed.
CPU module
L02CPU,
L02CPU-P
L06CPU,
L26CPU,
L26CPU-BT,
L26CPU-PBT
*1
Communication
Pattern
Number of communication points for one setting
Read
Write
Transfer
Read
Write
Transfer
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
32 words for each
*1
(Total 64 words)
64 words for each
*1
(Total 128 words)
256 words for each
*1
(Total 512 words)
Number of points for each device (bit device and word device)
11.0
12.0
13.0
14.0
20.0
10.0
11.0
11.0
10.0
10.0
11.0
12.0
13.0
14.0
20.0
Processing time by the number of settings (unit: ms)
1 8 16
10.0
17.6
29.8
11.0
11.0
17.9
37.4
30.2
-
18.1
18.2
39.5
26.7
26.9
58.3
30.7
31.0
-
47.4
47.9
-
17.6
17.9
37.4
18.1
18.2
39.5
26.7
26.9
58.3
31.0
-
47.4
47.9
-
29.8
30.2
-
30.7
A
143
Appendix 5
Specifications Comparison with Ethernet
Module
(1) Specifications Comparison with the Ethernet Module
The following table lists the comparison of specifications between the Built-in Ethernet port LCPU and the
Ethernet module (LJ71E71-100).
Item Description
4E frame
• Reads/writes data in the CPU module from/to an external device.
• A frame format that can receive multiple request messages at a time.
MC protocol communication
QnA-compat ible 3E frame
Reading/Writing data in device memory
Other
Reads/writes data (device) in the CPU module from/to an external device.
A-compatible 1E frame
Reads/writes data (file) in the CPU module from/to an external device.
• Reads/writes data in the CPU module from/to an external device.
• A frame format that is compatible with A series E71.
Fixed buffer communication
With procedure ("Procedure exist")
Without procedure ("No procedure")
Sends/receives any data between the CPU module and an external device using the fixed buffer of the Ethernet module.
Random access buffer communication
E-mail function
Communications using data link instructions
File transfer (FTP server function)
Web function
Communications relayed through CC-Link IE Controller
Network, CC-Link IE Field Network, MELSECNET/H, and/or MELSECNET/10
Router relay function
Send frame setting
Ethernet (V2.0)
IEEE802.3
Reads/writes data from/in the random access buffer of the
Ethernet module from/to multiple external devices.
Sends/receives data by e-mail.
• Sending/receiving e-mail by the CPU module
• Sending/receiving e-mail using the CPU module monitoring function (the automatic notification function) of the Ethernet module
Reads/writes data in the CPU module on another station via Ethernet using data link instructions.
Reads/writes data in the CPU module in file units from/to an external device using FTP commands.
Communicates CPU module information (a state of the
CPU module or a device value) with a personal computer or a programmable controller in remote locations through
Internet.
Communicates data over multiple networks in the system where an Ethernet network and other networks co-exist, or where data are communicated over multiple Ethernet networks.
Communicates data via a router or gateway. (The router relay function is not a function by which the Ethernet module works as a router.)
Sends data using the frame format selected for the
Ethernet header of the data link layer.
Availability
Built-in Ethernet port LCPU
LJ71E71-100
×
*1 *8
×
×
×
×
×
×
×
×
×
*9
*2
*3
144
APPENDICES
Item Description
Check with Ping ("Use the Ping")
Alive check function
(alive check of an external device)
Check with KeepAlive ("Use the
KeepAlive")
Pairing open
Communication using automatic open UDP port setting
Remote password check
Simultaneous broadcast
Connection to MELSOFT products or GOT
Find CPU function
Time setting function (SNTP client)
User connection
Checks the connection status of an external device by sending a Ping message (ICMP Echo) to an external device. Closes the corresponding connection if no response message is received.
Checks the connection status of an external device by sending an ACK message, which notifies an open status of the connection opened using the TCP protocol to an external device.
Enables data communications using two connections with opening of one port, by pairing the receiving connection with the sending connection.
Enables communications without performing open/close processing after the station, in which an Ethernet module is mounted, is started up.
Prevents unauthorized access to the CPU module by users in remote locations.
Enables simultaneous broadcast to all Ethernet module connected stations within the same Ethernet network, when 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 programming tool and MX Component) or GOT
Finds the CPU modules connected to the same hub as GX
Developer, and displays a list.
Collects time information from the time information server and sets time in the CPU module automatically.
Connection which is used by user during communications using the MC protocol or the fixed buffer.
Can be used as MELSOFT communication port of system connection by setting parameters.
Up to 16 connections can be used.
System connection
Auto open UDP port
FTP transmission port
MELSOFT transmission port
(UDP/IP)
MELSOFT transmission port
(TCP/IP)
HTTP port
MELSOFT direct connection
Connection which is used by the system only.
Simple CPU communication function
IP packet transfer function
Allows data communications between specified devices at the specified timing just by doing simple settings from a programming tool.
Communicates data (using FTP or HTTP) through the built-in Ethernet ports from an Ethernet device (such as a personal computer) to the following IP-compatible devices connected via a CC-Link IE Field Network module.
• External devices on CC-Link IE Field Network
• External devices on the Ethernet network, which are connected through the built-in Ethernet ports
Availability
Built-in Ethernet port LCPU
LJ71E71-100
×
×
×
*10
×
*4
*5
×
*5
×
×
×
×
×
*6
*6 *7
A
145
146
*1 Available commands are limited. (
*2
*3
*4
*5
*6
*7
*8
*9
The "quote cpuchg" command cannot be used. (
Only the default router can be specified.
Settings are fixed to the following: Interval timer: 5 seconds, Resend timer: 8 times.
Up to 16 devices can be connected by setting "MELSOFT Connection" for user connections in PLC parameter.
The MELSOFT transmission port corresponds to the GX Developer transmission port of LJ71E71-100.
Up to 17 devices can be connected (including one system connection) by setting "MELSOFT Connection" for user connections in the network parameter.
For processing on the external device side, refer to Page 147, Appendix 5 (2).
versions of the CPU module and programming tool before using the function. (
*10 Executable with the socket communication function. Check the versions of the CPU module and programming tool before using the function. (
*11 Check the versions of the CPU module and programming tool before using the function. (
Remark
For Ethernet modules, refer to the following.
MELSEC-L Ethernet Interface Module User's Manual (Basic)
APPENDICES
(2) Differences on MC protocol functions between the Built-in Ethernet port LCPU and Ethernet module
connection
Item
Data sending method on
TCP when the response message size exceeds
1460 bytes
(TCP Maximum Segment
Size Option transmission)
Wait time for receiving entire message (from the first message to the last message) when a request message is split and sent
Operation when request messages are consecutively sent to one
LJ71E71-100
Data sending method is selectable.
(Default: "Disable TCP
Maximum Segment
Size Option transmission")
1 to 16383.5 seconds.
(Default: 30 seconds)
(The time value can be changed in "Response monitoring timer" under
"Timer setting" of GX
Developer.)
Even when one connection consecutively receives request messages, each request message can be processed.
Built-in Ethernet port
LCPU
Data sending method is fixed to "Enable TCP
Maximum Segment
Size Option transmission" and cannot be changed.
Fixed to one second. (A request message is discarded if the next part of the split message cannot be received within one second.)
When one connection receives another request message before responding a request message, the second message is discarded.
Consequence of a communication with the
Built-in Ethernet port LCPU
Action
If the response message size exceeds 1460 bytes, the message split by the external device may not be read correctly.
If each part of the split request message is not sent within one second, a response message is not returned and a communication timeout occurs in the external device.
If request messages are consecutively sent to one connection, response messages are not returned and a communication timeout may occur in the external device.
Perform the procedure described
external device can process split data.
Retry communication from the external device.
If a communication timeout frequently occurs, reduce the load of the external device or Ethernet network.
Check that the external device receives a response message before sending next request message.
(Do not consecutively send request messages from the external device.)
A
147
(3) Differences between the socket communication and the nonprocedural communication using a fixed buffer of the Ethernet module
Item
Instruction name
Pairing open not required
Automation of UDP and
TCP-Full/Unpassive open
Data sending method on TCP when the message size exceeds 1460 bytes (TCP
Maximum Segment
Size Option transmission)
LJ71E71-100 Built-in Ethernet port LCPU
Consequence of a communication with the
Built-in Ethernet port LCPU
ZP.OPEN
ZP.CLOSE
ZP.BUFRCV
Z.BUFRCVS
ZP.BUFSND
When sending or receiving data using one connection, two connections are occupied by the paring open setting.
Select whether UDP and
TCP-Full/Unpassive open is performed by the initial timing setting parameter automatically or by an instruction.
SP.SOCOPEN
SP.SOCCLOSE
SP.SOCRCV
S.SOCRCVS
SP.SOCSND
When sending or receiving data using one connection, paring setting is not used.
UDP and TCPFull/
Unpassive open is automatically performed.
-
-
-
Select whether to enable
TCP Maximum Segment Size
Option transmission in the buffer memory.
(Default: "Disable TCP
Maximum Segment Size
Option transmission")
"Enable TCP Maximum
Segment Size Option transmission"
When communications with the LJ71E71-100 are used for a CPU module which performs TCP communications with an external device with the message size over 1460 bytes, the external device may not correctly read split data.
Connection information acquisition and setting methods
Activation of an interrupt program in data receiving
Performed by reading from or writing to the buffer memory.
Performed using socket function instructions.
-
-
Host station port number
Specification of alive check
Ethernet address specification using the OPEN instruction
Maximum communication data size
An interrupt program can be activated during data receiving.
The following numbers cannot be used as host station port number.
1388
H
to 138A
H
(5000 to
5002)
Select whether to perform alive check of TCP/IP and
UDP/IP using parameters.
An interrupt program cannot be activated during data receiving.
The following numbers cannot be used as host station port number.
1388
H
to 1391
H
(5000 to
5009)
Alive check for TCP/IP is performed by default.
Alive check for UDP/IP is not available.
Ethernet address (MAC address) of the external device can be specified using the ZP.OPEN instruction.
Ethernet address (MAC address) of the external device cannot be specified.
2046 bytes
• Serial number (first 5 digits) is "12051" or earlier:
2046 bytes
• Serial number (first 5 digits) is "12052" or later:
10238 bytes
-
-
-
-
Action
Replace the instruction name.
Set only one connection by parameter.
When connection No. of the instruction is the same as the second connection
No. of paring open, replace it with the first connection No.
Delete the instructions for open and close for UDP and
TCP-Full/Unpassive.
Perform the procedure indicated in
Page 60, Section 6.3 (7) so that the external device can process split data.
Replace the information acquisition and setting methods with the
SP.SOCCINF or SP.SOCCSET instruction.
Program the data receiving processing at the beginning of the scan program.
Change the port number.
As described in the left columns.
Specify "0" for the Ethernet address.
(No specification is required. The
Ethernet address is automatically acquired for communication.)
-
148
INDEX
A
Active open
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
B
binary bye
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
C
class
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Close
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
CPU module
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
CPU-module-dedicated subcommands
D
delete
. . . . . . . . . . . . . . . . . . 39
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
. . . . . . . . . . . . . . . . . . . . . . . . . 31
E
. . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Ethernet communication
. . . . . . . . . . . . . . . . . . . . 22
F
FTP
. . . . . . . . . . . . . . . . . . . . . . . 94
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
. . . . . . . . . . . . . . . . . . . . . . . . . 101
Fullpassive
. . . . . . . . . . . . . . . 104
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
G
get
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
H
Hosts file
Hub
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
K
KeepAlive
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
L
ls
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Lock processing
. . . . . . . . . . . . . . . . . . . . . . . . . 115
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
M
mdir
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
mget
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
mls
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
mput
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
N
NAK message
. . . . . . . . . . . . . . . . . . . . . . . . . . . 36
O
open
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
P
passwd-rd
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
passwd-wr
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
password-lock
. . . . . . . . . . . . . . . . . . . . . . . . . . 109
password-unlock
. . . . . . . . . . . . . . . . . . . . . . . . 108
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Programming tool
. . . . . . . . . . . . . . . . . . . . . . . . . 17
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 pwd
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Q
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 quote
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
R
recv function
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Routers
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
S
SD memory card
. . . . . . . . . . . . . . . . . . . . . . . . . 17
Simple connection
. . . . . . . . . . . . . . . . . . . . 27
. . . . . . . . . . . . . . . . . . . . . . . . 31
. . . . . . . . . . . . . . . . . . . . 56
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SNTP client
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Socket communication function instructions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Subcommand
. . . . . . . . . . . . . . . . . . . . . . . . . . . 102
T
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
I
2
7
8
149
TCP fixed-length receive mode
. . . . . . . . . . . . . . . 87
. . . . . . . . . . . . . . . . . . . . . . 40
TCP standard receive mode
TIME SETTING FUNCTION
. . . . . . . . . . . . . . . . . 87
. . . . . . . . . . . . . . . . . 91
U
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
unlock processing
Unpassive
. . . . . . . . . . . . . . . . . . . . . . . 115
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
W
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
150
INSTRUCTION INDEX
S
S(P).SOCRDATA
S.SOCRCVS
. . . . . . . . . . . . . . . . . . . . . . . . . 89
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
SP.SOCCINF
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
. . . . . . . . . . . . . . . . . . . . . . . . . . 67
SP.SOCCLOSE
. . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SP.SOCRCV
. . . . . . . . . . . . . . . . . . . . . . . . . . . 62
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
SP.SOCSND
. . . . . . . . . . . . . . . . . . . . . . . . . . 86
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7
8
I
2
151
REVISIONS
Print date *Manual number
January 2010 SH(NA)-080891ENG-A First edition
April 2010 SH(NA)-080891ENG-B
*The manual number is given on the bottom left of the back cover.
Revision
Partial correction
Section 8.5
January 2011 SH(NA)-080891ENG-C
Partial correction
TERMS, Chapter 2, Section 3.5, 5.1, 6.1, 6.2, 6.3, 6.4.1, 6.4.3, 6.4.4, 6.4.5,
6.4.6, 8.4.2, 8.5
Additions
Appendix 2
July 2011 SH(NA)-080891ENG-D Addition of LCPU models
Model addition
L02CPU-P, L26CPU-PBT
Partial correction
INTRODUCTION, Chapter 1, Section 5.2.2, 6.3, 6.4.1, 6.4.6, Appendix 1
Additions
Chapter 10, Section 10.1, 10.2 10.3, 10.4, 10.5, Appendix 3, Appendix 4
September 2011 SH(NA)-080891ENG-E
Partial correction
SAFETY PRECAUTIONS, RELEVANT MANUALS, TERMS, Chapter 2,
Section 3.5, 5.2.2
May 2012 SH(NA)-080891ENG-F
Partial correction
Section 3.1, 3.5, 5.1, 6.1, 6.2, 8.4.2, 10.1
February 2013 SH(NA)-080891ENG-G Addition of LCPU models and overall revision because of the model addition
Model addition
L06CPU, L26CPU
Japanese manual version SH-080875-H
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.
© 2010 MITSUBISHI ELECTRIC CORPORATION
152
WARRANTY
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product within the gratis warranty term, the product shall be repaired at no cost via the sales representative or
Mitsubishi Service Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at the customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing on-site that involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of repair parts shall not exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc., which follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels on the product.
(2) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused by the user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions or structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary by industry standards, had been provided.
4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the instruction manual had been correctly serviced or replaced.
5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force majeure such as earthquakes, lightning, wind and water damage.
6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from
Mitsubishi.
7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA Center may differ.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation of damages caused by any cause found not to be the responsibility of Mitsubishi, loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products, special damages and secondary damages whether foreseeable or not, compensation for accidents, and compensation for damages to products other than Mitsubishi products, replacement by the user, maintenance of on-site equipment, start-up test run and other tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
153
Microsoft, Windows, Windows NT, and Windows Vista are registered trademarks of Microsoft Corporation in the United
States and other countries.
Pentium is a trademark of Intel Corporation in the United States and other countries.
Ethernet is a trademark of Xerox Corporation.
The SD logo and SDHC logo are trademarks.
All other company names and product names used in this manual are trademarks or registered trademarks of their respective companies.
154
SH(NA)-080891ENG-G
MITSUBISHI ELECTRIC
HEADQUARTERS
MITSUBISHI ELECTRIC EUROPE B.V.
German Branch
Gothaer Straße 8
D-40880 Ratingen
Phone: +49 (0)2102 / 486-0
Fax: +49 (0)2102 / 486-1120
EUROPE
MITSUBISHI ELECTRIC EUROPE B.V.-org.sl.
Czech Branch
Avenir Business Park, Radlická 714/113a
CZ-158 00 Praha 5
Phone: +420 - 251 551 470
Fax: +420 - 251-551-471
CZECH REP.
FRANCE MITSUBISHI ELECTRIC EUROPE B.V.
French Branch
25, Boulevard des Bouvets
F-92741 Nanterre Cedex
Phone: +33 (0)1 / 55 68 55 68
Fax: +33 (0)1 / 55 68 57 57
IRELAND MITSUBISHI ELECTRIC EUROPE B.V.
Irish Branch
Westgate Business Park, Ballymount
IRL-Dublin 24
Phone: +353 (0)1 4198800
Fax: +353 (0)1 4198890
MITSUBISHI ELECTRIC EUROPE B.V.
Italian Branch
Viale Colleoni 7
I-20864 Agrate Brianza (MB)
Phone: +39 039 / 60 53 1
Fax: +39 039 / 60 53 312
ITALY
MITSUBISHI ELECTRIC EUROPE B.V.
Poland Branch
Krakowska 50
PL-32-083 Balice
Phone: +48 (0)12 / 630 47 00
Fax: +48 (0)12 / 630 47 01
MITSUBISHI ELECTRIC EUROPE B.V.
52, bld. 3 Kosmodamianskaya nab 8 floor
RU-115054 Мoscow
Phone: +7 495 721-2070
Fax: +7 495 721-2071
POLAND
RUSSIA
MITSUBISHI ELECTRIC EUROPE B.V.
Spanish Branch
Carretera de Rubí 76-80
SPAIN
E-08190 Sant Cugat del Vallés (Barcelona)
Phone: 902 131121 // +34 935653131
Fax: +34 935891579
MITSUBISHI ELECTRIC EUROPE B.V.
UK Branch
Travellers Lane
UK-Hatfield, Herts. AL10 8XB
Phone: +44 (0)1707 / 27 61 00
Fax: +44 (0)1707 / 27 86 95
UK
JAPAN MITSUBISHI ELECTRIC CORPORATION
Office Tower “Z” 14 F
8-12,1 chome, Harumi Chuo-Ku
Tokyo 104-6212
Phone: +81 3 622 160 60
Fax: +81 3 622 160 75
MITSUBISHI ELECTRIC AUTOMATION, Inc.
500 Corporate Woods Parkway
Vernon Hills, IL 60061
Phone: +1 847 478 21 00
Fax: +1 847 478 22 53
USA
EUROPEAN REPRESENTATIVES
GEVA
Wiener Straße 89
AT-2500 Baden
Phone: +43 (0)2252 / 85 55 20
Fax: +43 (0)2252 / 488 60
TECHNIKON
Oktyabrskaya 19, Off. 705
BY-220030 Minsk
Phone: +375 (0)17 / 210 46 26
Fax: +375 (0)17 / 210 46 26
ESCO DRIVES & AUTOMATION
Culliganlaan 3
BE-1831 Diegem
Phone: +32 (0)2 / 717 64 30
Fax: +32 (0)2 / 717 64 31
Koning & Hartman b.v.
Woluwelaan 31
BE-1800 Vilvoorde
Phone: +32 (0)2 / 257 02 40
Fax: +32 (0)2 / 257 02 49
AUSTRIA
BELARUS
BELGIUM
BELGIUM
INEA RBT d.o.o.
BOSNIA AND HERZEGOVINA
Aleja Lipa 56
BA-71000 Sarajevo
Phone: +387 (0)33 / 921 164
Fax: +387 (0)33/ 524 539
BULGARIA AKHNATON
4, Andrei Ljapchev Blvd., PO Box 21
BG-1756 Sofia
Phone: +359 (0)2 / 817 6000
Fax: +359 (0)2 / 97 44 06 1
INEA RBT d.o.o.
Losinjska 4 a
HR-10000 Zagreb
Phone: +385 (0)1 / 36 940 - 01/ -02/ -03
Fax: +385 (0)1 / 36 940 - 03
CROATIA
AutoCont C.S. s.r.o.
Technologická 374/6
CZ-708 00 Ostrava-Pustkovec
Phone: +420 595 691 150
Fax: +420 595 691 199
CZECH REPUBLIC
DENMARK Beijer Electronics A/S
Lykkegårdsvej 17
DK-4000 Roskilde
Phone: +45 (0)46/ 75 76 66
Fax: +45 (0)46 / 75 56 26
Beijer Electronics Eesti OÜ
Pärnu mnt.160i
EE-11317 Tallinn
Phone: +372 (0)6 / 51 81 40
Fax: +372 (0)6 / 51 81 49
ESTONIA
FINLAND Beijer Electronics OY
Peltoie 37
FIN-28400 Ulvila
Phone: +358 (0)207 / 463 540
Fax: +358 (0)207 / 463 541
UTECO
5, Mavrogenous Str.
GR-18542 Piraeus
Phone: +30 211 / 1206 900
Fax: +30 211 / 1206 999
MELTRADE Kft.
Fertő utca 14.
HU-1107 Budapest
Phone: +36 (0)1 / 431-9726
Fax: +36 (0)1 / 431-9727
Beijer Electronics SIA
Ritausmas iela 23
LV-1058 Riga
Phone: +371 (0)784 / 2280
Fax: +371 (0)784 / 2281
Beijer Electronics UAB
Savanoriu Pr. 187
LT-02300 Vilnius
Phone: +370 (0)5 / 232 3101
Fax: +370 (0)5 / 232 2980
GREECE
HUNGARY
LATVIA
LITHUANIA
EUROPEAN REPRESENTATIVES
ALFATRADE Ltd.
99, Paola Hill
Malta- Paola PLA 1702
Phone: +356 (0)21 / 697 816
Fax: +356 (0)21 / 697 817
INTEHSIS srl bld. Traian 23/1
MD-2060 Kishinev
Phone: +373 (0)22 / 66 4242
Fax: +373 (0)22 / 66 4280
HIFLEX AUTOM.TECHNIEK B.V.
Wolweverstraat 22
NL-2984 CD Ridderkerk
Phone: +31 (0)180 – 46 60 04
Fax: +31 (0)180 – 44 23 55
Koning & Hartman b.v.
Haarlerbergweg 21-23
NL-1101 CH Amsterdam
Phone: +31 (0)20 / 587 76 00
Fax: +31 (0)20 / 587 76 05
Beijer Electronics AS
Postboks 487
NO-3002 Drammen
Phone: +47 (0)32 / 24 30 00
Fax: +47 (0)32 / 84 85 77
Fonseca S.A.
R. João Francisco do Casal 87/89
PT - 3801-997 Aveiro, Esgueira
Phone: +351 (0)234 / 303 900
Fax: +351 (0)234 / 303 910
MALTA
MOLDOVA
NETHERLANDS
NETHERLANDS
NORWAY
PORTUGAL
Sirius Trading & Services srl
Aleea Lacul Morii Nr. 3
RO-060841 Bucuresti, Sector 6
Phone: +40 (0)21 / 430 40 06
Fax: +40 (0)21 / 430 40 02
INEA RBT d.o.o.
Izletnicka 10
SER-113000 Smederevo
Phone: +381 (0)26 / 615 401
Fax: +381 (0)26 / 615 401
SIMAP s.r.o.
Jána Derku 1671
SK-911 01 Trencín
Phone: +421 (0)32 743 04 72
Fax: +421 (0)32 743 75 20
PROCONT, spol. s r.o. Prešov
Kúpelná 1/A
SK-080 01 Prešov
Phone: +421 (0)51 7580 611
Fax: +421 (0)51 7580 650
ROMANIA
SERBIA
SLOVAKIA
SLOVAKIA
INEA RBT d.o.o.
Stegne 11
SI-1000 Ljubljana
Phone: +386 (0)1 / 513 8116
Fax: +386 (0)1 / 513 8170
Beijer Electronics AB
Box 426
SE-20124 Malmö
Phone: +46 (0)40 / 35 86 00
Fax: +46 (0)40 / 93 23 01
SLOVENIA
SWEDEN
Omni Ray AG
Im Schörli 5
CH-8600 Dübendorf
Phone: +41 (0)44 / 802 28 80
Fax: +41 (0)44 / 802 28 28
SWITZERLAND
GTS
Bayraktar Bulvari Nutuk Sok. No:5
TURKEY
TR-34775 Yukarı Dudullu-Ümraniye-İSTANBUL
Phone: +90 (0)216 526 39 90
Fax: +90 (0)216 526 3995
UKRAINE CSC Automation Ltd.
4-B, M. Raskovoyi St.
UA-02660 Kiev
Phone: +380 (0)44 / 494 33 55
Fax: +380 (0)44 / 494-33-66
EURASIAN REPRESENTATIVES
TOO Kazpromavtomatika
Ul. Zhambyla 28
KAZ-100017 Karaganda
Phone: +7 7212 / 50 10 00
Fax: +7 7212 / 50 11 50
KAZAKHSTAN
MIDDLE EAST REPRESENTATIVES
I.C. SYSTEMS LTD.
23 Al-Saad-Al-Alee St.
EG-Sarayat, Maadi, Cairo
Phone: +20 (0) 2 / 235 98 548
Fax: +20 (0) 2 / 235 96 625
ILAN & GAVISH Ltd.
24 Shenkar St., Kiryat Arie
IL-49001 Petah-Tiqva
Phone: +972 (0)3 / 922 18 24
Fax: +972 (0)3 / 924 0761
GIRIT CELADON LTD
12 H'aomanut Street
IL-42505 Netanya
Phone: +972 (0)9 / 863 39 80
Fax: +972 (0)9 / 885 24 30
EGYPT
ISRAEL
ISRAEL
CEG INTERNATIONAL
Cebaco Center/Block A Autostrade DORA
Lebanon - Beirut
Phone: +961 (0)1 / 240 430
Fax: +961 (0)1 / 240 438
LEBANON
AFRICAN REPRESENTATIVE
CBI Ltd.
Private Bag 2016
ZA-1600 Isando
Phone: + 27 (0)11 / 977 0770
Fax: + 27 (0)11 / 977 0761
SOUTH AFRICA
Mitsubishi Electric Europe B.V. /// FA - European Business Group /// Gothaer Straße 8 /// D-40880 Ratingen /// Germany
Tel.: +49(0)2102-4860 /// Fax: +49(0)2102-4861120 /// [email protected] /// www.mitsubishi-automation.com
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement