MELSEC-L Ethernet Interface Module User`s

MELSEC-L Ethernet Interface Module
User's Manual (Basic)
-LJ71E71-100
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
Indicates that incorrect handling may cause hazardous conditions,
resulting in death or severe injury.
CAUTION
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.
1
[Design Precautions]
WARNING
● 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.
● To prevent the malfunction of the programmable controller system due to harmful e-mails, take
preventive measures (such as antivirus measures) so that the mail server for this module does not
receive harmful e-mails.
● To maintain the safety of the programmable controller system against unauthorized access from
external devices via the network, take appropriate measures. To maintain the safety against
unauthorized access via the Internet, take measures such as installing a firewall.
● When connecting a peripheral with the CPU module or connecting an external device, such as a
personal computer, with an intelligent function module to modify data of a running programmable
controller, configure an interlock circuit in the program to ensure that the entire system will always
operate safely. For other forms of control (such as program modification or operating status change)
of a running programmable controller, read the relevant manuals carefully and ensure that the
operation is safe before proceeding. Especially, when a remote programmable controller is controlled
by an external device, immediate action cannot be taken if a problem occurs in the programmable
controller due to a communication failure. To prevent this, configure an interlock circuit in the program,
and determine corrective actions to be taken between the external device and CPU module in case of
a communication failure.
● Do not write any data to the "system area" and "write-protect area" (R) of the buffer memory in the
intelligent function module. Also, do not use any "use prohibited" signals as an output signal from the
CPU module to the intelligent function module. Doing so may cause malfunction of the programmable
controller system.
[Design Precautions]
CAUTION
● Do not install the control lines or communication cables together with the main circuit lines or power
cables. Keep a distance of 100mm or more between them. Failure to do so may result in malfunction
due to noise.
● When changing the operating status of the CPU module (such as remote RUN/STOP) from the
external device, select "Always wait for OPEN (Communication possible at STOP time)" for the "Initial
timing" setting in the network parameter. The communication line will be closed when "Do not wait for
OPEN (Communications impossible at STOP time)" is selected and the remote STOP is executed
from the external device. Consequently, the CPU module cannot reopen the communication line, and
the external device cannot execute the remote RUN.
2
[Installation Precautions]
CAUTION
● Use the programmable controller in an environment that meets the general specifications in the Safety
Guidelines included with the MELSEC-L series CPU module.
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.
● 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.
● Do not directly touch any conductive parts and electronic components of the module. Doing so can
cause malfunction or failure of the module.
[Wiring Precautions]
CAUTION
● Securely connect the connector to the module. Poor contact may cause malfunction.
● 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.
● When disconnecting the communication and power cables from the module, do not pull the cables by
hand. For the cable with connector, hold the connector part of the cable. 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.
[Startup and Maintenance Precautions]
WARNING
● Shut off the external power supply (all phases) used in the system before cleaning the module. Failure
to do so may result in electric shock.
[Startup and Maintenance Precautions]
CAUTION
● Do not disassemble or modify the module. Doing so may cause failure, malfunction, injury, or a fire.
● Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may cause the module to fail or malfunction.
● After the first use of the product (module and display unit), the number of connections/disconnections
is limited to 50 times (in accordance with IEC 61131-2). Exceeding the limit may cause malfunction.
● 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.
3
[Operating Precautions]
CAUTION
● When changing data and operating status, and modifying program of the running programmable
controller from a personal computer connected to an intelligent function module, read relevant
manuals carefully and ensure the safety before operation. Incorrect change or modification may
cause system malfunction, damage to the machines, or accidents.
[Disposal Precautions]
CAUTION
● When disposing of this product, treat it as industrial waste.
4
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.
5
INTRODUCTION
Thank you for purchasing the Mitsubishi MELSEC-L series programmable controllers. This manual describes the
operating procedure, system configuration, parameter settings, functions, programming, and troubleshooting of the
LJ71E71-100 Ethernet interface module (hereafter referred to as E71).
Before using this 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 an 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.
Remark
Unless otherwise specified, this manual describes the program examples in which the I/O numbers of X/Y00 to X/Y1F are
assigned for an E71.
For I/O number assignment, refer to the following.
MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)
COMPLIANCE WITH EMC AND LOW VOLTAGE
DIRECTIVES
(1) Method of ensuring compliance
To ensure that Mitsubishi programmable controllers maintain EMC and Low Voltage Directives when incorporated
into other machinery or equipment, certain measures may be necessary. Please refer to one of the following
manuals.
• MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)
• Safety Guidelines (This manual is included with the CPU module.)
The CE mark on the side of the programmable controller indicates compliance with EMC and Low Voltage
Directives.
(2) Additional measures
To ensure that this product maintains EMC and Low Voltage Directives, please refer to one of the manuals listed
under (1).
6
RELEVANT MANUALS
The manuals related to this product are listed below. Please place an order as needed.
(1) E71 relevant manual
Manual name
Description
<manual number (model code)>
E-mail function, communication function (communications via
MELSEC-Q/L Ethernet Interface Module User's Manual (Application)
<SH-080010, 13JL89>
CC-Link IE Controller Network, CC-Link IE Field Network,
MELSECNET/H, or MELSECNET/10, and communications by
using the data link instructions), and file transfer (FTP server)
function of the E71
MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)
<SH-080180, 13JR40>
MELSEC Communication Protocol Reference Manual
<SH-080008, 13JF89>
Web function of the E71
Details of MELSEC communication protocol (MC protocol) that
is used for data communication between a target device and a
CPU module
(2) CPU module user’s manual
Manual name
Description
<manual number (model code)>
MELSEC-L CPU Module User's Manual (Hardware Design,
Maintenance and Inspection)
<SH-080890ENG, 13JZ36>
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
MELSEC-L CPU Module User's Manual (Function Explanation, Program
Fundamentals)
Functions and devices of the CPU module, and programming
<SH-080889ENG, 13JZ35>
(3) Operating manual
Manual name
Description
<manual number (model code)>
GX Works2 Version 1 Operating Manual (Common)
<SH-080779ENG, 13JU63>
GX Works2 Version 1 Operating Manual (Intelligent Function Module)
<SH-080921, 13JU69>
System configuration, parameter settings, and online
operations of GX Works2, which are common to Simple projects
and Structured projects
Parameter settings for intelligent function modules, monitoring
operations, and the predefined protocol support function of GX
Works2
7
CONTENTS
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
COMPLIANCE WITH EMC AND LOW VOLTAGE DIRECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
MANUAL PAGE ORGANIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
PACKING LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
CHAPTER 1 FEATURES
19
CHAPTER 2 PART NAMES
25
CHAPTER 3 SPECIFICATIONS
27
3.1
General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2
Performance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.3
Function List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.4
3.5
3.3.1
Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
3.3.2
Use with other functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
List of I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.5.1
Configuration of the buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
3.5.2
List of buffer memory addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
CHAPTER 4 PROCEDURES BEFORE OPERATION
55
CHAPTER 5 SYSTEM CONFIGURATION
57
5.1
Overall System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
5.2
Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.3
Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
CHAPTER 6 INSTALLATION AND WIRING
6.1
Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
6.2
Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
CHAPTER 7 COMMUNICATION PROCEDURE
7.1
7.2
8
61
64
Setting Parameters Required for Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.1.1
Parameter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
7.1.2
Basic setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
7.1.3
Ethernet Operation Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
7.1.4
Open Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
TCP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
7.2.1
Establishing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
7.2.2
Communication process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
7.3
7.2.3
Active open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
7.2.4
Passive open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77
UDP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.3.1
Communication process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
7.3.2
Open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80
CHAPTER 8 CONNECTING MELSOFT PRODUCTS AND A GOT
82
8.1
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
8.2
Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
CHAPTER 9 MC PROTOCOL COMMUNICATIONS
85
9.1
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
9.2
Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
9.3
Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
9.4
Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
CHAPTER 10 SLMP COMMUNICATIONS
89
10.1
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
10.2
Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
10.3
Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
10.4
Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
10.5
Available command list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL 95
11.1
Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
11.2
Communication Type of Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
11.3
Packet Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
11.4
Execution Condition of Predefined Protocol Communication . . . . . . . . . . . . . . . . . . . . . . . . . 108
11.5
Example of Predefined Protocol Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.5.1
System configuration example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
11.5.2
Parameter Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
11.5.3
Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.1
120
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
12.1.1 Differences between the "Procedure Exist" and "No Procedure" control methods . . . . . . . .120
12.2
Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
12.3
Data Sending Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
12.4
Data Receiving Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
12.4.1 Data receiving using the main program (BUFRCV instruction) . . . . . . . . . . . . . . . . . . . . . . .125
12.4.2 Data receiving using an interrupt program (BUFRCVS instruction) . . . . . . . . . . . . . . . . . . . .128
12.5
Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
12.5.1 Parameter setting when using an interrupt program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
9
12.6
Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
12.6.1 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
12.6.2 Application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133
12.7
Pairing Open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
12.7.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139
12.7.2 Parameter setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140
12.8
Broadcast Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
12.8.1 Sending/receiving procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
12.8.2 Parameter setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
12.8.3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .145
12.9
Example of Communications Using a Fixed Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
12.9.1 System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
12.9.2 Parameter setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .146
12.9.3 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
13.1
13.2
154
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
13.2.1 How data is read from a connected device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
13.2.2 How a connected device writes data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156
13.3
Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
13.4
Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
13.4.1 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
13.4.2 Application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .159
13.4.3 Examples of command and response formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163
13.5
Precautions when Creating Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
13.6
Physical and Logical Addresses of a Random Access Buffer . . . . . . . . . . . . . . . . . . . . . . . . 167
13.7
Example of Communications Using a Random Access Buffer . . . . . . . . . . . . . . . . . . . . . . . . 168
CHAPTER 14 OTHER FUNCTIONS
14.1
169
Router Relay Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
14.1.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
14.1.2 Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
14.2
Communications Using an Auto-open UDP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
14.2.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .174
14.3
IP Filter Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
14.3.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175
14.3.2 Setting method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176
14.3.3 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179
14.3.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
14.4
Remote Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
14.4.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .181
14.4.2 Remote password setting processes (unlock and lock processes) . . . . . . . . . . . . . . . . . . . .182
14.4.3 Remote password check procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183
10
14.4.4 Differences in functions according to the remote password check status (enabled/disabled)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .186
14.4.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188
14.4.6 Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190
14.5
Hub Connection Status Monitor Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
14.6
IP Address in Use Detection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
14.7
Alive Check Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
CHAPTER 15 DEDICATED INSTRUCTIONS
196
15.1
List of Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
15.2
Parameter Settings for Using Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
15.2.1 When using data link instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197
15.3
Precautions for Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
15.4
Organization of the Dedicated Instruction Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
15.5
ZP.OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
15.6
ZP.CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
15.7
GP.ECPRTCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
15.8
ZP.BUFSND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
15.9
ZP.BUFRCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
15.10 Z.BUFRCVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
15.11 ZP.ERRCLR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
15.12 ZP.ERRRD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
15.13 ZP.UINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
CHAPTER 16 TROUBLESHOOTING
239
16.1
Before Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
16.2
Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
16.3
Checking with the Module Error Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
16.4
Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
16.4.1 If the RUN LED turns off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
16.4.2 If the ERR. LED or COM.ERR. LED turns on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242
16.4.3 If the SD/RD LED does not flash when data is sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243
16.5
Checking with a Display Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
16.6
Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
16.6.1 Communications cannot be performed with the connected device.. . . . . . . . . . . . . . . . . . . .245
16.6.2 The E71 frequently fails to receive a message sent from the connected device. . . . . . . . . .247
16.6.3 A dedicated instruction is not completed.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247
16.6.4 MC protocol communications cannot be performed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .248
16.6.5 Communications using SLMP cannot be performed.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .249
16.6.6 Communications using the predefined protocol cannot be performed. . . . . . . . . . . . . . . . . .249
16.6.7 The protocol setting data cannot be read or written. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .250
16.6.8 Data cannot be sent with communications using a fixed buffer.. . . . . . . . . . . . . . . . . . . . . . .251
16.6.9 Data cannot be received with communications using a fixed buffer. . . . . . . . . . . . . . . . . . . .252
16.6.10 Communications using a random access buffer cannot be performed. . . . . . . . . . . . . . . . . .253
16.6.11 The access cannot be allowed/denied correctly by the IP filter.. . . . . . . . . . . . . . . . . . . . . . .254
11
16.6.12 An e-mail cannot be sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255
16.6.13 An e-mail cannot be received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256
16.6.14 Communications using data link instructions cannot be performed. . . . . . . . . . . . . . . . . . . .257
16.7
Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
16.7.1 End codes returned to a connected device during data communications . . . . . . . . . . . . . . .268
16.7.2 Abnormal codes returned during communications using an A-compatible 1E frame. . . . . . .272
16.7.3 Error codes stored in the buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273
16.8
Ethernet Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
16.9
Checking the Status of the E71 with the System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
16.10 How to Turn Off the COM.ERR. LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
APPENDICES
304
Appendix 1 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Appendix 2 Port Numbers Used for the E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Appendix 3 New and Improved Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Appendix 4 Initial Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Appendix 4.1
Setting the initial process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Appendix 4.2
Reinitialization process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315
Appendix 5 Line Status Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Appendix 5.1
PING test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .322
Appendix 5.2
Loopback test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .328
Appendix 6 Self-Diagnostic Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Appendix 6.1
Self-loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .332
Appendix 6.2
Hardware test (H/W Test). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
Appendix 7 Differences from Ethernet Modules of Other Series . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Appendix 7.1
Differences from a built-in Ethernet port LCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334
Appendix 7.2
Differences from Q series modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334
Appendix 7.3
Differences from QnA/A series modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334
Appendix 8 Operation Image and Data Structure of Predefined Protocol . . . . . . . . . . . . . . . . . . . . 339
Appendix 8.1
Operation image of each communication type of protocol . . . . . . . . . . . . . . . . . . . . .339
Appendix 8.2
Verification operation of receive packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345
Appendix 8.3
Data examples of packet elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .346
Appendix 9 Sample Program on the Connected Device Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Appendix 9.1
When Visual C++(R).NET is used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .352
Appendix 9.2
When Visual Basic(R).NET is used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .361
Appendix 10 Checking the Serial Number, Function Version, and MAC address . . . . . . . . . . . . . . . 370
Appendix 11 External Dimension Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Appendix 12 ASCII Code List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
INDEX
373
REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
12
MANUAL PAGE ORGANIZATION
In this manual, pages are organized and the symbols are used as shown below.
The following illustration is for explanation purpose only, and should not be referred to as an actual documentation.
"" is used for window
names and items.
The chapter of
the current page is shown.
shows operating
procedures.
shows mouse
operations.*1
[ ] is used for items
in the menu bar and
the project window.
The section of
the current page is shown.
Ex. shows setting or
operating examples.
shows reference
manuals.
shows notes that
requires attention.
shows
reference pages.
shows useful
information.
*1
The mouse operation example (for GX Works2) is provided below.
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.
[Parameter]
Project window
[PLC 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
13
Pages describing instructions are organized as shown below.
The following illustration is for explanation purpose only, and should not be referred to as an actual documentation.
Instruction
name
Execution condition of the instruction
Structure of the instruction
in the ladder mode
A device with is
applicable to
the instruction.
Setting side
User: A device value is set by the user.
System: A device value is set
by the CPU module.
Descriptions
of setting data
and data type
• Instructions can be executed under the following conditions.
Any time
During on
On the rising edge
During off
On the falling edge
No symbol
• The following devices can be used.
Internal device
*1
Bit*1
Word
X, Y, M, L, F, V, B
T, ST, C, D, W
Constant
File register
R, ZR
For bit data, a bit-specified word device can be used. For example,
K, H
$
K, H
$
Word device.Bit No.
is used for the bit
specification of a word device. (The bit number is specified in hexadecimal.)
For example, the bit 10 of D0 is specified by D0.A . However, bit specification cannot be used for timer (T), retentive
timer (ST), and counter (C).
14
For details on each device, refer to the following.
User's manual (function explanation, program fundamentals) for the CPU module used
The following data types can be used.
Data type
Description
Bit
Bit data or the start number of bit data
BIN 16-bit
16-bit binary data or the start number of word device
BIN 32-bit
32-bit binary data or the start number of double-word device
BCD 4-digit
Four-digit binary-coded decimal data
BCD 8-digit
Eight-digit binary-coded decimal data
Real number
Floating-point data
Character string
Character string data
Device name
Device name data
15
TERMS
Unless otherwise specified, this manual uses the following terms.
Term
ARP
Buffer memory
Buffer memory address
Description
The abbreviation for Address Resolution Protocol. This protocol is used to obtain the MAC address
of Ethernet from an IP address.
A memory in an intelligent function module, where data (such as setting values and monitoring
values) exchanged with a CPU module are stored
An address that indicates the storage location of data assigned to the buffer memory in an
intelligent function module
BUFRCV
The abbreviation for ZP.BUFRCV
BUFRCVS
The abbreviation for Z.BUFRCVS
BUFSND
The abbreviation for ZP.BUFSND
C24
Another term for the L series serial communication module
CLOSE
The abbreviation for ZP.CLOSE
Dedicated instruction
An instruction that simplifies programming for using functions of intelligent function modules
Device
A device (X, Y, M, D, or others) in a CPU module
DNS
The abbreviation for Domain Name System. This system is mainly used to convert host names on
the Internet or domain names used for e-mails to IP addresses.
E71
Another term for the LJ71E71-100
E71-connected station
The abbreviation for the station where the E71 is connected
ECPRTCL
The abbreviation for GP.ECPRTCL
ERRCLR
The abbreviation for ZP.ERRCLR
ERRRD
The abbreviation for ZP.ERRRD
FTP
GX Developer
GX Works2
HTTP
ICMP
Intelligent function module
IP
MAC address
The abbreviation for File Transfer Protocol. This protocol is used to transfer data files over a
network.
The product name of the software package for the MELSEC programmable controllers
The abbreviation for Hyper Text Transfer Protocol. This protocol is used to send and receive
content, such as HTML files, between a Web browser and a Web server.
The abbreviation for Internet Control Message Protocol. This protocol is used to exchange
messages of errors in an IP network or other information related to an Ethernet network.
A module that has functions other than an input or output, such as an A/D converter module and
D/A converter module
The abbreviation for Internet Protocol
A unique identifier assigned to each external device on a network. This address is also known as
an Ethernet hardware address.
The abbreviation for MELSEC Communication Protocol. This protocol is used to access MC
MC protocol
protocol supporting modules, such as the C24 and E71, or programmable controllers connected to
MC protocol supporting modules from external devices.
MELSECNET/10
The abbreviation for a MELSECNET/10 network system
MELSECNET/H
The abbreviation for a MELSECNET/H network system
MELSECNET/H remote I/O station
A generic term for the QJ72LP25-25, QJ72LP25G, and QJ72BR15
MRECV
The abbreviation for ZP.MRECV
MSEND
The abbreviation for ZP.MSEND
MX Component
The abbreviation for MX Component (SW0D5C-ACT-E or later)
OPEN
POP3
16
The abbreviation for ZP.OPEN
The abbreviation for Post Office Protocol Ver.3. This protocol is used to transfer e-mails from a
mail server to a local computer.
Term
Description
A function of GX Works2.
Predefined protocol support function
This function sets protocols appropriate to each external device and reads/writes protocol setting
data from/to the flash ROM of the E71.
Programming tool
Another term for GX Works2
READ
The abbreviation for JP.READ and GP.READ
RECV
The abbreviation for JP.RECV and GP.RECV
RECVS
The abbreviation for Z.RECVS
REQ
The abbreviation for J.REQ, JP.REQ, G.REQ, and GP.REQ
SEND
The abbreviation for JP.SEND and GP.SEND
The abbreviation for Seamless Message Protocol.
SLMP
This protocol is used to access an SLMP-compatible device or a programmable controller
connected to an SLMP-compatible device from an external device.
SMTP
SREAD
The abbreviation for Simple Mail Transfer Protocol. This protocol is used to transfer e-mails over
the Internet.
The abbreviation for JP.SREAD and GP.SREAD
A number used to logically divide one network into multiple subnetworks and manage them easily.
The following Ethernet network systems can be configured:
Subnet mask
• A small-scale Ethernet network system in which multiple network devices are connected
• A medium- or large-scale network system in which multiple small-scale network systems are
connected via routers or other network communication devices
SWRITE
The abbreviation for JP.SWRITE and GP.SWRITE
UINI
The abbreviation for ZP.UINI
WRITE
The abbreviation for JP.WRITE and GP.WRITE
ZNRD
The abbreviation for J.ZNRD and JP.ZNRD
ZNWR
The abbreviation for J.ZNWR and JP.ZNWR
17
PACKING LIST
The following items are included in the package of this product. Before use, check that all the items are included.
LJ71E71-100
LJ71E71-100
18
Before Using the Product
CHAPTER 1 FEATURES
CHAPTER 1
FEATURES
1
An Ethernet module (hereafter abbreviated as E71) is an interface module on the programmable controller side for
connecting a programmable controller system to the host system, such as a personal computer and a workstation,
over Ethernet. The module can collect and modify programmable controller data, monitor and control CPU operating
status, and exchange data in TCP/IP or UDP/IP.
Internet
Connected device
Own station
Connected device
Connected device
Another station
Connected device
Web server
Programming tool
The E71 has the following basic functions.
• Connection with MELSOFT products and a GOT
• Collection and modification of CPU module data from connected devices (MC protocol communications)
• Communications using SLMP
• Data communications using the predefined protocol (predefined protocol support function)
• Exchange of data with connected devices (communications using a fixed buffer and random access buffer)
• Prevention of unauthorized access through the IP filter (IP filter function)
• Prevention of unauthorized access through a remote password (remote password)
• E-mail sending/receiving (e-mail function)
• Data sending/receiving using the Web function
19
(1) Connection with MELSOFT products and a GOT
In Ethernet, a programming tool can create programming of a programmable controller and monitor a
programmable controller (MELSOFT connection), and the GOT can monitor and test a programmable controller.
Remote operations making full use of the Ethernet capability, long-distance connectivity and high-speed
communications, are achieved.
GOT
E71
Programming tool
(2) Collection and modification of CPU module data from connected devices (MC
protocol communications)
The MC protocol enables connected devices to access MC protocol supporting modules over Ethernet. The E71
can communicate with a personal computer and HMI (Human Machine Interface) as long as the connected
devices can receive/send messages in the MC protocol control procedure. By using a separately sold
communication support tool (MX Component), a communication program for the host system can be created
without considering detailed protocols (communication procedures). (
Page 85, CHAPTER 9)
Response
Command
E71
Connected device
(3) Communications using SLMP
SLMP is a protocol that enables connected devices to access SLMP supporting devices over Ethernet. SLMP
communications are available among devices that can receive/send messages in the SLMP control procedure.
(
20
Page 89, CHAPTER 10)
CHAPTER 1 FEATURES
1
(4) Data communications using the predefined protocol (predefined protocol
support function)
Registering protocol data in advance using GX Works2 allows communications by executing only an ECPRTCL
instruction program. In addition, the protocol setting required to communicate with the connected device, such as
a measuring instrument or a bar code reader, can be configured easily using the Predefined Protocol Support
Function of GX Works2. (
Page 95, CHAPTER 11)
1) Setting protocols
Protocols can be set easily using the
predefined protocol support function of
GX Works2.
2) Writing protocols
Write the set protocols in the flash ROM of the E71.
GX Works2
Sending
Connected device
E71
Receiving
3) Executing protocols
Execute protocols by dedicated instructions.
Multiple protocols can be executed by one dedicated
instruction.
Connected device
Data can be communicated
with protocols appropriate to
each connected device.
21
(5) Exchange of data with connected devices (communications using a fixed
buffer and random access buffer)
(a) Communications using a fixed buffer
Up to 1K-word data can be exchanged among programmable controllers or between a programmable
controller and the host system. While MC protocol communications are passive, communications using a fixed
buffer are an active protocol. If an error occurs in equipment or certain conditions are met, the programmable
controller can send data to the host system. Using an interrupt program allows the CPU module to quickly read
received data. (
Page 120, CHAPTER 12)
Send/receive
Another station
Send/receive
Own station
Connected device
(b) Communications using a random access buffer
Up to 6K-word data can be communicated. This buffer is useful when the data size is too large for
communications using a fixed buffer (capacity: 1K word). (
Read/write
Page 154, CHAPTER 13)
Read/write
E71
Connected device
Connected device
(6) Prevention of unauthorized access through the IP filter
The IP address of the connected device to be allowed or denied access is set in the buffer memory, and access
from connected devices is restricted. (
Page 175, Section 14.3)
(7) Prevention of unauthorized access through a remote password
This function prevents unauthorized remote access to the CPU module. The E71 checks an entered remote
password in data communications from a connected device using remote password-protected connection.
(
22
Page 181, Section 14.4)
CHAPTER 1 FEATURES
1
(8) E-mail sending/receiving (e-mail function)
This function sends and receives e-mails to and from a connected device in a remote location via the Internet.
For details, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Application)
(a) E-mail sending/receiving through the CPU module
The following data can be sent and received using the MSEND/MRECV instructions.
• The CPU module can receive/send up to 6K-word data from/to a personal computer or other E71 modules
as an e-mail attachment.
• The CPU module can send up to 960-word data to a personal computer or portable terminal as the main
text of an e-mail.
(b) E-mail sending using the programmable controller CPU monitoring function
Notification conditions (CPU module status or device values) that have been set using parameters are regularly
monitored. When the conditions are met, up to 960-word data can be sent by either of the following data
formats.
• Attachment
• Main text
Internet
Sending/receiving e-mail
Mail server
Mail server
E71
Connected device
23
(9) Data sending/receiving using the Web function
The system administrator can monitor a CPU module in a remote location via the Internet using a Web browser.
For details, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)
HTTP
header
MC protocol
(command message)
HTTP
MC protocol
(response message)
E71
HTTP
header
Web server
HTML
ASP
Communication
library
24
Connected device
Web browser
Display of
requests/
results
CHAPTER 2 PART NAMES
CHAPTER 2
PART NAMES
2
This chapter describes the E71 parts.
1)
1)
2)
5)
3)
4)
1)
No.
1)
1)
Name
Application
Module joint lever
A lever to fix modules

RUN
ON
In normal operation
OFF
An error has occurred. (

INIT.
ON
ON
An open process normally completed (no connection)

ON
Indicates hardware failure status.
A hardware failure has occurred.
OFF
Normal

COM.ERR.*2
Indicates open process status.
An open process normally completed (connection open)
OFF
ERR.
Indicates initial process status.
Not processed

OPEN*1
Page 242, Section 16.4.1)
Normal completion
OFF
2)
Indicates operating status.
Indicates whether a communication failure has occurred.
ON
A communication failure has occurred. (
OFF
Normal communications in progress
Page 242, Section 16.4.2)
25
No.
Name
Application

SPEED
ON
100Mbps
OFF
10Mbps or a cable not connected

3)
SD/RD
Indicates a transmission speed.
Indicates data communication status.
ON
Data communications in progress
OFF
Data not sent or not received (
10BASE-T/100BASE-TX
communication connector
(RJ45)
Page 243, Section 16.4.3)
A connector to connect an E71 to the 10BASE-T or 100BASE-TX network (An E71 judges whether
to connect to the 10BASE-T or 100BASE-TX network based on the hub.)
4)
Serial number display
A display indicating the serial number printed on the rating plate
5)
DIN rail hook
A hook to install the module on a DIN rail
*1
*2
The OPEN LED turns on and off depending on the open status of user connections 1 to 16. (The open status of the
system connections (e.g. automatic open UDP port) is not included.)
If the COM.ERR. LED is on, it does not turn off even if the error cause is eliminated. For how to turn off the LED, refer to
"How to Turn Off the COM.ERR. LED". (
26
Page 303, Section 16.10)
CHAPTER 3 SPECIFICATIONS
CHAPTER 3
SPECIFICATIONS
This chapter describes the performance specifications, functions, CPU module I/O signals, and buffer memory areas
of an E71.
3
3.1
General Specifications
For the general specifications of an E71, refer to the following.
"Safety Guidelines", the manual included with the CPU module
3.2
Performance Specifications
The following table lists the performance specifications of an E71.
Specifications
Item
LJ71E71-100
Data transmission speed
100BASE-TX
10BASE-T
100Mbps
10Mbps
Full-duplex: IEEE802.3x
Flow control
Half-duplex: Back pressure congestion
Back pressure congestion control
Transmission
specifications
Interface
RJ45 (AUTO MDI/MDI-X)
Communication mode
Full-duplex/Half-duplex
Transmission method
Maximum segment length
Maximum number of cascade
connections
Number of simultaneous
open connections
Sending/receiving
data storage
memory
Base band
100m (length between a hub and a node)*1
Cascade connection (maximum of 2
Cascade connection (maximum of 4
levels)*2
levels)*2
16 connections (Connections usable on a program)
Fixed buffer
1k word  16
Random access buffer
6k words  1
Attachment
6k words  1
E-mail
Main text
Number of occupied I/O points
Internal current consumption (5VDC)
External dimensions
Weight
Half-duplex
960 words  1
32 points (I/O assignment: Intelligent 32 points)
0.60A
90 (H)  28.5 (W)  95 (D) [mm]
0.18kg
27
3.1 General Specifications
control
Specifications
Item
LJ71E71-100
100BASE-TX
Data
Attachment
size
Main text
Data transfer method
Subject
Attachment format
MIME
10BASE-T
6k words  1
960 words  1
When sending: Send either a file as attachment or main text (select one).
When receiving: Receive a file as attachment.
Us-ASCII format or ISO-2022-JP (Base64)
MIME format
Version 1.0
Can be selected from binary, ASCII, and CSV.
Data of attachment format
(CSV: Comma Separated Value)
Transmission
specifications
Division of attachment
sending/receiving
data
File name: XXXX.bin (binary), XXXX.asc (ASCII), XXXX.csv (CSV)
Cannot be divided (Only one file can be sent/received.)*3
Subject: Base64/7 bits
When sending (encode)
Main text: 7 bits
Attachment: Base64
Subject: (Does not decode)
When receiving (decode)
Main text: (Cannot be received)
Attached file: Base64/7 bits/8 bits/Quoted Printable*4
Encryption
None
Compression
None
Communications with a mail
server
Operation check mailer
*1
*2
*3
*4
28
SMTP (sending server) Port number = 25, POP3 (receiving server) Port number = 110
Microsoft Corporation Microsoft Office Outlook 2003
For the maximum segment length (a length between hubs), consult with the manufacturer of the switching hub used.
This applies when a repeater hub is used. For the number of levels that can be constructed when a switching hub is
used, consult with the manufacturer of the switching hub used.
If divided files are received, only the first file is received and the remaining files are discarded.
If an e-mail is sent from a connected device to the programmable controller side, specify the encoding method
(Base64/7 bits/8 bits/Quoted Printable) of the attachment.
CHAPTER 3 SPECIFICATIONS
3.3
Function List
This section lists the E71 functions.
3.3.1
Function list
3
The following table lists the functions of the E71.
(1) Basic functions
The following table lists the basic E71 functions explained in this manual.
Function
Connecting with MELSOFT products and a GOT
MC protocol communications
Description
An E71 can be connected with MELSOFT products, such as
a programming tool and MX Component, and a GOT.
CPU module data can be read/written from/to connected
devices. Access to files can be also performed.
Reference
Page 82, CHAPTER 8
Page 85, CHAPTER 9
The connected device can read/write data from/to the buffer
memory or device of an SLMP supporting device connected
Communications using SLMP
to the shared network with the E71. In addition, the
Page 89, CHAPTER 10
connected device can read/write data from/to the device of
the CPU module where an E71 is connected.
Data can be sent/received with protocols appropriate to each
Data communications using the predefined
protocol
connected device.
The connected device side protocol can be easily selected,
Page 95, CHAPTER 11
Works2.
Procedure exists
Any data is sent/received between a CPU module and
No procedure
connected devices using the fixed buffer of an E71.
Page 120, CHAPTER 12
Paring receiving/sending connections enables data
Communications
Pairing open
communications with two connections by performing the
Page 139, Section 12.7
open process for one port.
using a fixed buffer
Broadcast communications are enabled with all E71Broadcast
connected stations in the same Ethernet network that is
communications
connected to the E71 when "No Procedure" communications
Page 141, Section 12.8
using a fixed buffer are performed using UDP/IP.
Communications using a random access buffer
Data is read/written from multiple connected devices to the
random access buffer of an E71.
Page 154, CHAPTER 13
Data communications are performed through a router and a
Router relay function
gateway. This function is not the function where an E71
Page 169, Section 14.1
operates as a router.
Communications using an auto-open UDP port
Communications are enabled without the open/close
processes after an E71-connected station is started up.
Page 174, Section 14.2
The IP address of the connected device to be allowed or
IP filter function
denied access is set in the buffer memory, and access from
Page 175, Section 14.3
connected devices is restricted.
Remote password
Unauthorized remote access to a CPU module is prevented.
Page 181, Section 14.4
The current connection status and transmission speed of an
Hub connection status monitor function
E71 and a hub and the number of times that the E71
Page 191, Section 14.5
detected disconnection can be checked.
29
3.3 Function List
3.3.1 Function list
or created/edited from the Predefined Protocol Library of GX
Function
IP address in use detection function
Description
Reference
If different stations in the same network use the same IP
address, the address in use can be detected.
Whether a connected device is normally operating after a
Alive check function
connection is established (open process) can be checked.
Page 192, Section 14.6
Page 194, Section 14.7
An error that has occurred in an E71 can be stored in the
CPU module as error history. The history data can be stored
Module error collection function
on a memory with the backup power feature; therefore, error
Page 241, Section 16.3
details are held even if the CPU module is reset or the
system is powered off.
(2) Special functions
The following special functions are also available. For the functions, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Application)
Function
Description
Data are sent/received using an e-mail.
• Data sent/received by a CPU module
E-mail function
• Data sent using the programmable controller CPU monitoring function
(automatic notification function)
CC-Link IE Controller Network, CC-Link IE Field
Network, MELSECNET/H, MELSECNET/10 relay
communications
Communications using data link instructions
File transfer (FTP server) function
Data are communicated over multiple network systems where Ethernet and other
networks exist together or network systems that relay multiple Ethernet networks.
Data of a CPU module in other stations can be read/written over Ethernet using
data link instructions.
Data can be read/written in files from connected devices using an exclusive FTP
command.
(3) Web function
This function allows data to be read/written from/to a remote CPU module over the Internet using a Web browser.
For the function, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)
30
CHAPTER 3 SPECIFICATIONS
3.3.2
Use with other functions
The following table lists the relationships between functions that can be used together.
: Available, : Not available or this function does not correspond to the functions in the "Communication function" column.
CC-Link IE
Controller Network,
CC-Link IE Field
Network,
MELSECNET/H,
MELSECNET/10
relay
communications
Router
relay
function
Alive
check
function
*1

Communications
using a fixed buffer
(TCP/IP, UDP/IP)

Communications
using SLMP
(TCP/IP, UDP/IP)
Communication
function
(Communication
method)
3
Pairing
open
Communications
using an auto-open
UDP port
IP filter
function
Remote
password
*2

*1















*3
Data
communications
using the predefined
protocol
(TCP/IP, UDP/IP)







*3
Communications
using a random
access buffer
(TCP/IP, UDP/IP)








E-mail function
(TCP/IP)








Communications
using data link
instructions
(UDP/IP)








File transfer (FTP
server) function
(TCP/IP)








Web function
(TCP/IP)








MC protocol
communications
(TCP/IP, UDP/IP)

*1 *3

*3 *4
3.3 Function List
3.3.2 Use with other functions
*1
*2
*3
*4
Broadcast
communications
These functions cannot be used with an A-compatible 1E frame.
The auto-open UDP port is excluded.
These functions can be used only for UDP/IP communication.
These functions cannot be used for communications using a fixed buffer in the "Procedure Exist" control method.
31
3.4
List of I/O Signals
The following table lists the I/O signals for an E71. The I/O signal assignment of when the start I/O number of an E71 is
0000 is listed below.
Device
number
Signal name
Device
Signal name
number
X0
For fixed buffer communication of connection No.1 (ON:
Sending normal completion or reception completion, OFF: -)
Y0
Connection No.1 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X1
For fixed buffer communication of connection No.1 (ON:
Detection of sending error or reception error, OFF: -)
Y1
Connection No.2 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X2
For fixed buffer communication of connection No.2 (ON:
Sending normal completion or reception completion, OFF: -)
Y2
Connection No.3 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X3
For fixed buffer communication of connection No.2 (ON:
Detection of sending error or reception error, OFF: -)
Y3
Connection No.4 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X4
For fixed buffer communication of connection No.3 (ON:
Sending normal completion or reception completion, OFF: -)
Y4
Connection No.5 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X5
For fixed buffer communication of connection No.3 (ON:
Detection of sending error or reception error, OFF: -)
Y5
Connection No.6 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X6
For fixed buffer communication of connection No.4 (ON:
Sending normal completion or reception completion, OFF: -)
Y6
Connection No.7 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X7
For fixed buffer communication of connection No.4 (ON:
Detection of sending error or reception error, OFF: -)
Y7
Connection No.8 (ON: At sending request or reception complete
confirmation signal, OFF: -)
X8
For fixed buffer communication of connection No.5 (ON:
Sending normal completion or reception completion, OFF: -)
Y8
Connection No.1
(ON: Open request, OFF: -)
X9
For fixed buffer communication of connection No.5 (ON:
Detection of sending error or reception error, OFF: -)
Y9
Connection No.2
(ON: Open request, OFF: -)
XA
For fixed buffer communication of connection No.6 (ON:
Sending normal completion or reception completion, OFF: -)
YA
Connection No.3
(ON: Open request, OFF: -)
XB
For fixed buffer communication of connection No.6 (ON:
Detection of sending error or reception error, OFF: -)
YB
Connection No.4
(ON: Open request, OFF: -)
XC
For fixed buffer communication of connection No.7 (ON:
Sending normal completion or reception completion, OFF: -)
YC
Connection No.5
(ON: Open request, OFF: -)
XD
For fixed buffer communication of connection No.7 (ON:
Detection of sending error or reception error, OFF: -)
YD
Connection No.6
(ON: Open request, OFF: -)
XE
For fixed buffer communication of connection No.8 (ON:
Sending normal completion or reception completion, OFF: -)
YE
Connection No.7
(ON: Open request, OFF: -)
XF
For fixed buffer communication of connection No.8 (ON:
Detection of sending error or reception error, OFF: -)
YF
Connection No.8
(ON: Open request, OFF: -)
X10
Open completed for connection No.1
(ON: Open completion signal, OFF: -)
Y10
Use prohibited
X11
Open completed for connection No.2
(ON: Open completion signal, OFF: -)
Y11
Use prohibited
X12
Open completed for connection No.3
(ON: Open completion signal, OFF: -)
Y12
Use prohibited
X13
Open completed for connection No.4
(ON: Open completion signal, OFF: -)
Y13
Use prohibited
X14
Open completed for connection No.5
(ON: Open completion signal, OFF: -)
Y14
Use prohibited
X15
Open completed for connection No.6
(ON: Open completion signal, OFF: -)
Y15
Use prohibited
X16
Open completed for connection No.7
(ON: Open completion signal, OFF: -)
Y16
Use prohibited
X17
Open completed for connection No.8
(ON: Open completion signal, OFF: -)
Y17
COM.ERR. LED Off request
(ON: At off request, OFF: -)
X18
Open abnormal detection signal
(ON: At off request, OFF: -)
Y18
Use prohibited
32
CHAPTER 3 SPECIFICATIONS
Device
Signal name
number
Device
Signal name
number
X19
Initial normal completion signal
(ON: Normal completion, OFF: -)
Y19
Initial request signal
(ON: At request, OFF: -)
X1A
Initial abnormal end signal
(ON: Abnormal end, OFF: -)
Y1A
Use prohibited
X1B
Use prohibited
Y1B
Use prohibited
X1C
COM.ERR. LED lit confirmation
(ON: lit, OFF: off)
Y1C
Use prohibited
X1D
Predefined protocol ready
(ON: Ready, OFF: -)
Y1D
Use prohibited
X1E
Use prohibited
Y1E
Use prohibited
X1F
Watchdog timer error detection
(ON: Watchdog timer error, OFF: -)
Y1F
Use prohibited
3
Do not use any use prohibited signal as an I/O signal to the CPU module. Doing so may cause malfunction of the
programmable controller system.
Remark
The I/O signals listed in this section are mainly applied when QnA series module programs are used. For the L series, the
I/O signals for intelligent function modules are turned on and off with dedicated instructions. When QnA series module
programs are used, it is recommended to replace the signals with the dedicated instructions described in the section that
describes the corresponding functions.
3.4 List of I/O Signals
33
3.5
Buffer Memory
This section describes the E71 buffer memory.
3.5.1
Configuration of the buffer memory
This section describes a buffer memory configuration.
(1) Buffer memory address configuration
A buffer memory area consists of 16 bits per address.
b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0
(2) Buffer memory area configuration
Buffer memory consists of user areas and system areas.
(a) User areas
A user area is an area where a user writes or reads data. A user area consists of a parameter area for the initial
process and data communications, an area for data communications, and an area to store communication
status and communication error data. Data communications may take long if user areas are used continually;
therefore, use them only when needed.
(b) System areas
A system area is an area used by a system.
Do not write any data to the "system area". Doing so may cause malfunction of the programmable controller system.
34
CHAPTER 3 SPECIFICATIONS
3.5.2
List of buffer memory addresses
The following table lists the buffer memory addresses of an E71.
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
0 and 1
(0H and 1H)
Own station E71 IP address
2 and 3
(2H and 3H)
System area
C00001FEH

Special function settings
Router relay function (b5, b4)
• 00: Do not use
• 01: Use
Conversion system setting for CC-Link IE Controller Network, CC-Link IE
Field Network, MELSECNET/H, MELSECNET/10 relay function (b7, b6)
• 00: Automatic response system
• 01: IP address computation system
• 10: Table exchange system
• 11: Use-together system
FTP function setting (b9, b8)
• 00: Do not use
• 01: Use
4
(4H)
3


0100H

Bits other than those described above are reserved for system use.
5 to 10
(5H to AH)
11
(BH)
3CH
TCP ULP timer value
(Setting time = setting value  500 ms)
Initial process
parameter setting
area

(60)
14H
TCP zero window timer value
(Setting time = setting value  500 ms)
(20)
13
(DH)
TCP resend timer value
(Setting time = setting value  500 ms)
(20)
14
(EH)
TCP end timer value
(Setting time = setting value  500 ms)
(40)
IP assembly timer value
(Setting time = setting value  500 ms)
(10)
15
(FH)
Monitoring
timer
16
(10 H)
Response monitoring timer value
(Setting time = setting value  500 ms)
17
(11H)
Destination existence confirmation starting interval timer
value
(Setting time = setting value  500 ms)
18
(12 H)
Destination existence confirmation interval timer value
(Setting time = setting value  500 ms)
19
(13 H)
Destination existence confirmation resending time
20
(14H)
21 to 29
(15H to 1DH)
14H
28H
AH
3CH
(60)
4B0H
(1200)
14H
(20)
3H
(3)
1388H
Auto-open UDP port number
System area



3.5 Buffer Memory
3.5.2 List of buffer memory addresses
12
(CH)

System area









35
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
TCP Maximum Segment Transmission setting area
• 0H: Enable TCP Maximum Segment Size Option transmission
30
(1EH)
• 8000H: Disable TCP Maximum Segment Size Option transmission
8000H

0H

Re-initialization makes the set value effective.
31
(1FH)
Initial process
parameter setting
area (For
reinitialization)
Communication condition setting (Ethernet Operation Setting) area
Communication data code setting (b1)
• 0: Binary Code
• 1: ASCII Code
TCP existence confirmation setting (b4)
• 0: Use the Ping
• 1: Use the KeepAlive
Send frame setting (b5)
• 0: Ethernet
• 1: IEEE 802.3
Setting of write enable/disable at RUN time (b6)
• 0: Disable
• 1: Enable
Initial timing setting (b8)
• 0: Do not wait for OPEN (Communications impossible at STOP time)
• 1: Always wait for OPEN (Communication possible at STOP time)
Reinitialization specification (b15)
• 0: Reinitialization process complete (reset by the system)
• 1: Reinitialization process request (set by the user)
Bits other than those described above are reserved for system use.
36
CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
32
(20 H)
Connection
usage
setting area
Connection No.1
Usage of fixed buffer (b0)
• 0: For sending, or communications using a fixed buffer
are not performed
• 1: For receiving
Destination existence confirmation (b1)
• 0: No confirm
• 1: Confirm
Pairing open (b7)
• 0: Disable
• 1: Enable
Communication method (protocol) (b8)
• 0: TCP/IP
• 1: UDP/IP
Fixed buffer communication procedure (b10, b9)
• 00: Procedure exists
• 01: No procedure
• 10: Predefined protocol
Open system (b15, b14)
• 00: Active open or UDP/IP
• 10: Unpassive open
• 11: Fullpassive open
3
0H

Own station port No.
0H

Destination IP address
0H

Destination Port No.
0H

FFFFFFFFFFFFH

Bits other than those described above are reserved for
system use.
33
(21 H)
34
(22H)
Connection No.2 (The bit configuration is the same as Connection No.1.)
Communication
parameter setting
area
Connection No.3 (The bit configuration is the same as Connection No.1.)
Connection No.4 (The bit configuration is the same as Connection No.1.)
36
(24H)
Connection No.5 (The bit configuration is the same as Connection No.1.)
37
(25H)
Connection No.6 (The bit configuration is the same as Connection No.1.)
38
(26H)
Connection No.7 (The bit configuration is the same as Connection No.1.)
39
(27H)
Connection No.8 (The bit configuration is the same as Connection No.1.)
40
(28H)
41 to 42
(29H and 2AH)
43
(2BH)
44 to 46
(2CH to 2EH)
Connection
No.1
Communica
tion address
setting area
Destination MAC address
47 to 53
(2FH to 35H)
Connection No.2 (The bit configuration is the same as Connection No.1.)
54 to 60
(36H to 3CH)
Connection No.3 (The bit configuration is the same as Connection No.1.)
3.5 Buffer Memory
3.5.2 List of buffer memory addresses
35
(23H)
37
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
61 to 67
(3DH to 43H)
Connection No.4 (The bit configuration is the same as Connection No.1.)
68 to 74
(44H to 4AH)
Connection No.5 (The bit configuration is the same as Connection No.1.)
75 to 81
(4BH to 51H)
82 to 88
(52H to 58H)
tool setting
applicability
Communication
parameter setting
area
Communica
tion address
setting area
Connection No.6 (The bit configuration is the same as Connection No.1.)
Connection No.7 (The bit configuration is the same as Connection No.1.)
89 to 95
(59H to 5FH)
Connection No.8 (The bit configuration is the same as Connection No.1.)
96 to 102
(60H to 66H)
System area


103 and 104
(67H and 68H)
System area


105
(69H)
106 and 107
(6AH and 6BH)
108 to 110
(6CH to 6EH)
111 to 115
(6FH to 73H)
Area for the
initial
process
116
(74H)
Initial error code
0H

Own station IP address
0H

Own station MAC address
0H


0H
Auto-open UDP port number

117
(75H)
System area
118
(76H)
Station number (b0 to b7)
Network number of the own station (b8 to b15)
0H

Own station group number
0H

Own station port No.
0H

Destination IP address
0H

123
(7BH)
Destination Port No.
0H

124
(7CH)
Open error code
0H

Fixed buffer sending error code
0H

126
(7EH)
Connection end code
0H

127
(7FH)
Fixed buffer communication time
(Maximum value)
0H

128
(80H)
Fixed buffer communication time
(Minimum value)
0H

129
(81H)
Fixed buffer communication time
(Current value)
0H

119
(77H)
120
(78H)
Communication
status storage area
121 and 122
(79H and 7AH)
125
(7DH)
38

System area
Connection
information
area
Connection
No.1


CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
130 to 139
(82H to 8BH)
Connection No.2 (The bit configuration is the same as Connection No.1.)
140 to 149
(8CH to 95H)
Connection No.3 (The bit configuration is the same as Connection No.1.)
150 to 159
(96H to 9FH)
Connection No.4 (The bit configuration is the same as Connection No.1.)
Connection
information
area
160 to 169
(A0H to A9H)
3
Connection No.5 (The bit configuration is the same as Connection No.1.)
170 to 179
(AAH to B3H)
Connection No.6 (The bit configuration is the same as Connection No.1.)
180 to 189
(B4H to BDH)
Connection No.7 (The bit configuration is the same as Connection No.1.)
190 to 199
(BEH to C7H)
Connection No.8 (The bit configuration is the same as Connection No.1.)
200
(C8H)
tool setting
applicability
LED on/off status (Stores the on/off status of the LEDs on
the front of the Ethernet module)
INIT.LED (b0)
• 0: OFF
• 1: ON (initial process completed)
OPEN LED (b1)
• 0: OFF
• 1: ON (connection open processing completed)
ERR.LED (b3)
• 0: OFF
• 1: ON (hardware failure)
COM.ERR.LED (b4)
• 0: OFF
• 1: ON (communication error)
0H

201
(C9H)
Hub connection status area
Communication mode (b9)
• 0: Half duplex
• 1: Full duplex
Hub connection status (b10)
• 0: Hub not connected/disconnected
• 1: Hub connected
Data transmission speed (b15, b14)
• 00: Operating at 10BASE-T
• 01: Operating at 100BASE-TX
Bits other than those described above are reserved for
system use.
0H

202
(CAH)
Switch status (operational mode setting)
Communication data code setting
• 0: Online
• 1: Offline
• 2: Self-loopback test
• 3: Hardware test
0H

Communication
status storage area
Bits other than those described above are reserved for
system use.
3.5 Buffer Memory
3.5.2 List of buffer memory addresses
Area for
module
status
39
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
203
(CBH)
Module
status area
Communication
status storage area
Status of settings with a programming tool
Communication data code setting (b1)
• 0: Communications in a binary code
• 1: Communications in an ASCII code
Initial/open method setting (b2)
• 0: No parameter setting (start up according to the
program)
• 1: Parameter setting (start up according to the
parameters)
TCP existence confirmation setting (b4)
• 0: Use the Ping
• 1: Use the KeepAlive
Send frame setting (b5)
• 0: Ethernet
• 1: IEEE 802.3
Setting of write enable/disable at RUN time (b6)
• 0: Disable
• 1: Enable
Initial timing setting (b8)
• 0: Do not wait for OPEN (Communications impossible at
STOP time)
• 1: Always wait for OPEN (Communication possible at
STOP time)
0H

Bits other than those described above are reserved for
system use.
204
(CCH)
System area
205
(CDH)
RECV instruction execution request
206
(CEH)
208
(D0H)
209
(D1H)
210 to 223
(D2H to DFH)
228
(E4H)
40
System area
System area
Error log area


0H



0H
ZNWR instruction
System area
224 to 226
(E0H to E2H)
0H
ZNRD instruction
Data link
instruction
execution result


System area
Area for
sending/rec
eiving
instructions
207
(CFH)
227
(E3H)






Number of errors
0H

Error log write pointer
0H

CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
229
(E5H)
Error code/end code
0H

230
(E6H)
Subheader
0H

231
(E7H)
Command code
0H

Connection No.
0H

Own station port No.
0H

Destination IP address
0H

236
(ECH)
Destination Port No.
0H

237
(EDH)
System area
232
(E8H)
Error log block
1
233
(E9H)
234 and 235
(EAH and EBH)

238 to 246
(EEH to F6H)
Error log block 2 (The bit configuration is the same as Error log block 1.)
247 to 255
(F7H to FFH)
Error log block 3 (The bit configuration is the same as Error log block 1.)
256 to 264
(100H to 108H)
Error log block 4 (The bit configuration is the same as Error log block 1.)
265 to 273
(109H to 111H)
Error log area
Error log
block area
283 to 291
(11BH to 123H)
Error log block 7 (The bit configuration is the same as Error log block 1.)
292 to 300
(124H to 12CH)
Error log block 8 (The bit configuration is the same as Error log block 1.)
301 to 309
(12DH to 135H)
Error log block 9 (The bit configuration is the same as Error log block 1.)
310 to 318
(136H to 13EH)
Error log block 10 (The bit configuration is the same as Error log block 1.)
319 to 327
(13FH to 147H)
Error log block 11 (The bit configuration is the same as Error log block 1.)
328 to 336
(148H to 150H)
Error log block 12 (The bit configuration is the same as Error log block 1.)
337 to 345
(151H to 159H)
Error log block 13 (The bit configuration is the same as Error log block 1.)
346 to 354
(15AH to 162H)
Error log block 14 (The bit configuration is the same as Error log block 1.)
355 to 363
(163H to 16BH)
Error log block 15 (The bit configuration is the same as Error log block 1.)
364 to 372
(16CH to 174H)
Error log block 16 (The bit configuration is the same as Error log block 1.)

3.5 Buffer Memory
3.5.2 List of buffer memory addresses
Error log block 6 (The bit configuration is the same as Error log block 1.)
System area

Error log block 5 (The bit configuration is the same as Error log block 1.)
274 to 282
(112 H to 11AH)
373 to 375
(175H to 177H)
3

41
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
376 and 377
(178H and 179H)
Received IP packet count
0H

378 and 379
(17AH and 17BH)
Received IP packet count discarded
due to sumcheck error
0H

Sent IP packet total count
0H

IP
380 and 381
(17CH and 17DH)
382 to 407
(17EH to 197H)
System area


408 and 409
(198H and 199H)
Received ICMP packet count
0H

410 and 411
(19AH and 19BH)
Received ICMP packet count discarded
due to sum check error
0H

412 and 413
(19CH and 19DH)
Sent ICMP packet total count
0H

414 and 415
(19EH and 19FH)
Echo request total count of received
ICMP packets
0H

Echo reply total count of sent ICMP
packets
0H

Echo request total count of sent ICMP
packets
0H

Echo reply total count of received ICMP
packets
0H

ICMP
416 and 417
(1A0H and 1A1H)
418 and 419
(1A2H and 1A3H)
420 and 421
(1A4H and 1A5H)
Error log area
Status for
each
protocol
422 to 439
(1A6H to 1B7H)
System area


440 and 441
(1B8H and 1B9H)
Received TCP packet count
0H

442 and 443
(1BAH and 1BBH)
Received TCP packet count discarded
due to sum check error
0H

Sent TCP packet total count
0H

444 and 445
(1BCH and 1BDH)
TCP
446 to 471
(1BEH to 1D7H)
System area


472 and 473
(1D8H and 1D9H)
Received UDP packet count
0H

474 and 475
(1DAH and 1DBH)
Received UDP packet count discarded
due to sum check error
0H

Sent UDP packet total count
0H

476 and 477
(1DCH and 1DDH)
UDP
478 to 481
(1DEH to 1E1H)
482 to 511
(1E2H to 1FFH)
42
System area
System area




CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
512 and 513
(200H and 201H)
Sub-net mask
0H

514 and 515
(202H and 203H)
Default router IP address
0H

Number of registered routers
0H

Sub-net address
0H

Router IP address
0H

516
(204H)
517 and 518
(205H and 206H)
Router 1
519 and 520
(207H and 208H)
521 to 524
(209H to 20CH)
525 to 528
(20DH to 210H)
Router 2 (The bit configuration is the same as Router 1.)
Router relay
parameter setting
area
Router 3 (The bit configuration is the same as Router 1.)
529 to 532
(211H to 214H)
Router 4 (The bit configuration is the same as Router 1.)
533 to 536
(215H to 218H)
Router 5 (The bit configuration is the same as Router 1.)
537 to 540
(219H to 21CH)
Router 6 (The bit configuration is the same as Router 1.)
541 to 544
(21DH to 220H)
Router 7 (The bit configuration is the same as Router 1.)
545 to 548
(221H to 224H)
Router 8 (The bit configuration is the same as Router 1.)
System area


550 to 551
(226H and 227H)
System area


552
(228H)
553 and 554
(229H to 22AH)
Conversion
information
No.1
555 and 556
(22BH to 22CH)
559 to 564
(22FH to 234H)
Station No.<-> IP
information setting
area
937 and 938
(3A9H and 3AAH)
939 to 943
(3ABH to 3AFH)

Communication request destination/source stations
network number and station number
0H

External station Ethernet module IP address
0H


System area

Conversion information No.2 (The bit configuration is the same as Conversion information No.1.)
to
931 to 936
(3A3H to 3A8H)
0H
Number of conversion table data
3.5 Buffer Memory
3.5.2 List of buffer memory addresses
549
(225H)
557 and 558
(22DH to 22EH)
3
to
Conversion information No.64 (The bit configuration is the same as Conversion information No.1.)
Subnet mask pattern for CC-Link IE Controller Network, CC-Link IE Field
Network, MELSECNET/H, and MELSECNET/10 routing
System area
0H



43
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
944 to 949
(3B0H to 3B5H)
FTP login name
"LJ71E71"

950 to 953
(3B6H to 3B9H)
Password
"LJ71E71"

708H

AH

954
(3BAH)
FTP setting area
955
(3BBH)
Command input monitoring timer
Programmable controller CPU monitoring timer
956 to 1663
(3BCH to 67FH)

System area
1664
(680H)
Fixed buffer
No.1
1665 to 2687
(681H to A7FH)
Data length
0H

Fixed buffer data
0H

0H

2688 to 3711
(A80H to E7FH)
Fixed buffer No.2 (The bit configuration is the same as Fixed buffer No.1.)
3712 to 4735
(E80H to 127FH)
Fixed buffer No.3 (The bit configuration is the same as Fixed buffer No.1.)
4736 to 5759
(1280H to 167FH)
Fixed buffer data
area
Fixed buffer No.4 (The bit configuration is the same as Fixed buffer No.1.)
5760 to 6783
(1680H to 1A7FH)
Fixed buffer No.5 (The bit configuration is the same as Fixed buffer No.1.)
6784 to 7807
(1A80H to 1E7FH)
Fixed buffer No.6 (The bit configuration is the same as Fixed buffer No.1.)
7808 to 8831
(1E80H to 227FH)
Fixed buffer No.7 (The bit configuration is the same as Fixed buffer No.1.)
8832 to 9855
(2280H to 267FH)
Fixed buffer No.8 (The bit configuration is the same as Fixed buffer No.1.)
9856 to 16383
(2680H to 3FFFH)
16384 to 18431
(4000H to 47FFH)
18432 to 20479
(4800H to 4FFFH)
44
Shared area for
random access
buffers and e-mail
buffers
Send/receive area
for predefined
protocol support
function

Shared area for random access buffers and e-mail buffers
System area
Send/receive area for predefined protocol support function


0H

CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
Open completion signal
• 0: Open incomplete
• 1: Open completed
Connection No.1 (b0)
Connection No.2 (b1)
to
Connection No.16 (b15)
20480
(5000H)
20481
(5001H)
Connection
status
information
area
20482
(5002H)
20483 and 20484
(5003H and 5004H)
tool setting
applicability
Connection status
storage area
System area
0H
3

Open request signal
• 0: No open request
• 1: Open being requested
Connection No.1 (b0)
Connection No.2 (b1)
to
Connection No.16 (b15)
System area


0H



Fixed buffer
information
area
20486
(5006H)
Remote
password
status
storage
area
Remote password status
• 0: Unlock status/no remote password setting
• 1: Lock status
Connection No.1 (b0)
Connection No.2 (b1)
to
Connection No.16 (b15)
0H

20487
(5007H)
Remote
password
status
storage
area
Remote password status
• 0: Unlock status/no remote password setting
• 1: Lock status
• Auto-open UDP port (b0)
• MELSOFT application transmission port (UDP) (b1)
• MELSOFT application transmission port (TCP) (b2)
• FTP transmission port (b3)
0H

System port use prohibited designation
• 0: Use allowed
• 1: Use prohibited
• Auto-open UDP port (b0)
• MELSOFT application transmission port (UDP) (b1)
• MELSOFT application transmission port (TCP) (b2)
0H

System port
information area
20488
(5008H)
20489 to 20591
(5009H to 506FH)
System port
use
prohibited
designation
area
System area

0H

3.5 Buffer Memory
3.5.2 List of buffer memory addresses
20485
(5005H)
Fixed buffer reception status signal
• 0: Data not received
• 1: Data being received
Connection No.1 (b0)
Connection No.2 (b1)
to
Connection No.16 (b15)

45
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
20592
(5070H)
Remote password mismatch notification accumulated
count designation (For user open port)
• 0: No designation
• 1 or higher: Notification accumulated count
1H

20593
(5071H)
Remote password mismatch notification accumulated
count designation (For auto-open UDP port, MELSOFT
application transmission port (TCP/ UDP) and FTP
transmission port)
• 0: No designation
• 1 or higher: Notification accumulated count
2H

20594
(5072H)
Accumulated count of unlock process
normal completion
0H

20595
(5073H)
Accumulated count of unlock process
abnormal end
0H

Accumulated count of lock process
normal completion
0H

Accumulated count of lock process
abnormal end
0H

Accumulated count of lock process
based on close
0H

20596
(5074H)
Connection
No.1
20597
(5075H)
20598
(5076H)
20599 to 20603
(5077H to 507BH)
Monitoring area
Remote
password
function
monitoring
area
Connection No.2 (The bit configuration is the same as Connection No.1.)
20604 to 20608
(507CH to 5080H)
Connection No.3 (The bit configuration is the same as Connection No.1.)
20609 to 20613
(5081H to 5085H)
Connection No.4 (The bit configuration is the same as Connection No.1.)
20614 to 20618
(5086H to 508AH)
Connection No.5 (The bit configuration is the same as Connection No.1.)
20619 to 20623
(508BH to 508FH)
Connection No.6 (The bit configuration is the same as Connection No.1.)
20624 to 20628
(5090H to 5094H)
Connection No.7 (The bit configuration is the same as Connection No.1.)
20629 to 20633
(5095H to 5099H)
Connection No.8 (The bit configuration is the same as Connection No.1.)
20634 to 20638
(509AH to 509EH)
Connection No.9 (The bit configuration is the same as Connection No.1.)
20639 to 20643
(509FH to 50A3H)
Connection No.10 (The bit configuration is the same as Connection No.1.)
46
tool setting
applicability
CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
20644 to 20648
(50A4H to 50A8H)
Connection No.11 (The bit configuration is the same as Connection No.1.)
20649 to 20653
(50A9H to 50ADH)
Connection No.12 (The bit configuration is the same as Connection No.1.)
20654 to 20658
(50AEH to 50B2H)
Connection No.13 (The bit configuration is the same as Connection No.1.)
20659 to 20663
(50B3H to 50B7H)
Connection No.14 (The bit configuration is the same as Connection No.1.)
20664 to 20668
(50B8H to 50BCH)
20669 to 20673
(50BDH to 50C1H)
tool setting
applicability
Monitoring area
Remote
password
function
monitoring
area
3
Connection No.15 (The bit configuration is the same as Connection No.1.)
Connection No.16 (The bit configuration is the same as Connection No.1.)
20674 to 20678
(50C2H to 50C6H)
Auto-open UDP port (The bit configuration is the same as Connection No.1.)
20679 to 20683
(50C7H to 50CBH)
MELSOFT application transmission port (UDP) (The bit configuration is the same as Connection
No.1.)
20684 to 20688
(50CCH to 50D0H)
MELSOFT application transmission port (TCP) (The bit configuration is the same as Connection
No.1.)
20689 to 20693
(50D1H to 50D5H)
FTP transmission port (The bit configuration is the same as Connection No.1.)
20694 to 20736
(50D6H to 5100H)

System area

Error log pointer
0H

20738
(5102H)
Log counter (HTTP response code 100 to 199)
0H

20739
(5103H)
Log counter (HTTP response code 200 to 299)
0H

20740
(5104H)
Log counter (HTTP response code 300 to 399)
0H

20741
(5105H)
Log counter (HTTP response code 400 to 499)
0H

Log counter (HTTP response code 500 to 599)
0H

20742
(5106H)
20743
(5107H)
HTTP status
storage area
20744
(5108H)
20745 and 20746
(5109H and 510AH)
20747 to 20750
(510BH to 510EH)

System area
Error log
block 1

HTTP response code
0H

Destination IP address
0H

Error time
0H

20751 to 20757
(510FH to 5115H)
Error log block 2 (The bit configuration is the same as Error log block 1.)
20758 to 20764
(5116H to 511CH)
Error log block 3 (The bit configuration is the same as Error log block 1.)
3.5 Buffer Memory
3.5.2 List of buffer memory addresses
20737
(5101H)
47
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
20765 to 20771
(511DH to 5123H)
Error log block 4 (The bit configuration is the same as Error log block 1.)
20772 to 20778
(5124H to 512AH)
Error log block 5 (The bit configuration is the same as Error log block 1.)
20779 to 20785
(512BH to 5131H)
Error log block 6 (The bit configuration is the same as Error log block 1.)
20786 to 20792
(5132H to 5138H)
Error log block 7 (The bit configuration is the same as Error log block 1.)
20793 to 20799
(5139H to 513FH)
Error log block 8 (The bit configuration is the same as Error log block 1.)
20800 to 20806
(5140H to 5146H)
Error log block 9 (The bit configuration is the same as Error log block 1.)
20807 to 20813
(5147H to 514DH)
HTTP status
storage area
Error log block 10 (The bit configuration is the same as Error log block 1.)
20814 to 20820
(514EH to 5154H)
Error log block 11 (The bit configuration is the same as Error log block 1.)
20821 to 20827
(5155H to 515BH)
Error log block 12 (The bit configuration is the same as Error log block 1.)
20828 to 20834
(515CH to 5162H)
Error log block 13 (The bit configuration is the same as Error log block 1.)
20835 to 20841
(5163H to 5169H)
Error log block 14 (The bit configuration is the same as Error log block 1.)
20842 to 20848
(516AH to 5170H)
Error log block 15 (The bit configuration is the same as Error log block 1.)
20849 to 20855
(5171H to 5177H)
Error log block 16 (The bit configuration is the same as Error log block 1.)
20856 to 20994
(5178H to 5202H)
20995
(5203H)
20996 to 21055
(5204H to 523FH)
21056
(5240H)*1
21057 to 21119
(5241H to 527FH)
Disconnection
detection storage
area
Receive buffer
status storage area
48

Receive buffer full detection signal
0: Receive buffer not full
1: Receive buffer full
0H
Same IP address detection flag
• 0: Unique IP addresses
• 1: Same IP address for multiple stations
System area



System area
IP address status
storage area

0H
Disconnection detection count
System area
21124 to 21126
(5284H to 5286H)
21127 to 21279
(5287H to 531FH)

System area
21120
(5280H)
21121 to 21123
(5281H to 5283H)
tool setting
applicability


0H

The MAC address of the station that has been already connected to the
network (The address is stored in the station with the same IP address.)
FFFFFFFFFFFFH

The MAC address of the station with the IP address used for another
station (The address is stored in the station that has been already
connected to the network.)
FFFFFFFFFFFFH



CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
21280 to 21283
(5320H to 5323H)

System area
21284
(5324H)
21285
(5325H)
21286
(5326H)
21287
(5327H)
Protocol setting data error
information
Protocol setting
data check area
21288
(5328H)
System area
21296 to 21311
(5330H to 533FH)
Protocol registration
0H

Setting type
0H

Packet No.
0H

Element No.
0H

0H


21696
(54C0H)
Protocol execution status
21697
(54C1H)
System area
Connection
No.1
0H


0H



0H

21714
(54D2H)
Number of protocol executions
0H

21715
(54D3H)
Protocol cancellation specification
0H

21736 to 21755
(54E8H to 54FBH)
Predefined protocol
support function
execution status
check area
3.5 Buffer Memory
3.5.2 List of buffer memory addresses
Received data verification result (receive packet No.1 to
16)
21716 to 21735
(54D4H to 54E7H)
3


System area
21698 to 21713
(54C2H to 54D1H)

Protocol No.
Number of registered protocols
21289 to 21295
(5329H to 532FH)
21312 to 21695
(5340H to 54BFH)
tool setting
applicability
Connection No.2 (The bit configuration is the same as Connection No.1.)
Connection No.3 (The bit configuration is the same as Connection No.1.)
21756 to 21775
(54FCH to 550FH)
Connection No.4 (The bit configuration is the same as Connection No.1.)
21776 to 21795
(5510H to 5523H)
Connection No.5 (The bit configuration is the same as Connection No.1.)
21796 to 21815
(5524H to 5537H)
Connection No.6 (The bit configuration is the same as Connection No.1.)
21816 to 21835
(5538H to 554BH)
Connection No.7 (The bit configuration is the same as Connection No.1.)
21836 to 21855
(554CH to 555FH)
Connection No.8 (The bit configuration is the same as Connection No.1.)
49
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
21856 to 21875
(5560H to 5573H)
Connection No.9 (The bit configuration is the same as Connection No.1.)
21876 to 21895
(5574H to 5587H)
Connection No.10 (The bit configuration is the same as Connection No.1.)
21896 to 21915
(5588H to 559BH)
Connection No.11 (The bit configuration is the same as Connection No.1.)
21916 to 21935
(559CH to 55AFH)
21936 to 21955
(55B0H to 55C3H)
Predefined protocol
support function
execution status
check area
Connection No.12 (The bit configuration is the same as Connection No.1.)
Connection No.13 (The bit configuration is the same as Connection No.1.)
21956 to 21975
(55C4H to 55D7H)
Connection No.14 (The bit configuration is the same as Connection No.1.)
21976 to 21995
(55D8H to 55EBH)
Connection No.15 (The bit configuration is the same as Connection No.1.)
21996 to 22015
(55ECH to 55FFH)
Connection No.16 (The bit configuration is the same as Connection No.1.)
22016 to 22271
(5600H to 56FFH)
tool setting
applicability

System area

22272 (5700H)
Use of IP filter settings
• 0: Do not use
• 1: Use
0H

22273 (5701H)
IP filter function type setting
• 0: Allow
• 1: Deny
0H

Start IP address
0H

End IP address
0H

IP address setting 2 (The bit configuration is the same as
IP address setting 1.)
0H

IP address setting 3 (The bit configuration is the same as
IP address setting 1.)
0H

IP address setting 4 (The bit configuration is the same as
IP address setting 1.)
0H

22290 to 22293
(5712H to 5715H)
IP address setting 5 (The bit configuration is the same as
IP address setting 1.)
0H

22294 to 22297
(5716H to 5719H)
IP address setting 6 (The bit configuration is the same as
IP address setting 1.)
0H

22298 to 22301
(571AH to 571DH)
IP address setting 7 (The bit configuration is the same as
IP address setting 1.)
0H

22302 to 22305
(571EH to 5721H)
IP address setting 8 (The bit configuration is the same as
IP address setting 1.)
0H

Number of access denied by the IP filter function
0H

IP address denied by the IP filter function
0H

22274 to 22275
(5702H to 5703H)
IP address
setting 1
22276 to 22277
(5704H to 5705H)
22278 to 22281
(5706H to 5709H)
22282 to 22285
(570AH to 570DH)
22286 to 22289
(570EH to 5711H)
IP filter
settings
IP filter function
area
22306 to 22307
(5722H to 5723H)
IP filter
monitoring
area
22308 to 22309
(5724H to 5725H)
22310 to 22559
(5726H to 581FH)
50
System area


CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
22560
(5820H)
Own station port No.
0H

Destination IP address
0H

22563
(5823H)
Destination Port No.
0H

22564
(5824H)
Open error code
0H

Fixed buffer sending error code
0H

22566
(5826H)
Connection end code
0H

22567
(5827H)
Fixed buffer communication time
(Maximum value)
0H

Fixed buffer communication time
(Minimum value)
0H

Fixed buffer communication time
(Current value)
0H

22561 and 22562
(5821H to 5822H)
22565
(5825H)
22568
(5828H)
22569
(5829H)
Connection
No.9
Communication
status storage area
Connection
information
area
Connection No.10 (The bit configuration is the same as Connection No.9.)
22580 to 22589
(5834H to 583DH)
Connection No.11 (The bit configuration is the same as Connection No.9.)
22590 to 22599
(583EH to 5847H)
Connection No.12 (The bit configuration is the same as Connection No.9.)
22600 to 22609
(5848H to 5851H)
Connection No.13 (The bit configuration is the same as Connection No.9.)
22610 to 22619
(5852H to 585BH)
Connection No.14 (The bit configuration is the same as Connection No.9.)
22620 to 22629
(585CH to 5865H)
Connection No.15 (The bit configuration is the same as Connection No.9.)
22630 to 22639
(5866H to 586FH)
Connection No.16 (The bit configuration is the same as Connection No.9.)
3.5 Buffer Memory
3.5.2 List of buffer memory addresses
22570 to 22579
(582AH to 5833H)
3
51
Address
Decimal
Programming
Application
Name
Initial value
tool setting
applicability
(Hexadecimal)
22640
(5870H)
Number of mails remaining on the server
0H

22641
(5871H)
Dedicated instruction normal completion count
0H

22642
(5872H)
Dedicated instruction abnormal end count
0H

22643
(5873H)
Normal receiving count
0H

22644
(5874H)
Attached file receiving count
0H

22645
(5875H)
Server inquiry count
0H

Server communication error count
0H

Error log write count
0H

Receiving error log write pointer
0H

22646
(5876H)
22647
(5877H)
22648
(5878H)
E-mail status
storage area
Receive
22649
(5879H)
Error code
0H

22650
(587AH)
Command code
0H

From
0H

22659 to 22662
(5883H to 5886H)
Date
0H

22663 to 22692
(5887H to 58A4H)
Subject
0H

22651 to 22658
(587BH to 5882H)
52
Error log block
1
CHAPTER 3 SPECIFICATIONS
Address
Decimal
Programming
Application
Name
Initial value
(Hexadecimal)
22693 to 22736
(58A5H to 58D0H)
Error log block 2 (The bit configuration is the same as Error log block 1.)
22737 to 22780
(58D1H to 58FCH)
Error log block 3 (The bit configuration is the same as Error log block 1.)
22781 to 22824
(58FDH to 5928H)
Error log block 4 (The bit configuration is the same as Error log block 1.)
22825 to 22868
(5929H to 5954H)
Error log block 5 (The bit configuration is the same as Error log block 1.)
22869 to 22912
(5955H to 5980H)
Error log block 6 (The bit configuration is the same as Error log block 1.)
22913 to 22956
(5981H to 59ACH)
Error log block 7 (The bit configuration is the same as Error log block 1.)
22957 to 23000
(59ADH to 59D8H)
Error log block 8 (The bit configuration is the same as Error log block 1.)
23001 to 23044
(59D9H to 5A04H)
Receive
Error log block 10 (The bit configuration is the same as Error log block 1.)
23089 to 23132
(5A31H to 5A5CH)
Error log block 11 (The bit configuration is the same as Error log block 1.)
23133 to 23176
(5A5DH to 5A88H)
Error log block 12 (The bit configuration is the same as Error log block 1.)
E-mail status
storage area
3
Error log block 9 (The bit configuration is the same as Error log block 1.)
23045 to 23088
(5A05H to 5A30H)
23177 to 23220
(5A89H to 5AB4H)
tool setting
applicability
Error log block 13 (The bit configuration is the same as Error log block 1.)
Error log block 14 (The bit configuration is the same as Error log block 1.)
23265 to 23308
(5AE1H to 5B0CH)
Error log block 15 (The bit configuration is the same as Error log block 1.)
23309 to 23352
(5B0DH to 5B38H)
Error log block 16 (The bit configuration is the same as Error log block 1.)
23353
(5B39H)
Dedicated instruction normal completion count
0H

23354
(5B3AH)
Dedicated instruction abnormal end count
0H

23355
(5B3BH)
Number of mails normally completed
0H

Attached file sending count
0H

Sending to the server count
0H

23358
(5B3EH)
Number of mails abnormally completed
0H

23359
(5B3FH)
Error log write count
0H

23360
(5B40H)
Sending error log write pointer
0H

23356
(5B3CH)
23357
(5B3DH)
3.5 Buffer Memory
3.5.2 List of buffer memory addresses
23221 to 23264
(5AB5H to 5AE0H)
Send
53
Address
Programming
Application
Decimal
Name
Initial value
tool setting
applicability
(Hexadecimal)
23361
(5B41H)
Error code
0H

23362
(5B42H)
Command code
0H

To
0H

23371 to 23374
(5B4BH to 5B4EH)
Date
0H

23375 to 23404
(5B4FH to 5B6CH)
Subject
0H

23363 to 23370
(5B43H to 5B4AH)
Error log block
1
23405 to 23448
(5B6DH to 5B98H)
23449 to 23492
(5B99H to 5BC4H)
Error log block 2 (The bit configuration is the same as Error log block 1.)
E-mail status
storage area
Send
Error log block 3 (The bit configuration is the same as Error log block 1.)
23493 to 23536
(5BC5H to 5BF0H)
Error log block 4 (The bit configuration is the same as Error log block 1.)
23537 to 23580
(5BF1H to 5C1CH)
Error log block 5 (The bit configuration is the same as Error log block 1.)
23581 to 23624
(5C1DH to 5C48H)
Error log block 6 (The bit configuration is the same as Error log block 1.)
23625 to 23668
(5C49H to 5C74H)
Error log block 7 (The bit configuration is the same as Error log block 1.)
23669 to 23712
(5C75H to 5CA0H)
Error log block 8 (The bit configuration is the same as Error log block 1.)
23713 to 24575
(5CA1 H to 5FFFH)

System area
24576
(6000H)
Fixed buffer
No.9
24577 to 25599
(6001H to 63FFH)
Data length
0H

Fixed buffer data
0H

25600 to 26623
(6400H to 67FFH)
Fixed buffer No.10 (The bit configuration is the same as Fixed buffer No.9.)
26624 to 27647
(6800H to 6BFFH)
Fixed buffer No.11 (The bit configuration is the same as Fixed buffer No.9.)
27648 to 28671
(6C00H to 6FFFH)
Fixed buffer data
area
Fixed buffer No.12 (The bit configuration is the same as Fixed buffer No.9.)
28672 to 29695
(7000H to 73FFH)
Fixed buffer No.13 (The bit configuration is the same as Fixed buffer No.9.)
29696 to 30719
(7400H to 77FFH)
Fixed buffer No.14 (The bit configuration is the same as Fixed buffer No.9.)
30720 to 31743
(7800H to 7BFFH)
Fixed buffer No.15 (The bit configuration is the same as Fixed buffer No.9.)
31744 to 32767
(7C00H to 7FFFH)
Fixed buffer No.16 (The bit configuration is the same as Fixed buffer No.9.)
*1
54

Availability depends on the version of the E71. (
Page 310, Appendix 3)
CHAPTER 4 PROCEDURES BEFORE OPERATION
CHAPTER 4
PROCEDURES BEFORE OPERATION
This chapter describes how to connect an E71 to Ethernet. For how to communicate with connected devices after the
E71 is connected, refer to the communication procedure. (
Page 64, CHAPTER 7)
Checkbox
System consideration
Page 27, CHAPTER 3,
Design the system configuration of the E71.
Page 57, CHAPTER 5
4
Installation
Page 25, CHAPTER 2,
Page 61, Section 6.1
Connect the E71.
Wiring
Page 58, Section 5.2,
Page 62, Section 6.2
Connect an Ethernet cable to the E71.
Setting parameters
Set the following parameters, which are required to start up
the E71, from the programming tool.
Basic setting
Ethernet operation setting
Restarting the CPU module
Page 66, Section 7.1.2,
Page 67, Section 7.1.3
MELSEC-L CPU Module User's
Manual (Hardware Design,
Reflect the parameter settings by turning off and on the CPU
module or resetting the CPU module.
Maintenance and Inspection)
Network diagnostics
Check that the cables are connected properly or that
communications are performed properly with the set
parameters. (PING test, loopback test)
Continued to COMMUNICATION PROCEDURE (
Page 322, Appendix 5
Page 64, CHAPTER 7)
55
Memo
56
CHAPTER 5 SYSTEM CONFIGURATION
CHAPTER 5
5.1
SYSTEM CONFIGURATION
Overall System Configuration
The following is a system configuration example of when using an E71.
Display unit
(optional)
5
Power supply module
CPU module
E71
I/O modules
or
intelligent function modules
END cover
5.1 Overall System Configuration
57
5.2
Network Components
This section describes the devices used for Ethernet.
Connected device
E71
Hub
An E71 determines whether to use 100BASE-TX or 10BASE-T and the full-duplex or half-duplex transmission mode
according to the hub. For connection to a hub without the automatic negotiation function, set the half-duplex mode on the
hub side.
(1) 100BASE-TX connection
To configure a system for 100BASE-TX connection, use devices that meet the IEEE 802.3 100 BASE-TX
standards.
Configuration device
Description
Shielded twisted pair
Straight cable
A Category 5 or 5e cross cable is usable.
cable (STP)*2
Cross cable
A Category 5 or 5e cross cable is usable.
Connector
RJ45 connector
Hub
100Mbps hub
*1
*2

Up to two levels of cascade connection can be configured.*1
This applies when a repeater hub is used. For the number of levels that can be constructed when a switching hub is
used, consult with the manufacturer of the switching hub used.
Data can be communicated with an E71 (between LJ71E71-100 modules). In addition, an E71 can be directly connected
to a GOT.
During high-speed communications (100Mbps) using 100BASE-TX connection, a communication error may occur due to
high-frequency noise from devices other than a programmable controller in a given installation environment. The following
lists countermeasures to be taken on the E71 side to avoid high-frequency noise influence.
● Wiring connection
• Do not bundle the cable with the main circuit or power cable or do not place it near those lines.
• Put the cable in a duct.
● Communication method
• Use TCP/IP for data communications with connected devices.
• Increase the number of retries of communications if needed.
● 10Mbps communications
• Use a 10Mbps hub for the E71 and set the data transmission speed to 10Mbps.
• Change the transmission speed of the E71 to 10Mbps using the UINI instruction. (
15.13)
Remark
Consult a network specialist for required devices.
58
Page 233, Section
CHAPTER 5 SYSTEM CONFIGURATION
(2) 10BASE-T connection
To configure a system for 10BASE-T connection, use devices that meet the IEEE 802.3 10BASE-T standards.
Configuration device
Unshielded twisted pair
Straight cable
cable (UTP) or shielded
twisted pair cable (STP)*2
A Category 3, 4, or 5 straight cable or cross cable is usable.
Cross cable
Connector
RJ45 connector
Hub
10Mbps hub
*1
*2
Description

Up to four levels of cascade connection can be configured.*1
This applies when a repeater hub is used. For the number of levels that can be constructed when a switching hub is
used, consult with the manufacturer of the switching hub used.
Data can be communicated with an E71 (between LJ71E71-100 modules). In addition, an E71 can be directly connected
to a GOT.
5
Remark
Consult a network specialist for required devices.
5.2 Network Components
59
5.3
Applicable Systems
This section describes MELSEC-L series systems that include an E71.
(1) Applicable CPU modules and the number of connectable modules
An E71 can be connected to an LCPU with an serial number (first five digits) of 14112 or later.
For the number of connectable modules, refer to the following.
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)
(2) Applicable software
GX Works2 is required for setting and diagnosing an E71. GX Developer cannot be used.
60
Software
Version
GX Works2
1.95Z or later
CHAPTER 6 INSTALLATION AND WIRING
CHAPTER 6
INSTALLATION AND WIRING
This chapter describes installation and wiring of the E71.
6.1
Installation
This section describes installation of the E71.
(1) Installation method
For the module installation environment and position, refer to the following.
MELSEC-L CPU Module
User's Manual (Hardware Design, Maintenance and Inspection)
6
(2) Handling precautions
Do not drop or apply strong shock to the E71 case since it is made from resin.
6.1 Installation
61
6.2
Wiring
This section describes Ethernet cable wiring and wiring precautions. For a network configuration and cables and hubs
used, refer to "SYSTEM CONFIGURATION". (
Page 57, CHAPTER 5)
(1) Ethernet cable connection
The following is how to connect and disconnect an Ethernet cable.
(a) Connecting the cable
1.
2.
Power off the E71 and the connected device.
Push the Ethernet cable connector into the E71 until
it clicks. Pay attention to the connector's direction.
3.
Power on the E71 and the connected device.
1.
2.
Power off the system.
(b) Disconnecting the cable
62
Press the latch down and unplug the Ethernet cable.
CHAPTER 6 INSTALLATION AND WIRING
(2) Precautions
This section describes wiring precautions.
(a) Handling
Place the Ethernet cable 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.
Do not touch the core of the cable-side or module-side connector, and protect it from dirt or dust. If oil from your
hand, dirt or dust is attached to the core, it can increase transmission loss, arising a problem in data link.
Check the following:
• Is any Ethernet cable disconnected?
• Is any Ethernet cable shorted?
• Are the connectors securely connected?
(b) Broken cable latch
Do not use Ethernet cables with broken latches. Doing so may cause the cable to unplug or malfunction.
6
(c) Connecting and disconnecting the Ethernet cable
Hold the connector part when connecting and disconnecting the Ethernet cable. Pulling a cable connected to
the module may damage the module or cable or result in malfunction due to poor contact.
(d) Maximum station-to-station distance (maximum cable length)
The maximum station-to-station distance is 100m. However, the distance may be shorter depending on the
operating environment of the cable. For details, contact your cable manufacturer.
(e) Bend radius
The bend radius of the Ethernet cable is limited. For details, see the specifications of the Ethernet cable to be
6.2 Wiring
used.
63
CHAPTER 7
COMMUNICATION PROCEDURE
This chapter describes the procedure for communicating with connected devices after the E71 is connected to
Ethernet. For the procedure for connecting the E71 to Ethernet, refer to "PROCEDURES BEFORE OPERATION".
Continued from PROCEDURES BEFORE OPERATION
(
Page 55, CHAPTER 4)
Parameter settings
Page 65, Section 7.1,
Set the parameters (excluding the basic setting and Ethernet operation
setting) if necessary.
Starting the CPU module
Parameter setting of each function
MELSEC-L CPU Module User's
Manual (Hardware Design,
Reflect the parameter settings by turning off and on the CPU module or
resetting the CPU module.
Maintenance and Inspection)
Initial process
The initial process of the E71 is automatically performed.
Open process
Page 72, Section 7.2,
The open process is to establish a connection with a connected device.
Page 79, Section 7.3
Data communications using
each function
Close process
The close process is to disconnect (cancel) the connection with the
connected device established by the open process.
64
Page 72, Section 7.2,
Page 79, Section 7.3
CHAPTER 7 COMMUNICATION PROCEDURE
7.1
Setting Parameters Required for Communications
This section describes how to set parameters to communicate between the E71 and connected devices.
7.1.1
Parameter list
The following table lists parameters set through a programming tool.
Item
Description
Reference
Network Type
Start I/O No.
Basic setting
Network No.
Group No.
Configure settings to use the E71 as a network module.
Page 66, Section 7.1.2
Station No.
Mode
Operation Setting
Configure the settings, such as an IP address, to
connect the E71 to Ethernet.
Initial Setting
Set a data communication timer value.
Open Setting
Configure connection settings.
Page 67, Section 7.1.3
7
Page 311, Appendix 4.1
Page 69, Section 7.1.4,
Parameter setting of each
function
Network
Router Relay Parameter
Parameter
FTP Parameters
E-mail Setting
Interrupt Settings
Routing Parameters
Valid Module During Other Station
Access
devices on Ethernet via a router and a gateway.
Configure settings (e.g. network number and station
number) to communicate with other network modules.
Configure the settings of the file transfer (FTP)
function.
MELSEC-Q/L Ethernet
Interface Module User's
Manual (Application)
Configure the settings of the e-mail function and the
automatic notification function.
Set the control number (SI) on the E71 side to request
an interrupt to the CPU module.
Set the communication path to communicate with a
station having a different network number.
Page 131, Section 12.5.1
MELSEC-Q/L Ethernet
Interface Module User's
Manual (Application)
Select a relay module when an access request with no
network number specified is issued from another
-
station.
The connected device side protocol can be easily
Predefined Protocol Support Function
selected, or created/edited from the Predefined
Page 95, CHAPTER 11
Protocol Library of GX Works2.
Remote Password
Select the connection protected by a remote password.
Page 181, Section 14.4
65
7.1 Setting Parameters Required for Communications
7.1.1 Parameter list
Station No. <-> IP Information
Configure settings to communicate with connected
7.1.2
Basic setting
Set items, such as a network number and station number.
Project window
[Parameter]
[Network Parameter]
[Ethernet/CC IE Field]
Select
"Ethernet" under "Network Type".
Item
Description
Network Type
Select "Ethernet".
Start I/O No.
Set the start I/O number of the E71 in units of 16 points.
Setting range

Within the number of I/O points of the
CPU module
Network No.
Set the network number of the E71.
1 to 239
Group No.
Set the group number of the E71.
0 to 32
Station No.
Set the station number of the E71.
1 to 64
• Online
Mode
Select the operation mode of the E71.
• Offline
• Self-Loopback Test
• H/W Test
66
CHAPTER 7 COMMUNICATION PROCEDURE
7.1.3
Ethernet Operation Setting
Configure the settings, such as an IP address, to connect the E71 to Ethernet.
Project window
[Parameter]
[Network Parameter]
"Ethernet" under "Network Type".
Item
[Ethernet/CC IE Field]
button
Description
Communication Data Code
Select
Select the communication data code for the connected device.
7
Setting range
• Binary Code
• ASCII Code
• Do not wait for OPEN
(Communications
impossible at STOP
Page 68, Section 7.1.3 (1)
Initial Timing
time)
(Communication
possible at STOP time)
Input Format
Select the IP address input format.
Set the IP address of the own station. Make sure that the E71 on the own
IP Address
station and the connected device to be communicated with have the same
Setting
IP Address
class and subnet address. Consult with the network administrator for the IP
address setting.
Page 68, Section 7.1.3 (2)
• DEC
• HEX
• DEC:
0.0.0.1 to
255.255.255.254
• HEX
00.00.00.01 to
FF.FF.FF.FE
Select the frame of the Ethernet header for the data link layer to be sent by the
Send Frame Setting
E71.
• Ethernet (V2.0)
An E71 receives data from the connected device both with the Ethernet frame
• IEEE802.3*1
and the IEEE802.3 frame.
Enable Online Change
TCP Existence Confirmation
Setting
*1
Select whether to enable connected devices to write data in MC protocol
• Selected: Enable
communications while the CPU module is in RUN.
• Not selected: Disable
Select an alive check method in TCP/IP communications.
• Use the KeepAlive
• Use the Ping
The IEEE802.3 frame format can be used only when the connected device is compatible with the frame. Generally,
using the Ethernet frame is recommended.
67
7.1 Setting Parameters Required for Communications
7.1.3 Ethernet Operation Setting
• Always wait for OPEN
(1) Initial Timing
This setting configures the open timing of the connection where "TCP" (Passive open) or "UDP" has been
selected under "Open System" in the open setting. (
Page 69, Section 7.1.4)
(a) Do not wait for OPEN (Communications impossible at STOP time)
Connections are opened or closed using a program. Communications cannot be performed while the switch on
the CPU module is set to STOP.
(b) Always wait for OPEN (Communication possible at STOP time)
Connections always wait for the open status according to the "Open System" parameter. (This eliminates the
need to open/close connections using a program.*1) Communications can be performed while the switch on the
CPU module is set to STOP.
*1
If the program of the CPU module on the own station closes a connection, the station does not enter the OPEN request
wait status after the connection is disconnected.
When remotely controlling the CPU module from a connected device, select "Always wait for OPEN (Communication
possible at STOP time)". If "Do not wait for OPEN (Communications impossible at STOP time)" is selected, the
communication line is closed during remote STOP. After the line is closed, the line cannot be reopened on the CPU module
side, and remote RUN cannot be performed from the connected device.
(2) IP address setting
Set the IP address of the own station so that it has the same class and subnet address as that of the connected
device to be communicated.
Ex. When a subnetwork is not used
• IP address of the own station: 129.5.1.1
• IP address of the connected device: 129.5.47.1
• Subnet mask of the connected device: None
In the above case, the IP address of the connected device is class B.
Since class B has a default subnet mask of 255.255.0.0, set the IP address of the own station so that the first and
second octets are the same as those of the connected device.
Ex. When a subnetwork is used
• IP address of the own station: 129.5.47.5
• IP address of the connected device: 129.5.47.1
• Subnet mask of the connected device: 255.255.255.0
In the above case, although the IP address of the connected device is class B, the first to third octets are the
subnet address because the subnet mask is set to the first to third octets.
Therefore, set the IP address of the own station so that the first to third octets are the same as those of the
connected device.
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
68
CHAPTER 7 COMMUNICATION PROCEDURE
7.1.4
Open Setting
Configure settings to open connections for data communications with connected devices.
Project window
[Parameter]
[Network Parameter]
[Ethernet/CC IE Field]
"Ethernet" under "Network Type".
Select
button
7
Item
IP Address/Port No. Input
Format
Setting range
• DEC
Select the input format for the IP address and port number.
• HEX
Select the communication protocol for the connected device.
• TCP
(
• UDP
Page 72, Section 7.2, Page 79, Section 7.3)
7.1 Setting Parameters Required for Communications
7.1.4 Open Setting
Protocol
Description
• Active
Open System
• Unpassive
Set this item when "TCP" is selected under "Protocol".
(
Page 73, Section 7.2.2, Page 75, Section 7.2.3, Page 77, Section 7.2.4)
• Fullpassive
• MELSOFT
Connection*1
For communications using a fixed buffer, select whether to use the buffer for
Fixed Buffer
sending or for receiving in a connection to the connected device. When not
performing communications using a fixed buffer, select "Send". (
Page 120,
CHAPTER 12)
• Send
• Receive
• Predefined protocol
Fixed Buffer
Select a communication method for communications using a fixed buffer. (
• Procedure Exist
Communication
Page 120, CHAPTER 12)
• No Procedure
Configure the pairing open setting for communications using a fixed buffer.
• Disable
(
• Enable
Pairing Open
Existence Confirmation
Page 139, Section 12.7)
Select whether to use the alive check function. (
Page 194, Section 14.7)
• No Confirm
• Confirm
• DEC:
1025 to 4999, 5003 to
Host Station Port No.
Set the E71 connection port numbers.
65534*2
• HEX:
401H to 1387H, 138BH
to FFFEH*2
69
Item
Description
Setting range
• DEC:
0.0.0.0 to
Destination IP Address
255.255.255.255
Set the IP address of the connected device.
• HEX:
00.00.00.00 to
FF.FF.FF.FF
• DEC:
Destination Port No.
Set port numbers for connections of connected devices.
1 to 65535*3
• HEX:
1H to FFFFH*3
*1
An E71 is always waiting for an open request from a connected device (communications can be performed during
*2
Do not enter 5000 (1388H) to 5002 (138AH). (
*3
The range of 1 (1H) to 1024 (400H) is available only in the E71 with the serial number (first five digits) of "15042" or later.
STOP), regardless of the initial timing setting in the Ethernet operation setting. (
70
Page 67, Section 7.1.3)
Page 309, Appendix 2)
CHAPTER 7 COMMUNICATION PROCEDURE
● Note the following points when setting port numbers.
: Can be set, : Cannot be set
Communication
Connection status
Description
protocol
TCP/IP
UDP/IP




Connected device
When connecting multiple connected devices, set multiple
E71
Connected device
Connected device
When connecting multiple connected devices, set a single
own station port number. (However, connections need to be
E71
Connected device
E71
own station port numbers.
Connected device
opened by the number of connections.) This setting cannot
be configured when the own station is Unpassive.
When connecting multiple ports on a connected device, set
multiple port numbers of the E71.
7








When connecting multiple ports on a connected device, set
E71
Connected device
a single port number of the E71. (However, connections
need to be opened by the number of connections.) This
setting cannot be configured when the own station is
E71
Connected device
When connecting the same port on a connected device, set
multiple port numbers of the E71. (However, connections
need to be opened by the number of connections.)
E71
Connected device
Multiple ports can be set for the same port on a connected
device and on the E71 only when paring open has been set.
● Consult with the network administrator for setting the port numbers of the E71 and the connected device and the IP
address of the connected device.
71
7.1 Setting Parameters Required for Communications
7.1.4 Open Setting
Unpassive.
7.2
TCP/IP Communications
This section describes TCP/IP communications.
7.2.1
Establishing a connection
TCP/IP communications require establishing connections between communication devices. When the server-side
device is in standby status after performing a Passive open process, a connection is established after the client-side
device issues an open request (Active open process) to the server and a response is received.
In TCP/IP communications, the system establishes a connection and checks whether each data has arrived at the
recipient normally, thereby ensuring data reliability. Compared to UDP/IP communications, however, TCP/IP places a
greater load on the line.
Ex. When the E71 is in Passive open status
Client
Server
Open request
Response
E71
Passive open
(passive)
72
Connection
Connected device
Active open
(active)
CHAPTER 7 COMMUNICATION PROCEDURE
7.2.2
Communication process
This section describes the process from establishing a connection to terminating communications.
Server
Client
E71
After the server performs
Passive open, it will wait
for an open request from
the client.
Connected device
Passive open
Open request
Active open
Response
Connection established
Connection established
Data sending
Response
Receive process
Data sending
When the client sends
Active open request and
the server accepts it,
the connection is
established between
the client and the server.
Data sending
The client requests data
sending and sends data.
7
The client receives the response
to the data.
Data sending
The client receives data and sends
back the response to the data.
Response
7.2 TCP/IP Communications
7.2.2 Communication process
Close request
Receive process
Close process
Response
Close request
Close request
Response
Closed
The packet to stop communications is
exchanged then the connection is
disconnected.
Closed
73
● The corresponding bit of Open completion signal (address: 5000H) automatically turns off and the communication line is
closed in the following situations:
• A timeout has occurred in the alive check function. (
Page 194, Section 14.7)
• An E71 has received a close request and the ABORT (RST) instruction from a connected device.
• An E71 has received Alive open request from a connected device again with open completed in TCP.
After an E71 sends an ACK to a connected device, the E71 closes the connection when receiving the RST
command from the connected device. If the E71 with a different IP address or port number receives Active open
request from the connected device again, the E71 only sends the RST command. (It does not close the
connection.)
• A timeout has occurred upon transmission in TCP.
● After the connected device sends a close request to the E71, wait for 500ms or more before performing an open process
again.
74
CHAPTER 7 COMMUNICATION PROCEDURE
7.2.3
Active open procedure
Active open is a connection method that performs an active open process on a connected device in Passive open wait
status. The procedure that the E71 performs an Active open process is as follows. For the OPEN/CLOSE instructions,
refer to "DEDICATED INSTRUCTIONS". (
Page 196, CHAPTER 15)
Ex. Open/close processes for the connection number 1
Parameter communication
Power-on
completed
Open status
1
Open allowed status
(closed)
Closed status
Initial normal completion
signal X19
2
OPEN instruction
7
1 scan
OPEN instruction
completion device
Abnormally ended
OPEN instruction
completion device + 1
Abnormally ended
Open abnormal detection
signal X18
5
7.2 TCP/IP Communications
7.2.3 Active open procedure
CLOSE instruction
1 scan
CLOSE instruction
completion device
Abnormally
ended
CLOSE instruction
completion device + 1
Open completion signal
(address: 5000H)
Open request signal
(address: 5002H)
ACK
SYN
3
ACK
FIN
7
6
SYN + ACK
FIN + ACK
4
1
After parameter communications, check that the initial process of the E71 is normally completed.
(Initial normal completion signal (X19): ON)
2
Start the open process using the OPEN instruction. (Open request signal (address: 5002H (b0)): ON)
3
The E71 performs the open process. (The E71 sends an open request (SYN) to the connected device.)
4
When the open process is normally completed, data communications are enabled.*1
5
Start a close process using the CLOSE instruction. (Open request signal: OFF)
6
The E71 performs the close process. (The E71 sends a close request (FIN) to the connected device.)
7
When the close process is normally completed, data communications terminate.*2
75
*1
*2
76
If the E71 sends an SYN and the connected device returns a RST, Open abnormal detection signal (X18) turns on
immediately and the open process terminates. (Open abnormal end)
If an ACK and a FIN are not returned within the time specified by the TCP end timer value, the E71 forcibly closes the
connection (sends a RST). (Close abnormal end)
CHAPTER 7 COMMUNICATION PROCEDURE
7.2.4
Passive open procedure
The E71 has the following two connection methods for Passive open.
Unpassive
Fullpassive
Performs a passive open process on connections for all devices connected to the network,
regardless of the IP address and port number of the destination device.
Performs a passive open process on connections for the connected device specified by the
IP address and port number.
Under the Passive open method, the open/close processes are performed using the procedures described below,
according to the Ethernet operation setting.
(1) When "Always wait for OPEN (Communication possible at STOP time)" is
selected for the Ethernet operation setting
As the E71 is set to always wait for open, a connection is established when an Active open is requested from the
connected device. This eliminates the need for open/close processing programs on the E71 side.
Parameter
communication
Power-on completed 1
7
Open status
*1
Open allowed status (closed)
(Active open acceptance enabled)
Closed status
4
Open completion signal
(address: 5000H)
Open request signal
(address: 5002H)
SYN + ACK
FIN + ACK
3
2
SYN
1
7.2 TCP/IP Communications
7.2.4 Passive open procedure
Initial normal completion
signal X19
ACK
FIN
ACK
After parameter communications, check that the initial process of the E71 is normally completed.
(Initial normal completion signal (X19): ON)
After the initial process is normally completed, the connection enters open enable status and the E71 waits for an open
request from the connected device.
The E71 starts the open process upon receiving the open request (SYN) from the connected device. When the open
2
process is normally completed, Open completion signal (address: 5000H (b0)) turns on and data communications are
enabled.
3
The E71 starts the close process upon receiving the close request (FIN) from the connected device. When the close
process is completed, Open completion signal (address: 5000H (b0)) turns off and data communications are disabled.
4
After the internal process of the E71 is completed, the connection returns to the OPEN request wait status.
*1
An open request (SYN) received after the normal completion of an initial process and before the E71 is in the OPEN
request wait status will cause an error, and the E71 sends a connection forced close (RST).
When the open/close processes are performed from the E71 side using a dedicated instruction, even if "Always wait for
OPEN" has been selected for the Ethernet operation setting, the connection will not return to the open acceptance enable
status after the close process is completed.
77
(2) When "Do not wait for OPEN (Communications impossible at STOP time)" is
selected for the Ethernet operation setting
Executing the OPEN/CLOSE instructions is required on the E71 to make the E71 enter open/close wait status
before receiving an open/close request from the connected device. When the open process is normally
completed, data sending and receiving are enabled. For the OPEN/CLOSE instructions, refer to "DEDICATED
INSTRUCTIONS". (
Page 196, CHAPTER 15)
Ex. Open/close processes for the connection number 1
Parameter
communication
Power-on completed
Open status
1
*1
Open allowed status (closed)
(Active open acceptance enabled)
Closed status
Initial normal completion
signal X19
2
OPEN instruction
1 scan
OPEN instruction
completion device
Abnormally
ended
OPEN instruction
completion device + 1
Abnormally ended
Open abnormal detection
signal X18
5
CLOSE instruction
1 scan
CLOSE instruction
completion device
Abnormally
ended
CLOSE instruction
completion device + 1
Open completion signal
(address: 5000H)
Open request signal
(address: 5002H)
SYN + ACK
3
SYN
1
FIN + ACK
4
ACK
FIN
ACK
After parameter communications, check that the initial process of the E71 is normally completed.
(Initial normal completion signal (X19): ON)
2
Start the open process using the OPEN instruction. (Open request signal (address: 5002H (b0)): ON)
The E71 starts the open process upon receiving the open request (SYN) from the connected device. When the open
3
process is normally completed, Open completion signal (address: 5000H (b0)) turns on and data communications are
enabled.
4
The E71 starts the close process upon receiving the close request (FIN) from the connected device. When the close
process is completed, Open completion signal (address: 5000H (b0)) turns off and data communications are disabled.
5
Start the close process using the CLOSE instruction. (Open request signal: OFF)
*1
78
An open request (SYN) received after the normal completion of an initial process and before the E71 is in the OPEN
request wait status will cause an error, and the E71 sends a connection forced close (RST).
CHAPTER 7 COMMUNICATION PROCEDURE
● Change connection settings before executing the OPEN instruction.
● Once an open process is performed, an open request cannot be canceled before the open process is completed.
Perform a close process (Execute the CLOSE instruction) after the open process is completed.
7.3
UDP/IP Communications
This section describes UDP/IP communications. In UDP/IP communications, the system does not establish a
connection and does not check whether each data has arrived at the destination normally, thereby reducing the load
on the line. However, UDP/IP communications do not guarantee data reliability as the TCP/IP communications do.
7.3.1
Communication process
Unlike TCP/IP communications, UDP/IP communications do not require connections to be established with connected
7
devices.
Server
Client
7.3 UDP/IP Communications
7.3.1 Communication process
E71
Connected device
Open
Open
Data sending
Data sending request
The client opens
the port.
The client specifies
the destination and
sends data to it.
The server requests
Receive process (reading)
data reception and
reads the received data.
Data sending request
Data sending
Receive process (reading)
Close
Close
The client performs
the close process.
● If a timeout has occurred in the alive check function, the corresponding bit of Open completion signal (address: 5000H)
automatically turns off and the communication line is closed.
● After the connected device sends a close request to the E71, wait for 500ms or more before performing an open process
again.
79
7.3.2
Open procedure
The open/close processes are performed by the procedures described below, according to the Ethernet operation
setting.
(1) When "Always wait for OPEN (Communication possible at STOP time)" is
selected for the Ethernet operation setting
After the E71-connected station is started up, the connection in UDP/IP communications automatically opens and
data sending/receiving are enabled. Creating open/close processing programs is not required.
When open/close processes are performed from the E71 side using a dedicated instruction with "Always wait for OPEN
(Communication possible at STOP time)" set in the Ethernet operation setting, all open/close processes with the subsequent
connected devices must be performed in a program.
80
CHAPTER 7 COMMUNICATION PROCEDURE
(2) When "Do not wait for OPEN (Communications impossible at STOP time)" is
selected for the Ethernet operation setting
Executing the OPEN/CLOSE instructions is required on the E71 to make the E71 enter open/close wait status
open/close wait status before receiving an open/close request from the connected device. When the open
process is normally completed, data sending and receiving are enabled. For the OPEN/CLOSE instructions, refer
to "DEDICATED INSTRUCTIONS".
(
Page 196, CHAPTER 15)
Ex. Open/close processes for the connection number 1
Power-on
Open status
Parameter
communication
completed
1
Open allowed status (closed)
Closed status
7
Initial normal completion
signal X19
2
OPEN instruction
1 scan
OPEN instruction
completion device
7.3 UDP/IP Communications
7.3.2 Open procedure
Abnormally ended
OPEN instruction
completion device + 1
5
CLOSE instruction
1 scan
CLOSE instruction
completion device
Abnormally
ended
CLOSE instruction
completion device + 1
Open completion signal
(address: 5000H)
Open request signal
(address: 5002H)
3
1
Internal process
4
6
Internal process
7
After parameter communications, check that the initial process of the E71 is normally completed.
(Initial normal completion signal (X19): ON)
2
Start the open process using the OPEN instruction. (Open request signal (address: 5002H (b0)): ON)
3
The E71 performs the open process. (Internal process only)
4
Data communications are enabled when the open process is normally completed.
5
Start the close process using the CLOSE instruction. (Open request signal: OFF)
6
The E71 performs the close process. (Internal process only)
7
When the close process is normally completed, data communications terminate.
81
CHAPTER 8
CONNECTING MELSOFT PRODUCTS
AND A GOT
This chapter describes the connection of the E71 with MELSOFT products (such as a programming tool and MX
Component) and the GOT.
8.1
Applications
This section describes applications according to a connection type.
(1) Programming and monitoring over Ethernet
In Ethernet, a programming tool can create programming of a programmable controller and monitor a
programmable controller (MELSOFT connection), and the GOT can monitor and test a programmable controller.
Remote operations making full use of the Ethernet capability, long-distance connectivity and high-speed
communications, are achieved.
GOT
Programming tool
E71
(2) Connecting multiple products
Multiple MELSOFT products and GOTs can be connected using MELSOFT application communication ports.
The connection used in the connection with MELSOFT products is only for data communications with the MELSOFT
products and cannot be used for data communications with connected devices other than MELSOFT products.
(a) Connection using the TCP/IP communications
The E71 can connect to up to 17 MELSOFT products using one dedicated system connection and 16 user
connections. GOTs cannot be connected using the TCP/IP communications. (Use the UDP/IP
communications.)
(b) Connection using the UDP/IP communications
The E71 can connect a MELSOFT product and a GOT using one dedicated system connection.
82
CHAPTER 8 CONNECTING MELSOFT PRODUCTS AND A GOT
8.2
Data Communication Procedure
This section describes the data communication procedure in the MELSOFT connection.
Ex. Connecting the E71 and a personal computer (programming tool)
1.
Write the parameter settings (
Page 69, Section
7.1.4) in the CPU module. To connect multiple
products in the TCP/IP communications, set the
connection for the second product or more in the
open setting. In the following cases, the open
setting is not required.
 Only one product is connected in the TCP/IP
communications.
 The network is running in the UDP/IP communications.
2.
Set the connection target in the programming tool.
Connection destination window
[Connection1]
8
Select "Ethernet Board" under "PC side I/F" and
double-click the item. The window shown to left
appears.
On the window, enter the network number and station
number of the personal computer, not of the E71.
Determine the network number and station number of
the personal computer as follows:
The network number must be the same as that of the
E71.
The station number must be different from that of the
E71 on the same network.
83
8.2 Data Communication Procedure
3.
4.
Select "Ethernet Module" under "PLC side I/F" and
double-click the item. The window shown to left
appears. Set the station number and the IP address
according to the network parameters.
5.
Set "Other Station Setting" and "Network
Communication Route" when required.
6.
A Passive open process is performed on all the
MELSOFT products connected to the network. (The
E71 will wait for an Active open request to itself.)
84
CHAPTER 9 MC PROTOCOL COMMUNICATIONS
CHAPTER 9
MC PROTOCOL COMMUNICATIONS
9
Using MC protocol communications, connected devices that can send and receive data in accordance with the MC
protocol can access a CPU module. Because an E71 processes and sends/receives data based on commands from
connected devices, no programs for data communications are required on the programmable controller side.
For MC protocol communications, refer to the following.
MELSEC Communication Protocol Reference Manual
9.1
Applications
Applications of MC protocol communications are as follows.
(1) Data read/write
Data can be read/written from/to a CPU module device and intelligent function module buffer memory. This
allows a connected device to monitor the CPU module operation, perform data analysis, and manage production
control.
(2) File read/ write
Files such as a program and parameter stored in a CPU module can be read/written. This allows a connected
device to manage CPU module files and switch execution programs.
9.1 Applications
(3) Remote control of a CPU module
The remote operation allows a connected device to remotely operate a CPU module.
(4) Turning off the COM.ERR. LED
The COM.ERR. LED on an E71 can be turned off from a connected device.
(5) Remote password lock/unlock
A remote password can be locked/unlocked from a connected device.
(6) Access to a programmable controller in other stations over other networks
In a system containing CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H,
MELSECNET/10, and Ethernet, access to a programmable controller in other stations can be performed over
each network from a connected device.
85
9.2
Communication Structure
When a connected device sends a message to an E71 in the MC protocol message format, the E71 performs the
process according to the message. During communications, a CPU module including the E71 operates as a server,
and the connected device (a personal computer or other terminals) operates as a client. Based on the command
message received from the client, the server (the E71) automatically sends an appropriate response message.
Client
Server
Connected device
E71
Command message
Header
Application data
Text (command)
Subheader
Ethernet
Response message
Header
The frames that can be used with an E71 are as follows.
• 4E frame
• QnA-compatible 3E frame
• A-compatible 1E frame
86
Application data
Subheader
Text (command)
CHAPTER 9 MC PROTOCOL COMMUNICATIONS
9.3
Data Communication Procedure
9
The following is a data communication procedure for MC protocol communications.
1.
2.
Set the parameters. (
Perform the open process and establish a connection between the E71 and the connected device.
(
3.
4.
Page 88, Section 9.4)
Page 72, Section 7.2, Page 79, Section 7.3)
Once the connection is established, the connected device sends an MC protocol message.
The connection is closed after the communications are completed.
In the cases described below, an E71 performs a remote password check when the connected device accesses the
programmable controller. If communications cannot be performed, unlock the remote password. (
Page 182, Section
14.4.2)
• When a remote password has been set in the CPU module
• When the connection for data communications with the connected device is to be subjected to the remote
password check
9.3 Data Communication Procedure
87
9.4
Parameter Setting
Set the following parameters for MC protocol communications.
• Basic setting (
Page 66, Section 7.1.2)
• Ethernet operation setting (
• Open setting (
Item
Page 67, Section 7.1.3)
Page 69, Section 7.1.4)
Description
Fixed Buffer
Select the communication method for communications using a fixed buffer. For
Communication
MC protocol communications, select "Procedure Exist".
88
Setting range
Procedure Exist
CHAPTER 10 SLMP COMMUNICATIONS
CHAPTER 10 SLMP COMMUNICATIONS
SLMP is a protocol that enables connected devices to access SLMP supporting devices over Ethernet.
SLMP communications are available among devices that can receive/send messages in the SLMP control procedure.
10
This function is available only in the E71 with the serial number (first five digits) of "15042" or later.
For SLMP communications, refer to the following.
SLMP Reference Manual
10.1
Applications
Applications of SLMP communications are as follows.
(1) Data read/write
Data can be read/written from/to a device of the CPU module where an E71 is connected and intelligent function
module buffer memory. This allows a connected device to monitor the operation of the CPU module where an
E71 is connected, perform data analysis, and manage production control.
(2) Remote control of a CPU module
The remote operation allows a connected device to remotely operate a CPU module where an E71 is connected.
(3) Turning off the COM.ERR. LED
10.1 Applications
The COM.ERR. LED on an E71 can be turned off from a connected device.
89
10.2
Communication Structure
When a connected device sends a message to an E71 in the SLMP message format, the E71 performs the process
according to the message. During communications, a CPU module including the E71 operates as a server, and the
connected device (a personal computer or other terminals) operates as a client. Based on the request message
received from the client, the server (the E71) automatically sends an appropriate response message.
Client
Connected device
Server
E71
Request message
Header
Subheader
Access
destination
Command
Ethernet
Response message
Header
90
Subheader
Response data
CHAPTER 10 SLMP COMMUNICATIONS
10.3
Data Communication Procedure
The following is a data communication procedure for SLMP communications.
1.
2.
Set the parameters. (
Page 92, Section 10.4)
Perform the open process and establish a connection between the E71 and the connected device.
(
3.
4.
10
Page 72, Section 7.2, Page 79, Section 7.3)
Once the connection is established, the connected device sends an SLMP message.
The connection is closed after the communications are completed.
In the cases described below, an E71 performs a remote password check when the connected device accesses the
programmable controller. If communications cannot be performed, unlock the remote password. (
Page 182, Section
14.4.2)
• When a remote password has been set in the CPU module
• When the connection for data communications with the connected device is to be subjected to the remote
password check
10.3 Data Communication Procedure
91
10.4
Parameter Setting
Set the following parameters for SLMP communications.
• Basic setting (
Page 66, Section 7.1.2)
• Ethernet operation setting (
• Open setting (
Item
Page 67, Section 7.1.3)
Page 69, Section 7.1.4)
Description
Fixed Buffer
Select the communication method for communications using a fixed buffer. For
Communication
SLMP communications, select "Procedure Exist".
92
Setting range
Procedure Exist
CHAPTER 10 SLMP COMMUNICATIONS
10.5
Available command list
The following table lists the commands that can be executed from a connected device to the E71.
10
The  part in the Subcommand column varies depending on the specified device.
For details on each command, refer to the following.
SLMP Reference Manual
Item
Type
Operation
Command
Subcommand
001
Read
0401
Write
1401
000
001
Read Random
0403
Device
Write Random
000
Remote
Control
Remote
Password
• Reads values in 16-point units from bit devices (consecutive device numbers).
• Reads values in 1-word units from word devices (consecutive device numbers).
Writes values to bit devices (consecutive device numbers) in 1-point units.
• Writes values to bit devices (consecutive device numbers) in 16-point units.
• Writes values to word devices (consecutive device numbers) in 1-word units.
000
001
Specifies a device number in 1-point units to write a value to a bit device. Discrete
device numbers can be used.
1402
• Specifies a device number in 16-point units to write a value to a bit device.
Discrete device numbers can be used.
• Specifies a device number in 1- or 2-word units to write a value to a word
device. Discrete device numbers can be used.
Entry Monitor Device
0801
000
Registers a device to be read by Execute Monitor (command: 0802).
Execute Monitor
0802
0000
Reads the value of the device registered by Entry Monitor Device (command:
0801).
Read Block
0406
000
Specifies n points (1 point: 16 bits) of word or bit devices as one block, and reads
multiple blocks of data. Discrete device numbers can be used.
Write Block
1406
000
Specifies n points (1 point: 16 bits) of word or bit devices as one block, and writes
multiple blocks of data. Discrete device numbers can be used.
Read
0613
0000
Reads buffer memory data of the E71.
Write
1613
0000
Writes data to the buffer memory of the E71.
Read
0601
0000
Reads buffer memory data of the intelligent function module.
Write
1601
0000
Writes data to the buffer memory of the intelligent function module.
Remote Run
1001
0000
Executes remote RUN to the CPU module where an E71 is connected.
Remote Stop
1002
0000
Executes remote STOP to the CPU module where an E71 is connected.
Remote Pause
1003
0000
Executes remote PAUSE to the CPU module where an E71 is connected.
Remote Latch Clear
1005
0000
Executes remote latch clear to the CPU module where an E71 is connected.
Remote Reset
1006
0000
Executes remote RESET to the CPU module where an E71 is connected.
Read Type Name
0101
0000
Reads the model name and code of the CPU module where an E71 is connected.
Lock
1631
0000
Specifies the remote password to disable the communication with other devices.
(The locked state is activated from the unlocked state.)
Unlock
1630
0000
Specifies the remote password to enable communication with other devices. (The
unlocked state is activated from the locked state.)
93
10.5 Available command list
Extend Unit
Reads values in 1-point units from bit devices (consecutive device numbers).
Specifies a device number to read the device value. Discrete device numbers can
be used.
• Reads bit devices in 16- or 32-point units.
• Reads word devices in 1- or 2-word units.
000
Memory
Description
Item
Type
File
Command
Subcommand
Read Directory/File
1810
0000
Reads file list information from the CPU module where an E71 is connected.
Search Directory/File
1811
0000
Reads the file number of the specified file from the CPU module where an E71 is
connected.
New File
1820
0000
Reserves storage area for the specified file of the CPU module where an E71 is
connected.
Delete File
1822
0000
Deletes a file in the CPU module where an E71 is connected.
Copy File
1824
0000
Copies the specified file in the CPU module where an E71 is connected.
Change File State
1825
0000
Changes the attributes of the file in the CPU module where an E71 is connected.
Operation
Description
Change File Date
1826
0000
Changes the creation date of the file in the CPU module where an E71 is
connected.
Open File
1827
0000
Locks a file so that the data of the file is not changed by other devices in the CPU
module where an E71 is connected.
Read File
1828
0000
Reads the data of a file from the CPU module where an E71 is connected.
Writes the data to a file in the CPU module where an E71 is connected.
Write File
1829
0000
Close File
182A
0000
Cancels the file lock by the open process.
Self Test
0619
0000
Tests whether the communication with the E71 is normally executed or not.
Clear Error
1617
0000
Turns off the COM.ERR. LED on the E71.
94
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
CHAPTER 11
DATA COMMUNICATIONS USING
THE PREDEFINED PROTOCOL
Data can be transferred between a connected device and the CPU module with a protocol appropriate to the
connected device (such as a measuring instrument or a bar code reader).
Device or buffer memory data can be taken into communication packets, and thereby this protocol communications are
suitable for data that may change in each communication.
The protocol setting required to communicate with the connected device can be configured in GX Works2.
Protocols can be selected from the Predefined Protocol Library or can be created and edited.
This function is available only in the E71 with the serial number (first five digits) of "15042" or later.
1) Setting protocols
2) Writing protocols
Protocols can be set easily using the predefined
protocol support function of GX Works2.
Write the set protocols in the flash ROM of the E71.
GX Works2
Sending
Connected device
E71
Receiving
3) Executing protocols
Execute protocols by dedicated instructions.
Multiple protocols can be executed by one dedicated
instruction.
Connected device
Data can be communicated
with protocols appropriate to
each connected device.
For the protocol setting method, refer to the following.
GX Works2 Version 1 Operating Manual (Intelligent Function Module)
95
11
● The followings are the maximum numbers of protocols and packets that can be registered.
• Protocols: Up to 128
• Packets: Up to 256
• Packet data area size: Up to 12288 bytes
If once the number of packets reaches the upper limit, protocols cannot be added even though the number of protocols
has not reached the upper limit.
In addition, if once the packet data area size reaches the upper limit, protocols and packets cannot be added even though
the numbers of protocols and packets have not reached the upper limit.
For details, refer to the following.
GX Works2 Version 1 Operating Manual (Intelligent Function Module)
● From Connection No.1 to 16 are available.
● The Communication Data Code becomes Binary Code regardless of the setting.
96
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
11.1
Data Communication Procedure
By using the predefined protocol support function, data can be communicated with the connected device in the
following procedure.
1.
Display the "Predefined Protocol Support Function"
window.
[Tool]
[Predefined Protocol Support Function]
11
[Ethernet Module...]
2.
Create a new file.
[File]
3.
[New...]
"Add"
Select "Predefined Protocol Library" or "Add New"
in the "Add Protocol" window.
When "Predefined Protocol Library" is selected, select
in GX Works2.
If "User Protocol Library" is selected in the "Add Protocol" window, protocols saved by user can be read. For details on the
User Protocol Library, refer to the following.
GX Works2 Version 1 Operating Manual (Intelligent Function Module)
97
11.1 Data Communication Procedure
the protocol from Predefined Protocol Library registered
4.
Set the items required for the data communications.
• Set communication parameters in the "Protocol Detailed
Setting" window.
"Protocol Detailed Setting" window
protocol
[Edit]
Select a
[Protocol Detailed Setting...]
• Set the configuration of packets to be sent and received in
the "Packet Setting" window.
"Protocol Detailed Setting" window
Unset] or [Element Unset]

98
[Variable
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
5.
Write the protocol setting data to the flash ROM.
[Online]
[Write to PLC...]
Select a target module and write the protocol setting
data to the flash ROM.*1
11
*1
When the initial process is not completed, the protocol setting data cannot be written to the flash ROM. Before writing
the data, set the network parameters and check that the initial process is completed.
(The initial process completion can be checked using Initial normal completion signal (X19).)
● The following data cannot be read out because they are not written to the E71. However, when the protocols are
selected from the Predefined Protocol Library, the followings can be displayed.
• Manufacturer
• Packet Name
• Protocol Detailed Setting Type, Version, Explanation
• Packet Setting Element Name
● Module Selection using the Predefined Protocol Support Function is available only when "Not Specification" is set in the
Transfer Setup of GX Works2.
When other station is specified, the E71 specified in the Transfer Setup of GX Works2 becomes the target module.
6.
Execute the protocol by using a dedicated
instruction.
the dedicated instruction (ECPRTCL instruction).
● Protocols can be executed only when the target connection is in the following status:
• When Open completion signal is on
• When "Predefined protocol" is set to Fixed Buffer Communication in the open setting
If the protocol is executed to the connection where the above conditions are not satisfied, the ECPRTCL instruction
ends abnormally.
99
11.1 Data Communication Procedure
Execute the protocol written to the flash ROM by using
11.2
Communication Type of Protocols
Receive and send packets from/to the connected device for the process execution are registered in a protocol. Packet
elements set using the predefined protocol support function correspond to the data part of the send/receive packets.
The following shows an example of packet configuration. For details on the packet elements, refer to Page 346,
Appendix 8.3.
(1) TCP/IP
Maximum data length: 1514 bytes
Header
Destination Sender's MAC
MAC address:
address:
6 bytes
6 bytes
Type:
2 bytes
Ethernet header
IP:
20 bytes
TCP:
20 bytes
Data
TCP/IP header
40 to 1500 bytes
(2) UDP/IP
Maximum data length: 1514 bytes
Header
Destination
Sender's
MAC address: MAC address:
6 bytes
6 bytes
Ethernet header
Type:
2 bytes
IP:
20 bytes
UDP:
8 bytes
Data
UDP/IP header
28 to 1500 bytes
Communications with the connected device using the predefined protocol function are performed with the
following procedure (communication types).
For the operations of each communication type, refer to Page 339, Appendix 8.1.
Communication type name
Send Only
Sends a send packet once.
Receive Only
Receives a packet if it matches any of up to 16 defined receive packets.
Send&Receive
100
Description
Sends a send packet, then receives a packet if it matches any of up to 16 defined
receive packets.
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
11.3
Packet Elements
A packet consists of packet elements.
Up to 32 elements can be placed in a packet, and the maximum data length is 2046 bytes per packet.
The following shows the details of the packet elements.
For examples of packet element data, refer to Page 346, Appendix 8.3.
11
(1) Static Data
This element is used when a specific code or character string such as a command exists in a packet.
• When sending: The specified code and character string are sent.
• When receiving: Receive data are verified.
Multiple Static Data elements can be placed anywhere in the data part.
The following table lists the items.
Item
Element Name

Set name of the element.
Select a data type of the setting value.

ASCII String/ASCII Control Code/HEX
Set data within 1 to 50 bytes.
Code type and setting range are as follows:
Setting Value
Remark
• ASCII String: 20H to 7FH
• ASCII Control Code: Control code of 00H to 1FH and 7FH
• HEX: Hexadecimal data of 00H to FFH
Setting example
ASCII String: "ABC"
ASCII Control Code: STX
HEX: FFFF
101
11.3 Packet Elements
Code Type
Description
(2) Length
This element is used when an element indicating the data length is included in a packet.
• When sending: The data length of the specified range is calculated and the result is added to a send packet.
• When receiving: The data (setting value) corresponds to the Length in the receive data is verified as the data
length of the specified range.
Length elements can be placed anywhere in the data part.
The following table lists the items.
Item
Description
Element Name

Set name of the element.
Select a format of the data length.
Code Type

ASCII Hexadecimal/HEX
Select the data length on the line.
Data Length

The range is 1 to 4.
Forward Direction
(Upper ByteLower Byte)
Reverse Direction
(Lower ByteUpper Byte)
Data Flow
Remark
When sending: The calculated Length is sent from the
upper byte.
When receiving: The data is received from the upper byte.
When sending: The calculated Length is sent from the
lower byte.
When receiving: The data is received from the lower byte.
Not settable when Data
Length is 1 byte
When sending: The calculated Length is sent swapping
Byte Swap (by Word)*1
the upper byte and lower byte by word.
When receiving: The data is received swapping the upper
byte and lower byte by word.
Calculating
Range
Start
End
*1
102
Select the start element number of the calculating range.
The range is 1 to 32.
Select the end element number of the calculating range.
The range is 1 to 32.
Available only when the Data Length is 4 bytes.

CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
● Multiple Length elements can be placed in a packet.
● When there is no element other than a Length element, an element error occurs.
(To use a Length element, one or more element(s) other than Length is/are required.)
● When the number of digits of calculation result is greater than that specified in "Data Length", digits greater than the
specified digit are omitted (ignored).
For example, if the data length is 2 bytes and the data size calculation results are "123" bytes, the data length will be "23".
● When a Non-conversion Variable (Variable length) or Non-verified Reception (Variable number of characters) is placed
behind a Length and is not included in the Length calculating range, place Static Data immediate after the Nonconversion Variable or Non-verified Reception.
11
● When "Code Type" is "ASCII Hexadecimal", a corresponding packet is regarded as a mismatch packet if a string except
for "0" to "9", "A" to "F", and "a" to "f" is received.
● When sending data converted to ASCII characters, use "0" to "9" or "A" to "F".
● When multiple Length elements are placed, the calculating range cannot be set as follows:
• A Length calculating range overlaps the others.
• The calculating range of a Length is greater than that of the Length placed before.
● Length element cannot be placed at the end of the packet elements.
11.3 Packet Elements
103
(3) Non-conversion Variable
This element is used to send data in the device memory of a CPU module or buffer memory as a part of a send
packet, or to store a part of a receive packet to the device memory of a CPU module device or buffer memory.
The following table lists the items.
Item
Element Name
Description
Set name of the element.
Fixed Length
Fixed Length/Variable Length
Sends and receives the data whose length is fixed.
When sending: The data length at the time of the protocol execution is
Variable Length
specified and the data is sent.
When receiving: The data of which the length is variable is received.
Set the length of data to be sent and received.
Data Length/Maximum Data
(For the variable length data, set the maximum data length that can be specified to the data length storage
Length
area.)
The range is 1 to 2046.
When sending: Each one word (2 bytes) data in the data storage area is sent in
Lower Byte + Upper Byte
the order of the lower byte to the upper byte.
When receiving: The receive data is stored to the data storage area in the
order of the lower byte to the upper byte.
Unit of Stored Data
When sending: Each lower byte data in the data storage area is sent.
Lower Bytes Only
The E71 ignores data in the upper byte.
When receiving: The receive data is stored to each lower byte in the data
storage area. The E71 stores 00H in the upper byte.
When sending: When "Enable" is selected, data in the upper byte and lower
byte are swapped by word (2 bytes) and sent.
When "Unit of Stored Data" is "Lower Byte + Upper Byte" and "Data
Length" is an odd number of bytes, the upper byte is sent at transmission
of the last byte.
When "Unit of Stored Data" is "Lower Bytes Only" and "Data Length" is
an odd number of bytes, data without any byte swap is sent at
Byte Swap
Disable/Enable
transmission of the last byte.
When receiving: When "Enable" is selected, data in the upper byte and lower
byte are swapped by word (2 bytes) and sent.
When "Unit of Stored Data" is "Lower Byte + Upper Byte" and "Data
Length" is an odd number of bytes, the last byte is stored to the upper
byte.
When "Unit of Stored Data" is "Lower Bytes Only" and "Data Length" is
an odd number of bytes, the last byte is stored without any byte swap.
104
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
Item
Description
Specify a start device to store variable value.
Available devices are as follows:
• Internal user*1*2
Input relay (X)
Output relay (Y)
Internal relay (M)
Data Storage Area
Latch relay (L)
Specification
Link relay (B)
11
Data register (D)
Link register (W)
• File register*2
File register (R, ZR)
• Buffer memory
G device (G) (Send/receive area for predefined protocol support function (address: 4800H to 4FFFH))
*1
*2
Do not set local devices.
Set within the device range specified in the "Device" window of PLC Parameter.
The following describes the configuration of the data storage area.
(a) When "Fixed Length/Variable Length" is "Fixed Length"
An area starting from the device number which is specified in the "Element Setting" window is considered as
the data storage area.
The data storage area to be occupied varies depending on the setting of "Unit of Stored Data".
• When "Lower Byte + Upper Byte" is selected, the same size as the data length is occupied.
(However, when the data length of a send packet is an odd number, the upper byte (lower byte for "Byte
Swap") of the last device is not sent. When the data length of a receive packet is an odd number, the last
data is stored with one byte of 00H.)
(Word)
11.3 Packet Elements
• When "Lower Bytes Only" is selected, twice the size of the data length is occupied.
Specified device
+0
Send
packet
Data storage area
Data storage area
Send packet: The user stores the send data.
Receive packet: The E71 stores the receive data.
Receive
packet
Data storage area
+n
105
(b) When "Fixed Length/Variable Length" is "Variable Length"
An area starting from the device number which is specified in the "Element Setting" window +1 is considered as
the data storage area.
The data storage area to be occupied varies depending on the setting of "Unit of Stored Data".
• When "Lower Byte + Upper Byte" is selected, the same size as the data length + one word (length for the
data length storage area) are occupied. (However, when the data length of a send packet is an odd
number, the upper byte (lower byte for "Byte Swap") of the last device is not sent. When the data length of
a receive packet is an odd number, the last data is stored with one byte of 00H.)
• When "Lower Bytes Only" is selected, twice size of the data length + one word (length for the data length
storage area) are occupied.
(Word)
+0
Specified device
Data length storage area*
+1
Send
packet
Data storage area
Data storage area
Send packet: The user stores the send data.
Receive packet: The E71 stores the receive data.
Receive
packet
Data storage area
+n
*: The unit of the data length is fixed to byte.
● Multiple Non-conversion Variable elements can be placed in a packet.
● When "Fixed Length/Variable Length" is "Variable Length" and the configuration is set as follows, an error occurs:
• An element other than Static Data is placed behind a Non-conversion Variable element when Non-conversion
Variable is out of the Length calculating range or when there is no Length element (except for when Nonconversion Variable is placed at the end of the packet elements).
• Multiple Non-conversion Variable elements are placed in the Length calculating range, while a Length element is
not placed.
• A Non-conversion Variable element is placed before a Length element in the Length calculating range.
106
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
(4) Non-verified Reception
11
This element is used when receive data include unnecessary data.
The E71 skips characters as many as the specified number if a receive packet includes a Non-verified Reception.
The following table lists the items.
Item
Element Name
Data Length
Description

Set name of the element.
0 (Variable number of
Set this item when the number of characters not to
characters)
be verified varies in each communication.
1 to 2046 (Specified number
of characters)
Remark

Set the number of characters not to be verified.
● Multiple Non-verified Reception elements can be placed in a packet.
107
11.3 Packet Elements
● When "Data Length" is set to 0 and the configuration is set as follows, an error occurs:
• An element other than Static Data is placed behind a Non-verified Reception element when Non-verified
Reception is out of the Length calculating range or when there is no Length element (except for when Non-verified
Reception is placed at the end of the packet elements).
• Multiple Non-verified Reception elements are placed in the Length calculating range, while a Length element is
not placed.
• A Non-verified Reception element is placed before a Length element in the Length calculating range.
11.4
Execution Condition of Predefined Protocol
Communication
Communications using the predefined protocol can be executed when Predefined protocol ready (X1D) is on.
This section describes the operations of Predefined protocol ready (X1D).
(1) When the power supply is on or reset
The E71 checks the written protocol setting data when the power supply is on or reset.
If the protocol setting data is set correctly, the E71 turns on Predefined protocol ready (X1D) then the protocols
can be executed.
Predefined protocol ready (X1D) is used as an interlock signal when the protocols are executed.
If an error has occurred in the protocol setting data, Predefined protocol ready (X1D) stays off and the error
details are stored to the protocol setting data check area (address: 5320H to 533FH).
If no protocol setting data has been set, the E71 does not check the data and Predefined protocol ready (X1D)
stays off.
The information about whether protocol setting data has been registered can be checked in Number of registered
protocols (address: 5328H) and Protocol registration (address: 5330H to 533FH).
(a) If the protocol setting data is set correctly
Power on/reset
Check result normal
E71
Checking the
protocol setting data
X1D turns on when the
check result is normal.
Predefined protocol ready
(X1D)
Protocol setting data
check area
(address: 5320H to 533FH)
108
The number of registered protocols and information
about whether protocols have been registered are stored.
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
(b) If an error has occurred in the protocol setting data
Power on/reset
Check result error
E71
Checking the
protocol setting data
11
X1D stays off.
Predefined protocol ready
(X1D)
Protocol setting data
check area
(address: 5320H to 533FH)
The error details are stored.
(2) When the protocol setting data is written
When the protocol setting data writing from GX Works2 is completed, Predefined protocol ready (X1D) turns off.
After the completion, the E71 checks the protocol setting data. If the protocol setting data is set correctly, the E71
turns on Predefined protocol ready (X1D).
If an error has occurred in the protocol setting data, Predefined protocol ready (X1D) stays off and the error
details are stored to the protocol setting data check area (address: 5320H to 533FH).
Start to write
the protocol setting data.
Check result normal
E71
Writing the protocol
setting data
X1D turns on when the
protocol setting data has been
set correctly before data write.
Checking the protocol
setting data
X1D turns off.
X1D turns on when the
check result is normal.
Predefined protocol ready
(X1D)
X1D turns off if no protocol setting data
has been set or an error has occurred in
the protocol setting data before data write.
Protocol setting data
check area
(address: 5320H to 533FH)
The number of registered protocols and
information about whether protocols have
been registered are stored.
109
11.4 Execution Condition of Predefined Protocol Communication
(a) If the protocol setting data is set correctly
(b) If an error has occurred in the protocol setting data
Start to write
the protocol setting data.
Check result error
E71
Writing the protocol
setting data
X1D turns on when the
protocol setting data has
been set correctly before
data write.
Checking the protocol
setting data
X1D turns off.
X1D stays off.
Predefined protocol ready
(X1D)
X1D turns off if no protocol setting data has been
set or an error has occurred in the protocol setting
data before data write.
Protocol setting data
check area
(address: 5320H to 533FH)
The error details are stored.
(3) When the UINI instruction is being executed
The E71 does not check the protocol setting data when the UINI instruction is being executed.
Predefined protocol ready (X1D) keeps its status even when the instruction is executed.
(4) The operations of X1D and COM.ERR.LED
If an error has occurred in the protocol setting data when the power supply is on or reset, or at the data check
after the data writing, Protocol setting data error (error code: C402H) occurs.
Predefined protocol ready (X1D) turns off and the COM.ERR.LED turns on at this time.
110
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
11.5
Example of Predefined Protocol Communications
This section describes an example of communications using the predefined protocol under the following system
configuration.
11.5.1
System configuration example
11
(1) System configuration
GX Works2
LCPU-1
(192.0.1.100)
LCPU-2
(192.0.1.101)
Ethernet
11.5 Example of Predefined Protocol Communications
11.5.1 System configuration example
111
11.5.2
Parameter Setting
(1) Sending side (LCPU-1 side)
The following is an example of the parameter settings of the sending side (LCPU-1 side).
(a) Basic setting
The following is an example of the basic setting.
(b) Ethernet operation setting
The following is an example of the Ethernet operation setting.
112
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
(c) Open setting
The following is an example of the open setting.
11
11.5 Example of Predefined Protocol Communications
11.5.2 Parameter Setting
113
(d) Protocol setting data
The value in D100 to D109 of the destination station can be read by using SLMP (Device Read) command in
the Predefined Protocol Library.
The followings are setting examples of the protocol setting data using the Predefined Protocol Support
Function.
[Protocol Setting]
[Packet Setting]
• Send Packet (Request)
114
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
• Receive Packet (Normal response)
11
• Receive Packet (Error response)
11.5 Example of Predefined Protocol Communications
11.5.2 Parameter Setting
115
(2) Receiving side (LCPU-2 side)
The following is an example of the parameter settings of the receiving side (LCPU-2 side).
(a) Basic setting
The following is an example of the basic setting.
(b) Ethernet operation setting
116
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
(c) Open setting
11
11.5 Example of Predefined Protocol Communications
11.5.2 Parameter Setting
117
11.5.3
Program example
The following is a program example that specifies Connection No.1 and executes a protocol by using the ECPRTCL
instruction.
(1) Sample program
(a) Sending side (LCPU-1 side)
<<Open process program>>
<<Program for predefined protocol communications>>
118
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
11
<<Close process program>>
11.5 Example of Predefined Protocol Communications
11.5.3 Program example
119
CHAPTER 12 COMMUNICATIONS USING A FIXED
BUFFER
This chapter describes communications using a fixed buffer.
12.1
Applications
In communications using a fixed buffer, a programmable controller can actively send data; therefore, data can be sent
from the programmable controller to the host system when an error occurs in machine equipment or some other
conditions are satisfied. A maximum of 1K word of data can be sent or received between programmable controllers or
between a programmable controller and the host system.
12.1.1
Differences between the "Procedure Exist" and "No
Procedure" control methods
There are two control methods for communications using a fixed buffer; "Procedure Exist" control method and "No
Procedure" control method. This section describes the differences between the "Procedure Exist" and "No Procedure"
control methods.
Item
Difference
Procedure Exist
No Procedure
Data is sent/received in the message format of the
Message format
Data is sent/received in a fixed data format.
A response to data receiving
A response to data receiving is sent.
A response to data receiving is not sent.
Communications can be performed using a
Communications are performed using only a binary
binary code or ASCII code.
code.
Specified by the number of words.
Specified by the number of bytes.
Maximum of 1017 words
Maximum of 2046 bytes
Data code
Data length specified using a
dedicated instruction
Amount of application data per
communication
connected device.
A connection with a connected device is dedicated for "No Procedure" communications using a fixed buffer. MC protocol
communications and "Procedure Exist" communications using a fixed buffer and random access buffer cannot be performed
at the same time as "No Procedure" communications using a fixed buffer.
120
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.2
Communication Structure
This section describes the structure of communications using a fixed buffer.
(1) Data flow
In communications using a fixed buffer, data is sent/received using dedicated instructions.
• Sending data: BUFSND instruction
• Receiving data: BUFRCV instruction or BUFRCVS instruction
When the "Procedure Exist" control method is used, the CPU module and the connected device communicate on
12
a 1:1 basis. The CPU module sends/receives data to/from the connected device while handshaking with the
connected device.
When the "No Procedure" control method is used, the CPU module sends/receives data to/from the connected
device in a non-procedural manner.
E71
Fixed buffer
BUFSND instruction
CPU module
BUFRCV instruction
No.1
No.2
No.3
No.4
Connected device
No.16
(2) Connected devices where data communications can be performed
• Devices in Ethernet where an E71 is connected
• Devices connected with the router relay function
When using each fixed buffer (numbers 1 to 16) as shown in the figure below, set the destination devices and
usage conditions (e.g. for sending/receiving and "Procedure Exist"/"No Procedure") in the open setting to fix a
connected device to each buffer.
Fixed buffer No.1
To send data to the connected device 1
Fixed buffer No.2
To receive data from the connected device 1
Fixed buffer No.3
To receive data from the connected device 8
Connected device 1
Connected device 8
Fixed buffer No.16 To send data to the connected device 28
Connected device 28
Note the following points when changing connected devices.
• During TCP/IP communications, a connected device can be changed only when the connection with the
connected device is not established (when Open completion signal is off).
• During UDP/IP communications, a connected device can be changed regardless of the status of connection
with the connected device.
121
12.2 Communication Structure
Data communications can be performed with the following connected devices.
● When changing connected devices, do not use the pairing open or alive check function.
● When "No Procedure" is selected for a connection, the connection is dedicated to "No Procedure" communications using
a fixed buffer after the open process is completed. When "Procedure Exist" is selected for a connection, the following
data communications can be performed after the open process is completed.
• MC protocol communications
• Communications using a fixed buffer using the "Procedure Exist" control method
• Communications using a random access buffer
(3) Processes during data sending/receiving
(a) When data is sent
When a CPU module executes the BUFSND instruction, the E71 sends data of the applicable fixed buffer
number n to the connected device that is specified in Communication address setting area (addresses: 28H to
5FH) corresponding to the fixed buffer number n.
(b) When data is received
An E71 processes the data that is received from the connected device set in the communication address
setting area corresponding to the fixed buffer number n.*1 In addition, when an E71 stores the received data in
the corresponding fixed buffer in the receive process, it updates the IP address and destination port number of
the connected device in Connection information area (addresses: 78H to C7H and 5820H to 586FH)
corresponding to the fixed buffer number n. If data is received from a connected device not set in the
connection information area of the buffer memory, an E71 ignores the received data.
*1
With the TCP/IP Unpassive open, data is sent to or received from a connected device stored in the connection
information area of the buffer memory.
When received data is stored in the corresponding fixed buffer in the receive process of broadcast communications, an E71
updates the destination IP address and port number in Connection information area (address: 78H to C7H and 5820H to
586FH) corresponding to the fixed buffer number n.
122
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.3
Data Sending Procedure
This section describes how an E71 sends data to the connected device.
(1) Procedure exists
The following is the data send process performed in the fixed buffer number 1 area for the connection number 1.
Initial process Open process
Sending data
Receiving a response
12
Initial normal completion
signal X19
Open completion signal
(address: 5000H [b0])
1
2
BUFSND instruction
3
6
BUFSND instruction
completion device
1 scan
ACK
(TCP only)
Response
Sending data
BUFSND instruction
completion device + 1
5
Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
1
Establish a connection between the E71 and the connected device and confirm the normal completion of the
2
open process of the connection number 1.
3
Execute the BUFSND instruction. (The data is sent.)
4
The send data in the fixed buffer number 1 is sent to the connected device by the send data length.
When the connected device receives the data from the E71, the connected device sends a response to the
5
E71.
When the E71 receives the response from the connected device, the E71 stops sending data. If a response is
6
not sent within the response monitoring timer value, a data send error occurs.*1
After the data send process abnormally ends, execute the BUFSND instruction again to repeat the send
process.
*1
Refer to the section describing the initial setting when adjusting the monitoring timer value. (
4.1)
Page 311, Appendix
● The items configured in the open setting become enabled when Open completion signal of an E71 is started up.
● Do not send data (command) before data communications are completed (or a response is received) in response to the
previous data (command).
● When an E71 communicates data with multiple connected devices, data can be sent sequentially; however, switching the
connected devices before sending/receiving data is recommended to prevent communication problems. When a
connection opened using the UDP/IP protocol is used, change the setting values in the communication address setting
area before sending or receiving data to switch the connected devices.
123
12.3 Data Sending Procedure
4
ACK
(TCP only)
(2) No procedure
The following is the data send process performed in the fixed buffer number 1 area for the connection number 1.
Initial process
Open process
Sending data
1
Initial normal completion
signal X19
Open completion signal
(address: 5000H [b0])
2
3
BUFSND instruction
5
BUFSND instruction
completion device
1 scan
Sending data
BUFSND instruction
completion device + 1
ACK
(TCP only)
4
1
2
Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
Establish a connection between the E71 and the connected device and confirm the normal completion of the
open process of the connection number 1.
3
Execute the BUFSND instruction. (The data is sent.)
4
The send data in the fixed buffer number 1 is sent to the connected device by the send data length.
5
The E71 stops sending data. After the data send process abnormally ends, execute the BUFSND instruction
again to repeat the send process.
During UDP/IP communications, when the internal process of an E71 is normally completed, the data send process ends
even if the communication line between a CPU module and the connected device is not connected due to cable
disconnection or other causes. It is recommended to set an original communication procedure to send/receive data.
124
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.4
Data Receiving Procedure
This section describes how an E71 receives data from the connected device. The following methods for receiving data
are offered:
• Data receiving using the main program (BUFRCV instruction)
• Data receiving using an interrupt program (BUFRCVS instruction)
12.4.1
Data receiving using the main program (BUFRCV instruction)
12
A receive process in the main program is performed using the BUFRCV instruction.
(1) Procedure exists
The following is the data receive process performed in the fixed buffer number 1 area for the connection number
1.
Initial process
Initial normal completion
signal X19
Open process
Receiving data
Sending a response
1
Open completion signal
(address: 5000H [b0])
2
6
BUFRCV instruction
completion device
1 scan
BUFRCV instruction
completion device + 1
3
1
2
3
ACK
(TCP only)
Response
Receiving data
Fixed buffer reception status signal
(Address: 5005H [b0])
ACK
(TCP only)
5
Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
Establish a connection between the E71 and the connected device and confirm the normal completion of the
open process of the connection number 1.
Receive data from the destination.
• Fixed buffer reception status signal (address: 5005H (b0)): ON
Execute the BUFRCV instruction to read the receive data length and receive data from the fixed buffer
4
number 1.
• Fixed buffer reception status signal (address: 5005H (b0)): OFF
5
6
When the receive data length and the receive data are completely read out, a response is sent to the
destination.
End the receive process. If the data receive process is abnormally ended, execute the BUFRCV instruction
again to repeat the receive process.
125
12.4 Data Receiving Procedure
12.4.1 Data receiving using the main program (BUFRCV instruction)
4
BUFRCV instruction
● The items configured in the open setting become enabled when Open completion signal of an E71 is started up.
● When the buffer memory area that stores Fixed buffer reception status signal is turned off and on, execute the BUFRCV
instruction.
● When abnormal data is received, Fixed buffer reception status signal does not turn on. In addition, data is not stored in
the fixed buffer number 1 area.
126
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(2) No procedure
The following is the receive process performed in the fixed buffer number 1 area for the connection number 1.
Initial process
Open process
Receiving data
1
Initial normal completion
signal X19
Open completion signal
(address: 5000H [b0])
12
2
4
BUFRCV instruction
5
BUFRCV instruction
completion device
1 scan
BUFRCV instruction
completion device + 1
Receiving data
Fixed buffer reception status signal
(Address: 5005H [b0])
ACK
(TCP only)
1
2
3
Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
Establish a connection between the E71 and the connected device and confirm the normal completion of the
open process of the connection number 1.
Receive data from the connected device.
• Fixed buffer reception status signal (address: 5005H (b0)): ON
Execute the BUFRCV instruction to read the receive data length and receive data from the fixed buffer
4
number 1.
• Fixed buffer reception status signal (address: 5005H (b0)): OFF
5
End the receive process. If the data receive process is abnormally ended, execute the BUFRCV instruction
again to repeat the receive process.
● The items configured in the open setting become enabled when Open completion signal of an E71 is started up.
● When the buffer memory area that stores Fixed buffer reception status signal is turned off and on, execute the BUFRCV
instruction.
● When abnormal data is received, Fixed buffer reception status signal does not turn on. In addition, data is not stored in
the fixed buffer number 1 area.
127
12.4 Data Receiving Procedure
12.4.1 Data receiving using the main program (BUFRCV instruction)
3
12.4.2
Data receiving using an interrupt program (BUFRCVS
instruction)
A receive process in an interrupt program is performed using the BUFRCVS instruction. An interrupt program is started
up when data is received from a connected device, and receive data for a CPU module can be read.
The following settings are required to use an interrupt program: (
Page 131, Section 12.5.1)
• Interrupt pointer setting
• Interrupt settings
(1) Procedure exists
The following is the receive process performed in the fixed buffer number 2 area for the connection number 2.
Initial
process
Initial normal completion
signal X19
Open
process
Sending a response
Receiving data
1
Open completion signal
(address: 5000H [b1])
2
BUFRCVS instruction
4
6
ACK
(TCP only)
3
Scan
ACK
(TCP only)
5
Cycle
Program
Response
Receiving data
In interrupt process
Cycle
END
process
Scan
Interrupt process
Scan
END
process
Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
1
Establish a connection between the E71 and the connected device and confirm the normal completion of the
2
open process of the connection number 2.
Receive data from the destination.
3
• Fixed buffer reception status signal (address: 5005H (b1)): ON
• Request the CPU module to start up the interrupt program.
The interrupt program starts up. Execute the BUFRCVS instruction to read the receive data length and
4
receive data from the fixed buffer number 2.
When the receive data length and the receive data are completely read out, a response is sent to the
5
destination.*1
End the interrupt program to restart the main program.
6
*1
128
If the data receive process is abnormally ended, the E71 does not return a response.
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(2) No procedure
The following is the receive process performed in the fixed buffer number 2 area for the connection number 2.
Initial
process
Initial normal completion
signal X19
Open
process
Receiving data
1
Open completion signal
(address: 5000H [b1])
12
2
BUFRCVS instruction
4
5
Receiving data
In interrupt process
ACK
(TCP only)
3
Cycle
Program
1
3
END
process
Scan
Interrupt process
Scan
END
process
Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
Establish a connection between the E71 and the connected device and confirm the normal completion of the
open process of the connection number 1.
Receive data from the destination.
• Request the CPU module to start up the interrupt program.
4
The interrupt program starts up. Execute the BUFRCVS instruction to read the receive data length and
receive data from the fixed buffer number 1.
5
End the interrupt program to restart the main program.
129
12.4 Data Receiving Procedure
12.4.2 Data receiving using an interrupt program (BUFRCVS instruction)
2
Scan
Cycle
12.5
Parameter Setting
Set the following parameters to perform communications using a fixed buffer.
• Basic setting (
Page 66, Section 7.1.2)
• Ethernet operation setting (
• Open setting (
Page 67, Section 7.1.3)
Page 69, Section 7.1.4)
Item
Fixed Buffer
Fixed Buffer
Communication
Description
Setting range
Select whether to use the fixed buffer for connection with the connected device for
• Send
sending or receiving.
• Receive
Select the communication method for communications using a fixed buffer.
Select whether to disable or enable the pairing open for communications using a
Pairing Open
fixed buffer.
(
130
Page 194, Section
14.7) Select "No Confirm" to send data by broadcast communications during "No
Procedure" communications using a fixed buffer.
• No Procedure
• Disable
• Enable
Page 139, Section 12.7)
Select whether or not to use the alive check function. (
Existence Confirmation
• Procedure Exist
• No Confirm
• Confirm
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.5.1
Parameter setting when using an interrupt program
Configure the parameter setting on a programming tool to start up an interrupt program.
CPU module
E71
Connection No.1
Connection No.2
Setting
of (2)
Control
number
interrupt
(SI) No.
0
to
15
Connection No.16
<Program>
Setting
of (1)
Interrupt
pointer
(Ixx)
Ixx
Z.BUFRCVS
50
to
255
12
(1) Interrupt pointer setting
The following is a setting example.
Project window
[Parameter]
PLC Side
Interrupt Pointer Start No.
Description
Set the start number of the interrupt pointer used in a
program.
button
Setting range
50 to 255
Interrupt Pointer Count
Set the number of interrupt pointers used in a program.
1 to 16
Start I/O No.
Set the start I/O number of an E71.
0000H to 0FE0H
Intelligent Module
Side
[PLC System]
Among maximum 16 interrupt (SI) numbers (control numbers
Start SI No.
on the Ethernet module side) to be set in the interrupt
0 to 15
program, set the smallest numbers 0 to 15.
131
12.5 Parameter Setting
12.5.1 Parameter setting when using an interrupt program
Item
[PLC Parameter]
(2) Interrupt settings
The following is a setting example.
Project window
[Parameter]
[Network Parameter]
[Ethernet/CC IE Field]
"Ethernet" under "Network Type".
Item
button
Description
Input Format
The input format of each data is decimal number only.
Device Code
Select a device code. Select "Fixed Buffer" in this setting.
Channel No./Connection No.
Interrupt (SI) No.
*1
Select
Set the connection number of the fixed buffer to trigger the
interrupt program.
Set the interrupt control number for the E71 for when an interrupt
request is issued from the E71 to the CPU module.*1
Setting range

Fixed Buffer
1 to 16
0 to 15
Do not set the same interrupt (SI) numbers as those to be set for an interrupt of other communications using a fixed
buffer or the RECV instruction.
Interrupt (SI) numbers can be assigned by the user to receive up to 16 communications using a fixed buffer and
communications using the RECV instruction in an interrupt program. The user must manage the interrupt (SI) numbers
assigned for receiving data.
132
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.6
Data Format
Communication data consists of a header and application data.
12.6.1
Header
The header for TCP/IP or UDP/IP is used. Because an E71 automatically adds and deletes a header, the user setting
is not required.
12
(1) Detailed header sizes
(a) TCP/IP
Ethernet
(14 bytes)
IP
(20 bytes)
TCP
(20 bytes)
(b) UDP/IP
Ethernet
(14 bytes)
UDP
(8 bytes)
Application data
12.6 Data Format
12.6.1 Header
12.6.2
IP
(20 bytes)
This section describes the application data configuration.
(1) Procedure exists
In the application data for communications with the "Procedure Exist" control method, the following data code is
expressed in a binary code or an ASCII code. To switch between a binary code and an ASCII code, use the
Ethernet operation setting.
Project window
[Parameter]
"Ethernet" under "Network Type".
[Network Parameter]
[Ethernet/CC IE Field]
Select
button
133
(a) Format
• Communications using a binary code
Application data area
(command message)
Communication
request source
2 bytes
2 bytes
Subheader
Data length
setting
L
H
L
H
Maximum of
1017 words
Text
(command)
Communication
request destination
Subheader
End code
1 byte
1 byte
Application data area
(Response)
• Communications using an ASCII code
Application data area
(command message)
Communication
request source
4 bytes
4 bytes
Subheader
Data length
setting
H - - L
H Communication
request destination
-
L
Maximum of
1016 words
Text
(command)
Subheader
H
L
2 bytes
End code
H
2 bytes
Application data area
(Response)
134
L
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(b) Subheader
Because an E71 automatically adds and deletes a header, the user setting is not required.
Command
to
b7
0
1
1
Communications using
a binary code
0
0
0
"6"
Communications using
an ASCII code
1
6H
0
1
Response
to
1
0
1
b0
0
0
E0H
Subheader
Subheader
to
1
b7
60H 00H
b7
0
0
b0
0
0
0
"0"
0
b0
b7
0
1
0H
36H 30H 30H 30H
Subheader
0
12
b0
to
1
"E"
0
1
EH
45H
0
0
0
"0"
0
0
0H
30H
Subheader
(c) Data length setting
The following are the data sizes of a text (command).
• Communications using a binary code: Maximum of 1017 words
• Communications using an ASCII code: Maximum of 508 words
12.6 Data Format
12.6.2 Application data
135
(d) Text (command)
The following is the format of a command/response.
• Communications using a binary code
Command format
Maximum of 1017 words
60H
00H (L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Subheader
Data specifying/
storing device for sending/
receiving instructions
Data length
setting
n
n+1
(H)
(L)
n+2
(H)
(L)
n+3
(H)
(L)
n + setting data length
(H)
(L)
Send/
receive data
1 word (2 bytes)
• Communications using an ASCII code
Command format
Maximum of 1016 words
36H30H30H30H
(H) to (L)
(H) to (L)
(H) to (L)
Subheader
Data specifying/
storing device for sending/
receiving instructions
n
Send/
receive data
ASCII-binary conversion
Data length
setting
n+1
(H)
(L)
n+2
(H)
(L)
n + setting data length
(H)
(L)
Maximum of 508 words
1 word (2 bytes)
136
(H) to (L)
(H)
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(e) End codes
An error code is stored in the end code added to a response. For the error codes, refer to the error code list.
(
Page 268, Section 16.7.1) End codes are stored in the complete status area (in the control data) of the
BUFSND and BUFRCV instructions, as well as the communication status storage area of the buffer memory.
If an error code related to MC protocol communications or communications using a random access buffer is stored during
communications using a fixed buffer, it may be caused by the following.
Cause
Action
The data length value specified in the application data of the
Specify the actual text data size for the data length in the
message sent from a connected device to the E71 is different
application data.
from the actual text data size.
(Refer to "Remark" in this page.)
The subheader of the message sent from a connected
12
Correct the subheader specified in the application data.
device to the E71 is incorrect.
Remark
Depending on the restrictions of the buffers of the own station and destination station, data may be divided for
communications. Data received separately is restored (reassembled) by the E71 for communications. The received data is
restored (reassembled) based on the data length in the communication data. The E71 performs the following processes if
data in the communication data is incorrect.
● If the data length specified immediately after the subheader is smaller than the amount of text data received
1) The data immediately after the text data equivalent to the data length specified immediately after the subheader is
regarded as the next message.
2) Because the header of each message is a subheader, an E71 processes data according to the code in the subheader.
3) If the subheader contains a code that is not recognized by an E71, the E71 sends a response notifying about an
abnormal end to the connected device.
Data processed by the E71
(1st data)
Subheader
12.6 Data Format
12.6.2 Application data
Data sent from the connected device
(2nd data)
Subheader
This section is processed
as a subheader.
In the figure above, the E71 returns a response containing a code obtained by changing the most significant bit of the
code processed as a subheader to 1.
For example, if the subheader of a command is 65H, the subheader of the response is E5H.
● If the data length specified immediately after the subheader is larger than the amount of text data received
1) The E71 waits for the remaining data.
2) When the remaining data is received within the response monitoring timer value, the E71 processes data according
to the code in the subheader.
3)
If the remaining data could not be received within the response monitoring timer value, the E71 performs the
following processes.
• Sends the ABORT (RST) instruction to the connected device and closes the line.
• Notifies the CPU module that an open error has occurred by turning on Open abnormal detection signal (X18)
• Stores the error code in the open error code storage area. (The error code is not stored in the error log area.)
137
(2) No procedure
In the application data for communications in the "No Procedure" control method, the following data code is
expressed in a binary code. Communications are performed using a binary code regardless of the
communication data code setting.
Text (command)
Maximum of 2046 bytes
In communications in the "No Procedure" control method, a subheader or data length setting is not added unlike the
"Procedure Exist" control method; therefore, all data are handled as a valid text. In addition, the E71 turns on Fixed buffer
reception status signal after storing the size of the received message (packet) in the data length storage area. It is
recommended to set a checking method. For example, include data length and a data type code in the application data of a
message so that the number of bytes and data type of the application data can be identified on the receiving side.
138
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.7
Pairing Open
Pairing open is an opening method that connects the own station with the connected device using only one port by
pairing the receive and send connections for communications using a fixed buffer.
12.7.1
Applications
Enabling the pairing open allows data communications to be performed with two connections by performing the open
12
process for one port. MC protocol communications and communications using a random access buffer can be also
performed using paring-opened connections.
E71
(TCP/IP or UDP/IP communications)
Send data
Connection No.1 Fixed buffer (to receive data)
Connected device
Port
Receive data
Connection No.2 Fixed buffer (to send data)
● Connected devices where communications can be performed using the pairing open method are those in Ethernet where
an E71 is connected and those connected using the router relay function.
● The open/close processes in the receive connection where the pairing open has been enabled automatically perform the
open/close processes in the next connection (send connection).
12.7 Pairing Open
12.7.1 Applications
139
12.7.2
Parameter setting
The following is the pairing open setting.
Item
Description
Setting range
Set "Pairing Open" of the receive connection to "Enable". The next connection is
Pairing Open
automatically set as a send connection.*1
*1

When "Enable" has been set in "Pairing Open" for a send connection, the following window appears.
When the
button is selected, the applicable connection becomes a receive connection, and the next
connection is automatically set as a send connection. (When "Enable" has already been set in "Pairing Open", the
setting is overwritten.)
Because the fixed buffer of the connection with the connected device (for receiving) and the fixed buffer of the next
connection (for sending) are paired, set connection numbers 1 to 7 and 9 to 15 as receive connections. (Connection
numbers 8 and 16 cannot be set.)
140
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.8
Broadcast Communications
Broadcast communications mean that the same data is sent to all E71-connected stations in the same Ethernet
network and to the connected devices without specifying destinations. Broadcast communications can be performed
when the following conditions are met.
• When UDP/IP protocol is used
• When "No Procedure" communications using a fixed buffer or data communications using the predefined
protocol are performed
12
● When connected devices in the same Ethernet network do not need to receive communication messages by broadcast
communications, a discarding process is required.
● The user needs to determine the port numbers dedicated for data sending/receiving for broadcast communications.
● Sending/receiving procedures to perform the broadcast communications in communications using the predefined
protocol are same as that in communications using a fixed buffer except for setting "Predefined protocol" under "Fixed
Buffer Communication" of the open setting.
12.8.1
Sending/receiving procedures
(1) Sending procedure
To send data by broadcast communications, set the IP addresses of the connected devices where the E71 sends
data to FFFFFFFFH and perform the open process. The E71 sets all the host address bits to 1 and sends data
(2) Receiving procedure
To receive data as data for broadcast communications, set the IP addresses of the connected devices that send
data to the E71 to FFFFFFFFH and the port numbers to FFFFH and perform the open process.
141
12.8 Broadcast Communications
12.8.1 Sending/receiving procedures
over the Ethernet network.
Remark
The following is the outline of the internal process of an E71 when data is received in the "No Procedure" control method or
by broadcast communications. (The values specified in the buffer memory addresses 0H, 1H and 28H to 5FH are used for the
IP addresses and port numbers of the E71 in the own station as well as those of connected devices.)
Data received
Is the IP address of the
own station E71 the same as that of the
receive data request destination?
NO
Is the network
address (subnet address)
in the IP address of the own station
E71 the same as the network address (subnet
address) of the received data?
Are all the bits of the host address
of the received data 1?
YES
NO
YES
Is Destination
IP address FFFFFFFFH?
(Simultaneous Broadcast)
NO*1
YES
(Simultaneous Broadcast)
Is Destination
IP address the same as that of the receive
data request source?
NO
YES
Is Destination Port No. FFFFH?
NO
YES
(Simultaneous Broadcast)
Is Destination
Port No. the same as that of the receive
data request source?
NO
YES
The application data of the received data is stored
in the fixed buffer.
Fixed buffer reception status signal (address:
5005H) turns on.)
*1
142
The received data is ignored (discarded)
because it has not been sent to the own station.
When all the bits of the area expressing the host address of the IP address of the receive data request destination are 1,
proceed to "YES".
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.8.2
Parameter setting
The following is the parameter setting for broadcast communications.
(1) When sending data
The following is the parameter setting for data sending.
12
Item
Description
Setting range
Select "UDP".

Fixed Buffer
Select "Send".

Fixed Buffer Communication
Select "No Procedure".

Existence Confirmation
Select "No Confirm".

Destination IP Address
Set FFFFFFFFH.

12.8 Broadcast Communications
12.8.2 Parameter setting
Protocol
143
(2) When receiving data
The following is the parameter setting for data receiving.
Item
Description
Setting range
Protocol
Select "UDP".

Fixed Buffer
Select "Receive".

Fixed Buffer Communication
Select "No Procedure".

Existence Confirmation
Select "No Confirm".

Destination IP Address
Set FFFFFFFFH.

Destination Port No.
Set FFFFH.

144
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
12.8.3
Precautions
This section describes the precautions for broadcast communications.
(1) Port number
To perform broadcast communications, the user needs to determine the port numbers dedicated for data
sending/receiving for broadcast communications and specify these port numbers.
(2) Size of send/receive data per sending/receiving
A maximum of 2046 bytes of data in the application data can be processed per sending/receiving. To send data
12
with a size exceeding 2047 bytes, divide the data into smaller chunks at the send source.
Remark
An E71 temporarily stores a subsequent receive data in its internal buffer for the operating system until the current receive
process is completed. If data with a size exceeding the capacity of the internal buffer (approximately 40KB) is received by
broadcast communications, the data is discarded. In communications using a fixed buffer in the "Procedure Exist" control
method, the E71 sends a command message to the connected device, waits for a response message, then sends the next
command message. Therefore, the user need not take account of the above-mentioned internal buffer for the operating
system.
12.8 Broadcast Communications
12.8.3 Precautions
145
12.9
Example of Communications Using a Fixed Buffer
This section describes an example of communications using a fixed buffer in the "Procedure Exist" control method
between an E71 and the connected device.
12.9.1
System configuration
The following system configuration is used for explanation purpose.
LCPU-1
(10.97.85.222)
LCPU-2
(10.97.85.223)
Ethernet
12.9.2
Parameter setting
This section describes a parameter setting example.
(1) Sending side (LCPU-1 side)
The following is an example of the parameter settings of the sending side (LCPU-1 side).
(a) Basic setting
The following is an example of the basic setting.
146
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(b) Ethernet operation setting
The following is an example of the Ethernet operation setting.
12
(c) Open setting
The following is an example of the open setting.
12.9 Example of Communications Using a Fixed Buffer
12.9.2 Parameter setting
147
(2) Receiving side (LCPU-2 side)
The following is an example of the parameter settings of the receiving side (LCPU-2 side).
(a) Basic setting
The following is an example of the basic setting.
(b) Ethernet operation setting
The following is an example of the Ethernet operation setting.
148
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(c) Open setting
The following is an example of the open setting.
12
12.9 Example of Communications Using a Fixed Buffer
12.9.2 Parameter setting
149
12.9.3
Program
(1) Sample program procedures
This section describes the procedures for a sample program.
(a) Sending side (LCPU-1 side)
The following describes how communications are processed on the sending side (LCPU-1 side).
1.
Set each parameter on a programming tool and write the set parameters to the CPU module. Then
reset the CPU module and check that the initial process is completed.
2.
3.
Perform the open process (Active open) of the connection number 1.
Perform communications using a fixed buffer from the CPU module using the BUFSND
instruction.
4.
After the data is sent, perform the close process of the connection number 1.
(b) Receiving side (LCPU-2 side)
The following describes how communications are processed on the receiving side (LCPU-2 side).
1.
Set each parameter on a programming tool and write the set parameters to the CPU module. Then
reset the CPU module and check that the initial process is completed. When the initial process is
normally completed, the connection number 1 waits for an Active open request from the
connected device.
2.
3.
Perform communications using a fixed buffer from the connected device.
Use the BUFRCV instruction to read the data that have been received by the corresponding fixed
buffer data area of the E71 into the CPU module.
150
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(2) Sample program
(a) Program on the sending side (LCPU-1 side)
The following is a program on the sending side (LCPU-1 side).
<<Open process program>>
12
12.9 Example of Communications Using a Fixed Buffer
12.9.3 Program
<<Fixed buffer No.1 send program>>
Process upon completion
Process upon abnormal end
151
<<Close processing program>>
152
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
(b) Receiving side (LCPU-2 side)
The following is a program on the receiving side (LCPU-2 side).
<<Fixed buffer No.1 receive program>>
12
Process upon completion
Process upon abnormal end
● Secure sufficient device areas according to the maximum length of data sent from the send source to prevent the device
areas used for other purposes from being overwritten by the receive data.
153
12.9 Example of Communications Using a Fixed Buffer
12.9.3 Program
● To receive data at shorter intervals than the scan time of the CPU module, add the normally closed contact for the
completion device (M500) of the BUFRCV instruction to the execution conditions of the BUFRCV instruction as shown in
the above program. When there is no normally closed contact for the completion device (M500), the receive direction
(M5001) of the BUFRCV instruction is not turned off and on and the BUFRCV instruction may not be executed.
CHAPTER 13 COMMUNICATIONS USING A
RANDOM ACCESS BUFFER
This section describes communications using a random access buffer.
13.1
Applications
In communications using a random access buffer, data can be freely read from and written to any connected device
(not including an E71). A random access buffer is used as a common buffer area for all the connected devices in the
Ethernet network.
E71
Connected
device
Writing
Reading
Writing
Connected
device
Writing
Random
access
buffer
Reading
Reading
Writing
Reading
Writing
Connected
device
Connected
device
Reading
Connected
device
Data communications (sending/receiving) by e-mail using a CPU module cannot be used together with communications
using a random access buffer. Only one of the functions can be used at one time. (The e-mail sending function using the E71
programmable controller CPU monitoring function can be used together with communications using a random access
buffer.)
154
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
13.2
Communication Structure
This section describes the structure of communications using a random access buffer.
(1) Data flow
The data flow in communications using a random access buffer is as follows. The FROM/TO instructions or
intelligent function module devices are used to access a random access buffer from a CPU module.
E71
Writing data
CPU module
Random
access
buffer
Read request
Reading data
Connected
device
13
Using the FROM/TO
instructions or an
intelligent function module device
● Communications can be performed only with connected devices where communications using a fixed buffer in the
"Procedure Exist" control method are set using the connection with Open completion signal of an E71 on.
● Communications are performed asynchronously with the program. If synchronization is required, use communications
using a fixed buffer.
13.2 Communication Structure
(2) Connected devices where data communications can be performed
Data communications can be performed with the following connected devices:
• Devices in Ethernet where an E71 is connected
• Devices connected using the router relay function
155
13.2.1
How data is read from a connected device
The following figure shows how an E71 sends data in response to a read request sent from a connected device.
CPU module
2
E71
Writing using
the TO instruction
1
Read request (command)
ACK (TCP only)
Random access
buffer
3
Response/data read
ACK (TCP only)
1
Write data in the random access buffer of the E71 using the TO instruction.
2
Asynchronously with the process
1
Connected device
above, the connected device sends a read request to the E71. (The
E71 side: command receiving)
3
Upon receiving the read request from the connected device, the E71 sends the data written in the random
access buffer to the connected device that sent the read request. (The E71 side: response sending)
13.2.2
How a connected device writes data
The following figure shows how a connected device writes data to the E71 random access buffer.
1
CPU module
3
E71
Reading using
the FROM instruction
Writing data (command)
ACK (TCP only)
Random access
buffer
2
Response
ACK (TCP only)
1
Connected device
The connected device writes data to the random access buffer of the E71. (The E71 side: command
receiving)
2
The E71 processes the write request from the connected device and returns the writing result to the
connected device that sent the write request. (The E71 side: response sending)
3
Asynchronously with the processes
using the FROM instruction.
156
1
and
2
above, the data written in the random access buffer is read
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
13.3
Parameter Setting
Set the following parameters to perform communications using a random access buffer.
• Basic setting (
Page 66, Section 7.1.2)
• Ethernet operation setting (
• Open setting (
Page 67, Section 7.1.3)
Page 69, Section 7.1.4)
13
Item
Description
Select the communication method for communications using a fixed buffer. Select
Communication
"Procedure Exist" for communications using a random access buffer.
Setting range
Procedure Exist
13.3 Parameter Setting
Fixed Buffer
157
13.4
Data Format
Communication data consists of a header and application data.
13.4.1
Header
The header for TCP/IP or UDP/IP is used. Because an E71 automatically adds and deletes a header, the user setting
is not required.
(1) Detailed header sizes
(a) TCP/IP
Ethernet
(14 bytes)
IP
(20 bytes)
TCP
(20 bytes)
(b) UDP/IP
Ethernet
(14 bytes)
158
IP
(20 bytes)
UDP
(8 bytes)
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
13.4.2
Application data
In the application data for communications with the "Procedure Exist" control method, the following data code is
expressed in a binary code or an ASCII code. To switch between a binary code and an ASCII code, use the Ethernet
operation setting.
Project window
[Parameter]
[Network Parameter]
[Ethernet/CC IE Field]
"Ethernet" under "Network Type".
Select
button
(1) Format
• Communications using a binary code
13
Application data area
(command message data)
2 bytes
Communication
request
source
Subheader
H
00H
2 bytes
Start address
L
H
2 bytes
Data length
setting
L
H
Maximum of
1017 words
Text
(command)
(none at read
request)
Communication
request
destination
Subheader
Text
(response)
(none at write
request)
1 byte
Maximum of
1017 words
1 byte
Application data area
(response)
• Communications using an ASCII code
Application data area
(command message)
4 bytes
Communication
request source
Communication
request destination
Subheader
4 bytes
Start address
H L 30H 30H H -
-
Maximum of
1016 words
4 bytes
L
Text
(command)
(none at read
request)
L
Data length
setting
H -
-
Subheader
H
L
2 bytes
End code
H
L
2 bytes
Text
(response)
(none at write
request)
Maximum of
1016 words
Application data area
(response)
159
13.4 Data Format
13.4.2 Application data
End code
(2) Subheader
Because an E71 automatically adds and deletes a header, the user setting is not required.
b7
b6 b5
1
1
b4
b3
b2
b1 b0
0
0
0
0
00H
1
Only for command (none at response)
Command/response type
(When communications are performed using the random access
buffer, this format is used.)
For data reading: 61H
For data writing: 62H
Command/response flag
For command: 0
For response: 1
(a) When reading
Command (from the connected device to the E71)
b7
b0
to
0
1
0
1
1
1
1
0
1
0
Subheader
Subheader
to
1
"6"
0
1
6H
0
0
"1"
36H 31H 30H 30H
Subheader
160
0
E1H
b7
Communications using
an ASCII code
0
61H 00H
Communications using
a binary code
0
0
Response (from the E71 to the connected device)
b7
b0
to
0
1H
b0
b7
1
1
0
0
0
0
b0
to
1
"E"
0
1
EH
45H
1
0
"1"
31H
Subheader
1H
1
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
(3) Start address
Use a logical address to set the start address of a random access buffer that reads/writes data.
(
Page 167, Section 13.6)
(a) Communications using a binary code
Specify the start address using a binary value.
L
H
2 bytes
(b) Communications using an ASCII code
13
Specify the start address using an ASCII code value expressed in hexadecimal.
H
-
L
-
4 bytes
(4) Data length setting
Set the number of words of the read/written data in the random access buffer range.
(a) Communications using a binary code
Specify the number of words using a binary value. (Maximum of 1017 words)
13.4 Data Format
13.4.2 Application data
L
H
2 bytes
(b) Communications using an ASCII code
Specify the number of words using an ASCII code value expressed in hexadecimal. (Maximum of 508 words)
H
-
-
L
4 bytes
161
(5) Text
Text is a data written to and read from a random access buffer.
(a) Communications using a binary code
Data length (maximum of 1017 words)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
Random access
buffer
Specified
address
n
(H)
(L)
n+1
(H)
(L)
n+2
(H)
(L)
(H)
(L)
n + set number of
words to be read
1 word (2 bytes)
(b) Communications using an ASCII code
Data length 2 (maximum of 1016 words)
(H) to (L) (H) to (L)
(H) to (L)
ASCII-binary conversion
Random access
buffer
Specified
address
n
(H)
(L)
n+1
(H)
(L)
(H)
(L)
n + set number of
words to be read
(Maximum of 508 words)
Ex.
(H)
(L)
n
12H
34H
n+1
56H
78H
31H
(H)
162
32H
to
33H
34H
35H
(L)
(H)
36H
37H
to
38H
(L)
(H)
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
(6) End code
An error code is stored in the end code added to a response. For the error codes, refer to the error code list.
(
Page 268, Section 16.7.1) End codes are stored in the communication status storage area of the buffer
memory.
13.4.3
Examples of command and response formats
This section describes examples of command and response formats.
(1) Writing data to a random access buffer upon a write request from a connected
device
13
(a) Communications using a binary code
• Command format (from the connected device to the E71)
Subheader Start address Data length
62H
00H
Text (10 words)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
(H)
(L)
00H
00H
0AH
00H
34H
12H
78H
56H
BCH 9AH
(H)
(L)
Logical address
(L)
(H)
BCH 9AH
Random access buffer
2680H( 9856)
12H
34H
0H( 0)
2681H( 9857)
56H
78H
1H( 1)
2682H( 9858)
9AH
BCH
2H( 2)
2689H( 9865)
9AH
BCH
9H( 9)
13.4 Data Format
13.4.3 Examples of command and response formats
Physical address (H)
(10 words)
3E7FH(15999)
17FFH(6143)
• Response format (from the E71 to the connected device)
Subheader
End code
E2H
00H
163
(b) Communications using an ASCII code
• Command format (from the connected device to the E71)
Start address
Subheader
(H)
-
-
Data length
(L)
(H)
-
-
(L)
00H
00H
00H
41H
36H
32H
30H
30H
00H
00H
00H
00H
(H)
-
-
(L)
(H)
-
-
(L)
(H)
-
-
(L)
(H)
-
-
(L)
31H
32H
33H
34H
35H
36H
37H
38H
39H
41H
42H
43H
39H
41H
42H
43H
Text (20 words)
ASCII-binary conversion
Random access buffer
Physical address (H)
(L)
Logical address
2680H( 9856)
12H
34H
0H( 0)
2681H( 9857)
56H
78H
1H( 1)
2682H( 9858)
9AH
BCH
2H( 2)
2689H( 9865)
9AH
BCH
9H( 9)
(10 words)
3E7FH(15999)
17FFH(6143)
• Response format (from the E71 to the connected device)
Subheader
45H
164
32H
End code
30H
30H
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
(2) Reading data from a random access buffer upon a read request from a
connected device
(a) Communications using a binary code
• Command format (from the connected device to the E71)
Subheader Start address Data length
61H
00H
(L)
(H)
(L)
(H)
14H
00H
0AH
00H
• Response format (from the E71 to the connected device)
Subheader
End code
E1H
00H
13
Text (10 words)
(L)
(H)
(L)
(H)
(L)
34H
12H
78H
56H
BCH 9AH
(H)
(L)
(H)
BCH 9AH
Random access buffer
Physical address (H)
(L)
2680H( 9856)
Logical address
0H( 0)
12H
34H
14H( 20)
2695H( 9877)
56H
78H
15H( 21)
2696H( 9878)
9AH
BCH
16H( 22)
269DH( 9885)
9AH
BCH
1DH( 29)
13.4 Data Format
13.4.3 Examples of command and response formats
2694H( 9876)
(10 words)
3E7FH(15999)
17FFH(6143)
165
(b) Communications using an ASCII code
• Command format (from the connected device to the E71)
Start address
Subheader
36H
31H
30H
30H
Data length
(H)
-
-
(L)
(H)
-
-
(L)
00H
00H
31H
34H
00H
00H
00H
41H
• Command format (from the connected device to the E71)
Subheader
End code
45H
31H
30H
30H
(H)
-
-
(L)
(H)
-
-
(L)
(H)
-
-
(L)
(H)
-
-
(L)
31H
32H
33H
34H
35H
36H
37H
38H
39H
41H
42H
43H
39H
41H
42H
43H
Text (20 words)
ASCII-binary conversion
Random access buffer
Physical address (H)
(L)
2680H( 9856)
Logical address
0H( 0)
2694H( 9876)
12H
34H
14H( 20)
2695H( 9877)
56H
78H
15H( 21)
2696H( 9878)
9AH
BCH
16H( 22)
269DH( 9885) 9AH
BCH
1DH( 29)
(10 words)
3E7FH(15999)
166
17FFH(6143)
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
13.5
Precautions when Creating Programs
This section describes the precautions when creating programs for communications using a random access buffer.
(1) Completion of the initial and open processes
The initial process and the connection open process need to be completed.
(2) Send request from a CPU module
A CPU module cannot issue send requests. In addition, reception completion in a CPU module is not confirmed.
When it is necessary to synchronize data sending/receiving between the CPU module and the connected device,
use communications using a fixed buffer.
13
(3) Random access buffer address
The address specified by the connected device and the address specified using the FROM/TO instructions are
different. For details, refer to the physical and logical addresses of a random access buffer. (
Page 167,
Section 13.6)
13.6
Physical and Logical Addresses of a Random Access
Buffer
This section describes the start address of the E71 random access buffer (without battery backup), which is specified
Note that when designating the start address of a random access buffer, the address specified by a connected device
is different from that specified using the FROM/TO instructions.
• Physical address: Address specified with the FROM/TO instructions of a program
• Logical address: Address specified by a connected device as the start address in the command
Physical address
Buffer memory areas
680H( 1664)
Fixed buffer
267FH( 9855)
Logical address
0H( 0)
2680H( 9856)
Random access
buffer
3E7FH(15999)
17FFH(6143)
167
13.5 Precautions when Creating Programs
in commands.
13.7
Example of Communications Using a Random Access
Buffer
The following figure shows an example of a write operation from a connected device.
CPU module
Device memory
E71
Random access buffer
11710
R20000
Data received
R20009
Data received
11719
11720
1
Receive process program
1
The receive completion flag is provided at the end of the received data.
2
The receive completion flag is monitored.
3
168
Connected
device
1
Receive completion flag
When the receive completion flag turns on, the data is transmitted from the random access buffer to the CPU
module.
CHAPTER 14 OTHER FUNCTIONS
CHAPTER 14 OTHER FUNCTIONS
This chapter describes basic functions of the E71 other than those described in the preceding chapters.
14.1
Router Relay Function
This section describes the router relay function.
14.1.1
Applications
This function allows the E71 to communicate with connected devices on other Ethernet networks via a router and
gateway. This function does not allow the E71 to operate as a router. One default router and up to eight routers can be
14
set.
14.1.2
Parameter settings
Configure the settings in the following window.
[Parameter]
"Ethernet" under "Network Type".
[Network Parameter]
[Ethernet/CC IE Field]
Select
button
169
14.1 Router Relay Function
14.1.1 Applications
Project window
Item
Description
Setting range
Router Relay Function
Select whether to use the router relay function.
Not Used/Use
Subnet Mask Pattern
Refer to (1) in this section.
C0000000H to FFFFFFFCH
Default Router IP Address
Refer to (2) in this section.
Input Format
Select the input format of router information.
Router
Information
Sub-net Address
Refer to (3) (a) in this section.
Router IP Address
Refer to (3) (b) in this section.
A value other than 00000000H and
FFFFFFFFH
DEC/HEX
A value other than 00000000H and
FFFFFFFFH
A value other than 00000000H and
FFFFFFFFH
(1) Subnet mask pattern
Set the subnet mask. (Consult with the network administrator for the setting.) When not using the subnet mask,
set any of the following values according to the class.
Class
Mask value
Class A
FF000000H
Class B
FFFF0000H
Class C
FFFFFF00H
(a) Setting example
The following shows a Class B setting example.
Ex. Class B
Network address
IP address
81H
05H
2FH
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
Subnet mask
FFH
FFH
FCH
00H
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
Subnet address
IP address
Host address
81H
05H
2FH
01H
1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
● All devices on the same subnetwork must have the common subnet mask.
● When not managed by the subnetwork, the connected devices need not have subnet masks. (Set the network address of
the corresponding class.)
170
CHAPTER 14 OTHER FUNCTIONS
(2) Default router IP address
Set the IP address of the router (default router) when the E71 communicates with the connected devices on other
Ethernet networks via a router other than the one specified in the router information. Set the value that satisfies
the following conditions.
• Condition 1: The IP address class is any of A, B, and C.
• Condition 2: The subnet address of the default router is the same as that of the E71 on the own station.
• Condition 3: The host address bits are not all "0" or all "1".
If the corresponding subnet address does not exist in the router information when the connection is opened or data
communications are performed, communications are performed via the default router.
(3) Router information
14
(a) Subnet address
Set the network
address*1
or subnet
address*2
of the connected device when the E71 communicates with the
connected devices on other Ethernet networks via a router other than the default router. Set the value that
satisfies the following conditions.
• Condition 1: The IP address class is any of A, B, and C.
• Condition 2: The host address bits are all "0".
*1
*2
Own station E71
Class B
IP address: 81052F01H(129.5.47.1)
Subnet mask: FFFFFC00H (255.255.252.0)
Ethernet 4
Router 2
Router 1
Ethernet 1
Ethernet 2
Router 3
Ethernet 3
Setting example 1
Setting example 2
Setting example 3
Connected device 1
Class B
IP address: 81044001H
(129.4.64.1)
Connected device 2
Class A
IP address: 71044001H
(113.4.64.1)
Connected device 3
Class B
IP address: 81052902H
(129.5.41.2)
171
14.1 Router Relay Function
14.1.2 Parameter settings
If the class (network address) of the E71 on the own station differs from that of the connected device, set the network
address of the connected device.
If the class (network address) of the E71 on the own station is the same as that of the connected device, set the subnet
address of the connected device.
Ex. When the network addresses differ between the E71 on the own station and the connected device
Network address
81H
05H
2FH
01H
Own station E71
IP address (Class B) 1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
81H
04H
40H
01H
Connected device 1
IP address (Class B) 1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Set the network address of
the connected device 1.
Network address
Subnet address
81H
04H
00H
00H
setting value 1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Ex. When the classes differ between the E71 on the own station and the connected device
Network address
81H
05H
2FH
01H
Own station E71
IP address (Class B) 1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
71H
04H
40H
01H
Connected device 2
IP address (Class A) 0 1 1 1 0 0 0 1 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Network address
Subnet address setting value
Set the network address of
the connected device 2.
71H
00H
00H
00H
0 1 1 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Ex. When the network address of the E71 on the own station is the same as that of the connected device
Network address
81H
05H
2FH
01H
Own station E71
IP address (Class B) 1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 1 1 1 0 0 0 0 0 0 0 1
Subnet mask
FFH
FCH
00H
FFH
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0
81H
05H
29H
02H
Connected device 3
IP address (Class B) 1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 0 0 1 0 0 0 0 0 0 1 0
Set the subnet address of
the connected device 3.
Subnet address
00H
81H
05H
28H
Subnet address
setting value 1 0 0 0 0 0 0 1 0 0 0 0 0 1 0 1 0 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0
172
CHAPTER 14 OTHER FUNCTIONS
(b) Router IP address
Set the IP addresses of the routers when the E71 communicates with the connected devices on other Ethernet
networks via a router other than the default router. Set the value that satisfies the following conditions.
• Condition 1: The IP address class is any of A, B, and C.
• Condition 2: The subnet address of the router is the same as that of the E71 on the own station.
• Condition 3: The host address bits are not all "0" or all "1".
● When the E71 communicates with the connected devices via a router in Passive open status, communications can be
performed without using the router relay function.
● The router relay function is not needed in a system that uses the Proxy router.
14
14.1 Router Relay Function
14.1.2 Parameter settings
173
14.2
Communications Using an Auto-open UDP Port
This section describes communications using the auto-open UDP port.
14.2.1
Application
The auto-open UDP port is a UDP/IP port that automatically opens and closes at the following timing. Using this port
makes the E71 ready for communications upon completion of an initial process, thus enabling communications without
using any programs regardless of the open status of connection numbers 1 to 16.
(1) Open and close timing
The port automatically opens according to the registered parameter settings upon completion of the initial
process of the E71. In addition, it automatically closes when the E71-connected station is powered off or reset.
● The E71 enables communications using an auto-open UDP port after the initial process is normally completed, and the
E71 on the own station waits for communication requests to itself (auto open).
● The E71 accepts requests from anywhere as long as they are addressed to the E71 itself.
● When a communication request is accepted from the connected device, the corresponding port number is occupied until
the process is completed. Even if the next communication request is accepted during this time, the communication
process will be waited.
● To change the auto-open UDP port number, a reinitialization process is required. (
174
Page 315, Appendix 4.2)
CHAPTER 14 OTHER FUNCTIONS
14.3
IP Filter Function
This section describes the IP filter function.
This function is available only in the E71 with the serial number (first five digits) of "18072" or later.
14.3.1
Application
This function identifies the IP address of the access source, and prevents unauthorized access performed by IP
address specification.
The IP address of the connected device to be allowed or denied access is set in the buffer memory, and access from
connected devices is restricted.
Use of this function is recommended when using the E71 in an environment connected to a LAN line.
Ethernet
14
Access permitted
External device
IP address: 192.168.1.2
E71
Access permitted
External device
IP address: 192.168.1.3
14.3 IP Filter Function
14.3.1 Application
Access prohibited
External device
IP address: 192.168.1.5
The IP filter function is one method of preventing unauthorized access (such as program or data destruction) from external
devices. However, this function does not guarantee prevention of all unauthorized access. To have the programmable
controller system fully secured against unauthorized access from the external devices, take additional measures. Mitsubishi
Electric Corporation does not hold any responsibility for any system problems caused by unauthorized access.
The following are examples of measures against unauthorized access.
• Install a firewall.
• Install a personal computer as a relay station and control the relay of communication data using an application
program.
• Install an external device for which the access rights can be controlled as a relay station (Contact the network
provider or equipment dealer for details on the external devices for which access rights can be controlled.)
175
14.3.2
Setting method
This section describes the setting method of IP filter.
(1) Setting procedure
The IP filter settings become enabled after the reinitialization process.
The following is a procedure for IP filter settings.
1.
2.
Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
Terminate all data communications with the connected devices and perform a close process on all
connections.
3.
4.
5.
Write the settings in the buffer memory areas, IP filter settings (address: 5700H to 5721H).
Perform reinitialization process. (
Page 315, Appendix 4.2)
Confirm the normal completion of the reinitialization process with the following buffer memory
areas.
• Reinitialization specification (address: 1FH (b15)): 0H
• Initial error code (address: 69H): 0H
• When a connected device accesses the E71 before the completion of reinitialization process, the access cannot
be denied because the IP filter is not yet enabled.
• The values stored in IP filter monitoring area (address: 5722H to 5725H) are cleared when the reinitialization
process completes.
• Even if the connection is established as set with the open setting of E71 or the program, access from the
connected device is either allowed or denied following IP address settings. Therefore, if the IP address set in the
open setting of E71 is set to be denied with the IP filter settings, the IP filter function is enabled and
communication with the connected device is denied.
• When the UINI instruction is executed with the IP filter settings written in the buffer memory (address: 5700H to
5721H), IP filter settings are applied as in the case of reinitialization process by the buffer memory. When using
the UINI instruction, check the setting values in IP filter settings (address: 5700H to 5721H) before executing the
instruction.
176
CHAPTER 14 OTHER FUNCTIONS
(2) Buffer memory areas used
The following buffer memory areas are used for IP filter settings.
Address
Buffer memory name
Description
Decimal
(Hexadecimal)
Ethernet operation setting upon reinitialization process is set.
Communication data code setting (b1)
• 0H: Binary Code
• 1H: ASCII Code
TCP existence confirmation setting (b4)
• 0H: Use the Ping
• 1H: Use the KeepAlive
Send frame setting (b5)
Communication condition setting
(Ethernet Operation Setting) area
• 0H: Ethernet
31 (1FH)
• 1H: IEEE 802.3
Setting of write enable/disable at RUN time (b6)
14
• 0H: Disable
• 1H: Enable
Initial timing setting (b8)
• 0H: Do not wait for OPEN (Communications impossible at STOP time)
• 1H: Always wait for OPEN (Communications possible at STOP time)
Reinitialization specification (b15)
• 0H: Reinitialization process complete (reset by the system)
• 1H: Reinitialization process request (set by the user)
The processing results of initial process and reinitialization process are
105 (69H)
Use of IP filter settings
22272 (5700H)
stored.
• 0H: Normal completion
• Other than 0H: Abnormal end (error code)
14.3 IP Filter Function
14.3.2 Setting method
Initial error code
Set when using the IP filter function.
• 0H: Do not use (default)
• 1H: Use
Select whether to allow or deny the access from the IP addresses
IP filter function type setting
22273 (5701H)
specified in IP address setting 1 to 8.
• 0H: Allow (default)
• 1H: Deny
Set the IP address to be allowed or denied.
When specifying the IP addresses by range, set the start IP address of the
Start IP address
22274 to 22275
(5702H to 5703H)
range.
22274 (5702H): Third octet, fourth octet
22275 (5703H): First octet, second octet
• 00000000H: No setting (default)
IP address
• 00000001H to DFFFFFFEH (0.0.0.1 to 223.255.255.254)
setting 1
Set the end IP address of a range to be allowed or denied.
When not specifying by range, set 00000000H.
End IP address
22276 to 22277
22276 (5704H): Third octet, fourth octet
(5704H to 5705H)
22277 (5705H): First octet, second octet
• 00000000H: No setting/No range specification (default)
• 00000001H to DFFFFFFEH (0.0.0.1 to 223.255.255.254)
IP address setting 2 to 8
22278 to 22305
(5706H to 5721H)
The configuration is the same as IP address setting 1.
177
Address
Buffer memory name
Decimal
Description
(Hexadecimal)
The number of times an access is denied by the IP filter function.
Number of access denied by the IP
22306 to 22307
filter function
(5722H to 5723H)
• 0H: None (default)
• 1H to FFFFFFFFH (1 to 4294967295): Number of access denied (When
this value exceeds 4294967295, it returns to "1" and starts counting
again.)
The latest IP address denied by the IP filter function is stored.
IP address denied by the IP filter
22308 to 22309
function
(5724H to 5725H)
22308 (5724H): Third octet, fourth octet
22309 (5725H): First octet, second octet
• 0H: None (default)
• Other than 0H: IP address denied by the IP filter function
Remark
For example, when the IP address 192.168.3.40 is set to be allowed or denied as the start IP address in IP address setting
1, the stored values in the buffer memory will be as follows.
• 22274 (5702H): 0328H
• 22275 (5703H): C0A8H
178
CHAPTER 14 OTHER FUNCTIONS
14.3.3
Program example
The following is a program example that allows access only from the IP addresses 192.168.3.1 to 192.168.3.5. (When
the I/O signals of the E71 are X/Y00 to X/Y1F)
(1) Sample program
Set the IP filter function to "Use".
14
Set "Allow".
Set the start IP address to "192.168.3.1".
14.3 IP Filter Function
14.3.3 Program example
Set the end IP address to "192.168.3.5".
179
Process upon completion
Process upon abnormal end
IP filter function enabled
Remark
This is a sample program for communications using connection numbers 1 and 2. When using another connection number,
specify the corresponding signals and bits.
14.3.4
Precautions
• If there is a proxy server in the LAN line, deny access from the IP address of the proxy server. If it is allowed,
it will not be possible to prevent access from personal computers that access the proxy server.
• Powering off and on or resetting the CPU module will clear the IP filter settings. When the CPU module is
powered off and on or reset, set the values in the buffer memory (address: 5700H to 5721H) again and
perform the reinitialization process again.
180
CHAPTER 14 OTHER FUNCTIONS
14.4
Remote Password
The CPU module can be protected by a remote password.
A remote password is one method of preventing unauthorized access (such as program or data destruction) from external
devices. However, this function does not guarantee prevention of all unauthorized access. To have the programmable
controller system fully secured against unauthorized access from the external devices, take additional measures. Mitsubishi
Electric Corporation does not hold any responsibility for any system problems caused by unauthorized access.
The following are examples of measures against unauthorized access.
• Install a firewall.
• Install a personal computer as a relay station and control the relay of communication data using an application
program.
• Install an external device for which the access rights can be controlled as a relay station (Contact the network
provider or equipment dealer for details on the external devices for which access rights can be controlled.)
14.4.1
14
Application
This function allows or prohibits access from connected devices to the CPU module through the following modules.
This prevents remote unauthorized access to the CPU module.
• E71
• Built-in Ethernet port LCPU
• C24
14.4 Remote Password
14.4.1 Application
181
14.4.2
Remote password setting processes (unlock and lock
processes)
This section describes the processes that enable/disable access from the connected devices to the programmable
controller.
(1) Access permission process (unlock process)
To access the specified CPU module, the connected device performs a remote password unlock process for the
remote password-protected E71 on the station in direct connection (own station). The following are unlock
process methods.
• Dedicated command of the MC protocol (remote password (unlock): 1630)
• When the file transfer (FTP server) function is in use: Dedicated FTP command (password-unlock)
• Programming tool: Input of the remote password in the window
• When the Web function is in use: Input of a remote password in the window displayed on the Web browser
When the unlock process is not performed, the remote password-set E71 that has accepted a communication
request checks an entered remote password and disables access to the specified station.
All data received prior to the unlock process is treated as an error.
(2) Access process
Access to the specified station is enabled when the remote password unlock process is completed normally.
Specify the station to be accessed and access the station.
(3) Access prohibition process (lock process)
To terminate the access to the specified station, the connected device performs the remote password lock
process to disable subsequent access. The following are lock process methods.
• Dedicated command of the MC protocol (remote password (lock): 1631)
• When the file transfer (FTP server) function is in use: Dedicated FTP command (password-lock)
• Programming tool: Automatically executes the lock process.
• When the Web function is in use: Automatically performs a lock process when the Web browser is closed.
182
CHAPTER 14 OTHER FUNCTIONS
14.4.3
Remote password check procedure
This section describes the procedure of the remote password check performed by the E71.
(1) Communications in which an entered remote password is checked
When the following parameters have been set for the E71 on the LCPU station, the E71 checks a remote
password for communication requests listed below.
• When a remote password has been set in the CPU module
• When the connection where the E71 communicates with a connected device has been set as the target for
the remote password check
The E71 checks an entered remote password for a communication request addressed to the own station/another
station received from a connected device.
The E71 performs a send process upon the following send requests without checking an entered remote
password.
• Send request from the CPU module on the own station (such as communications using a fixed buffer)
• Communication request from the connected device (including the programming tool connected to the CPU
14
module on the own station) to send data to another station upon request from the CPU module
E71
LCPU
Remote password
(Own station)
Remote password
check
Path checked using
a remote password
Path not checked using
a remote password
(Another station)
14.4 Remote Password
14.4.3 Remote password check procedure
Programming tool
LCPU
Remote
password
Remote password
check
(*1)
Programming tool
E71
*1
A communication request from the connected device cannot be accepted because a remote password check has been
set. If the remote password check has not been set, the communication request is accepted, and the E71 can
communicate with the connected devices.
(2) Selecting a connection for which the remote password check is performed
A connection for which an entered remote password is checked can be selected using a parameter. (
Page
190, Section 14.4.6)
183
(3) Stations that can be accessed when the remote password check is performed
When the CPU module is protected with a remote password, the stations accessible by the connected device and
the LCPU stations that can perform the remote password unlock/lock processes are limited to those in the same
network. The following shows an example of accessible stations.
Ex. When a remote password has been set in the LCPU on the station 1-1, and the remote password check
has been set in 1) on the station 1-1
Station 1-2
1)
Station A
LCPU
E71
Ethernet
Network No.1
Station 1-1
1)
Remote
password
Remote
password
check
LCPU
E71
Station B
Programming tool
Ethernet
Station 3-2
2)
LCPU
Network No.3
Station 2-2
1)
E71
LCPU
E71
E71
Network No.2
Station 2-1
1)
LCPU
1)
E71
2)
E71
Ethernet
Station 3-1
LCPU
1)
E71
Station C
Station D
The station A is the only connected device that can perform an unlock/lock process for 1) of the station 1-1.
●: Stations that can be accessed from the connected device after the remote password unlock process
: Stations that can be accessed from the connected device without performing the remote password unlock
process
Connected
device
Target programmable controller station (request destination)
*1
(request
source)
Station 1-1
Station 1-2
Station 2-1
Station 2-2
Station 3-1
Station 3-2
LCPU
LCPU
LCPU
LCPU
LCPU
LCPU
Station A
●

●
●
●
●
Station B






Station C






Station D






*1
184
The station A can access the stations marked with ● after the remote password unlock process is completed for 1) of the
station 1-1. It can access the stations marked with  when the communication lines are open. Stations B, C, and D can
access the stations marked with  when the communication lines are open.
CHAPTER 14 OTHER FUNCTIONS
Ex. When a remote password and the remote password check have been set in multiple LCPU stations
Station 1-2
1)
LCPU
E71
Station A
Ethernet
Network No.1
Station 1-1
1)
Remote
password
Remote
password
check
LCPU
E71
Station B
Programming tool
Ethernet
2)
Remote
password
Remote
password
check
LCPU
E71
Network No.3
Station 2-2
1)
Remote
password
E71
LCPU
1)
E71
Network No.2
Station 2-1
Station 3-2
1)
Station 3-1
Remote
password
check
QCPU
Station C
2)
E71
Ethernet
LCPU
14
1)
E71
E71
Station D
The unlock/lock process can be performed for the following connected devices.
• 1) of the station 1-1: By the station A only
• 1) of the station 2-2: By the station C only
• 1) of the station 3-2: By the station D only
●: Stations that can be accessed from the connected device after the remote password unlock process
unlock process
: Stations that cannot be accessed from the connected device
Connected device*1
Target programmable controller station (request destination)
Station 1-1
Station 1-2
Station 2-1
Station 2-2
Station 3-1
Station 3-2
LCPU
LCPU
LCPU
LCPU
LCPU
LCPU
Station A
●

●



Station B






Station C



●
●

Station D





●
(request source)
*1
The station A can access the stations marked with ● after the remote password unlock process is completed for 1) of the
station 1-1, and can access the stations marked with  when the communication lines are open. The station B can
access the stations marked with  when the communication lines are open. The station C can access the stations
marked with ● after the remote password unlock process is completed for 1) of the station 2-2, and can access the
stations marked with  when the communication lines are open. The station D can access the stations marked with ●
after the remote password unlock process is completed for 1) of the station 3-2, and can access the stations marked with
 when the communication lines are open.
To disable access from the connected devices to other stations through CC-Link IE Controller Network, CC-Link IE Field
Network, MELSECNET/H, and MELSECNET/10 relay communication functions, select "MELSOFT Application
Transmission port (UDP/IP), Dedicated Instruction, CC-Link IE, NET10(H) Relay Transmission Port" in the remote password
setting of the relay station or a station to be accessed.
185
14.4 Remote Password
14.4.3 Remote password check procedure
: Stations that can be accessed from the connected device without performing the remote password
14.4.4
Differences in functions according to the remote password
check status (enabled/disabled)
The following table lists the behavior of the functions according to the remote password check status
(enabled/disabled).
Function
Remote password check setting
Disabled
Enabled
After an initial process is completed,
After the remote password is entered,
Connection with MELSOFT products and a
communications are enabled by
communications are enabled. The remote
GOT
establishing a connection in the
password lock process is automatically
programming tool.
performed when the project is closed.
After an open process is completed,
User open port
After an open process is completed,
communications are enabled from the time
communications are enabled.
that the unlock command is received until
the lock command is received.
MC protocol
communications
After an initial process is completed,
Auto-open UDP port
After an initial process is completed,
communications are enabled from the time
communications are enabled.
that the unlock command is received until
the lock command is received.
Communications
using SLMP
User open port
Auto-open UDP port
Communications using the predefined protocol
After an open process is completed,
Use MC protocol to communicate with the
communications are enabled.
CPU module where a remote password is
After an initial process is completed,
set because SLMP does not have unlock
communications are enabled.
and lock commands.
After an open process is completed,
After an open process is completed,
communications are enabled.
communications are enabled.*1
After the remote password is entered,
Communications using the predefined protocol
support function
After an initial process is completed,
communications are enabled. The remote
communications are enabled by
password lock process is automatically
establishing a connection in GX Works2.
performed when the protocol setting data
are closed.
After an open process is completed,
Communications
communications are enabled from the time
Procedure exists
that the unlock command is received until
the lock command is received.
using a fixed buffer
No procedure
After an open process is completed,
After an open process is completed,
communications are enabled.
communications are enabled.*1
After an open process is completed,
communications are enabled from the time
Communications using a random access buffer
that the unlock command is received until
the lock command is received.
E-mail function
After an initial process is completed, data
sending and receiving are
enabled.*2
After an initial process is completed, data
sending and receiving are enabled.*2
After the remote password is entered,
communications are enabled. The remote
Web function
password lock process is automatically
After an initial process is completed,
CC-Link IE Controller Network, CC-Link IE Field
communications are enabled.
performed when the Web browser is
closed.
Network, MELSECNET/H, and
After an initial process is completed,
MELSECNET/10 relay communications
communications are enabled.*3
Communications using data link instructions
186
CHAPTER 14 OTHER FUNCTIONS
Function
Remote password check setting
Disabled
Within Ethernet, communications are
File transfer (FTP server) function
enabled with the connected device that
has completed an open process.
*1
*2
*3
Enabled
After an open process is completed,
communications are enabled from the time
that the unlock command is received until
the lock command is received.
A dedicated connection is used for "No Procedure" communications using a fixed buffer or communications using the
predefined protocol. Do not set the remote password for the connection with the connected device.
Remote password check is not performed against the e-mail function.
If a remote password has been set to the CPU module on the relay station or station to be accessed where the E71 is
connected, access to another station may not be performed.
14
14.4 Remote Password
14.4.4 Differences in functions according to the remote password check status (enabled/disabled)
187
14.4.5
Precautions
The precautions for using the remote password function of the E71 are provided below.
(1) Timing of activating a remote password
To enable the remote password setting, power off or reset the CPU module. After a remote password has been
set, restart the CPU module.
(2) Target connections
Set a remote password check only for the connections used for data communications with the connected devices
that can perform unlock and lock processes.
Ex. In communications using a fixed buffer, do not set the remote password check for the connections
through which the connected device receives data sent from the CPU module.
(3) Connections where "No Procedure" communications using a fixed buffer are
performed
Do not set a remote password check for connections where "No Procedure" communications using a fixed buffer
are performed. The remote password check is not performed for such connections.
(4) Access to the programmable controller on another station
When the connected device accesses the programmable controller on another station through the E71, it may fail
to access the remote-password-protected CPU modules on the relay station or the station to be accessed.
(5) For UDP/IP communications
(a) Connected device for data communications
Do not perform data communications with unspecified connected device. Set the destination device.
(b) Alive check function
Use the alive check function of the E71.*1 Also, when terminating data communications, perform the remote
password lock process. If the process is not performed, data communications from other devices are enabled
until a timeout occurs by the alive check function of the E71. For this reason, when setting a connection with
the connected device using a programming tool, set the parameters as follows.
• When configuring the initial setting, set the start interval timer value and the interval timer value for the
alive check function as small as possible.
• When configuring the open setting, select "Confirm" under "Existence Confirmation".
*1
The alive check is automatically performed when the connection for data communications through the auto-open UDP
port is set as the target for the remote password check.
(6) Communications from the programming tool in the Ethernet connection
For communications from a programming tool in the Ethernet connection, using TCP/IP communications is
recommended.
188
CHAPTER 14 OTHER FUNCTIONS
(7) When the unlock process or lock process fails
If the remote password unlock/lock process fails, check the remote password of the CPU module then perform
the unlock/lock process again.
(a) E71 operation in case of a process failure
If the number of process failures exceeds the notification accumulated count*1 set in the buffer memory area,
the E71 performs the following operations.
• The E71 turns on the COM.ERR. LED.
• The E71 stores C200H in the error code and end code storage area in the buffer memory area, Error log
area (address: E3H to 174H).
*1
This is the number of times stored in Remote password mismatch notification accumulated count designation (address:
5070H and 5071H) by the CPU module (using an instruction such as the TO instruction) when the E71 starts up.
In the above case, identify the connection where the unlock/lock process has failed using the following buffer
14
memory areas.
• Accumulated count of unlock process abnormal end (address of Connection No.1: 5073H)
• Accumulated count of lock process abnormal end (address of Connection No.1: 5075H)
(b) Corrective action against a process failure
Take the following actions if required.
• Close the connection with the connected device.
• Write "0" in the buffer memory areas, Accumulated count of unlock process abnormal end (address: 20595
(5073H) and Accumulated count of lock process abnormal end (address: 20597 (5075H)). If this action is
not taken, the process (a) above will be performed each time a process failure occurs exceeding the
above accumulated notification count, the possible cause is unauthorized access from the connected
device. Disable the connection using the buffer memory area, System port use prohibited designation area
(address: 5008H) (After this, the unlock process cannot be performed for the connection until "Use
allowed" is set.)
• Inform the system manager that the number of unlock/lock process failures is greater than the
accumulated notification count, and take corrective actions.
● For the method to turn off the COM.ERR. LED, refer to the method using the Ethernet diagnostics. (
Section 16.10)
Page 303,
● The accumulated counts of unlock/lock process abnormal end for Connection Nos.1 to 16 stored in the buffer memory
can be cleared.
• Accumulated count of unlock process abnormal end (address of Connection No.1: 5073H)
• Accumulated count of lock process abnormal end (address of Connection No.1: 5075H)
189
14.4 Remote Password
14.4.5 Precautions
notification accumulated count.
• If the number of unlock/lock process failures for the connection to the connected device is greater than the
14.4.6
Parameter settings
The remote password setting of the E71 is described.
Project window
[Parameter]
[Remote Password]
Item
Password Setting
Remote
Password
Setting
Password Active Module
Setting
User Connection No.*1*3
Description
Setting range
Enter a password set for the CPU module.

Model Name
Select the module model that checks an
entered remote password against the remote
password set for the CPU module.
Start XY
Set the start address of the module that checks
an entered remote password.
Condition
Opens the "Remote Password Detail Setting"
window.

Specify a connection where an entered remote
password is checked.

LJ71E71-100
0000H to 0FE0H
Connection 1 to Connection 16
Auto Open UDP Port
FTP Transmission Port (TCP/IP)
Remote
Password
Detail Setting
System Connection*2
MELSOFT Application Transmission Port
(TCP/IP)
MELSOFT Application Transmission Port
(UDP/IP), Dedicated Instruction, CC-Link IE,
NET/10(H) Relay Transmission Port
HTTP Port, HTTP Protocol
*1
*2
*3
The user connection is used to perform MC protocol communications and fixed buffer communications.
The system connection is used in the system to perform FTP communications and MELSOFT communications (TCP/IP,
UDP/IP).
When "MELSOFT Connection" has been selected in the open setting, select the MELSOFT application communication
port in "System Connection".
MELSOFT connection is performed to the MELSOFT application communication port of the system connection, not of
the user connection. If the MELSOFT application communication port is not selected in "System Connection" , a window
for a password does not appear.
When determining a remote password, take care of the following.
• Avoid a simple character string (e.g. Character string consisting of alphanumeric characters only).
• Combine alphanumeric characters and special characters (e.g. "?", "!", "&", and "%").
• Avoid using a character string that represents the user's name or the date of birth.
190
CHAPTER 14 OTHER FUNCTIONS
14.5
Hub Connection Status Monitor Function
The current connection status and transmission speed of an E71 and a hub and the number of times that the E71
detected disconnection can be checked using the following buffer memory areas. For details on buffer memory areas,
refer to the list of buffer memory addresses. (
Page 35, Section 3.5.2)
Buffer memory area
Hub connection status area (address: C9H)
Description
Stores the current connection status and transmission speed
of an E71 and a hub.
Stores the number of times that the E71 detected
disconnection after an initial process. Disconnection is
detected in any of the following cases.
Disconnection detection count (address: 5203H)
• Disconnection between the E71 and a hub
• Cable removal from the hub side connector
• Hub power-off
• Cable removal from the E71 side connector
14
If an error has occurred 65536 times or more, the count stops at 65535 (FFFFH). Write "0" to this area using a program to
clear the stored value.
14.5 Hub Connection Status Monitor Function
191
14.6
IP Address in Use Detection Function
If different stations in the same network use the same IP address, the address in use can be detected. This prevents a
network from stopping due to incorrect IP address.
When the connected device with the same IP address does not support the IP address in use detection function, the
error is not detected.
If a station and another station with the same
IP address exist on the same network, another
station cannot be connected to the network.
(The COM.ERR.LED turns on and COM.ERR.LED
turning on check (X1C) turns on.)
The station that has been already
connected to the network continues
communications even if the station
with the same IP address is connected.
The module
connected later
IP address:
10.97.24.1 (overlapped)
MAC address:
00 26 92 89 2E 89
IP address:
10.97.24.2
MAC address:
00 26 92 45 16 CC
This station
cannot be
connected to
the network,
resulting in
an error.
IP address:
IP address:
10.97.24.1 (overlapped)
10.97.24.3
MAC address:
MAC address:
00 1A 4D 5D 5D D8
00 26 92 DE 26 90
(1) Checking the IP address already in use
The following two methods are available:
• Checking buffer memory areas
• Checking using the Ethernet diagnostics
(a) Checking buffer memory areas
Both the station already connected to the network and the station with the same IP address (station connected
to the network later), and the MAC addresses of the stations with the same IP address can be checked. The
destination IP address can be checked only in the station with the same IP address (station connected to the
network later).
Buffer memory area
Destination IP address (stored in the station with the same IP address
connected to the network later.)
The MAC address of the station that has been
already connected to the network (stored in the
station with the same IP address connected to
the network later).
IP address status
storage area
The MAC address of the station with the same IP
address connected to the network later (stored in
the station that has been already connected to
the network).
192
Buffer memory
address
Description
234 (EAH)
The third and fourth octets of the IP
address
235 (EBH)
The first and second octets of the IP
address
21121 (5281H)
The fifth and sixth octets of the MAC
address
21122 (5282H)
The third and fourth octets of the MAC
address
21123 (5283H)
The first and second octets of the MAC
address
21124 (5284H)
The fifth and sixth octets of the MAC
address
21125 (5285H)
The third and fourth octets of the MAC
address
21126 (5286H)
The first and second octets of the MAC
address
CHAPTER 14 OTHER FUNCTIONS
Remark
When the MAC address of the station that has been already connected to the network is 00.26.92.89.2E.89, the IP address
already in use is 10.97.24.01, and the MAC address of the station connected to the network later is 00.26.92.DE.26.90, the
value stored in each buffer memory area is as follows.
• 234 (EAH): 1801H (the third and fourth octets of the IP address)
• 235 (EBH): 0A61H (the first and second octets of the IP address)
• 21121 (5281H): 2E89H (the fifth and sixth octets of the MAC address)
• 21122 (5282H): 9289H (the third and fourth octets of the MAC address)
• 21123 (5283H): 0026H (the first and second octets of the MAC address)
• 21124 (5284H): 2690H (the fifth and sixth octets of the MAC address)
• 21125 (5285H): 92DEH (the third and fourth octets of the MAC address)
• 21126 (5286H): 0026H (the first and second octets of the MAC address)
(b) Checking using the Ethernet diagnostics
An error code (C00FH) is displayed in the "Ethernet Diagnostics" window, and the IP address used in multiple
stations is displayed in the "Destination IP Address" column. The destination IP address can be checked only
in the station with the same IP address (station connected to the network later).
[Diagnostics]
14
[Ethernet Diagnostics...]
14.6 IP Address in Use Detection Function
193
14.7
Alive Check Function
When the E71 has not communicated with the connected device for a certain period of time while the connection is
open, this function checks whether the connected device is alive by sending an alive check message to the connected
device and waiting for the response.
(1) Parameter setting
To enable the alive check function, select "Confirm" under "Existence Confirmation" in the open setting.
(
Page 69, Section 7.1.4) In TCP/IP communications, the following methods can be selected in the Ethernet
operation setting. (
Page 67, Section 7.1.3)
(2) Alive check method
The following alive check methods are available.
(a) Check using the PING command
This method is used for a connection opened using TCP/IP or UDP/IP. The E71 performs an alive check by
sending the PING command (ICMP echo request/response function) to the connected device with which
communications have not been performed for a certain period of time and waiting to see whether the response
is received.*1
*1
The E71 automatically sends an echo response packet when it receives a PING echo request. (It sends a response to
the received PING command even if the connection used in the data communications with the connected device is
closed.)
(b) Check using the KeepAlive function
This method is used for a connection opened using TCP/IP. The E71 performs an alive check by sending a
KeepAlive ACK message to the connected device with which communications have not been performed for a
certain period of time and waiting to see whether the response is received.*1
*1
194
The connection may be disconnected if the connected device does not support the TCP KeepAlive function (response to
a KeepAlive ACK message).
CHAPTER 14 OTHER FUNCTIONS
(3) If a response message cannot be received from the connected device
If a response message cannot be received from the connected device (or if an error has been detected) using the
alive check function, the following processes are performed.
• The corresponding connection will be forcibly closed. (The line is disconnected.) Open the connection using
a user program again.
• Open completion signal is turned off, and the error code (C035H) is stored in the open error code storage
area.
Ex. Assuming that the values*1 are set so that the number of retries may be three, the E71 performs an alive
check at the timing shown in the figure below (an example of alive check using the PING command).
Connection
forced close
(error code: C035H)
Open completion signal
(address: 5000H)
E71
The last
communications
Starting interval
timer for alive check
of the target device
*1
Alive check
Alive check
(1st time)
Alive check
resent
(2nd time)
Alive check
resent
(3rd time)
Interval timer
value for alive
check of the
target device
Interval timer
value for alive
check of the
target device
Interval timer
value for alive
check of the
target device
Interval timer
value for alive
check of the
target device
The values of the number of retries and timers can be changed in the initial setting. (
14
RST sending
(TCP only)
Page 311, Appendix 4.1)
14.7 Alive Check Function
195
CHAPTER 15 DEDICATED INSTRUCTIONS
Dedicated instructions facilitate programming for using intelligent function modules. This chapter describes dedicated
instructions that can be used in the E71.
15.1
List of Dedicated Instructions
(1) Dedicated instructions for using basic functions
The following table lists dedicated instructions for using the functions explained in this manual.
Instruction
OPEN
CLOSE
ECPRTCL
BUFSND
BUFRCV
BUFRCVS
ERRCLR
Description
Reference
Establishes (opens) a connection with the connected device to perform data
communications.
Disconnects (closes) a connection with the connected device performing data
communications.
Executes the protocols registered in the flash ROM of the E71 using the
Predefined Protocol Support Function of GX Works2.
Sends data to the connected device through communications using a fixed
buffer.
Reads data received from the connected device through communications using
a fixed buffer. (used in the main program)
Reads data received from the connected device through communications using
a fixed buffer. (used in an interrupt program)
Turns off LEDs of the E71 or clears error information stored in the buffer
memory.
Page 199, Section 15.5
Page 203, Section 15.6
Page 206, Section 15.7
Page 216, Section 15.8
Page 220, Section 15.9
Page 224, Section 15.10
Page 226, Section 15.11
ERRRD
Reads error information stored in the buffer memory of the E71.
Page 230, Section 15.12
UINI
Re-initializes the E71.
Page 233, Section 15.13
(2) Dedicated instructions for using special functions
The following table lists dedicated instructions for using special functions. For details on the dedicated
instructions, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Application)
Function
E-mail function
Instruction
MRECV
Reads the received e-mails.
MSEND
Sends e-mails.
READ
Reads word device data from other stations.
RECV
Reads data received from other stations. (Used in the main program.)
RECVS
Reads data received from other stations. (Used in an interrupt program.)
REQ
Communications using
data link instructions
196
Description
Performs remote RUN/STOP to CPU modules on other stations.
Reads/writes the clock data of other stations.
SEND
Sends data to other stations.
SREAD
Reads word device data from other stations. (with a completion device)
SWRITE
Writes word device data to other stations. (with a completion device)
WRITE
Writes word device data to other stations.
ZNRD
Reads word device data from other stations (ACPU).
ZNWR
Writes word device data to other stations (ACPU).
CHAPTER 15 DEDICATED INSTRUCTIONS
15.2
Parameter Settings for Using Dedicated Instructions
When using dedicated instructions, set the parameters of each function.
15.2.1
When using data link instructions
When using data link instructions, set the following parameters.
• Station No. <-> IP information setting
• Routing parameters setting
For details on the settings, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Application)
15
15.2 Parameter Settings for Using Dedicated Instructions
15.2.1 When using data link instructions
197
15.3
Precautions for Dedicated Instructions
This section describes precautions for using dedicated instructions.
(1) When changing data specified by dedicated instructions
Do not change any data (e.g. control data) until execution of the dedicated instruction is completed.
(2) When the dedicated instruction is not completed
Check that "Online" has been set under "Mode" in the network parameter window. Dedicated instructions cannot
be executed during offline.
(3) Securing service process time
When accessing a programmable controller on another station using a data link instruction during the Ethernet
diagnostics, execution of the instruction may be delayed. Take the following measures to execute the data link
instruction after the Ethernet diagnostics.
• Execute the COM instruction.
• Reserve time for a communication process for 2 to 3 ms. Use a programming tool for the setting.
Project window
[Parameter]
[PLC Parameter]
"Service Processing Setting" under the
"PLC System" tab
(4) Specifying the first argument of a dedicated instruction (Un)
The first argument of a dedicated instruction (Un) can be also specified with double quotation marks (" ").
15.4
Organization of the Dedicated Instruction Sections
For the organization of the dedicated instruction sections, refer to Page 13.
198
CHAPTER 15 DEDICATED INSTRUCTIONS
15.5
ZP.OPEN
This instruction establishes (opens) a connection with the connected device to perform data communications.
Command
ZP.OPEN
ZP.OPEN
Un
(S1)
(S2)
(D1)
Available device
Setting data*1
Internal device
(system, user)
File
register
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Word
K, H
$







(S2)







(D1)







*1
Word
Others
Bit
(S1)
Bit
Constant
The file registers set for each local device and program cannot be used.
15
(1) Setting data
Setting data
Un/"Un"
Description
Set by
Start I/O number of the E71 (00 to FEH: The first two digits
of the three-digit I/O number)
Connection number (1 to 16)
(S2)
Start number of the device that stores control data
BIN 16-bit/character
User
string
15.5 ZP.OPEN
(S1)
Data type
BIN 16-bit
User, system
Device name
The start number of the bit device in the own station that
(D1)
turns on for one scan upon completion of the instruction.
System
Bit
(D1)+1 also turns on if the instruction ends abnormally.
199
(2) Control data
Device
Item
Setting data
Setting range
Set by
To open a connection, specify whether to use the
parameter settings of a programming tool or to use
Execution
(S2)+0
type/completion
type
the settings stored in the following control data
starting from (S2)+2.
• 0000H: Use the parameter settings of the
0000H,
User
8000H
programming tool.
• 8000H: Use the settings of control data starting
from (S2)+2 to (S2)+9.
Stores the status at completion.
(S2)+1
Completion
• 0000H: Normal completion
status
• Values other than 0000H: Abnormal end (error

System
As described in the left
User
code)
Specify the application of a connection.
• Usage of fixed buffer (b0)
0: For sending or fixed buffer communications are
not performed
1: For receiving
• Destination existence confirmation (b1)
0: No confirm
1: Confirm
• Pairing open (b7)
0: Disable
(S2)+2
Usage setting
area
1: Enable
• Communication method (protocol) (b8)
0: TCP/IP
1: UDP/IP
• Fixed buffer communication procedure (b10, b9)
00: Procedure exists
01: No procedure
10: Predefined protocol
• Open system (b15, b14)
00: Active open or UDP/IP
10: Unpassive open
11: Fullpassive open
(S2)+3
No.
(S2)+4
Destination IP
(S2)+5
address
(S2)+6
(S2)+7
(S2)+8
(S2)+9
*1
200
Own station port
Destination port
No.
Destination MAC
address
Specify the port number of the own station.
401H to 1387H, 138BH
to FFFEH
User
1H to FFFFFFFFH
Specify the IP address of the connected device.
(FFFFFFFFH:
User
broadcast)
Specify the port number of the connected device.
Specify the MAC address of the connected device.
1H to FFFFH *1(FFFFH:
broadcast)
000000000000H to
FFFFFFFFFFFFH
The range of 1H to 400H is available only in the E71 with the serial number (first five digits) of "15042" or later.
User
User
CHAPTER 15 DEDICATED INSTRUCTIONS
(3) Functions
• This instruction performs the open process for a connection specified by (S1) for the module specified by Un.
The setting value used for the open process is selected by (S2)+0.
• Completion of the OPEN instruction can be checked with Completion device (D1)+0 and (D1)+1.
Item
Completion device (D1)+0:
Description
Turns on at the END process of the scan where the OPEN instruction is completed and
turns off at the next END process.
Turns on and off depending on the completion status of the OPEN instruction.
Completion device (D1)+1:
• Normal completion: Stays off and does not change.
• Abnormal end: Turns on at the END process of the scan where the OPEN instruction is
completed and turns off at the next END process.
[Operation while the OPEN instruction is being executed]
Program
OPEN instruction
Scan
END
process
Scan
END
process
Scan
END
process
Executed
Completion device
Completion device + 1
15
Abnormally ended
Connection
opened
• The ZP.OPEN instruction is executed on the rising edge (OFF  ON) of the open command.
(4) Errors
If a dedicated instruction ends with an error, Completion device (D1)+1 turns on, and the error code is stored in
Completion status (S2)+1.
201
15.5 ZP.OPEN
Do not perform an open or close process using I/O signals and the dedicated instruction together for the same connection.
Doing so will result in malfunction.
(5) Program example
The following shows a sample program that performs an Active open process on the connection number 1 for
TCP/IP communications (when the I/O signals of the E71 are X/Y00 to X/Y1F).
*1
*2
*1
*2
202
Necessary when the open setting of the programming tool is used. (In this case, the program marked with *2 is
unnecessary.)
Necessary when the open setting of the program is used. (In this case, the program marked with *1 is unnecessary.)
CHAPTER 15 DEDICATED INSTRUCTIONS
15.6
ZP.CLOSE
This instruction disconnects (closes) a connection with the connected device performing data communications.
Command
ZP.CLOSE
ZP.CLOSE
Un
(S1)
(S2)
(D1)
Available device
Setting data*1
Internal device
(system, user)
File
register
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Word
(S1)







(S2)














*1
Word
K, H
Others
Bit
(D1)
Bit
Constant
$
The file registers set for each local device and program cannot be used.
15
(1) Setting data
Setting data
Description
Set by
Start I/O number of the E71 (00 to FEH: The first two digits
Un/"Un"
BIN 16-bit/character
string
User
(S1)
Connection number (1 to 16)
BIN 16-bit
(S2)
Start number of the device that stores control data
Device name
The start number of the bit device in the own station that
(D1)
turns on for one scan upon completion of the instruction.
System
15.6 ZP.CLOSE
of the three-digit I/O number)
Data type
Bit
(D1)+1 also turns on if the instruction ends abnormally.
(2) Control data
Device
(S2)+0
(S2)+1
Item
System area
Completion
status
Setting data
Setting range
Set by




System
Stores the status at completion.
• 0000H: Normal completion
• Values other than 0000H: Abnormal end (error code)
203
(3) Functions
• This instruction performs the close process for a connection specified by (S1) for the module specified by Un
(connection closed).
• Completion of the CLOSE instruction can be checked with Completion device (D1)+0 and (D1)+1.
Item
Completion device (D1)+0:
Description
Turns on at the END process of the scan where the CLOSE instruction is completed and
turns off at the next END process.
Turns on and off depending on the completion status of the CLOSE instruction.
Completion device (D1)+1:
• Normal completion: Stays off and does not change.
• Abnormal end: Turns on at the END process of the scan where the CLOSE instruction is
completed and turns off at the next END process.
[Operation while the CLOSE instruction is being executed]
Program
CLOSE instruction
Scan
END
process
Scan
END
process
Scan
END
process
Executed
Completion device
Completion device + 1
Abnormally ended
Connection
closed
• The ZP.CLOSE instruction is executed on the rising edge (OFF  ON) of the close command.
Do not perform a open/close process using I/O signals and using the dedicated instruction together for the same connection.
Doing so will result in malfunction.
(4) Errors
If a dedicated instruction ends with an error, Completion device (D1)+1 turns on, and the error code is stored in
Completion status (S2)+1.
204
CHAPTER 15 DEDICATED INSTRUCTIONS
(5) Program example
The following shows a sample program that closes the connection number 1 (when the I/O signals of the E71 are
X/Y00 to X/Y1F).
15
15.6 ZP.CLOSE
205
15.7
GP.ECPRTCL
This instruction executes the protocols registered in the flash ROM of the E71 using the predefined protocol support
function of GX Works2.
Command
GP.ECPRTCL
GP.ECPRTCL
Un
n1
n2
(S)
(D)
Available device
Setting data*1
Internal device
(system, user)
File
register
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Word
K,H
Others
Bit
Word
n1







n2







(S)







(D)







*1
Bit
Constant
$
The file registers set for each local device and program cannot be used.
(1) Setting data
Setting data
Un
Description
Set by
Start I/O number of the E71 (00 to FEH: The first two digits
BIN 16-bit
of the three-digit I/O number)
n1
Connection number (1 to 16)
n2
Number of consecutive protocol executions (1 to 8)
(S)
Start number of the device that stores control data
Data type
User
BIN 16-bit
Device name
BIN 16-bit
Device name
User/system
Device name
The start number of the bit device in the own station that
(D)
turns on for one scan upon completion of the instruction.
(D)+1 also turns on if the instruction ends abnormally.
206
System
Bit
CHAPTER 15 DEDICATED INSTRUCTIONS
(2) Control data
Device
Item
Setting data
Setting range
Set by
0, 1 to 8
System

System
1 to 128
User
Set the second protocol number to be executed.
0, 1 to 128
User
Set the third protocol number to be executed.
0, 1 to 128
User
Set the fourth protocol number to be executed.
0, 1 to 128
User
Set the fifth protocol number to be executed.
0, 1 to 128
User
Set the sixth protocol number to be executed.
0, 1 to 128
User
Set the seventh protocol number to be executed.
0, 1 to 128
User
Set the eighth protocol number to be executed.
0, 1 to 128
User
0, 1 to 16
System
0, 1 to 16
System
Stores the number of protocols which are executed
(S)+0
Execution count
result
by using the ECPRTCL instruction.
Protocols with errors are included in the count.
When settings of the setting data or control data
contain an error, "0" is stored.
Stores the status at completion.
(S)+1
Completion
status
When multiple protocols are executed, the status of
the protocol executed at last is stored.
0000H: Normal completion
Values other than 0000H (error code): Abnormal end
Execution
(S)+2
protocol number
Set the first protocol number to be executed.
specification 1
Execution
(S)+3
protocol number
specification 2
Execution
(S)+4
protocol number
specification 3
15
Execution
(S)+5
protocol number
specification 4
Execution
(S)+6
protocol number
specification 5
protocol number
specification 6
Execution
(S)+8
protocol number
specification 7
Execution
(S)+9
protocol number
specification 8
When the communication type of the first protocol
executed includes receiving, the matched receive
(S)+10
Matched receive
packet number is stored. When the communication
packet No.1
type is "Send Only", "0" is stored.
If an error occurs to the first protocol executed, "0" is
stored.
When the communication type of the second
protocol executed includes receiving, the matched
receive packet number is stored. When the
(S)+11
Matched receive
communication type is "Send Only", "0" is stored.
packet No.2
If an error occurs to the second protocol executed,
"0" is stored.
When the number of protocols which are executed is
less than 2, "0" is stored.
207
15.7 GP.ECPRTCL
Execution
(S)+7
Device
Item
Setting data
Setting range
Set by
0, 1 to 16
System
0, 1 to 16
System
0, 1 to 16
System
0, 1 to 16
System
0, 1 to 16
System
0, 1 to 16
System
When the communication type of the third protocol
executed includes receiving, the matched receive
packet number is stored. When the communication
(S)+12
Matched receive
type is "Send Only", "0" is stored.
packet No.3
If an error occurs to the third protocol executed, "0"
is stored.
When the number of protocols which are executed is
less than 3, "0" is stored.
When the communication type of the fourth protocol
executed includes receiving, the matched receive
packet number is stored. When the communication
(S)+13
Matched receive
type is "Send Only", "0" is stored.
packet No.4
If an error occurs to the fourth protocol executed, "0"
is stored.
When the number of protocols which are executed is
less than 4, "0" is stored.
When the communication type of the fifth protocol
executed includes receiving, the matched receive
packet number is stored. When the communication
(S)+14
Matched receive
type is "Send Only", "0" is stored.
packet No.5
If an error occurs to the fifth protocol executed, "0" is
stored.
When the number of protocols which are executed is
less than 5, "0" is stored.
When the communication type of the sixth protocol
executed includes receiving, the matched receive
packet number is stored. When the communication
(S)+15
Matched receive
type is "Send Only", "0" is stored.
packet No.6
If an error occurs to the sixth protocol executed, "0"
is stored.
When the number of protocols which are executed is
less than 6, "0" is stored.
When the communication type of the seventh
protocol executed includes receiving, the matched
receive packet number is stored. When the
(S)+16
Matched receive
communication type is "Send Only", "0" is stored.
packet No.7
If an error occurs to the seventh protocol executed,
"0" is stored.
When the number of protocols which are executed is
less than 7, "0" is stored.
When the communication type of the eighth protocol
executed includes receiving, the matched receive
packet number is stored. When the communication
(S)+17
Matched receive
type is "Send Only", "0" is stored.
packet No.8
If an error occurs to the eighth protocol executed, "0"
is stored.
When the number of protocols which are executed is
less than 8, "0" is stored.
208
CHAPTER 15 DEDICATED INSTRUCTIONS
(3) Functions
• The module specified by Un executes the protocol setting data written to the flash ROM.
The protocol is executed according to the control data of the device specified by (S) and the following
devices.
The connection specified by n1 is used.
• Protocols are executed consecutively for the number of times specified by n2 (up to eight protocols) by one
instruction.
• When two or more ECPRTCL instructions are executed simultaneously for the same connection, the
following instruction will be ignored until the first instruction is completed.
• The number of protocols is stored in (S)+0.
• Protocol execution status can be checked in the predefined protocol support function execution status check
area (address: 54C0H to 55FFH).
• The communication type of the protocol executed and fixed buffer setting of the connection No. specified by
n1 must be matched.
The following table lists the combination of the communication type and the connection No. that can be
specified by n1.
Communication type
When the communication type of all protocols executed (up
to eight protocols) is "Send Only"
When the communication type of all protocols executed (up
to eight protocols) is "Receive Only"
Connection No. that can be specified by n1
• A connection where "Send" is selected in the open setting
(no paring open setting)
• A connection where paring open is
15
set*1*2
• A connection where "Receive" is selected in the open
setting (no paring open setting)
• A connection where paring open is set*1*2
When the communication type of any protocol executed (up
to eight protocols) is "Send&Receive"
A connection where paring open is set*1*3
to eight protocols) are "Send Only" and "Receive Only"
*1
*2
*3
To specify a connection where paring open is set, either of pairing-opened connections can be specified.
When a pairing-opened connection is specified, an extra connection is used.
When the protocols executed include the communication type of "Send&Receive" or "Send Only" and "Receive Only",
pairing open setting is required.
209
15.7 GP.ECPRTCL
When the communication types of protocols executed (up
• Completion of the ECPRTCL instruction can be checked with Completion device (D) and (D1)+1.
Item
Description
Turns on at the END process of the scan where the ECPRTCL instruction is completed
Completion device (D1)+0
and turns off at the next END process.
Turns on and off depending on the completion status of the ECPRTCL instruction.
• Normal completion: Stays off and does not change.
Completion device (D1)+1
• Abnormal end: Turns on at the END process of the scan where the ECPRTCL
instruction is completed and turns off at the next END process.
[Operation while the ECPRTCL instruction is being executed]
Program
Scan
ECPRTCL instruction
END
process
Scan
END
process
Scan
END
process
Scan
END
process
Scan
END
process
Scan
Instruction executed
Completion device
Completion device + 1
At abnormal end
Protocol executed*2
Protocol execution status
(address: 54C0H*1)
(5: Completed)
(Execution status)
*1: Address of the connection 1
*2: Protocols are consecutively executed by the number of protocols specified in n2 of the setting data in the order
specified with the control data (up to eight protocols) with one ECPRTCL instruction.
Protocol
Protocol
Protocol
Protocol
Protocol
● When multiple protocols are executed and an error has occurred in one protocol, the following protocols are not executed
and the dedicated instruction ends abnormally.
● For the connection where the ECPRTCL instruction can be executed, "Predefined protocol" is set in Fixed Buffer
Communication. Thus, the following communications are not available.
• MC protocol communications
• Communications using a fixed buffer (procedure exists)
• Communications using a fixed buffer (no procedure)
• Communications using a random access buffer
● File transfer (FTP server) function, e-mail function, Web function, or MELSOFT connection, which uses a dedicated
connection, can be executed while the ECPRTCL instruction is being executed.
● When protocols which include Non-conversion Variable are executed and the data length of the variable for one packet
exceeds 1920 bytes, the value of the CPU module device may not be acquired at one scan.
Do not change the value of the CPU module device specified in Non-conversion Variable until the ECPRTCL instruction
is completed.
Buffer memory is not affected by the sequence scan of the CPU module. Assigning them in a variable enables more highspeed process than assigning the CPU module device.
● If the protocol setting data is written while the ECPRTCL instruction is being executed, protocol execution is canceled
upon the writing completion. Protocol setting data writing during the ECPRTCL instruction execution (error code: C430H)
occurs and the ECPRTCL instruction ends abnormally.
● When the open setting for the specified connection and the communication type of the protocol executed does not match,
Connection number setting error (error code: C407H) occurs and the ECPRTCL instruction ends abnormally.
● When the waiting time is set to "0" (wait infinitely) in the Protocol Detailed Setting, the dedicated instruction is not
completed until the data specified in the protocol setting is received.
210
CHAPTER 15 DEDICATED INSTRUCTIONS
(4) Errors
Completion device (D)+1 turns on and the error code is stored in Completion status (S)+1 in the following cases.
• When the setting value of the control data is abnormal
• When an error is detected in the protocol setting data registered in GX Works2
• When an error has occurred in protocols (the following protocols will not be executed.)
• When a value other than "Predefined protocol" is set in Fixed Buffer Communication for connection No.
specified by n1
(5) Program example
For the program example, refer to Page 111, Section 11.5.
(6) Canceling protocol execution
A protocol can be canceled during its execution.
This function is used to terminate the protocol execution forcibly when a communication error occurs with the
connected device.
(a) Execution method for cancel request
Set the cancel request to Protocol cancellation specification (address: 54D3H (Connection No.1)).
15
User
Connection No.n
Protocol cancellation specification
(54D3H (when the value of n is 1))
2: Cancel completed
15.7 GP.ECPRTCL
E71
1: Cancellation request
The E71 cancels the
protocols being executed
in connection No.n.
211
(b) Operations after execution of cancel request
[Operations of the ECPRTCL instruction]
• The ECPRTCL instruction ends abnormally and Protocol cancel request error (error code: C404H) is
stored in Completion status (S)+1.
• When cancel request is executed to the nth protocol while multiple protocols are being executed
consecutively, the E71 terminates the nth protocol forcibly and the following protocols are not executed.
The following table lists the control data that are stored when protocols are canceled.
Device
Item
Stored value
The number of protocols executed including canceled
(S)+0
Execution count result
(S)+1
Completion status
(S+10) to (S+17)
Matched receive packet No.1 to 8
protocols
(When cancel request is executed to the second
protocol, 2 is stored.)
Protocol cancel request error (error code: C404H)
Matched receive packet number of the executed
protocol
[Operations of the E71]
• If the cancel request is executed when any protocol is not being executed, the E71 completes the cancel
without any process.
● If any data is received from the connected device after the protocol whose communication type includes receiving is
canceled, the data will be discarded.
● The E71 checks whether any cancel request exists at periodic processing. For this reason, it may take some time to
process the cancellation after the cancel request is executed.
● When Protocol cancellation specification (address: 54D3H (Connection No.1)) is "1: Cancellation request", the next
ECPRTCL instruction cannot be executed.
212
CHAPTER 15 DEDICATED INSTRUCTIONS
(c) Timing chart
The E71 performs the following process according to the timing of cancel request.
Protocol execution status
E71 operations at cancel request
(address: 54C0H)
0: Unexecuted
No process
1: Waiting for transmission
The E71 cancels the sending and terminates the dedicated instruction forcibly.
2: Sending
The E71 terminates the dedicated instruction forcibly at sending completion.
3: Waiting for data reception
The E71 cancels the receiving and terminates the dedicated instruction forcibly.
4: Receiving
The E71 terminates the dedicated instruction forcibly at receiving completion.
5: Completed
The E71 terminates the dedicated instruction when protocols are executed
consecutively.
The followings describe the operations of protocol cancellation according to the timing.
• When the cancel request is performed before sending
(when "1" (Waiting for transmission) is set in Protocol execution status (address: 54C0H))
ECPRTCL instruction
15
Completion device
The device turns on
upon abnormal end.
Completion device + 1
1: Cancellation request
Waiting time
to send
Cancel
E71
2: Cancel completed
15.7 GP.ECPRTCL
Connection No.n
Protocol cancellation specification
(54D3H (when the value of n is 1))
The E71 does not send a send
packet to the connected device
even when a receive data or a
protocol exists.
Send packet
Connected device
Send packet
213
• When the cancel request is performed before sending completion
(when "2" (Sending) is set in Protocol execution status (address: 54C0H) and the sending has not been
completed)
ECPRTCL instruction
Completion device
The device turns on
upon abnormal end.
Completion device + 1
Connection No.n
Protocol cancellation specification
(54D3H (when the value of n is 1))
1: Cancel request
Waiting time
to send
2: Cancel completed
t: TCP ULP timer
E71
Send packet
The E71 does not send a
send packet to the connected
device even when a receive
data or a protocol exists.
Packet sending in progress is
completed without interruption.
Connected device
Cancel
Send packet
• When the cancel request is performed at sending completion
(when "2" (Sending) is set in Protocol execution status (address: 54C0H) and the sending has been
completed)
ECPRTCL instruction
Completion device
The device
turns on upon
abnormal end.
Completion device + 1
Connection No.n
Protocol cancellation specification
(54D3H (when the value of n is 1))
1: Cancellation
request
Waiting time
to send
2: Cancel
completed
t: TCP ULP timer
E71
Send packet
Cancel
Connected device
Send packet
214
The E71 does not send a
send packet to the connected
device even when a receive
data or a protocol exists.
CHAPTER 15 DEDICATED INSTRUCTIONS
• When the cancel request is performed before receiving
(when "3" (Waiting for data reception) is set in Protocol execution status (address: 54C0H))
ECPRTCL instruction
Completion device
The device turns on
upon abnormal end.
Completion device + 1
Connection No.n
Protocol cancellation specification
(54D3H (when the value of n is 1))
1: Cancellation request
t: waiting time to receive or the time specified
by the destination alive check timer
E71
2: Cancel completion
The E71 does not send a
send packet to the connected
device even when a receive
data or a protocol exists.
Cancel
15
Connected device
• When the cancel request is performed during receiving
(when "4" (Receiving) is set in Protocol execution status (address: 54C0H))
ECPRTCL instruction
15.7 GP.ECPRTCL
Completion device
The device turns on
upon abnormal end.
Completion device + 1
Connection No.n
Protocol cancellation specification
(54D3H (when the value of n is 1))
1: Cancellation request
t: waiting time to receive or the time specified
by the destination alive check timer
E71
2: Cancel completed
The E71 does not send a
send packet to the connected
device even when a receive
data or a protocol exists.
Receiving
Cancel
Connected device
The E71 interrupts the verification and
general data processing and forcibly
terminates the dedicated instruction.
Receive data
215
15.8
ZP.BUFSND
This instruction sends data to the connected device through communications using a fixed buffer.
Command
ZP.BUFSND
ZP.BUFSND
Un
(S1)
(S2)
(S3)
(D1)
Available device
Setting data*1
(S1)
Internal device
(system, user)
Bit
Word


File
register
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Bit
Word

Constant
K, H
$



Others

(S2)







(S3)







(D1)







*1
The file registers set for each local device and program cannot be used.
(1) Setting data
Setting data
Description
Un/"Un"
of the three-digit I/O number)
BIN 16-bit/character
string
User
(S1)
Connection number (1 to 16)
(S2)
Start number of the device that stores control data
(S3)
Data type
Set by
Start I/O number of the E71 (00 to FEH: The first two digits
BIN 16-bit
Start number of the device that stores send data
System
Device name
User
Device name
The start number of the bit device in the own station that
(D1)
turns on for one scan upon completion of the instruction.
System
Bit
(D1)+1 also turns on if the instruction ends abnormally.
(2) Control data
Device
(S2)+0
Item
System area
Setting data
Setting range
Set by




System
Stores the status at completion.
(S2)+1
Completion
• 0000H: Normal completion
status
• Values other than 0000H: Abnormal end (error
code)
216
CHAPTER 15 DEDICATED INSTRUCTIONS
(3) Send data
Device
Item
(S3)+0
length
range

Specify send data
Send data
Setting
Setting data

length. (Depending on
Procedure exists (communications using
the procedure of fixed
a binary code): Number of words
buffer communications,
Procedure exists (communications using
the data length is the
an ASCII code): Number of words
number of words or the
No procedure (communications using a
number of bytes.)
binary code): Number of bytes
Set by
1 to 1017
1 to 508
User
1 to 2046
(S3)+1
to
Send data

Specify the send data.
User
(S3)+n
(4) Functions
• This instruction sends the data specified by (S3) to the connected device of the connection specified by (S1)
for the module specified by Un.
CPU module
15
E71
Fixed buffer data area
(S3)
No.1
Send data length
Send data
:
BUFSND
No.n
:
:
Send data
No.16
Connected device
15.8 ZP.BUFSND
:
217
• Completion of the BUFSND instruction can be checked with Completion device (D1)+0 and (D1)+1.
Item
Completion device (D1)+0:
Description
Turns on at the END process of the scan where the BUFSND instruction is completed and
turns off at the next END process.
Turns on and off depending on the completion status of the BUFSND instruction.
Completion device (D1)+1:
• Normal completion: Stays off and does not change.
• Abnormal end: Turns on at the END process of the scan where the BUFSND instruction
is completed and turns off at the next END process.
[Operation while the BUFSND instruction is being executed]
Program
BUFSND instruction
Scan
END
process
Scan
END
process
Scan
END
process
Executed
Completion device
Completion device + 1
Abnormally ended
Sending data
• The ZP.BUFSND instruction is executed on the rising edge (OFF  ON) of the sending command.
Do not perform a send process using I/O signals and using the dedicated instruction together for the same connection.
Doing so will result in malfunction.
(5) Errors
If a dedicated instruction ends with an error, Completion device (D1)+1 turns on, and the error code is stored in
Completion status (S2)+1.
218
CHAPTER 15 DEDICATED INSTRUCTIONS
(6) Program example
The following shows a sample program that sends data stored on the fixed buffer of the connection number 1
(when the I/O signals of the E71 are X/Y00 to X/Y1F).
15
15.8 ZP.BUFSND
Process upon completion
Process upon abnormal end
219
15.9
ZP.BUFRCV
This instruction reads data received from the connected device through communications using a fixed buffer (used in
the main program).
Command
ZP.BUFRCV
ZP.BUFRCV
Un
(S1)
(S2)
(D1)
(D2)
Available device
Setting data*1
Internal device
(system, user)
File
register
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Word
(S1)



(S2)







(D1)














*1
Word
K, H
$


Others
Bit
(D2)
Bit
Constant


The file registers set for each local device and program cannot be used.
(1) Setting data
Setting data
Description
Set by
Start I/O number of the E71 (00 to FEH: The first two digits
Un/"Un"
of the three-digit I/O number)
(S1)
Data type
BIN 16-bit/character
string
User
Connection number (1 to 16)
BIN 16-bit
(S2)
Start number of the device that stores control data
Device name
(D1)
Start number of the device that stores receive data
The start number of the bit device in the own station that
(D2)
turns on for one scan upon completion of the instruction.
Device name
System
Bit
(D2)+1 also turns on if the instruction ends abnormally.
(2) Control data
Device
(S2)+0
Item
System area
Setting data
Setting range
Set by




System
Stores the status at completion.
(S2)+1
Completion
• 0000H: Normal completion
status
• Values other than 0000H: Abnormal end (error
code)
220
CHAPTER 15 DEDICATED INSTRUCTIONS
(3) Receive data
Device
Item
range
Stores the data length

of the data read from
Procedure exists (communications using a
the fixed buffer data
binary code): Number of words
area. (Depending on
(D1)+0
Setting
Setting data
Receive data
the procedure of fixed
length
buffer
Set by

Procedure exists (communications using
an ASCII code): Number of words
1 to 1017
1 to 508
System
communications, the
data length is the
No procedure (communications using a
number of words or
binary code): Number of bytes
1 to 2046
the number of bytes.)
(D1)+1
to
Receive data
(D1)+n
Stores the data read from the fixed buffer data area starting from
the smallest address.

System
(4) Functions
• This instruction reads the receive data (for fixed buffer communications) of the connection specified by (S1)
for the module specified by Un.
CPU module
15
E71
Fixed buffer data area
No.1
(D1) Receive data length
:
:
BUFRCV
15.9 ZP.BUFRCV
Receive data
No.n
:
:
Receive data
No.16
221
• Completion of the BUFRCV instruction can be checked with Completion device (D2)+0 and (D2)+1.
Item
Description
Completion device (D2)+0:
Turns on at the END process of the scan where the BUFRCV instruction is completed and
turns off at the next END process.
Turns on and off depending on the completion status of the BUFRCV instruction.
Completion device (D2)+1:
• Normal completion: Stays off and does not change.
• Abnormal end: Turns on at the END process of the scan where the BUFRCV instruction
is completed and turns off at the next END process.
[Operation while the BUFRCV instruction is being executed]
Scan
Program
BUFRCV instruction
END
process
Scan
END
process
Scan
END
process
Executed
Completion device
Completion device + 1
Receiving data
Abnormally ended
Storing the receive data
• The ZP.BUFRCV instruction is executed on the rising edge (OFF  ON) of the read command (bit for a
connection with the connected device set in Fixed buffer reception status signal (address: 5005H)).
● Do not perform a receive process using I/O signals and using the dedicated instruction together for the same connection.
Doing so will result in malfunction.
● When receive data is read from the same connection, the BUFRCVS instruction (for an interrupt program) cannot be
used together.
(5) Errors
If a dedicated instruction ends with an error, Completion device (D2)+1 turns on, and the error code is stored in
Completion status (S2)+1.
222
CHAPTER 15 DEDICATED INSTRUCTIONS
(6) Program example
The following shows a sample program that reads the receive data from the fixed buffer of connection number 1
(when the I/O signals of the E71 are X/Y00 to X/Y1F).
15
Process upon completion
15.9 ZP.BUFRCV
Process upon abnormal end
223
15.10
Z.BUFRCVS
This instruction reads data received from the connected device through communications using a fixed buffer (used in
an interrupt program).
Command
Z.BUFRCVS
Z.BUFRCVS
Un
(S1)
(D1)
Available device
Internal device
Setting data*1
(system, user)
File
register
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Word
K, H
Others
Bit
Word
(S1)







(D1)







*1
Bit
Constant
$
The file registers set for each local device and program cannot be used.
(1) Setting data
Setting data
Description
Set by
Start I/O number of the E71 (00 to FEH: The first two digits
Un/"Un"
BIN 16-bit/character
of the three-digit I/O number)
User
(S1)
Connection number (1 to 16)
(D1)
Start number of the device that stores receive data
Data type
string
BIN 16-bit
System
Device name
(2) Receive data
Device
Item
range
Stores the data length

of the data read from
Procedure exists (communications using
the fixed buffer data
a binary code): Number of words
area. (Depending on
(D1)+0
Setting
Setting data
Receive data
the procedure of fixed
length
buffer
Procedure exists (communications using
an ASCII code): Number of words
Set by

1 to 1017
1 to 508
System
communications, the
data length is the
No procedure (communications using a
number of words or
binary code): Number of bytes
1 to 2046
the number of bytes.)
(D1)+1
to
(D1)+n
224
Receive data
Stores the data read from the fixed buffer data area starting from
the smallest address.

System
CHAPTER 15 DEDICATED INSTRUCTIONS
(3) Functions
• This instruction reads the receive data (for fixed buffer communications) of the connection specified by (S1)
for the module specified by Un.
CPU module
E71
Fixed buffer data area
(D1) Receive data length
No.1
Receive data
:
:
BUFRCVS
No.n
:
:
Receive data
No.16
[Operation while the BUFRCVS instruction is being executed]
Scan
Program
END process
Interrupt program
15
Executed
BUFRCVS instruction
Receiving data
Storing
the receive data
• The Z.BUFRCVS instruction is executed in an interrupt program, and the process is completed within one
scan.
parameters of the programming tool. (
Page 131, Section 12.5.1)
● When receive data is read from the same connection, the BUFRCV instruction (for the main program) cannot be used
together.
(4) Errors
If a dedicated instruction ends with an error, Diagnostic errors (SM0) turns on, and the error code is stored in
SD0.
(5) Program example
The following shows a sample program that reads the receive data from the fixed buffer of connection number 2
(when the I/O signals of the E71 are X/Y00 to X/Y1F).
Enable the interrupt
program.
Execute the BUFRCVS
instruction.
225
15.10 Z.BUFRCVS
● To read receive data using an interrupt program, configure both the interrupt settings and interrupt pointer setting
15.11
ZP.ERRCLR
This instruction turns off LEDs of the E71 or clears error information stored in the buffer memory.
Command
ZP.ERRCLR
ZP.ERRCLR
Un
(S1)
(D1)
Available device
Setting data*1
Internal device
(system, user)
File
register
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Word
Others
Bit
Word
K, H
$
(S1)







(D1)







*1
Bit
Constant
The file registers set for each local device and program cannot be used.
(1) Setting data
Setting data
Un/"Un"
(S1)
Description
Start I/O number of the E71 (00 to FEH: The first two digits
of the three-digit I/O number)
Start number of the device that stores control data
Data type
Set by
User
User, system
BIN 16-bit/character
string
Device name
The start number of the bit device in the own station that
(D1)
turns on for one scan upon completion of the instruction.
(D1)+1 also turns on if the instruction ends abnormally.
226
System
Bit
CHAPTER 15 DEDICATED INSTRUCTIONS
(2) Control data
Device
(S1)+0
Item
Setting data
Setting range
Set by




System
As listed in the left
User
System area
Stores the status at completion.
(S1)+1
Completion
• 0000H: Normal completion
status
• Values other than 0000H: Abnormal end (error
code)
Specify error information to be cleared.
• 0000H: Initial error code
• 0001H to 0010H: Open error code for a connection
with the connected device
• 0100H: Error log block area
(S1)+2
Clear target
specification
• 0101H: Communication status - status for each
protocol
• 0102H: Communication status - e-mail receiving
status
• 0103H: Communication status - e-mail sending
status
• FFFFH: Clears all of the above
(S1)+3
Clear function
specification
Specify the function to be cleared.
0000H,
• 0000H: COM.ERR LED off, error code clear
FFFFH
• FFFFH: Error log clear
15
User
(S1)+4
to

System area


(S1)+7
• This instruction turns off the COM.ERR. LED and clears error information listed below for the module
specified by Un.
Target
Item
Function
specification specification
(S1)+2
(S1)+3
Initial error
0000H
0000H
Open error
0001H to 0010H
0000H
0100H
FFFFH
Status for each protocol
0101H
FFFFH
E-mail receiving status
0102H
FFFFH
E-mail sending status
0103H
FFFFH
FFFFH
FFFFH
Error log
Communication
status
All
Error information to be cleared
(buffer memory)
• Initial error code (address: 69H)
• COM.ERR. LED off
Open error code for a connection with the
connected device (address: 7CH, 86H...)
Error log (address: E3H to 174H)
Clears communication status.
(address: 178H to 1FFH)
E-mail receiving
(address: 5871H to 5B38H)
E-mail sending
(address: 5B39H to 5CA0H)
Clears all of the above.
227
15.11 ZP.ERRCLR
(3) Functions
• Completion of the ERRCLR instruction can be checked with Completion device (D1)+0 and (D1)+1.
Item
Completion device (D1)+0:
Description
Turns on at the END process of the scan where the ERRCLR instruction is completed and
turns off at the next END process.
Turns on and off depending on the completion status of the ERRCLR instruction.
Completion device (D1)+1:
• Normal completion: Stays off and does not change.
• Abnormal end: Turns on at the END process of the scan where the ERRCLR instruction
is completed and turns off at the next END process.
[Operation while the ERRCLR instruction is being executed]
Program
ERRCLR instruction
Scan
END
process
Scan
END
process
Scan
END
process
Executed
Completion device
Completion device + 1
Abnormally ended
Clearing the error
• The ZP.ERRCLR instruction is executed on the rising edge (OFF  ON) of the clear command.
(4) Errors
If a dedicated instruction ends with an error, Completion device (D1)+1 turns on, and the error code is stored in
Completion status (S1)+1.
228
CHAPTER 15 DEDICATED INSTRUCTIONS
(5) Program example
The following shows a sample program that clears the open error code of the connection number 1 (when the I/O
signals of the E71 are X/Y00 to X/Y1F).
Specify the open abnormal code of
connection 1.
Specify the error code clear.
Execute the ERRCLR instruction.
Process upon completion
(Error information is cleared.)
15
Process upon abnormal end
15.11 ZP.ERRCLR
229
15.12
ZP.ERRRD
This instruction reads error information stored in the buffer memory of the E71.
Command
ZP.ERRRD
ZP.ERRRD
Un
(S1)
(D1)
Available device
Setting data*1
Internal device
(system, user)
File
register
Bit
Word
(S1)



(D1)



*1
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Bit
Word
Constant
Others
K, H
$








The file registers set for each local device and program cannot be used.
(1) Setting data
Setting data
Un/"Un"
(S1)
Description
Start I/O number of the E71 (00 to FEH: The first two digits
of the three-digit I/O number)
Start number of the device that stores control data
Set by
User
User, system
Data type
BIN 16-bit/character
string
Device name
The start number of the bit device in the own station that
(D1)
turns on for one scan upon completion of the instruction.
(D1)+1 also turns on if the instruction ends abnormally.
230
System
Bit
CHAPTER 15 DEDICATED INSTRUCTIONS
(2) Control data
Device
(S1)+0
(S1)+1
Item
Setting data
Setting range
Set by




System
System area
Stores the status at completion.
Completion
• 0000H: Normal completion
status
• Values other than 0000H: Abnormal end (error code)
Specify error information to be read.
(S1)+2
Read information
• 0000H: Initial error code
specification
• 0001H to 0010H: Open error code for a connection
0000H, 0001H to
User
0010H
with the connected device
Read target
(S1)+3
Specify whether to read the latest error information.
information
• 0000H: Reads the latest error information.
specification
0000H
User

System


Stores the error information that has been read.
(S1)+4
Error information
• 0000H: No error
• Values other than 0000H (error code): Abnormal end
(S1)+5
to

System area
(S1)+7
15
(3) Functions
• This instruction reads the error information of the module specified for Un.
Function
specification
specification
(S1)+2
(S1)+3
Initial error
0000H
0000H
Open error
0001H to 0010H
0000H
Item
Error information to be read
(buffer memory)
15.12 ZP.ERRRD
Target
Initial error code (address: 69H)
Open error code for a connection with the
connected device
(address: 7CH, 86H...)
• Completion of the ERRRD instruction can be checked with Completion device (D1)+0 and (D1)+1.
Item
Completion device (D1)+0:
Description
Turns on at the END process of the scan where the ERRRD instruction is completed and
turns off at the next END process.
Turns on and off depending on the completion status of the ERRRD instruction.
Completion device (D1)+1:
• Normal completion: Stays off and does not change.
• Abnormal end: Turns on at the END process of the scan where the ERRRD instruction is
completed and turns off at the next END process.
[Operation while the ERRRD instruction is being executed]
Program
ERRRD instruction
Scan
END
process
Scan
END
process
Scan
END
process
Executed
Completion device
Completion device + 1
Abnormally ended
Reading the
error information
• The ZP.ERRRD instruction is executed on the rising edge (OFF  ON) of the read command.
231
(4) Errors
If a dedicated instruction ends with an error, Completion device (D1)+1 turns on, and the error code is stored in
Completion status (S1)+1.
(5) Program example
The following shows a sample program that reads the open error code of the connection number 1 (when the I/O
signals of the E71 are X/Y00 to X/Y1F).
Specify the open abnormal code of
connection 1.
Specify the latest error information.
Execute the ERRRD instruction.
Process upon completion
(Error information is read.)
Process upon abnormal end
232
CHAPTER 15 DEDICATED INSTRUCTIONS
15.13
ZP.UINI
This instruction changes the setting, such as the Ethernet operation setting, and re-initializes the E71.
Command
ZP.UINI
ZP.UINI
Un
(S1)
(D1)
Available device
Setting data*1
Internal device
(system, user)
File
register
Bit
Word
(S1)



(D1)



*1
Link direct device
Intelligent
Index
J\
function module
register
device U\G
Zn
Bit
Word
Constant
Others
K, H
$








The file registers set for each local device and program cannot be used.
15
(1) Setting data
Setting data
Un/"Un"
of the three-digit I/O number)
Start number of the device that stores control data
Set by
User
User, system
Data type
BIN 16-bit/character
string
Device name
15.13 ZP.UINI
(S1)
Description
Start I/O number of the E71 (00 to FEH: The first two digits
The start number of the bit device in the own station that
(D1)
turns on for one scan upon completion of the instruction.
System
Bit
(D1)+1 also turns on if the instruction ends abnormally.
233
(2) Control data
Device
Item
(S1)+0
System area
(S1)+1
Completion status
Setting data
Setting range
Set by



Stores the status at completion.
• 0000H: Normal completion
System
• Values other than 0000H: Abnormal end (error code)
Specify 0000H to update the address information on the connected
devices retained by the E71.
Specify the target for setting change among the own station IP
address, Ethernet operation setting, transmission speed, and
communication mode. Do not specify the transmission speed and
communication mode together with the own station IP address and
Ethernet operation setting. If doing so, only the specification of the
own station IP address and Ethernet operation setting is updated.
• Specification of own station IP address change (b0): Specify
whether to change the own station IP address.
(Set the address in (S1)+3 and (S1)+4.)
0: Do not change
(S1)+2
Specification of
changed item
0000H to
5000H
1: Change
User
• Specification of the Ethernet operation setting change (b1): Specify
whether to change the Ethernet operation setting.
(Set the parameters in (S1)+5.)
0: Do not change
1: Change
• Specification of transmission speed and communication mode
changes (b12 to b15): Specify the transmission speed and the
communicate mode.
0: Do not change
1: Auto negotiation
2: 100Mbps/full-duplex
3: 100Mbps/half-duplex
4: 10Mbps/full-duplex
5: 10Mbps/half-duplex
(S1)+3
Own station IP
(S1)+4
address
Specify the IP address of the own station.
00000001H to
FFFFFFFEH
User
Specify the Ethernet operation setting.
• Communication data code setting (b1)
0: Binary Code
1: ASCII Code
• TCP existence confirmation setting (b4)
0: Use the Ping
1: Use the KeepAlive
(S1)+5
Ethernet operation
setting
• Send frame setting (b5)
As listed in the
0: Ethernet
left
1: IEEE 802.3
User
• Setting of write enable/disable at RUN time (b6)
0: Disable
1: Enable
• Initial timing setting (b8)
0: Do not wait for OPEN (Communications impossible at STOP
time)
1: Always wait for OPEN (Communications possible at STOP time)
(S1)+6
(S1)+7
234
System area



CHAPTER 15 DEDICATED INSTRUCTIONS
*1
The E71 enables data exchange to be resumed by clearing the address information of the connected device retained in
the E71 and performing a reinitialization process. (Initial normal completion signal (X19) turns on.)
(3) Functions
• This instruction re-initializes the module specified by Un.
• Completion of the UINI instruction can be checked with Completion device (D1)+0 and (D1)+1.
Item
Description
Completion device (D1)+0:
Turns on at the END process of the scan where the UINI instruction is completed and turns
off at the next END process.
Turns on and off depending on the completion status of the UINI instruction.
Completion device (D1)+1:
• Normal completion: Stays off and does not change.
• Abnormal end: Turns on at the END process of the scan where the UINI instruction is
completed and turns off at the next END process.
[Operation while the UINI instruction is being executed]
Close process
Program
Scan
END
process
Scan
END
process
Scan
END
process
Scan
END
process
Scan
Initial normal completion
signal (X19)
15
Open completion signal
(address: 5000H)
UINI instruction
Executed
Completion device
15.13 ZP.UINI
Abnormally ended
Completion device + 1
Reinitialization specification
(address: 1FH (b15))
Processing reinitialization
Internal process of the E71
Requesting
reinitialization
Initializing the module
• The ZP.UINI instruction is executed on the rising edge (OFF  ON) of the reinitialization command.
To re-initialize the E71, note the following.
• Terminate all data communications with connected devices, check that all connections are closed, then reinitialize the E71.
• Do not perform a reinitialization process using both direct writing to the buffer memory and the UINI instruction.
Also, do not request another reinitialization process while reinitialization is being performed.
• When the IP address of the E71 has been changed, reset that of the connected device as well. (If the connected
device retains the MAC address of the destination device, the communications may not be continued after the IP
address of the E71 has been changed.)
235
(4) Errors
If a dedicated instruction ends with an error, Completion device (D1)+1 turns on, and the error code is stored in
Completion status (S1)+1.
(5) Program example
The following pages show sample programs that change the following setting items using the UINI instruction.
• Ethernet operation setting
• Transmission speed and communication mode
Remark
The following are sample programs for communications using connection numbers 1 and 2. When using other connections,
specify the corresponding signals and bits for each connection.
The UINI instruction is also used in the program for a reinitialization process. When performing a reinitialization
process using the UINI instruction, refer to the program for a reinitialization process. (
4.2)
236
Page 315, Appendix
CHAPTER 15 DEDICATED INSTRUCTIONS
(a) Changing the Ethernet operation setting
The following page provides a sample program that changes the Ethernet operation setting (enables writing
during RUN) (when the I/O signals of the E71 are X/Y00 to X/Y1F).
Specify the change
in the operation setting.
Read the current
operation setting.
Set "Enable Online
Change".
15
15.13 ZP.UINI
Process upon completion
Process upon abnormal end
Process upon completion
Process upon abnormal end
Communications enabled
237
(b) Changing the transmission speed and communication mode
The following page provides a sample program that changes the Ethernet operation setting (enables writing
during RUN) (when the I/O signals of the E71 are X/Y00 to X/Y1F).
Change the settings
to 10Mbps and
half-duplex.
Process upon completion
Process upon abnormal end
Process upon completion
Process upon abnormal end
Communications enabled
238
CHAPTER 16 TROUBLESHOOTING
CHAPTER 16 TROUBLESHOOTING
This chapter describes how to identify causes of problems that occur when an E71 is used and take corrective action.
16.1
Before Troubleshooting
Check that the POWER LED of the power supply module and the MODE LED of the CPU module are on. If either or
both are off, troubleshoot the CPU module.
User's Manual (hardware design, maintenance and inspection) for the CPU module used
16.2
Troubleshooting Procedure
How to identify the cause of a problem and take corrective action is explained below. Use a programming tool to
identify the cause and take corrective action.
(1) Procedure
1.
Connect the CPU module to a programming tool,
16
and open the "System Monitor" window.
[Diagnostics]
[System Monitor]
16.1 Before Troubleshooting
2.
When an error in the E71 is reported, select the E71
and click the
button.
When an error in a module other than the E71 is
reported, refer to the manual for that module.
239
3.
The "Module's Detailed Information" window is
displayed. Clicking the
button
displays the error details and corrective action.
4.
If the error details cannot be obtained in the step
above, perform the troubleshooting below.
 Checking the LEDs (
Page 242, Section 16.4)
 Troubleshooting by symptom
(
Page 245, Section 16.6)
 Ethernet Diagnostics (
240
Page 300, Section 16.8)
CHAPTER 16 TROUBLESHOOTING
16.3
Checking with the Module Error Collection Function
With the module error collection function, the errors that have occurred in the E71 are saved into the CPU module.
This allows error details to be held even if the power is turned off or the CPU module is reset. Check the E71's errors
collected by the CPU module on the "Error History" window.
[Diagnostics]
[System Monitor...]
button
16
16.3 Checking with the Module Error Collection Function
241
16.4
Checking the LEDs
The following describes how to troubleshoot the problem by checking the LEDs.
The on/off status of the INIT. LED, OPEN LED, ERR. LED, and COM.ERR. LED can be also checked with a programming
tool and in buffer memory.
• With a programming tool: "H/W Information" window (
Page 301, Section 16.9)
• In buffer memory: Area for module status (address: C8H) (
16.4.1
Page 35, Section 3.5.2)
If the RUN LED turns off
The following table lists the items to be checked and the actions to be taken if the RUN LED turns off after the E71 is
powered on.
Check item
Action
Reset the CPU module and check that the RUN LED turns on. If the RUN
Is it a watchdog timer error?
LED still does not turn on, the E71 may be faulty. Please consult your local
Mitsubishi representative.
Is the E71 connected properly?
Power off the E71, and connect the module properly.
Is the power capacity of the power supply module sufficient?
Check if the power supply module has enough power capacity.
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
Page 333, Appendix 6.2)
• Self-loopback test (
16.4.2
Page 332, Appendix 6.1)
If the ERR. LED or COM.ERR. LED turns on
Connect the CPU module connected to the E71 with the ERR. LED or COM.ERR. LED on to a programming tool to
identify the cause. (
Page 239, Section 16.2, Page 300, Section 16.8)
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
• Self-loopback test (
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
The COM.ERR. LED does not turn off even after the error cause is removed. To turn it off, refer to "How to Turn Off the
COM.ERR. LED". (
242
Page 303, Section 16.10)
CHAPTER 16 TROUBLESHOOTING
16.4.3
If the SD/RD LED does not flash when data is sent
The following table lists the items to be checked and the actions to be taken if the SD LED does not flash when data is
sent.
Check item
Is the ERR. LED or COM.ERR. LED on?
Action
Remove the cause that turned on the ERR. LED or COM.ERR. LED.
Check the cable connection. In addition, perform a line test to check if
Are the cables properly connected?
there is a problem with the cable connection and the Ethernet line.
(
Are the parameter settings correct?
Is the program correct?
Page 322, Appendix 5)
Correct the IP addresses of the own station and the communication
destination, router setting, and subnet mask setting.
Correct the send program of the connected device.
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
• Self-loopback test (
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
16
16.4 Checking the LEDs
16.4.3 If the SD/RD LED does not flash when data is sent
243
16.5
Checking with a Display Unit
With the buffer memory monitor/test of a display unit, a value in the buffer memory can be checked without a
programming tool, and a problem can be troubleshot.
For how to monitor buffer memory with a display unit, refer to the following.
MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)
244
CHAPTER 16 TROUBLESHOOTING
16.6
Troubleshooting by Symptom
The following describes how to troubleshoot for each phenomenon. When an error occurs in the E71, identify the
cause with the programming tool. (
16.6.1
Page 239, Section 16.2)
Communications cannot be performed with the connected
device.
The following table lists how to troubleshoot the problem when the E71 cannot communicate with the connected
device.
Check item
Action
Reset the CPU module. If resetting the CPU module does not turn on the
Is the RUN LED of the E71 on?
RUN LED on the E71, the hardware of the E71 may be faulty. Replace the
E71 and restart all the connected devices that were performing
communications with the own station.*1
Does the connected device conform to the Ethernet
Replace the device with one conforming to the Ethernet standard.
standard?
(
• Securely lock the cable.
Is the cable securely connected?
Is the network parameter mode set to "Online"?
Page 57, CHAPTER 5)
• Check the wiring. (
Page 62, Section 6.2)
16
Set the network parameter mode to "Online".
(
Page 66, Section 7.1.2)
If the data code settings do not match, data cannot be sent or received
setting match with that of the connected device?
because the connected device cannot normally decode commands.*2 Set the
same data code as that of the connected device in "Communication Data
Code" of the Ethernet operation setting.
(
Page 67, Section 7.1.3)
• If Initial normal completion signal (X19) is off, perform the initial process.
Has the initial process been completed normally? (Is Initial
normal completion signal (X19) on?)
(
Page 311, Appendix 4)
• If the initial setting of the programming tool is same as that of the initial
process program, delete the initial process program.
Was a device on the line (such as an E71, connected
device, hub, and router) replaced by the one with the same
Restart all the devices on the line.*1
IP address?
If the access from the connected device is denied by the IP filter function,
Is the access from the connected device set to be denied
correct the values in IP filter settings (address: 5700H to 5721H) and perform
by the IP filter function?
IP filter setting by the reinitialization process again. (
Page 175, Section
14.3)
245
16.6 Troubleshooting by Symptom
16.6.1 Communications cannot be performed with the connected device.
Does the communication data code (ASCII or binary)
*1
*2
*3
Devices on an Ethernet network contain the IP to Mac address mapping, called an "ARP cache". If a device on a line is
replaced by another device with the same IP address, the MAC address contained in the "ARP cache" and the MAC
address of the replaced device do not match; therefore, communications may not be performed normally. The "ARP
cache" is updated when the device is reset or after a certain period of time. The time varies depending on the devices.
If the communication data code setting is different between the E71 and the connected device, error codes that are not
found in the error code list may be returned to the connected device. When receiving data with different data codes, the
E71 cannot decode commands normally. The E71 returns an error response according to the communication data code
setting.
(
Page 137, Section 12.6.2 (1) (e), Remark)
If the LG and FG terminals of the power supply module on the E71-connected station are not connected, the
communication line may be closed (disconnected) due to noise; therefore, communications with the connected device
may not be performed.
If the action above does not solve the problem, check for an error in each communication process and take corrective
action.
(
246
Page 248, Section 16.6.4 to Page 257, Section 16.6.14)
CHAPTER 16 TROUBLESHOOTING
16.6.2
The E71 frequently fails to receive a message sent from the
connected device.
The following table lists how to troubleshoot the problem when the E71 frequently fails to receive a message sent from
the connected device.
Check item
Action
There may be a heavy load on the Ethernet line due to data sending and
Has the error code C0C7H been stored in Error code/end
receiving between connected devices.
• Taking action such as separating networks or decreasing the number of data
code (address: E5H ) in the error log block?
sending reduces the load on the Ethernet line.
• Consult the network administrator and reduce the load on the Ethernet line.
• Taking action such as separating networks or decreasing the number of data
sending reduces the load on the Ethernet line.
• When communications using a fixed buffer is used, check whether the
Has 1H been stored in Receive buffer full detection signal
BUFRCV instruction is executed. (
(address: 5240H)?*1
Page 125, Section 12.4.1)
• To receive data at shorter intervals than the scan time of the CPU module
using a fixed buffer, add the normally closed contact for the completion
device of the BUFRCV instruction to the execution conditions of the
BUFRCV instruction. (
Page 153, Section 12.9.3 (2) (b))
If the packets cannot be received even though the number of received TCP
Has the number in Received TCP packet count (address:
packets has increased, set the value of TCP Maximum Segment Transmission
1B8H and 1B9H) increased?
setting area (address: 1EH ) to 8000H. Then perform the initial process again.
(
*1
16
Page 311, Appendix 4)
Availability depends on the version of the E71. (
Page 310, Appendix 3)
• Hardware test (
• Self-loopback test (
16.6.3
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
A dedicated instruction is not completed.
The following table lists how to troubleshoot the problem when a dedicated instruction is not completed.
Check item
Action
Set the network parameter mode to "Online".
Is the network parameter mode set to "Online"?
(
Page 66, Section 7.1.2) (If a dedicated instruction is executed in the
"Offline" mode, no error occurs but the instruction is not completed.)
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
• Self-loopback test (
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
247
16.6 Troubleshooting by Symptom
16.6.2 The E71 frequently fails to receive a message sent from the connected device.
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
16.6.4
MC protocol communications cannot be performed.
The following table lists how to troubleshoot the problem when the E71 cannot perform MC protocol communications.
Check item
Action
• Open the connection with the connected device.
Has the connection with the connected device been opened?
• Check if the open/close process for I/O signals and the OPEN/CLOSE
(Check the corresponding bit of 5000H in the buffer
instructions are not used together for the same connection. If so, correct
memory.)*1
the program.
Did the connected device send a command?
Send a command to the E71.
• Check if the correct IP address was specified in the command. If not,
Was a response returned to the device that had sent the
correct the IP address and send the command again.
command?
• Check if the communication protocol (TCP/IP or UDP/IP) matches with
that of the connected device. If not, correct it.
Does the communication protocol (TCP/IP or UDP/IP) match
Use the same communication protocol (TCP/IP or UDP/IP) as that of the
with that of the connected device?
connected device.
If the data code settings do not match, data cannot be sent or received
Does the communication data code (ASCII or binary) setting
match with that of the connected device?
because the connected device cannot normally decode commands. *2Use
the same setting of "Communication Data Code" in the Ethernet operation
setting as that of the connected device.
(
Is the end code of the response 0?
Check the end and error codes to correct the error.
Is the correct command format used for the command type,
device, address, and others?
operation setting.
Has an open or initial error occurred in the error log area?
*2
Correct the command format.
Check the checkbox next to "Enable Online Change" in the Ethernet
Is the write operation during RUN enabled?
*1
Page 67, Section 7.1.3)
Check and correct the error.
If the connection of only the connected device is closed due to cable disconnection, personal computer restart, or other
reasons, reopen the connection using the same port used before the error occurred. The E71 does not close a
connection if it receives an Active open request again from the connected device with a different IP address or a port
number.
If the communication data code setting is different between the E71 and the connected device, error codes that are not
found in the error code list may be returned to the connected device. When receiving data with different data codes, the
E71 cannot decode commands normally. The E71 returns an error response according to the communication data code
setting.
(
Page 137, Section 12.6.2 (1) (e), Remarks)
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
• Self-loopback test (
248
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
CHAPTER 16 TROUBLESHOOTING
16.6.5
Communications using SLMP cannot be performed.
If communications cannot be performed with a connected device using SLMP, refer to the troubleshooting in the
following and take corrective action.
SLMP Reference Manual
16.6.6
Communications using the predefined protocol cannot be
performed.
The following table lists how to troubleshoot the problem when the E71 cannot perform communications using the
predefined protocol.
Check item
Action
• Open the connection with the connected device.
• Check if the open/close processes for I/O signals and the
Has the connection with the connected device been opened?
(Check the corresponding bit of 5000H in the buffer memory.)
OPEN/CLOSE instructions are not used together for the same
connection. If so, correct the program.
• Read Open error code (address: 7CH) in the communication status
storage area. Then check the error details and correct the error.
Is the IP address setting of the connected device correct?
Does the Protocol in the open setting match with that of the
connected device (TCP/IP or UDP/IP)?
Check and correct the IP address of the connected device.
16
Check and correct the settings if they are unmatched.
• Set "Predefined protocol" to Fixed Buffer Communication in the open
Is "Predefined protocol" set to Fixed Buffer Communication in
in the open setting matches the communication type of the protocol
(Send Only, Receive Only, or Send&Receive)*1.
Is Predefined protocol ready (X1D) on?
Write the protocol setting data to the E71.
Was the ECPRTCL instruction executed?
Correct the execution conditions of the ECPRTCL instruction.
Was the ECPRTCL instruction completed normally?
Check the error code in the ECPRTCL instruction completion status area
and correct the error.
Is the execution protocol number set to the control data of the
Set the execution protocol number to the control data of the ECPRTCL
ECPRTCL instruction?
instruction.
Is the communication status of the connected device normal?
Correct the error in the connected device.
Has an open or initial error occurred in the error log area?
Check and correct the error.
*1
For details on the settings, refer to Page 209, Section 15.7 (3).
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
• Self-loopback test (
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
249
16.6 Troubleshooting by Symptom
16.6.5 Communications using SLMP cannot be performed.
the open setting?
setting.
• Configure the setting so that the fixed buffer setting (Send or Receive)
16.6.7
The protocol setting data cannot be read or written.
The following table lists how to troubleshoot the problem when the protocol setting data cannot be read or written.
Check that GX Works2 and the CPU module are connectable on the Transfer Setup of GX Works2 before
troubleshooting the problem.
(1) To read the protocol setting data
Check item
Are the values in Protocol setting data error information
(address: 5324H to 5327H) and Number of registered
protocols (address: 5328H) set to 0?
Action
Write the protocol setting data to the E71 because they have not been
written.
(2) To write the protocol setting data
Check item
Action
Did the ERR.LED turn on after writing the protocol setting
Check the values in Protocol setting data error information (address: 5324H
data?
to 5327H) and correct the error.
When an error is detected in the edited protocol, check that the conditions for element placement are satisfied in the Packet
Setting.
Especially the following conditions must be satisfied.
• When a Non-conversion Variable (Variable length) or Non-verified Reception (Variable number of characters) is
placed behind a Length and is not included in the Length calculating range, place Static Data immediate after the
Non-conversion Variable or Non-verified Reception.
• When multiple Length elements are set in one packet, configure the setting so that each Length calculating range
does not overlap the others.
250
CHAPTER 16 TROUBLESHOOTING
16.6.8
Data cannot be sent with communications using a fixed
buffer.
The following table lists how to troubleshoot the problem when an E71 cannot send data with communications using a
fixed buffer.
Check item
Action
• Open the connection with the connected device.
• Check if the open/close processes for I/O signals and the OPEN/CLOSE
Has the connection with the connected device been opened?
(Check the corresponding bit of 5000H in the buffer memory.)
instructions are not used together for the same connection. If so, correct
the program.
• Read Open error code (address: 7CH) in the communication status
storage area. Then check the error details and correct the error.
Is the IP address setting of the connected device correct?
Check and correct the IP address of the connected device.
Does the communication protocol (TCP/IP or UDP/IP) match
Use the same communication protocol (TCP/IP or UDP/IP) as that of the
with that of the connected device?
connected device.
• Correct the execution conditions of the BUFSND instruction.
• Check if the send/receive process for I/O signals and the
Was the BUFSND instruction executed?
BUFSND/BUFRCV instructions are used together for the same
connection. If so, correct the program.
Was the BUFSND instruction completed normally?
Has the data length of the send data been set in the control
data?
Is the communication status of the connected device
normal?
Has an open or initial error occurred in the error log area?
Check the error code in the BUFSND instruction completion status area
and correct the error.
Write the data length.
16
Correct the error in the connected device.
Check and correct the error.
• Hardware test (
• Self-loopback test (
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
251
16.6 Troubleshooting by Symptom
16.6.8 Data cannot be sent with communications using a fixed buffer.
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
16.6.9
Data cannot be received with communications using a fixed
buffer.
The following table lists how to troubleshoot the problem when an E71 cannot receive data with communications using
a fixed buffer.
Check item
Action
Does the receive data length match with the amount of data
actually received?
If the amount of the actually received data is smaller than the receive data
length, receive the remaining data. If it is larger than the receive data
length, receive the excess data as the next request message or discard it.
• Open the connection with the connected device.
• Check if the open/close processes for I/O signals and the OPEN/CLOSE
Has the connection with the connected device been opened?
(Check the corresponding bit of 5000H in the buffer memory.)
instructions are not used together for the same connection. If so, correct
the program.
• Read Open error code (address: 7CH) in the communication status
storage area. Then check the error details and correct the error.
Is the IP address setting of the connected device correct?
Check and correct the IP address of the connected device.
Does the communication protocol (TCP/IP or UDP/IP) match
Use the same communication protocol (TCP/IP or UDP/IP) as that of the
with that of the connected device?
connected device.
Is the receive status signal of the corresponding fixed buffer
on? (Check the corresponding bit of 5005H in the buffer
memory.)
Data was not sent from the connected device. Check the connected device
on the sending side and correct the error.
• Correct the execution conditions of the BUFRCV instruction.
• Check if the send/receive processes for I/O signals and the
Was the BUFRCV instruction executed?
BUFSND/BUFRCV instructions are not used together for the same
connection. If so, correct the program.
Was the BUFRCV instruction completed normally?
Check the error code in the BUFSND instruction completion status area
and correct the error.
• Correct the interrupt setting of the programming tool.
• Check if the send/receive processes for I/O signals and the
Was the BUFRCVS instruction executed?
BUFSND/BUFRCV instructions are not used for the same connection. If
so, correct the program.
Is the control data of the BUFRCVS instruction correct?
Correct the control data.
Has an open or initial error occurred in the error log area?
Check and correct the error.
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
• Self-loopback test (
252
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
CHAPTER 16 TROUBLESHOOTING
16.6.10
Communications using a random access buffer cannot be
performed.
The following table lists how to troubleshoot the problem when an E71 cannot perform communications using a
random access buffer.
Check item
Action
• Open the connection with the connected device.
Has the connection with the connected device been opened?
(Check the corresponding bit of 5000H in the buffer memory.)
• Check if the open/close process for I/O signals and the OPEN/CLOSE
instructions are used together for the same connection. If so, correct the
program.
Did the connected device send a command?
Send a command to the E71.
• Check if the correct IP address was specified in the command. If not,
Was a response returned to the device that had sent the
command?
correct the IP address and send the command again.
• Check if the communication protocol (TCP/IP or UDP/IP) matches with
that of the connected device. If not, correct it.
Is the end code of the response 0?
Check the end and error codes to correct the error.
Is the correct buffer memory address specified for the
command?
Has data been set in the specified address of the random
access buffer?
Correct the buffer memory address and send the command again.
Write the data.
Has the write data been set in the connected device?
Set the data.
Has an open or initial error occurred in the error log area?
Check and correct the error.
16
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
16.6 Troubleshooting by Symptom
16.6.10 Communications using a random access buffer cannot be performed.
• Self-loopback test (
Page 333, Appendix 6.2)
Page 332, Appendix 6.1)
253
16.6.11
The access cannot be allowed/denied correctly by the IP filter.
The following table lists how to troubleshoot the problem when the access cannot be allowed/denied correctly by the IP
filter.
Check item
Action
Is the setting value in IP filter function type setting (address:
Correct the value in IP filter function type setting (address: 5701H) and
5701H) correct?
perform IP filter setting by the reinitialization process again.
Are the setting values in IP address setting 1 to 8 (address:
Correct the values in IP address setting 1 to 8 (address: 5702H to 5721H)
5702H to 5721H) correct?
and perform IP filter setting by the reinitialization process again.
Is the IP address of the proxy server set to be allowed?
Set the IP address of the proxy server to be denied.
254
CHAPTER 16 TROUBLESHOOTING
16.6.12
An e-mail cannot be sent.
The following table lists how to troubleshoot the problem when an E71 cannot send an e-mail.
(1) When sending an e-mail with a program
Check item
Was the MSEND instruction executed?
Was the MSEND instruction completed normally?
Is the error response received from the mail server using the
MRECV instruction?
Action
Correct the execution conditions of the MSEND instruction.
Check the error code in the MSEND instruction completion status area and
the e-mail sending error log to correct the error.
Check with the system administrator that the following settings are correct:
• DNS setting
• E-mail setting
If the action above does not solve the problem, check the following.
• Is the e-mail parameter setting of the E71 correct?
• Is the mail server system down?
• Is there any error in the communication path?
(2) When sending an e-mail with the programmable controller CPU monitoring
function
Check item
16
Action
Are the monitoring conditions satisfied?
Check the notification setting with the programming tool.
Was the first sending performed using the programmable
Check if there is any device outside the range of the device settings among
controller CPU monitoring function?
the condition devices and correct the condition device.
longer than the value set in "PLC Inquiry Interval".
• PLC Inquiry Interval
Were the second and subsequent sendings performed using
the programmable controller CPU monitoring function?
• Condition Device
Correct the following so that the sending time of the SMTP server and the
E71 becomes shorter than the value set in "PLC Inquiry Interval".
• Reduce the load on the SMTP server.
• When the SMTP server and the E71 are connected via routers or other
devices, connect the E71 to the same main line as the SMTP server.
If the action above does not solve the problem, check the following.
• Is the e-mail parameter setting of the E71 correct?
• Is the mail server system down?
• Is there any error in the communication path?
255
16.6 Troubleshooting by Symptom
16.6.12 An e-mail cannot be sent.
Correct the following so that the monitoring condition disable time becomes
16.6.13
An e-mail cannot be received.
The following table lists how to troubleshoot the problem when an E71 cannot receive an e-mail.
Check item
Was the MRECV instruction executed?
Was the MRECV instruction completed normally?
Action
Correct the execution conditions of the MSEND instruction.
Check the error code in the MRECV instruction completion status area and
correct the error.
• Shorten the inquiry interval.
Does the receive data exist in the device?
• Check if there is any error in the communication path.
• Check the number of e-mails remaining on the mail server.
Is the receive data value incorrect? (Are the characters in the
subject garbled?)
• Check and correct the e-mail parameter settings.
• Check if the mail server system is down.
• Check if there is any error in the communication path.
If EUC or SHIFT-JIS is used, perform the following:
• Send an e-mail from a personal computer to the own station.
• Check the header information of the received e-mail sent by the own
Is a device other than the E71 sending the data?
station.
For Outlook Express, select "Properties"  "Details". In the header
information, check that the setting is "Content-Type:text-plain:charset=iso2022jp". If it is "charset=EUC-jp" or "charset=SHIFT-JIS", correct it.
Is the E71 sending the data?
Because the E71 does not decode received data, it cannot receive an email normally. Try to send an e-mail from a device other than the E71.
Check the following.
• Convert the e-mail attachment into the binary code and send it.
• Check if the sent data (e-mail attachment) is not in the ASCII code.
Did the sending device send the e-mail in the ASCII code or
convert the ASCII code further into the ASCII code?
• When the destination is a personal computer, use another mailer. If the
received e-mails differ depending on the mailer used, check the mailer
settings.
• Check if the encoding and decoding methods of the mail server differs
from those of Ethernet.
256
CHAPTER 16 TROUBLESHOOTING
16.6.14
Communications using data link instructions cannot be
performed.
The following table lists how to troubleshoot the problem when an E71 cannot perform communications using data link
instructions.
Check item
Action
Is the communication status of the connected device
normal?
Correct the error of the connected device.
Is the number of resends set upon every instruction
Modify the program to set the number of resends upon every instruction
execution?
execution.
Does an error occur even after the arrival monitoring time is
increased?
Does an error occur even after the setting value in "TCP
Resend Timer" in the initial setting is increased?
Are the routing parameter settings correct?
Check and correct the arrival monitoring time.
Check and correct the setting value in "TCP Resend Timer".
Check the routing parameters and correct the error.
Set the "Station No.<->IP Information" setting in the network parameter
Is the Station No. <->IP information setting configured?
window. (
MELSEC-Q/L Ethernet Interface Module User's Manual
(Application))
If the action above does not solve the problem, perform the following tests on the E71 to check for hardware error.
• Hardware test (
• Self-loopback test (
Page 333, Appendix 6.2)
16
Page 332, Appendix 6.1)
16.6 Troubleshooting by Symptom
16.6.14 Communications using data link instructions cannot be performed.
257
16.7
Error Code List
This section describes the error codes (abnormal codes) of the errors that may occur in each process for performing
communications between the E71 and a connected device as well as errors caused by process requests issued from
the CPU module of the own station, the error details, and the actions to be taken. The following table lists the types of
errors that may occur.
Error type
Errors occurring in the initial process
Errors occurring in the open process
Errors occurring in communications using a
fixed buffer (sending) with the connected
device
Description
• Setting value error
• Initial process error
• Setting value error
• Open process error
Buffer memory area that
stores the error code
Page 259, Section 16.7 (1)
Page 259, Section 16.7 (2)
• Specified data error
Page 259, Section 16.7 (3),
• Sending error
Page 259, Section 16.7 (4)
• Specified data error
Errors occurring in communications using a
fixed buffer with the connected device
• Communication error (excluding errors occurring in
communications using a fixed buffer (sending) with
Page 259, Section 16.7 (4)
the connected device)
• Errors returned in communications using a fixed
buffer (end code)
Errors returned to the connected device when
communicating with it

• Errors returned in communications using a random
access buffer (end code)
Errors returned in communications using the MC
End code or error code for each
protocol
command
• Specified data error
Errors occurring while communicating with the
• Errors where the source cannot be found
destination (including the causes in the
• Errors that have occurred in MC protocol
"Description" column), and whose error codes
are stored in the error log area
communications
Page 260, Section 16.7 (5)
• Errors that have occurred in communications using
a random access buffer
Errors occurring in data communications
• Setting data error
Page 261, Section 16.7 (6)
using the predefined protocol
• Receiving error
Page 263, Section 16.7 (7)
Errors (response commands) occurring in
communications with the destination using the
file transfer (FTP server) function
Errors occurring in communications using the
Web function
Errors occurring when an e-mail is received
Errors occurring when an e-mail is sent
Errors occurring in communications using
data link instructions from the CPU module of
the own station
Errors occurring in communications using the
dedicated instructions from the CPU module
of the own station
258
• Specified data error
• Communication error
Communication error
• Setting data error
• Receiving error
• Setting data error
• Sending error
MELSEC-L CPU Module
User's Manual (Built-In Ethernet
Function)
Page 264, Section 16.7 (8)
Page 265, Section 16.7 (9) (a)
Page 267, Section 16.7 (9) (b)
• Specified data error
Not stored (stored in the complete
• Communication error
status area of the instructions)
• Specified data error
Not stored (stored in the complete
• Communication data error
status area of the instructions)
CHAPTER 16 TROUBLESHOOTING
(1) Initial error code (address: 69H)
The error codes generated when the initial process is executed are stored. Error codes are stored in binary when
Initial abnormal end signal (X1A) is on. The error codes are cleared when Initial normal completion signal (X19)
turns on, but can be also cleared by the following processes:
• Resetting or powering off the CPU module
• Writing 0 to the initial error code storage area using a program
(2) Open error code (address: 7CH to C1H, 5824H to 5869H)
The result of the open process for connection with the connected device is stored in binary.
• 0: Normal completion
• Values other than 0: Abnormal end (Open abnormal detection signal (X18): ON)
The error codes are cleared by the following operations:
• Reopening the connection that caused an open error
• Powering off and on or resetting the CPU module
(3) Fixed buffer sending error code (address: 7DH to C2H, 5825H to 586AH)
The error codes generated when an error has occurred in data sending to the destination during communications
using a fixed buffer in the connection with the connected device are stored. A sending error code is cleared when
the next data sending is completed normally.
16
(4) Connection end code (address: 7EH to C3H, 5826H to 586BH)
The codes returned in the responses from the destination during communications using a fixed buffer in the
the destination.
259
16.7 Error Code List
connection with the connected device are stored in binary. Process the end codes in the responses according to
(5) Error log area (address: E0H to 1FFH)
The following table lists the details of the error log area. The buffer memory addresses of the error log block are
those of the error log block 1. For the addresses of the error log block 2 and later, refer to the list of buffer memory
addresses. (
Buffer memory
name
Page 35, Section 3.5.2)
Address
E3H
Number of errors
Description
The number of errors registered in the error log block area is stored. When the number of
errors reaches 65536, the count stops at FFFFH(65535).*1
The number of the error log block where the latest error log is registered is stored.
• 0: No error (no registration of error log)
• 1 or more: The number of the error log block where the latest error log is registered.
Error log write pointer
E4H
If the pointer value is 16, it means that the latest error log is registered in the error log block
16 area. When the number of errors reaches 17, the error log is then registered in the error
log block 1 area again.*2
An error code indicating error details is stored. The subheader code of the error message is
Error
code/end
E5H
stored in bits 0 to 7 of the corresponding area. (Bits 8 to 15 store 0.) For errors below the
TCP/IP or UDP/IP level, 0 is stored.
code
The command code of the error message or the values of the lower bytes of the request type
and subrequest type of the data link instructions are stored.
Command
code
b15
E7H
to
Command code
b0
b15
or
to
b8 b7
Subrequest type
to
b0
Request type
0 is stored in the following cases:
• For messages not containing a command code
Error log
• For errors below the TCP/IP or UDP/IP level (because their commands are unknown)
block
Connection
No.
Own station
port No.
Destination
IP address
Destination
Port No.
Status for each protocol
*1
*2
E8H
E9H
The number of the error connection is stored in bits 0 to 7 of the corresponding area. (Bits 8
to 15 store 0.) For errors below the TCP/IP or UDP/IP level, 0 is stored.
The port number of the error own station is stored. For errors below the TCP/IP or UDP/IP
level, 0 is stored.
The IP address of the error connected device is stored. 0 is stored in the following cases:
EAH and EBH
• For errors below the IP level
• When an error response was sent through the CPU module
ECH
178H to 1FFH
The IP address of the error connected device is stored. For errors below the TCP/IP or
UDP/IP level, 0 is stored.
The number of occurrences of the corresponding status of each protocol is stored. When the
count value by the E71 exceeds two words, the count stops at FFFFFFFFH (4294967295).
The error information is continued to be stored into the following areas even if the count of the errors is stopped:
• Error log write pointer storage area
• Error log block
An error log block area consists of 16 error log blocks that have the same data order.
Values stored in the buffer memory are cleared when an E71-connected station is powered on or reset. (They are not
cleared during the initial process.) Although this area does not normally need to be read, read it when necessary for
maintenance or other purposes.
260
CHAPTER 16 TROUBLESHOOTING
(6) Protocol setting data check area (address: 5320H to 533FH)
The following table lists the details of the protocol setting data check area.
Buffer memory name
Address
Description
When an error is detected in the protocol setting data, the protocol No. where an error has
been detected is stored.
The protocols are checked from the lowest protocol No. and the first protocol No. where an
Protocol No.
5324H
error has been detected is stored.
• 0: No errors
• 1 to 128: Protocol No.
• 65535: Unidentified *1
When an error is detected in the Packet Setting or Element Setting, 0 is stored.
When an error is detected in the Protocol Detailed Setting, 1 is stored.
Setting type
5325H
(Valid when the Protocol No. value is 1 to 128)
• 0: Packet setting or element setting
• 1: Protocol detailed setting
• 65535: Unidentified*1
Protocol
setting data
When an error is detected in the protocol setting data, the packet No. where an error has been
error
detected is stored.
information
The send packet is checked first, then receive packet (expected packet) is checked from the
Packet No.
5326H
lowest packet No. and the first packet No. where an error has been detected is stored.
(Valid when the Setting type value is 0)
• 0: Send packet
• 1 to 16: Receive packet
16
• 65535: Unidentified*1
When an error is detected in the protocol setting data, the element No. where an error has
been detected is stored.
The elements are checked from the lowest element No. and the first element No. where an
5327H
16.7 Error Code List
Element No.
error has been detected is stored.
(Valid when the Setting type value is 0)
• 1 to 32: Element No.
• 65535: Unidentified*1
Number of registered protocols in the protocol setting data is stored.
Number of registered
protocols
5328H
When the check results include any error, 0 is stored.
• 0: No registration
• 1 to 128: Number of registrations
261
Buffer memory name
Address
Description
The information about whether protocol setting data has been registered is shown by on/off
status of the corresponding bit.
When the check results include any error, 0 is stored in all bits.
Registration status of
protocol No.16
b15 b14 b13
to
Buffer memory address 5330H
to
5331H
to
5337H
to
0 (OFF): Not registered
1 (ON): Registered
Protocol registration
Registration status of
protocol No.1
5330H to
533FH
Registration status of
protocol No.128
Registration status of
protocol No.113
5338H
to
533FH
to
Unused
(reserved)
*1
262
b2 b1 b0
When the setting value gets Unidentified (65535), the following causes are possible:
 When settings undetectable with the E71 used are written
 When the protocol setting data is broken (hardware failure)
CHAPTER 16 TROUBLESHOOTING
(7) Predefined protocol support function execution status check area (address:
54C0H to 55FFH)
The following table lists the details of the predefined protocol support function execution status check area.
The buffer memory addresses are those of Connection No.1. For the addresses of the Connection No.2 and later,
refer to the list of buffer memory addresses. (
Buffer memory name
Page 35, Section 3.5.2)
Address
Description
The status of protocols being executed in Connection No.1 is stored.
• 0: Unexecuted
• 1: Waiting for transmission
Protocol execution status
54C0H
• 2: Sending
• 3: Waiting for data reception
• 4: Receiving
• 5: Completed
Received data verification
result (receive packet No.1)
Received data verification
result (receive packet No.2
to 16)
Verification result of receive packet No.1 is stored. (
54C2H
Page 263, Section 16.7 (7) (a))
• b0 to b7: Element No. where the verification result did not match
• b8 to b15: The cause of mismatch (verification result code)
54C3H to
54D1H
The bit configuration is the same as receive packet No.1.
The number of protocol executions in Connection No.1 is stored.
Number of protocol
executions
54D2H
• 0: No protocol execution
• 1 to 65535: Number of executions (When the number exceeds 65535, the value remains
65535.)
16
Cancels the protocol executed in Connection No.1.
Protocol cancellation
specification
54D3H
• 0: No cancellation specification
• 1: Cancellation request (set by user)
16.7 Error Code List
• 2: Cancel completed (set by the system)
(a) Received data verification result
The following information is stored in Received data verification result.
• Element No. where the verification result did not match (b0 to b7)
Stored value
Description
0
Verification matched
1 to 32
Element No. where the verification result did not match
FFH
Verification not performed
• The cause of mismatch (verification result code) (b8 to b15)
Stored value
Description
00H
Normal
01H
Insufficient receive data
10H
Data not matched
11H
ASCII-binary conversion error
12H
Data length error
30H
Data length size error
FFH
Verification not performed
Cause
The total packet size of receive data is smaller than that set in protocol
data.
The receive data do not match the value set in protocol data.
When "ASCII Hexadecimal" is set in Code Type, data not in ASCII code
are received.
The received Length value exceeded 2046 bytes.
The Length value received from the connected device does not match the
actual length.
-
263
(8) HTTP status storage area (address: 5101H to 5177H)
The following table lists the HTTP status storage areas. The buffer memory addresses of the error log block are
those of the error log block 1. For the addresses of the error log block 2 and later, refer to the list of buffer memory
addresses. (
Buffer memory
name
Page 35, Section 3.5.2)
Address
Description
The number of the error log block where the latest error log is registered is stored.
• 0: No error (no registration of error log)
• 1 or more: The number of the error log block where the latest error log is registered.
5101H
Error log pointer
If the pointer value is 16, it means that the latest error log is registered in the error log block
16 area. When the number of errors reaches 17, the error log is then registered in the error
log block 1 area again.*1
5102H to 5106H
Log counter
The number of times the HTTP response code was returned from the E71 to the Web
browser is stored.
HTTP
response
5108H
The HTTP response code in case of an error is stored.
5109H to 510AH
The IP address of the server in case of an error is stored.
code
Destination
IP address
The time when the error occurred is stored in the BCD code.
b15
Error log
block
to
b8 b7
Month (01H to 12H)
b15
Error time
510BH to 510EH
to
b8 b7
to
b15
to
b0
b0
Day (01H to 31H)
b8 b7
Second (00H to 59H)
to
b0
Minute (00H to 59H)
b8 b7
Year (00H to 99H): First two digits of the year
264
to
Hour (00H to 23H)
b15
*1
to
Year (00H to 99H): Last two digits of the year
to
Day of the week (0 to 6)
An error log block area consists of 16 error log blocks that have the same data order.
b0
CHAPTER 16 TROUBLESHOOTING
(9) E-mail status storage area (address: 5870H to 5FFFH)
When the stored count exceeds FFFFH, the count starts from 0H again. The following table lists the details of the
e-mail status storage area. The buffer memory addresses of the error log block are those of the error log block 1.
For the addresses of the error log block 2 and later, refer to the list of buffer memory addresses.
(
Page 35, Section 3.5.2)
(a) Receive area
Buffer memory name
Address
Description
The number of remaining e-mails returned when the E71 inquired the receive mail server
Number of mails remaining on
the server
is stored.
5870H
• 0: No received mail in the server
• 1 to 15: The number of mails remaining in the server
• 16: The number of mails in the server is 16 or more.
The cumulative number of normal completions of the dedicated instruction (MRECV) is
Dedicated instruction normal
completion count
stored.
5871H
• 0: The MRECV instruction has not been executed or no executions have resulted in
normal completion.
• 1 or more: The cumulative number of normal completions of the MRECV instruction
The cumulative number of abnormal ends of the dedicated instruction (MRECV) is
Dedicated instruction abnormal
completion count
stored.
5872H
• 0: The MRECV instruction has not been executed or no executions have resulted in
abnormal end.
• 1 or more: The cumulative number of abnormal ends of the MRECV instruction
The cumulative number of received e-mails forwarded by the E71 to the mail buffer data
Normal receiving count
5873H
area is stored.
• 0: No mail has been transferred.
5874H
• 0: No e-mail with an attachment has been received.
• 1 or more: The number of normal reception of e-mails with an attachment
The cumulative number of inquiries to the receive mail server according to the parameter
Server inquiry count
5875H
setting is stored.
• 0: No inquiry has been made to the server.
• 1 or more: The cumulative number of inquiries to the server
The cumulative number of communication errors returned in response to inquiries to the
Server communication error
count
5876H
receive mail server is stored.
• 0: No communication error between servers or no inquiry
• 1 or more: The cumulative number of communication errors
The cumulative number of registrations in the receiving error log block area is stored.
Error log write count
5877H
• 0: No error or no inquiry to the server
• 1 or more: The cumulative number of writes to the error log block area
The number of the error log block where the latest receiving error log is registered is
stored.
• 0: No error (no registration of error log)
Receiving error log write
pointer
5878H
• 1 or more: The number of the error log block where the latest error log is registered.
If the pointer value is 16, it means that the latest error log is registered in the receiving
error log block 16 area. When the number of errors reaches 17, the error log is then
registered in the error log block 1 area again.*1
265
16.7 Error Code List
• 1 or more: The number of normal mail transfer completions
The cumulative number of e-mails with an attachment received by the E71 is stored.
Attached file receiving count
16
Buffer memory name
Address
Description
Error code
5879H
An error code indicating the error details is stored.
Command code
587AH
The system command code of the error message is stored.
The first eight words of the sender's e-mail address of the error e-mail in the
587BH
From
communications with the mail server are stored in the ASCII code.
(Example) If the sender's e-mail address is "use@from.add.sample.co.jp",
"use@from.add.sam" is stored in the ASCII code.
The date and time when the e-mail was received are stored in the BCD code.
b15
Error log
to
b8 b7
Month (01H to 12H)
block
b15
5883H
Date
to
b8 b7
Hour (00H to 23H)
b15
to
to
*1
266
5887H
to
b8 b7
b0
to
b0
Minute (00H to 59H)
b8 b7
Year (00H to 99H): First two digits of the year
Subject
b0
Day (01H to 31H)
Second (00H to 59H)
b15
to
Year (00H to 99H): Last two digits of the year
to
b0
Day of the week (0 to 6)
The first 30 words of the e-mail subject are stored. A subject is not stored successfully if
it contains characters other than alphanumeric and ASCII code characters.
A receiving error log block area consists of 16 error log blocks that have the same data order.
CHAPTER 16 TROUBLESHOOTING
(b) Send area
Buffer memory name
Address
Description
The cumulative number of normal completions of the dedicated instruction
(MSEND) is stored.
Dedicated instruction normal
completion count
5B39H
• 0: The MSEND instruction has not been executed or no executions have
resulted in normal completion.
• 1 or more: The cumulative number of normal completions of the MSEND
instruction
The cumulative number of abnormal ends of the dedicated instruction (MSEND) is
Dedicated instruction abnormal
completion count
stored.
5B3AH
• 0: The MSEND instruction has not been executed or no executions have
resulted in abnormal end.
• 1 or more: The cumulative number of abnormal ends of the MSEND instruction
The cumulative number of sent e-mails forwarded by the E71 to the send mail
Number of mails normally
completed
5B3BH
server is stored.
• 0: No mail has been sent.
• 1 or more: The number of normal completions of mail sending
The cumulative number of e-mails with an attachment sent by the E71 is stored.
Attached file sending count
5B3CH
• 0: No e-mail with an attachment has been sent.
• 1 or more: The number of normal sending of e-mails with an attachment
The cumulative number of e-mails sent by the E71 to the send mail server is
Sending to the server count
5B3DH
stored.
• 0: No e-mail has been sent to the server.
• 1 or more: The cumulative number of sending e-mails to the server
The cumulative number of communication errors returned in response to send
Number of mails abnormally
completed
5B3EH
16
requests to the send mail server is stored.
• 0: No communication error between servers or no e-mail sent
• 1 or more: The cumulative number of communication errors
5B3FH
• 0: No error or no inquiry to the server
• 1 or more: The cumulative number of writes to the error log block area
The number of the error log block where the latest send error log is registered is
stored.
• 0: No error (no registration of sending error log)
• 1 or more: The number of the error log block where the latest sending error log
Sending error log write pointer
5B40H
is registered.
If the pointer value is 8, it means that the latest error log is registered in the
receiving error log block 8 area. When the number of receiving errors reaches
nine, the error log is then registered in the error log block 1 area again.*1
Error code
5B41H
An error code indicating the error details is stored.
Command code
5B42H
The system command code of the error message is stored.
The first eight words of the receiver's e-mail address of the error e-mail in the
5B43H
To
Error log block
communications with the mail server are stored in the ASCII code.
(Example) If the sender's e-mail address is "use@from.add.sample.co.jp",
"use@from.add.sam" is stored in the ASCII code.
Date
5B4BH
Subject
5B4FH
The date and time when the e-mail was sent are stored in the BCD code (similar to
5883H of (a)).
The first 15 words of the e-mail subject are stored. A subject is not stored
successfully if it contains characters other than alphanumeric and ASCII code
characters.
*1
A sending error log block area consists of 16 error log blocks that have the same data order.
267
16.7 Error Code List
The cumulative number of registrations in the send error log block area is stored.
Error log write count
16.7.1
End codes returned to a connected device during data
communications
The following table lists the error codes stored in the end code appended to a response during data communications.
: Stored in the end code appended to a response
Data communication type
Error
Error description
code
Action
MC protocol
communications
Communications
Communications
using a fixed
using a random
buffer
access buffer




When each
00H
• Normal completion
communication is
normally completed, the

error code 00H is stored.
• The device range destination of
02H
devices to be read/written from/to is
incorrect.
• Check and correct the
specified start device
and the number of

points.
• Codes for the command/response
type of a subheader are not within the
specifications.
50H
• Check and correct the
MC protocol communications: 00H to
command/response
3CH
type set for the
Communications using a fixed buffer:
connected device.
60H
(Because the E71
Communications using a random access
automatically adds
buffer: 61H, 62H
the
• In communications using a fixed
buffer, if the data length setting is
smaller than the actual data amount,
the remaining data is processed as the
second data. In this case, a subheader

command/response
type, the user setting
is not required.)
• Check and correct the
data length.
undefined command type error may
occur.
• In communications using a random
access buffer, the start address
51H
• Check and correct the
specified by a connected device has
specified start
been set outside the range from 0 to
address.

6143.
• In communications using a random
access buffer, the start address and
the number of data words (depending
on the setting when reading data)
specified by a connected device
52H
exceeds the range from 0 to 6143.
• Data by the number of words specified
(text) cannot be sent in one frame.
(The data length value or the amount
of the text sent/received are not in the
allowable range.)
268
• Check and correct the
start address and the
number of data
words.
• Correct the number of
read/write points.


CHAPTER 16 TROUBLESHOOTING
Data communication type
Error
Error description
code
Action
MC protocol
communications
Communications
Communications
using a fixed
using a random
buffer
access buffer


• When "ASCII Code" has been
selected in the communication data
54H
code setting in the Ethernet operation
setting, ASCII code data which cannot
be converted into binary code data has
• Check and correct the
data sent from the

connected device.
been sent from the connected device.
• Enable (select)
"Enable Online
• When "Enable Online Change" was
55H
Change" in the
disabled (or not selected) in the
Ethernet operation
Ethernet operation setting, the
setting and write data.
connected device requested a data
(However, a
write while the CPU module was
parameter, program,
running.
or microcomputer
• While the CPU module was running,
the connected device requested for
writing a parameter, program, or
microcomputer program.

program cannot be
written while the CPU
module is running.)
• Set the switch on the
CPU module to STOP
and write the data.
56H
• The connected device specified a
wrong device.
• Correct the device
specification.

16
16.7 Error Code List
16.7.1 End codes returned to a connected device during data communications
269
Data communication type
Error
code
Error description
Action
MC protocol
communications
• The number of points for a command
specified by a connected device
exceeds the maximum number of
processing points (number of
processes that can be executed per
communication) for each process.
• Addresses from the start address
(start device number and start step
number) to the specified number of
• Correct the specified
points or the start
address (device

number and step
number).
points exceed the largest addresses
(device number and step number) for
each process.
• The byte length of a command is not
within the range defined by the
specifications.
57H
• When data is written, the set number
of write data points is different from the
• Check the data length
of the command and

set the data again.
specified number of points.
• A monitor request was issued even
though monitoring data is not
registered.
• Register the
monitoring data.

• Data cannot be read
• For data read/write in a microcomputer
from/written to an
program, an address after the last
area with an address
address that can be set in the
after the last address.
parameter setting has been specified.
Correct the specified

address.
• In the block number specification of
the extension file register, a block
number exceeding the range of the
corresponding memory cassette size
• Correct the block
number.

has been specified.
• The start address (start device number
and start step number) of a command
specified by a connected device has
• Correct the value to
been set outside the range that can be
the one within the
specified.
range that can be
• For data read/write in a microcomputer
program or file register, values

specified for each
process.
exceeding the CPU module parameter
setting range has been specified.
58H
• A block number specified for an
extension file register does not exist.
• A file register cannot be specified.
• Correct the block
number.
• Correct the device
specification.


• A word device has been specified for
the command for bit devices.
• The start number of bit devices has
• Correct the command
been specified using a value other
or specified device.
than a multiple of 16 in the command
for word devices.
270

Communications
Communications
using a fixed
using a random
buffer
access buffer
CHAPTER 16 TROUBLESHOOTING
Data communication type
Error
Error description
code
Action
MC protocol
communications
• An extension file register cannot be
59H
specified.
• The CPU module and the E71 cannot
communicate.
5BH
• The CPU module cannot process a
request from a connected device.
60H
• Correct the device
specification.
Communications
Communications
using a fixed
using a random
buffer
access buffer



• Check the error code
appended to the end
code and correct the

error.
• The communication time between the
• Increase the CPU
CPU module and the E71 exceeded
monitoring timer
the CPU monitoring timer value.
value.

• After unlocking the
remote password
using the MC
protocol, perform
• In communications using a fixed
buffer, the remote password of the port
63H
for the destination E71 is in the lock
status.
communications
using a fixed buffer.
• Exclude ports used
for communications
using a fixed buffer
from the targets of the
remote password
check.
A0H
to
FFFFH
The error details and how to troubleshoot the problem are the same as those for the error code stored in the buffer memory.
(
16
Page 273, Section 16.7.3)
16.7 Error Code List
16.7.1 End codes returned to a connected device during data communications
271
16.7.2
Abnormal codes returned during communications using an Acompatible 1E frame
The following table lists the error codes stored in the abnormal code appended to a response in the A-compatible 1E
frame in MC protocol communications. (An abnormal code is appended only when an end code is 5BH.)
Response format
Subheader
End code
Abnormal code
00H
If an abnormal code is stored,
"5BH" is stored here.
Error
Error
code
10H
PC number error
Error description
Action
The PC number specified with a command is not
Change the PC number to FFH of the own station
FF of the own station or not the station number set
or not the station number set using the link
with the MELSECNET link parameters.
parameter to perform communications again.
After the E71 receives a request from the
11H
Mode error
connected device normally, communications
Perform communications again. If the error occurs
cannot be normally performed between the E71
again, check for noise and other causes and/or
and the CPU module due to some causes such as
replace the E71.
noise.
The specified intelligent function module number
12H
Intelligent function
has not been assigned to an intelligent function
module designation
module that has the buffer memory and where
error
communications can be performed. (For example,
the specified module is an I/O module or empty.)
The remote RUN/STOP cannot be executed. (The
18H
Remote error
remote STOP/PAUSE has been already executed
from another module.)
1FH
Device error
Invalid device specification
Change the specified data contents in the control
procedure or change the connecting position of the
intelligent function module. Then perform
communications again.
Check if the remote STOP/PAUSE has been
already executed from another module. Then
cancel the operation to perform communications
again.
• Correct the specified device.
• Do not access a device which does not exist.
Check if the CPU module of the station number set
20H
Link error
The CPU module of the request destination has
for the PC number has been disconnected. Then
been disconnected from the data link.
remove the cause of the disconnection to perform
communications again.
Memory access to the intelligent function module
21H
Intelligent function
module bus error
cannot be performed due to the following causes:
• The control bus to the intelligent function module
is faulty.
• The intelligent function module is in failure.
272
There is a hardware problem with the CPU
module, intelligent function module, or the E71.
Please consult your local Mitsubishi
representative.
CHAPTER 16 TROUBLESHOOTING
16.7.3
Error codes stored in the buffer memory
The following table lists the error codes stored in each buffer memory area when an error occurs. For the buffer
memory areas where these error codes are stored, refer to the descriptions of the corresponding buffer memory area.
(
Page 35, Section 3.5.2)
Error code
Error description
Action
00H
02H
0050H
0051H
0052H
0054H
0055H
The error details and how to troubleshoot the problem are the same as those for the end code returned to the connected
device in data communications. (
Page 268, Section 16.7.1)
0056H
0057H
0058H
0059H
• The CPU module and the Ethernet module cannot
005BH
communicate.
• The programmable controller CPU cannot process the
• Check the error code appended to the end code and
correct the error.
16
request from the connected device.
• The communication time between the CPU module and
0060H
the Ethernet module exceeded the CPU monitoring timer
• Increase the CPU monitoring timer value.
value.
0063H
password of the port for the destination Ethernet module
is in the lock status.
00A0H
00A1H
00A2H
3E8H to
4FFFH
7000H to
7FFFH
B000H to
BFFFH
• After unlocking the remote password using the MC
protocol, perform communications using a fixed buffer.
• Exclude ports used for communications using a fixed
buffer from the targets of the remote password check.
This request cannot be specified in connection with the
• Correct the request details.
connected device.
• Correct the open setting.
Contents of the request cannot be analyzed because the
text length or request data length is too short.
This request cannot be processed.
• Check and correct the text length or request data length of
the Qn header. Then send data to the Ethernet module
again.
• Correct the request details and command.
• Refer to the troubleshooting section of the user's manual
(Errors detected by a programmable controller CPU)
(hardware design, maintenance and inspection) for the
CPU module used, and take corrective action.
(Errors detected by a module such as a serial
communication module)
(Errors detected by a CC-Link module)
• Refer to a manual such as a serial communication module
user's manual, and take corrective action.
• Refer to the CC-Link System Master/Local Module User's
Manual, and take corrective action.
• The IP address setting value of the E71 for the initial
C001H
process is incorrect.
• The setting value of the subnet mask field for the router
• Correct the IP address. Set the class to A/B/C.
• Correct the subnet mask.
relay function is incorrect.
C002H
C003H
Some of the various timer setting values for the initial
process are outside the allowable range.
The setting value of the auto-open UDP port number for
the initial process is outside the allowable range.
• Check and correct each timer setting value for the initial
process.
• Check and correct the auto-open UDP port number.
273
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
• In communications using a fixed buffer, the remote
Error code
C004H
Error description
The setting value of the subnet mask field is incorrect.
Action
• Correct the subnet mask and perform the initial process
again.
• The setting value of the default router IP address for the
router relay function is incorrect.
C005H
• The network address (network address after the subnet
mask) of the default router IP address is different from
that of the IP address of the Ethernet module in the own
• Correct the default router IP address and perform the
initial process again.
• Set the same network address as that of the IP address of
the Ethernet module in the own station.
station.
C006H
The setting value of the subnet address for the router relay
function is incorrect.
• The setting value of the router IP address for the router
relay function is incorrect.
C007H
• The network address (network address after the subnet
mask) of the router IP address is different from that of
the IP address of the Ethernet module in the own station.
C008H
The setting value in IP filter function type setting (address:
5701H) is not correct.
• Correct the subnet address and perform the initial process
again.
• Correct the router IP address and perform the initial
process again.
• Change the IP address of the Ethernet module in the own
station to the same address as the network address.
Correct the value in IP filter function type setting (address:
5701H) and perform IP filter setting by the reinitialization
process again.
• A value out of range is set in IP address setting 1 to 8
(address: 5702H to 5721H).
C009H
• In IP address setting 1 to 8 (address: 5702H to 5721H),
the value of start IP address is greater than the end IP
Correct the values in IP address setting 1 to 8 (address:
5702H to 5721H) and perform IP filter setting by the
reinitialization process again.
address.
C00EH
The send/receive process has been executed while the IP
Do not execute the send/receive process while executing
address in use detection function is being executed.
the IP address in use detection function.
• Set different IP addresses.
C00FH
One IP address is used for two or more modules.
The MAC addresses of the Ethernet modules in the stations
with the same IP address can be checked in IP address
status storage area (5281H to 5286H).
C010H
C011H
C012H
C013H
C014H
C015H
The setting value of the Ethernet module port number for
the open process is incorrect.
The setting value of the port number of the connected
device for the open process is incorrect.
The port number set is used in a connection already
opened in TCP/IP.
The port number used in a connection already opened is
set for the open process in UDP/IP.
The initial process or open process of the Ethernet module
is not completed.
The setting value of the IP address of the connected
device for the open process is incorrect.
The open process of the connection (or the next
C016H
connection) specified for pairing open has been already
completed.
• Correct the port number.
• Correct the port number.
• Correct the port numbers of the Ethernet module and the
connected device.
• Correct the port number of the Ethernet module.
• Perform the initial process or open process.
• Correct the IP address. Set the class to A/B/C.
• Check that none of the connections targeted for pairing
open has been opened.
• Correct the combination of modules set for pairing open.
• Check the operation of the connected device.
• Check the open process of the connected device.
• Correct the open setting of the communication
C017H
A connection could not be established in the open process
of the TCP connection.
parameters.
• Correct the port number of the Ethernet module, the IP
address and port number of the connected device, and the
open setting.
• Check if the cable is disconnected.
274
CHAPTER 16 TROUBLESHOOTING
Error code
C018H
Error description
The setting value of the IP address of the connected
device is incorrect.
Action
• Correct the IP address.
• Correct the data length.
C020H
The data length exceeds the allowable range.
• When the amount of data to be sent exceeds the limit,
An abnormal end response was received for
• Read the response end code from the connection end
divide the data into smaller chunks to send it.
C021H
communications using a fixed buffer.
• A response could not be received within the response
C022H
monitoring timer value.
• The connection with the connected device was closed
while waiting for a response.
code or error log area and perform the required action.
• Check the operation of the connected device.
• Correct the response monitoring timer value.
• Check the open status of the connection with the
connected device.
• The connection with the connected device has not been
C023H
opened.
• The connection with the connected device has been
• Open the connection with the connected device.
closed.
When "Predefined protocol" is set in "Fixed Buffer
Communication" setting, communications using a fixed
C024H
buffer or a random access buffer are executed.
When "Procedure Exist" or "No Procedure" is set in "Fixed
Buffer Communication" setting, a predefined protocol is
executed.
There is an error in the usage setting area when starting
C025H
the open process by the OPEN instruction or input/output
signals.
• Correct the connection number of
BUFSND/BUFRCV/BUFRCVS/ECPRTCL instructions.
• Correct the "Fixed Buffer Communication" setting
(Procedure Exist/No Procedure/Predefined protocol) of
the corresponding connection.
• When starting the open by using the OPEN instruction,
correct the usage setting area of the control data.
• When starting the open by input/output signals, correct the
connection usage setting area of the buffer memory.
16
• Check that connection cable with the engineering tool is
C026H
An error has occurred when reading/writing/verifying the
protocol setting data again.
• Do not write data simultaneously when writing protocol
setting data from multiple engineering tools.
• Because there may be congestion of packets on the line,
send data after a certain period of time.
C030H
A sending error has occurred.
• Check if the cable is disconnected.
• Perform the self-diagnostics test to check for an error in
the Ethernet module.
• Because there may be congestion of packets on the line,
send data after a certain period of time.
C031H
A sending error has occurred.
• Check if the cable is disconnected.
• Perform the self-diagnostics test to check for an error in
the Ethernet module.
• Check the operation of the connected device.
A TCP ULP timeout error has occurred in the TCP/IP
C032H
communication. (The connected device does not send an
ACK response.)
• Correct the TCP ULP timeout value and perform the initial
process again.
• Because there may be congestion of packets on the line,
send data after a certain period of time.
• Check if the cable is disconnected.
• Correct the IP address of the connected device and the
Ethernet address.
• Use the default value (FFFFFFFFFFFFH) if the connected
C033H
There is no connected device with the IP address that has
been set.
device has the ARP function. If it does not have the
function, set the MAC address.
• Check the operation of the connected device.
• Because there may be congestion of packets on the line,
send data after a certain period of time.
• Check if the cable is disconnected.
275
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
predefined protocol setting data.
not disconnected and read/write/verify the predefined
Error code
C034H
C035H
Error description
On the ARP table, there is no connected device with the IP
address that has been set.
The existence of the connected device could not be
checked within the response monitoring timer value.
Action
Decrease the number of communication destinations.
• Check the operation of the connected device.
• Correct the settings of the alive check.
• Check if the cable is disconnected.
• Check if the cable is disconnected.
C036H
Because a cable is not connected or disconnected, the
• Perform the loopback test to check for an error in the line.
send process cannot be executed.
• Perform the self-diagnostics test to check for an error in
the Ethernet module.
• Not all the data could be received within the response
monitoring timer value.
C040H
• Sufficient data for the data length could not be received.
• The remaining part of the message divided at the
TCP/IP level could not be received within the response
• Correct the data length of the communication data.
• Because there may be congestion of packets on the line,
correct the settings of the initial process.
• Send the same data from the connected device again.
monitoring timer value.
• Correct the checksum value sent from the connected
C041H
There is an error in the checksum of the receive data when
TCP is used.
device and send the correct value.
• Check the situation of the line, such as noise, the distance
between the line and power cable, and the grounding of
each device.
• Correct the checksum value sent from the connected
C042H
There is an error in the checksum of the receive data when
UDP is used.
device and send the correct value.
• Check the situation of the line, such as noise, the distance
between the line and power cable, and the grounding of
each device.
• Correct the checksum value sent from the connected
C043H
The checksum in the header of the IP packet received is
incorrect.
device and send the correct value.
• Check the situation of the line, such as noise, the distance
between the line and power cable, and the grounding of
each device.
C044H
An error packet of ICMP was received.
C045H
An error packet of ICMP was received.
C046H
An error packet of ICMP was received.
C047H
An error packet of ICMP was received.
C048H
An error packet of ICMP was received.
• Check the operation of the connected device.
• Check if the cable is disconnected.
• Check the operation of the connected device.
• Check if the cable is disconnected.
• Check the operation of the connected device.
• Check if the cable is disconnected.
• Check the operation of the connected device.
• Check if the cable is disconnected.
• Check the operation of the connected device.
• Check if the cable is disconnected.
• Check the operation of the connected device.
• Because there may be congestion of packets on the line,
C049H
An error packet of ICMP was received.
send data after a certain period of time.
• Check if the cable is disconnected.
• If an alive check timeout occurs, correct the IP assembly
timer value of the connected device.
• Check the operation of the connected device.
• Because there may be congestion of packets on the line,
C04AH
An error packet of ICMP was received. (An IP assembly
timeout error has occurred in the connected device.)
send data after a certain period of time.
• Check if the cable is disconnected.
• If an alive check timeout occurs, correct the IP assembly
timer value of the connected device.
276
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Check the operation of the connected device.
An IP assembly timeout error has occurred. (The
C04BH
remaining part of the divided data could not be received
and a timeout has occurred.)
Because there may be congestion of packets on the line,
send data after a certain period of time.
• Check if the cable is disconnected.
• Correct the IP assembly timer value and perform the initial
process again.
C04CH
• Because there is no space in the internal buffer, such as
the IP header buffer, data cannot be sent.
• Send the same data again and check the receipt of a
response.
• In communications using an auto-open UDP port or
communications using a fixed buffer in the "No
C04DH
Procedure" control method, there is an error in the data
length specified in the application data of the message
received by the Ethernet module.
• Correct the data length.
• Correct the text size so that the text data size is within the
receive buffer memory size.
• Not all the receive data can be stored.
When "ASCII Code" has been selected in the
communication data code setting in the Ethernet operation
C050H
setting, ASCII code data which cannot be converted into
binary code data has been sent from the connected
device.
C051H
C052H
C053H
C054H
range.
The number of read/write points is outside the allowable
range.
The number of read/write points is outside the allowable
range.
The number of read/write points is outside the allowable
range.
• The number of file data read/write points is outside the
allowable range.
Then restart the Ethernet module to perform
communications again.
• Check and correct the data sent from the connected
device and send it again.
• Correct the number of read/write points and send the data
to the Ethernet module again.
• Correct the number of read/write points and send the data
to the Ethernet module again.
• Correct the number of read/write points and send the data
to the Ethernet module again.
to the Ethernet module again.
• Correct the number of read/write points (or the number of
bytes) and send the data to the Ethernet module again.
• Correct the start address or the number of read/write
C056H
• The read/write request exceeds the largest address.
points and send the data to the Ethernet module again.
• The address is 0.
(Make sure that the request does not exceed the largest
address.)
C057H
C058H
C059H
C05AH
C05BH
C05CH
C05DH
The request data length does not match with the number of
data in the character (a part of text).
• Check and correct the text or requested data length of the
Qn header. Then send the data to the Ethernet module
again.
The request data length after the ASCII/binary conversion
• Check and correct the text or requested data length of the
does not match with the number of data in the character (a
Qn header. Then send the data to the Ethernet module
part of text).
again.
Incorrect designation of the command and subcommand
The Ethernet module cannot read/write data from/to the
specified device.
The Ethernet module cannot read/write data from/to the
specified device.
Incorrect request (For example, a request for data
read/write in bit units has been issued to a word device.)
The monitor registration is not performed.
16
• Correct the number of read/write points and send the data
• Correct the request details.
• Check the device for read/write.
• Check the device for read/write.
• Correct the request details and send it to the Ethernet
module again. (For example, change the subcommand.)
• Register the monitoring data and perform monitoring.
277
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
C055H
The number of read/write points is outside the allowable
• Select "Binary Code" in the Ethernet operation setting.
Error code
Error description
Action
• Increase the CPU monitoring timer value.
• Check that the programmable controller CPU is operating
The communication time between the Ethernet module
C05EH
and the programmable controller CPU exceeded the CPU
monitoring timer value.
normally.
• Correct the network number or PC number.
• If the destination is a station with a different network
number, correct the routing parameter setting.
• If the destination is a station with a different network
number, check if the network number is not in use.
C05FH
C060H
C061H
This request cannot be executed to the target
• Correct the network number or PC number.
programmable controller.
• Correct the read/write request details.
Incorrect request (For example, incorrect data was
• Correct the request details and send it to the Ethernet
specified for bit devices.)
The request data length does not match with the number of
data in the character (a part of text).
When writing was prohibited while the CPU was running,
C062H
module again. (For example, correct the data.)
• Check and correct the text or requested data length of the
Qn header. Then send the data to the Ethernet module
again.
• To write data to the remote I/O station using the MC
data has been written to the remote I/O station using the
protocol (with a QnA-compatible 3E frame or 4E frame),
MC protocol (with a QnA-compatible 3E frame or 4E
select "Enable Write at RUN time" in the Ethernet
frame).
operation setting.
• Read/write data without the device memory set for
extension.
C070H
The device memory cannot be extended for the target
station.
• Device memory can be extended only in an Ethernet
module-connected station and a Q/QnACPU via CC-Link
IE Controller Network, MELSECNET/H, or
MELSECNET/10.
C071H
The number of device points for data read/write set for
modules other than a Q/QnACPU is too large.
• Correct the number of device points for data read/write
and send the data to the Ethernet module again.
• Check whether the data can be requested to the target
C072H
Incorrect request (For example, a request for data
read/write in bit units has been issued to a word device.)
programmable controller CPU.
• Correct the request details and send it to the Ethernet
module again. (For example, change the subcommand.)
The Ethernet module cannot issue this request to the
C073H
target programmable controller CPU. (For example, the
number of double word access points cannot be specified
• Correct the request details.
for modules other than a Q/QnACPU.)
C074H
This request cannot be executed to the target
• Correct the network number or PC number.
programmable controller CPU.
• Correct the read/write request details.
• Set the Station No. <-> IP information in the Ethernet
The destination IP address could not be obtained during
C080H
CC-Link IE Controller Network, CC-Link IE Field Network,
module.
• Change the conversion method for the CC-Link IE
MELSECNET/H, MELSECNET/10 relay communications
Controller Network, CC-Link IE Field Network,
or communications using data link instructions.
MELSECNET/H, and MELSECNET/10 relay
communication parameters.
The termination process for the Ethernet module is in
C081H
process, and whether communications using data link
instructions have reached cannot be checked.
278
• Finish all the communications to perform the termination
process of the Ethernet module.
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Check if the relay station/connected station is operating
normally. (If the communication is alive, no action for this
The communication process was abnormally ended in the
following communications.
C082H
• Communications with a programming tool (UDP/IP)
• CC-Link IE Controller Network, CC-Link IE Field
Network, MELSECNET/H, MELSECNET/10 relay
communications
error is required.)
• Check if there is an error with the cable connection
between the own station and the connected station.
• If the line is heavily loaded, reduce the load.
• Increase the number of resends for the data link
instructions.
• Increase the time reserved for the communication process
in the service processing setting in "PLC System" under
"PLC Parameter".
• Check if the relay station/connected station is operating
normally. (If the communication is alive, no action for this
error is required.)
C083H
The communication process was abnormally ended in
communications using data link instructions.
• Check if there is an error with the cable connection
between the own station and the connected station.
• If the line is heavily loaded, reduce the load.
• Increase the time reserved for the communication process
in the service processing setting in "PLC System" under
"PLC Parameter".
• Check if the own station/relay station/connected station is
running normally.
• Check if there is a problem with the cable connection
C084H
The communication process was abnormally ended in
communications using data link instructions.
between the own station and the connected station.
• Increase the TCP resend timer value.
• Increase the time reserved for the communication process
16
in the service processing setting in "PLC System" under
"PLC Parameter".
The own station's channel specified by another station in
communications using data link instructions is currently in
• Execute the request from another station again.
use.
C086H
A message exceeding the receive message size was
received.
There is an error in the IP address set in the Station No. <-
C087H
• In the Station No.<->IP information setting, set the IP
> IP information setting for CC-Link IE Controller Network,
addresses for the CC-Link IE Controller Network, CC-Link
CC-Link IE Field Network, MELSECNET/H,
IE Field Network, MELSECNET/H, and MELSECNET/10
MELSECNET/10 relay communications.
relay communication target devices.
There is no insufficient space in the receive buffer of the
C0B2H
• Correct the send message size of the request source.
relay station PC number for MELSOFT connection or data
link instructions, or the communication request destination
station. (Receive buffer full error)
• Increase the request interval.
• Decrease the number of request nodes.
• Wait for a response to the previous request before
sending the next request.
• Correct the timeout value.
A request that cannot be processed was issued from the
• Correct the request details.
programmable controller CPU.
• Correct the network number or PC number.
Data that cannot be processed by the programmable
• Correct the request details.
controller CPU or Ethernet module was specified.
• Cancel the current request.
C0B6H
The channel number is outside the allowable range.
• Specify the channel number from 1 to 8.
C0B7H
A channel number currently in use was specified.
C0B3H
C0B5H
• Change the channel number.
• Perform communications again after the current
communications are completed.
• The network number or PC number is outside the
C0B8H
allowable range.
• A response from the programmable controller CPU is
• Correct the network number or PC number.
• Check the programmable controller CPU operation.
faulty.
279
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
C085H
Error code
Error description
Action
• Perform the open process.
C0B9H
The open process of the TCP connection has not been
completed.
• Check the operation of the connected device.
• After sending a close request (FIN) from the connected
device to the E71, perform the open process again and
wait for 500ms or more.
C0BAH
Because the close process is in process using the CLOSE
instruction, a send request cannot be accepted.
• Perform the open process and send the request.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0BBH
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C0BCH
C0BDH
The specified communication line is closed.
Requests have been accepted successively and cannot be
sent.
• Open the communication line.
• Correct the target connection number.
• Check if requests have been sent successively without
waiting for a response.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0BEH
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0BFH
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C0C0H
C0C1H
280
The open process of the UDP connection has not been
• Perform the open process.
completed.
• Check the operation of the connected device.
The transmission interval of UDP is too short.
• Check if a send request is being repeatedly issued.
• Increase the send interval.
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0C2H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0C3H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C0C4H
The UINI instruction has been executed during
communications.
• Execute the UINI instruction after closing all connections.
• Enable the router relay function and perform the initial
process.
• A send request was issued to the connected device with
C0C5H
the class/network address different from those of the
own station when the router relay function is not used.
• Set the correct data in the router relay parameter.
• Correct the IP address of the connected device and
perform the open process.
• Check if the network address is correct.
• After changing the network address, perform the initial
process again.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0C6H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Take action such as separating networks or decreasing
the number of data sending to reduce the load on the
Ethernet line.
• Consult the network administrator and reduce the load on
C0C7H
An Ethernet module system error has occurred.
the Ethernet line.
• Perform the self-diagnostics test to check for an error in
the Ethernet module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
281
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
• The setting of the router relay parameter is incorrect.
16
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0C8H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0C9H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0CAH
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C0CBH
Another send request was issued before the send process
has not been completed.
• Wait for completion of transmission before sending the
next send request.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0CCH
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
282
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0CFH
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C0D0H
Incorrect data length was specified.
• Correct the specified data length.
C0D1H
The number of resends is incorrect.
• Correct the number of resends.
C0D2H
The arrival monitoring time is incorrect.
• Correct the arrival monitoring time.
• Check the specified value for the communication
The number of relay stations in CC-Link IE Controller
C0D3H
Network, CC-Link IE Field Network, MELSECNET/H, and
MELSECNET/10 exceeded the allowable range.
destination.
• Correct the settings in the Station No. <-> IP information
for the stations between the own station and the
communication destination.
• Check the specified value for the communication
The number of relay stations in CC-Link IE Controller
C0D4H
Network, CC-Link IE Field Network, MELSECNET/H, and
MELSECNET/10 exceeded the allowable range.
destination.
• Correct the settings in the Station No. <-> IP information
for the stations between the own station and the
communication destination.
C0D5H
The number of retries is incorrect.
C0D6H
The network number or station number is incorrect.
16
• Correct the number of retries.
• Correct the settings for the communication destination.
• Correct the specified value for the communication
them to the CPU module. Then perform communications
C0D7H
Data were sent without the initial process completed.
with the connected device.
• Wait for normal completion of the initial process before
performing communications with the connected device.
C0D8H
The number of blocks exceeded the range.
• Correct the specified value for the number of blocks.
C0D9H
The subcommand value is incorrect.
• Correct the specified value for the subcommand.
• Correct the IP address and host name of the Ethernet
C0DAH
A response to the PING test could not be received within
the time of the communication time check.
module where the PING test is executed.
• Enable the Ethernet module where the PING test is
executed to perform communications. (Complete the initial
process.)
C0DBH
The IP address and host name of the Ethernet module for
the PING test are incorrect.
• Correct the IP address and host name of the Ethernet
module to perform the PING test.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0DCH
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
283
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
destination.
• Set the parameters with the programming tool and write
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0DDH
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Correct the specified arrival monitoring time.
C0DEH
Data could not be received within the specified arrival
• Correct the specified channel number.
monitoring time.
• Check the status of the send source station and relay
station.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0DFH
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E0H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E1H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E2H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
284
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E3H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E4H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E5H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
16
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
C0E6H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E7H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E8H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
285
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
• Check that the programmable controller CPU is not in the
Error code
Error description
Action
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0E9H
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0EAH
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0EBH
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0ECH
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0EDH
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0EEH
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
286
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Check that the programmable controller CPU and each
intelligent function module are properly connected.
• Check that the programmable controller CPU is not in the
C0EFH
An error was detected in the programmable controller
CPU.
reset status.
• Check if an error exists in the programmable controller
CPU. If an error exists, take the action required to correct
it.
• Replace the power supply module, programmable
controller CPU, or intelligent function module.
C0F0H
C0F1H
C0F3H
An Ethernet module RAM error was detected in the
hardware test (H/W test).
An Ethernet module ROM error was detected in the
hardware test (H/W test).
A system error (major error) was detected in the CPU
module.
• Perform the hardware test again. If an error occurs again,
the Ethernet module may have a hardware error. Please
consult your local Mitsubishi representative.
• Perform the hardware test again. If an error occurs again,
the Ethernet module may have a hardware error. Please
consult your local Mitsubishi representative.
• Remove the error cause of the CPU module in the own
station.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0F4H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
16
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0F5H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0F6H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Because there may be congestion of packets on the line,
send data from the connected device after a certain period
C0F7H
An error has occurred in the self-loopback test.
of time.
• Check if the cable is disconnected.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
287
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
• Follow the procedure below.
(1)
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C0F8H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C100H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Check the address of the DNS server.
• Check if communications with the DNS server can be
C101H
A response could not be received from the DNS client.
performed using the PING command.
• Check if the IP addresses of the own station and the DNS
server belong to the same class. (If they belong to
different classes, check the router setting.)
• Check if the SMTP server name has been registered in
the DNS.
C102H
A response from the SMTP layer could not be received.
• Delete the SMTP server name and change the setting to
the IP address setting. Then check the operation.
• Check if communications with the SMTP server can be
performed using the PING command.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C103H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C104H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
288
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C105H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C106H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
16
module conforms to the general specifications of the
C110H
CPU module.
System error (The OS detected an error.)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Check the cables and hubs.
C111H
A response could not be received from the DNS client.
• Check if communications with the DNS server can be
performed using the PING command.
• Check if the POP3 server name has been registered in the
DNS.
C112H
A response from the POP3 layer could not be received.
• Delete the POP3 server name and change the setting to
the IP address setting. Then check the operation.
• Check if communications with the POP3 server can be
performed using the PING command.
• Specify the attachment on the sending side.
• Check the program on the sending side.
• If data sending using the MSEND instruction previously
failed with the sending source of the mail server, check the
C113H
An e-mail without an attachment was received. (This error
occurs when an attachment is not read normally.)
destination of the MSEND instruction.
• Check if the e-mail specifications, such as the
encoding/decoding style and file format, on the sending
side are the same as those for the Ethernet module.
• Receive an e-mail with an unknown destination and
unknown destination server from the SMTP server.
289
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
(3)
Error code
Error description
Action
• Check if the file extension of the attachment is "bin" or
"asc" on the sending side.
C114H
An e-mail that was received has an attachment with an
• Check that the e-mail is not compressed or encrypted.
invalid name.
• Check the destination of the MSEND instruction.
• Receive an e-mail with an unknown destination and
unknown destination server from the SMTP server.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C115H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C116H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C117H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C118H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Read Mail information storage area (address: 2682H) of
C119H
There is no received mail.
the buffer memory and read received e-mails remaining
on the server.
290
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Check that the e-mail is not compressed or encrypted.
• Check if the e-mail specifications, such as the
C11AH
The received mail failed to be converted.
encoding/decoding style and file format, on the sending
side are the same as those for the Ethernet module.
• Check if the sending side has not divided the file.
• Receive an e-mail with an unknown destination and
unknown destination server from the SMTP server. (The
C11BH
An e-mail was sent and an error mail was received from
the mail server of the destination.
received mail is stored in the mail buffer.)
• Check if the portion before "@" is correct in the mail
address setting in the parameter settings.
• Check if the portion before "@" has been registered on the
destination mail server.
• Check if the attachment size is 6K words or less.
C11DH
The attachment size exceeded the allowable size.
• Check that the sending side has not divided the
attachment.
• Check that the port number of the SMTP server is 25.
C120H
The SMTP server could not be opened.
• Check if communications with the SMTP server can be
performed using the PING command.
C121H
C122H
C123H
Communications cannot be performed with the SMTP
server. (Error response)
Communications cannot be performed with the SMTP
server. (Abort)
Communications cannot be performed with the SMTP
server. (Reset response)
A response from the SMTP server timed out.
C125H
Forcefully disconnected from the SMTP server
C126H
The SMTP server could not be closed.
C127H
Closing the SMTP server gave an error response.
C130H
C131H
C132H
C133H
The communication channel is closed because the service
is not available.
The SMTP server is in process, and an error response was
received.
The SMTP server is in process, and an error response was
received. (Local error)
The SMTP server is in process, and an error response was
received. (Insufficient memory area)
• Check if the SMTP server is busy.
• Check if the SMTP server is busy.
16
• Check for an error in the SMTP server.
• Check if the network is heavily loaded.
• Check for an error in the SMTP server.
• Check if the network is heavily loaded.
• Check for an error in the SMTP server.
• Check if the network is heavily loaded.
• Check for an error in the SMTP server.
• Check if the network is heavily loaded.
• Check the status of the SMTP server.
• Check that a user name not registered in the server has
not been specified.
• Send the e-mail again after a certain period of time.
• Check the status of the SMTP server.
• Check the status of the SMTP server.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C134H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
291
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
C124H
• Check if the SMTP server is busy.
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C135H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C136H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C137H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C138H
The SMTP server is in process, and an error response was
received. (Mailbox not found)
• Check if the mail address of the Ethernet module has
been correctly set.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C139H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C13AH
C13BH
292
The SMTP server is in process, and an error response was
received. (Exceeded the allocation of the memory area)
The SMTP server is in process, and an error response was
received. (Illegal mailbox name)
• Check the status of the SMTP server.
• Check if the mail address of the Ethernet module has
been correctly set.
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C13CH
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Check that the port number of the POP3 server is 110.
C140H
The POP3 server could not be opened.
(The port number of the Ethernet module is fixed to 110.)
• Check if communications with the POP3 server can be
performed using the PING command.
C141H
C142H
C143H
Communications cannot be performed with the POP3
server. (Error response)
Communications cannot be performed with the POP3
server. (Abort)
Communications cannot be performed with the POP3
server. (Reset response)
• Check if the POP3 server is busy.
• Check if the POP3 server is busy.
• Check if the POP3 server is busy.
• Check for an error in the POP3 server.
C144H
A response from the POP3 server could not be received.
C145H
Forcefully disconnected from the POP3 server
C146H
The POP3 server could not be closed.
C147H
Closing the POP3 server gave an error response.
C150H
POP3 server verification error
• Check the status of the POP3 server.
The Ethernet module's mail address (e-mail setting
• Check the account name of the mailbox on the server side
parameter) is different from the account name in the
and correct the account of the mailbox set in the Ethernet
mailbox on the server side.
module.
The Ethernet module's password (e-mail setting
C152H
parameter) is different from the password on the server
side.
An error has occurred in acquisition of the received mail
C153H
list. (The list of the mail that arrived at the POP3 server
failed to be acquired.)
• Check for an error in the POP3 server.
16
• Check for an error in the POP3 server.
• Check if the network is heavily loaded.
• Check for an error in the POP3 server.
• Check the password on the server side and correct the
password of the Ethernet module.
• Reset the server inquiry time to the default value and
restart the CPU module of the own station.
• Check that the e-mail is not compressed or encrypted.
C154H
An error has occurred upon receiving a mail. (An e-mail
cannot be read from the POP3 server.)
• Check if the e-mail specifications, such as the
encoding/decoding style and file format, on the sending
side are the same as those for the Ethernet module.
C160H
C161H
A response was received from the DNS server after
• Check if the network is heavily loaded.
timeout.
• Check the status of the DNS server.
A response from the DNS server could not be received.
• Check if the network is heavily loaded.
• Check the status of the DNS server.
293
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
C151H
• Check if the network is heavily loaded.
Error code
Error description
Action
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C162H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C163H
CPU module.
System error (The OS detected an error.)
(3)
(4)
Check if the power capacity is sufficient.
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C171H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C172H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C173H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C174H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C175H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
294
CHAPTER 16 TROUBLESHOOTING
Error code
Error description
Action
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C176H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C177H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C178H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C179H
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C17AH
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C17CH
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C17DH
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C17EH
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
295
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
of the server specified in the DNS setting is properly
C17BH
16
Error code
Error description
Action
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and
C17FH
An error was returned from the DNS server.
POP server names) are correct.
• Check with the network administrator if the DNS function
of the server specified in the DNS setting is properly
operating.
C180H
The device specified in "Condition Device" in "News
Correct the device settings in the PLC parameter window
Setting" is outside the range set in the [Device] tab of the
and specify the condition devices within the range of the
PLC parameter window.
device settings.
Try again.
C1A0H
An illegal request was made.
If the same error occurs, the Ethernet module may have a
hardware error. Please consult your local Mitsubishi
representative.
C1A2H
A response to the request could not be received.
• Check and correct the response waiting time.
C1A4H
A request or subrequest is incorrect.
• Correct the request and subrequest.
C1A5H
The specified target station or clear target is incorrect.
• Correct the specified target station or clear target.
C1A6H
The specified connection number is incorrect.
• Specify the connection number within the range of 1 to 16.
• Do not select the connection number 8 or 16 when using
the pairing open method.
C1A7H
The specified network number is incorrect.
• Correct the specified network number.
C1A8H
The specified station number is incorrect.
• Correct the specified station number.
C1A9H
The specified device number is incorrect.
• Correct the specified device number.
C1AAH
The specified device name is incorrect.
• Correct the specified device name.
C1ACH
The specified number of resends is incorrect.
• Correct the number of resends.
C1ADH
The specified data length is incorrect.
• Correct the specified data length.
• Correct the specified send/receive data length and header
C1AEH
The send/receive data length and header length are
incorrect.
length to values within the allowable ranges.
• The send/receive data length needs to be equal to or
longer than the header length.
C1AFH
C1B0H
C1B1H
C1B2H
C1B3H
C1B4H
C1B5H
The specified port number is incorrect.
The open process of the specified connection has been
already completed.
The open process of the specified connection has not been
completed.
The OPEN or CLOSE instruction is being executed in the
specified connection.
Another send or receive instruction is being executed in
the specified channel.
The specified arrival monitoring time is incorrect.
Data could not be received within the specified arrival
monitoring time.
• Correct the specified port number.
• Perform the close process before the open process.
• Perform the open process.
• Try again after the OPEN or CLOSE instruction is
completed.
• Change the channel number.
• Try again after the send or receive instruction is
completed.
• Set the arrival monitoring time to a value within the
allowable range.
• Correct the specified arrival monitoring time.
• Correct the specified send mail address number.
C1B6H
The specified send mail address number is incorrect.
• Correct the send mail address setting in the parameter
A reading operation was executed while no receiving e-
• If there is an mail received in the mail information, execute
setting.
C1B7H
C1B8H
296
mail was stored in the mail buffer data area.
the MRECV instruction.
The RECV instruction was executed for the channel that
• Correct the execution condition of the RECV instruction.
had not received data.
• Correct the channel number.
CHAPTER 16 TROUBLESHOOTING
Error code
C1B9H
C1BAH
Error description
The OPEN instruction cannot be executed for the specified
connection.
The dedicated instruction was executed with the
initialization not completed.
C1BBH
The target station CPU type is incorrect.
C200H
The remote password is incorrect.
C201H
C202H
The remote password status of the port used for
communications is in the lock status.
When another station was accessed, the remote password
could not be unlocked.
Action
• Correct the connection number.
• Execute the dedicated instruction after the initial process
is completed.
• Correct the specified target station CPU type.
• Correct the remote password, and unlock/lock the remote
password again.
• After unlocking the remote password, perform
communications.
• When accessing another station, do not set the remote
password on the relay station or access station or do not
execute the remote password check on them.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C203H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C204H
password unlock.
When another station was accessed, the remote password
could not be unlocked.
• Request the lock process of the remote password from the
connected device that requested the unlock process of the
remote password.
• When accessing another station, do not set the remote
password on the relay station or access station or do not
execute the remote password check on them.
• Follow the procedure below.
(1)
Check if the Ethernet module, the power supply
module, and the CPU module are properly connected.
(2)
Check if the operating environment of the Ethernet
module conforms to the general specifications of the
C206H
CPU module.
System error (The OS detected an error.)
(3)
Check if the power capacity is sufficient.
(4)
Check if the hardware is normal according to the
manual for each module.
If the actions above do not solve the problem, please consult
your local Mitsubishi representative.
C207H
C300H
The file name has too many characters.
• Name the file with 255 characters or less.
A response could not be received within the response
• Check the operation of the connected device.
monitoring timer value.
• Correct the response monitoring timer value.
• Check that Predefined protocol ready (X1D) has turned on
before executing the ECPRTCL instruction.
C400H
Protocol not-ready error
• Execute the ECPRTCL instruction after rewriting the
protocol setting data to the Ethernet module.
• If an error still occurs even after rewriting, replace the
module.
• Correct the specified protocol number and execute the
C401H
Protocol unregistered error
protocol again.
• Register the corresponding protocol to the specified
protocol number.
C402H
Protocol setting data error
16
• Correct the protocol setting data and register it again.
297
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
C205H
The device is different from the one requesting the remote
Error code
Error description
Action
• Do not execute dedicated instructions which do not
C403H
Simultaneous dedicated instructions execution error
support simultaneous execution.
• Correct the specified connection number and execute the
dedicated instruction again.
• Check the canceled protocol in the control data of the
C404H
Protocol cancel request error
ECPRTCL instruction (execution count result) and
eliminate the cause of the cancellation.
C405H
Protocol number setting error
C406H
Continuous protocol execution count setting error
• Correct the specified protocol number and execute the
protocol again.
• Correct the number of protocols to be executed
continuously and execute the protocol again.
• Correct the specified connection number and execute the
C407H
Connection number setting error
protocol again.
• Correct the connection setting of the specified connection
number and execute the protocol again.
• Check if the cable is disconnected.
• Correct the connection setting of the specified connection
number and execute the protocol again.
• Check that there is no error in the connected device.
C410H
Receive wait timeout error
• Check that the sending from the connected device is not
interrupted.
• Check that there is no data lost due to a receive error.
• Check that there is no error in the data (packet) sent by
the connected device.
• Check the data sent by the connected device.
C411H
Packet size error
• To send data that exceeds 2046 bytes from the connected
device, divide the data into several parts and send them
separately.
• Check the maximum allowable data length and specify the
maximum length or less in the data length storage area.
C417H
Data length setting error, data quantity setting error
• Check the maximum allowable data quantity, and specify
the maximum quantity or less in the data quantity storage
area.
• Write the data again.
C420H
Flash ROM write error
• If an error still occurs even after rewriting, replace the
module.
C421H
C430H
Flash ROM write count over limit error
Protocol setting data writing during the ECPRTCL
instruction execution
• Replace the module because the number of writes
exceeded the limit.
• If the ECPRTCL instruction is under execution, cancel the
instruction and write the protocol setting data.
• Check the operation of the connected device.
C431H
Connection close during the ECPRTCL instruction
execution
• Check the connection open status with the connected
device.
• Open the connection with the connected device again and
execute the instruction.
D000H to
DFFFH
E000H to
EFFFH
F000H to
FFFFH
298
(Errors detected by CC-Link IE Field Network)
Refer to the manual for each module.
(Errors detected by CC-Link IE Controller Network)
Refer to the manual for each module.
(Errors detected by the MELSECNET/H and
MELSECNET/10 network system)
• Refer to the MELSECNET/H or MELSECNET/10 network
system reference manual, and take corrective action.
CHAPTER 16 TROUBLESHOOTING
Remark
The error codes listed in the table include those returned to the connected device. Each buffer memory may also store the
error numbers of the response messages returned from the connected device. If an error code other than those listed is
stored, check the manual for the connected device and the response message from the connected device.
16
16.7 Error Code List
16.7.3 Error codes stored in the buffer memory
299
16.8
Ethernet Diagnostics
Items such as the module status, parameter settings, communication status, and error history of an E71 can be
checked. Perform the diagnostics in the "Ethernet Diagnostics" window of the programming tool.
[Diagnostics]
[Ethernet Diagnostics...]
Item
Target Module Setting (Module No.)
Parameter Status
Description
Specify the E71 to be monitored. The number of other network modules is not
included.
Module information (such as the IP address and basic settings) is displayed.
The number of errors and their details (such as the error code and information about
Error History
the connection where the error has occurred) is displayed.
Status of Each Connection
Status of Each Protocol
The status of each connection (such as error codes and the open setting) is displayed.
Information such as the total number of data sending/receiving times for each protocol
is displayed.
LED Status
The operation mode and the LED status of the E71 are displayed.
Received E-mail Information
Received mail information and the error log are displayed.
Send E-mail Information
Sent mail information and the error log are displayed.
button
The "PING Test" window is displayed.
button
The "Loopback Test" window is displayed.
button
The COM.ERR. LED is turned off. (
Remark
For each window and detailed explanations, refer to the following.
Operating manual for the programming tool used
300
Page 303, Section 16.10)
CHAPTER 16 TROUBLESHOOTING
16.9
Checking the Status of the E71 with the System Monitor
Open the system monitor window of a programming tool to check the LED status, connection status, and operating
status of the E71.
1.
Open the "System Monitor" window.
[Diagnostics]
2.
[System Monitor]
Select the module to diagnose in the "Main Block" field in the upper left of the window. Then click
the
button.
16
3.
The "H/W Information" is displayed.
16.9 Checking the Status of the E71 with the System Monitor
301
Item
Display Format
Description
Switches the input format of "H/W LED Information" and "H/W SW Information".
INIT.
OPEN
H/W LED
Information
ERR.
Indicates the statuses of the LEDs on the E71.
0000: Off
0001: On
COM. ERR.
BUF1 to
BUF16
NET NO.
Indicates the connection statuses of the connection numbers 1 to 16.
0000: Open not completed
0001: Open completed
Indicates the network No. of the E71.
GRP NO.
Indicates the group No. of the E71.
ST NO.
Indicates the station number of the E71.
Indicates the mode of the E71.
0000: Online
MODE
0001: Offline
0002: Self-loopback test
0003: H/W test
Indicates the operating status of the E71, which has been set with a programming tool.
b15
H/W SW
b9
―
b8
b7 b6
b5
b4 b3
1/0 ― 1/0 1/0 1/0
b2
b1
b0
― 1/0 1/0
―
Information
6)
CONFIG
302
5)
1) Communication data code setting
0: Communications in a binary code
1: Communications in an ASCII code
2) Initial/open method setting
0: No parameter setting
(start up according to the sequence program)
1: Parameter setting
(start up according to the parameters)
3) TCP Existence confirmation setting
0: Use the Ping
1: Use the KeepAlive
4)
3)
2)
1)
4) Send frame setting
0: Ethernet frame
1: IEEE 802.3 frame
5) Setting of write enable/disable at RUN time
0: Disable
1: Enable
6) Initial timing setting
0: Do not wait for OPEN
(Communications impossible at STOP time)
1: Always wait for OPEN
(Communication possible at STOP time)
CHAPTER 16 TROUBLESHOOTING
16.10
How to Turn Off the COM.ERR. LED
The COM.ERR. LED turns on when an error occurs during communications with the connected device. The
COM.ERR. LED does not turn off even after the error cause is removed. Turn it off using the following methods.
(1) Using an I/O signal
Turn off the COM.ERR. LED by turning on COM.ERR. LED OFF request (Y17). An off request continues to be
issued while COM.ERR. LED OFF request (Y17) is on. However, this method does not clear the error information
in the error log area in the buffer memory.
[COM.ERR.] LED OFF request
signal (Y17)
(LED: ON)
(LED: OFF)
(LED: ON)
[COM.ERR.] LED ON
signal (X1C)
Error timing
Error
Error
Error
(2) Using a dedicated instruction
Turn off the COM.ERR. LED using the ERRCLR instruction. (
Page 226, Section 15.11) This method can
also clear the error information (initial error code, open error code) or the error log.
16
(3) In the "Ethernet Diagnostics" window
button in the "Ethernet Diagnostics" window. However,
this method does not clear the error information in the error log area in the buffer memory. For the window, refer
to "Ethernet Diagnostics".
(
Page 300, Section 16.8)
(4) Using the MC protocol
Turn off the COM.ERR. LED using the dedicated command for the MC protocol (LED off, Error code initialization:
1617). For details, refer to the following.
MELSEC Communication Protocol Reference Manual
303
16.10 How to Turn Off the COM.ERR. LED
Turn off the COM.ERR. LED by clicking the
APPENDICES
Appendix 1
Processing Time
Calculate the minimum processing time for each function using the expressions below. Note that the processing time
may become longer depending on the load factor on the network (how congested the line is), the window size of each
connected device, the number of connections, and system configuration. Use the values obtained from the
expressions as a guideline for the processing time when communications are performed in only one connection.
(1) Minimum processing time of communications using a fixed buffer
(communications between the E71s)
(a) Procedure exists
Tfs = St + Ke + (Kdf  Df) + Sr
Tfs
The time from the start of sending to the completion of sending (unit: ms)
St
Sending station scan time
Ke, Kdf
Constant (Refer to the table below.)
Df
Number of send data words
Sr
Receiving station scan time
LJ71E71-100
Item
TCP/IP communications
UDP/IP communications
Ke
Kdf
Ke
Kdf
Communications using a binary code
7.3
0.0033
6.2
0.0040
Communications using an ASCII code
7.3
0.0082
6.2
0.0081
(b) No procedures
Tfs = St + Ke + (Kdf  Df)
Tfs
The time from the start of sending to the completion of sending (unit: ms)
St
Sending station scan time
Ke, Kdf
Constant (Refer to the table below.)
Df
Number of send data bytes
LJ71E71-100
Item
Communications using a binary code
TCP/IP communications
UDP/IP communications
Ke
Kdf
Ke
Kdf
5.4
0.0010
3.8
0.0009
[Calculation example]
The time between the E71 sending 1017-word data of a binary code and it completing the sending when the
E71 communicates with another E71 in TCP/IP with the "Procedure Exist" method (unit: ms)
Assume that the scan time on the sending side is 10ms, and the scan time on the receiving side is 8ms.
• 28.6561 (ms)  10 + 7.3 + (0.0033  1017) + 8
304
APPENDICES
(2) Minimum processing time of communications using a random access buffer
A
Trs = Kr + (Kdr  Df) + ACK processing time of a connected device (added only for TCP/IP communications)
The time between the E71 receiving request data from a personal computer
Trs
and it completing the process (unit: ms)
Kr, Kdr
Constant (Refer to the table below.)
Df
Number of request data words
ACK processing time of the
The time between a random access buffer reading/writing completed and the
connected device
connected device returning ACK
LJ71E71-100
Item
Reading
Writing
TCP/IP communications
UDP/IP communications
Kr
Kdr
Kr
Kdr
Communications using a binary code
2.0
0.0010
1.4
0.0012
Communications using an ASCII code
2.0
0.0032
1.4
0.0033
Communications using a binary code
2.0
0.0016
1.4
0.0018
Communications using an ASCII code
2.0
0.0056
1.4
0.0048
[Calculation example 1]
The time between the E71 receiving request data from a personal computer and it completing reading when the
E71 communicates with the personal computer in TCP/IP and reads 508-word data of a binary code from a
random access buffer (unit: ms)
• 2.508 + ACK processing time of the connected device (ms)  2.0 + (0.0010  508) + ACK processing time
of the connected device
The time between the E71 receiving request data from a personal computer and it completing writing when the
E71 communicates with the personal computer in TCP/IP and writes 508-word data of a binary code to a random
access buffer (unit: ms)
• 2.8128 + ACK processing time of the connected device (ms)  2.0 + (0.0016  508) + ACK processing time
of the connected device
305
Appendix 1 Processing Time
[Calculation example 2]
(3) Minimum processing time of MC protocol communications (batch reading and
batch writing)
Tfs = Ke + (Kdt  Df) + Scr  number of scans required for the process + ACK processing time of the connected
device
The time between the E71 receiving request data from a personal computer and it completing
the process
Tfs
(unit: ms)*1
Ke, Kdt
Constant (Refer to the table below.)
Df
Number of request data words + number of response data words (Application data part)
CPU module processing time
Scr
• Own station access: E71-connected station scan time
• Another station access over MELSECNET/10: Transmission delay time + E71-connected
station scan time
LJ71E71-100
Item
Batch reading
Batch writing
*1
TCP/IP communications
UDP/IP communications
Ke
Kdt
Ke
Kdt
Communications using a binary code
3.3
0.0022
2.6
0.0018
Communications using an ASCII code
3.3
0.0046
2.7
0.0046
Communications using a binary code
3.3
0.0024
2.6
0.0033
Communications using an ASCII code
3.3
0.0073
2.7
0.0070
The time from when the E71 receives the request data from the personal computer until it completes the process is
shown below.
Connected device
(personal computer) Command
message
ACK
(TCP only)
Response
message
ACK
(TCP only)
E71
Step 0
Step 0
END
CPU module scan time
Tfs
306
END
APPENDICES
[Calculation example 1]
The time between the E71 receiving request data from a personal computer and it completing reading when the
E71 communicates with the personal computer in TCP/IP and reads 100-point data of an ASCII code from the
A
data register (D) in the own station (unit: ms)
Assume that the scan time of the E71-connected station is 10ms, the command data length is 21 words, and the
response data length is 211 words.
• 14.37 + ACK processing time of the connected device (ms)
 3.3 + (0.0046  (21 + 211)) + 10  1 + ACK processing time of the connected device
[Calculation example 2]
The time between the E71 receiving request data from a personal computer and it completing writing when the
E71 communicates with the personal computer in TCP/IP and writes 100-point data of an ASCII code to the data
register (D) in the own station (unit: ms)
Assume that the scan time of the E71-connected station is 10ms, the command data length is 221 words, the
response data length is 11 words, and writing during RUN is enabled.
• 14.99 (ms) + ACK processing time of the connected device
 3.3 + (0.0073  (221 + 11)) + 10  1 + ACK processing time of the connected device
Appendix 1 Processing Time
307
(4) Processing time of the dedicated instructions
The following table lists approximate operation processing time of each dedicated instruction. The operation
processing time differs depending on the system configuration and the scan time on the sending/receiving
stations.
Instruction
name
Processing time (unit: ms)
Number of access points
Condition 1)
LCPU
Condition 2)
For 1)
BUFRCV
BUFRCVS
1017
words
1 word
BUFSND
For 2)
0.80
1.16
0.23
0.61
7.44
CLOSE
Instruction execution condition
TCP/IP communications, binary code communications, and fixed
buffer communications (procedure exists)
10.80
1 port
2.36
ERRCLR
All error information is cleared.
1.06
ERRRD
An initial error code is read.
1.04

1 port
2.12
A UDP/IP transmission port is open.
OPEN
960 words
RECVS
960 words
READ
960 words
SREAD
960 words
960 words
SEND
960 words
960 words
ZNRD
230 words
ZNWR

UINI
*1
308
6.32
13.00
9.84
13.00
10.20
7.12
7.84
7.04
8.48
11.20
*1
ECPRTCL
8.32
7.36
480 words
Communications between E71-connected stations
1.86
7.28
480 words
SWRITE
2.00
4.64
480 words
WRITE
9.92
1.38
480 words
1 word
9.84
12.60
7.28
480 words
RECV
0.42
12.50
7.20
480 words

0.62
0.23
480 words
A UDP/IP transmission port is closed.
Time between the UINI instruction accepted and reinitialization
completed (X19 turning on)

The processing time of the ECPRTCL instruction differs depending on a connected device or a protocol.
APPENDICES
Appendix 2
Port Numbers Used for the E71
A
The following table lists port numbers reserved for an E71 system.
Port number
Application
1388H (5000)
Auto-open UDP port (Default value)*1
1389H (5001)
MELSOFT application transmission port (UDP)
138AH (5002)
MELSOFT application transmission port (TCP)
*1
The port number can be changed.
Ex. The port number can be changed by overwriting the buffer memory address, Automatic open UDP port
number (address: 14H).
Appendix 2 Port Numbers Used for the E71
309
Appendix 3
New and Improved Functions
The following table lists the new and improved functions in the E71 and supported versions of modules and
programming tool.
[How to see the table]
• Numbers in quotation marks in the table represent the first five digits of the serial number of each module.
: Available (No version restriction), : Not available
Function
Version of E71
Version of CPU module
Version of GX Works2
Reference
Communications using SLMP
Function version A or later of
"15042"


Page 89, CHAPTER 10
Data communications using the
predefined protocol
Function version A or later of
"15042"

Version 1.492N or later
Page 95, CHAPTER 11
Setting range extension of the
communication destination port
number (Port number 1 (1H) to
Function version A or later of
"15042"

Version 1.492N or later
Page 64, CHAPTER 7
Receive buffer full detection signal
(address: 5240H)
Function version A or later of
"17032"


Page 35, Section 3.5.2
IP filter function
Function version A or later of
"18072"


Page 175, Section 14.3
1024 (400H) can be set.)
310
APPENDICES
Appendix 4
Initial Process
A
The initial process is for enabling data communications with connected devices by setting the minimum number of
parameters for the E71.
In the MELSEC-L series, the initial process is performed automatically.
(1) Checking the initial process result
The results of the initial process can be checked using the LEDs and I/O signals.
Initial normal completion
Initial process
INIT.LED
Initial abnormal end signal
signal
(X1A)
(X19)
Upon normal completion
ON
ON
OFF
Upon abnormal end
OFF
OFF
ON
If the initial process is not normally completed, correct the set values of parameters listed in Chapter 7 and those
in the initial process setting parameter described in this chapter. After correcting the parameters, write them to the
CPU module again, power off and on the CPU module or reset the CPU module.
Appendix 4.1
Setting the initial process
Configure the setting in the initial setting window. Each setting time is calculated by "setting value  500ms".
[Parameter]
"Ethernet" under "Network Type".
[Network Parameter]
[Ethernet/CC IE Field]
Select
button
311
Appendix 4 Initial Process
Appendix 4.1 Setting the initial process
Project window
Item
TCP ULP Timer
Description
Set Time to Live during packet sending in TCP/IP.
Setting range
2 to 32767
Set the receive buffer value on the recipient. If the receive
buffer on the recipient has no free space (window size = 0),
TCP Zero Window Timer
data sending is waited until the recipient has free receive
buffer space. At this time, the sender sends packets for
2 to 32767
checking the sending window to the recipient according to the
TCP zero window timer value to check the receiving status.
Set the time to resend ACK if it is not returned when a
connection is opened or data is sent in TCP/IP. This timer is
also used for Time to Live for the ARP function. (ARP is resent
TCP Resend Timer
by the time of "TCP resend timer value/2" if no response to an
2 to 32767
ARP request is returned.) This timer is also used as the
minimum set time for arrival monitoring time for data link
instructions.
When closing the TCP/IP connection by the own station, set
the monitoring time for waiting for a FIN from the connected
device after the own station sends a FIN and an ACK is
TCP End Timer
returned from the connected device. If a FIN is not received
2 to 32767
from the connected device within the time specified by the
TCP end timer value, a RST is sent to the connected device
and the connection is forcibly closed.
Timer Setting
The communication data may be divided at the IP level before
IP Assembly Timer
being sent due to the buffer limitation of the sending station or
the receiving station. Set the waiting time for the divided data
1 to 32766
in such a case.
Set the following waiting time.
Response Monitoring Timer
• Time for waiting a response after a command is sent
• For receiving divided messages, time until the last message
2 to 32767
is received after the first message is received
Set the time until starting the alive check after
Dest. Confirmation Start Interval
communications with the connected device of the connection
that has been opened where the alive check target exists is
1 to 32767
lost.
For the connection that is opened where the alive check target
Dest. Confirmation Interval
exists, set the interval to perform the alive check again when a
response from the connected device as the alive check target
1 to 32767
is not received.
For the connection that has been opened where the alive
Dest. Confirmation Resend
check target exists, set the number of times that the alive
check is performed again when a response from the
1 to 32767
connected device as the alive check target is not received.
Input Format
Select an input format.
DNS
IP Address of DNS Server2
Setting*1
IP Address of DNS Server3
Set the IP address of each DNS server.
IP Address of DNS Server4
*1
The DNS setting is configured for using the e-mail function. For details, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Application)
312
DEC/HEX
IP Address of DNS Server1

APPENDICES
A
(1) Precautions for settings
• Specify the setting value of each timer on the E71 side so that the following formula is met.
Response
monitoring
timer value
TCP ULP
timer value
TCP
resend
timer value
TCP end
timer value
=
TCP
resend
timer value
IP
assembly
timer value
TCP zero window
timer value
When connecting Mitsubishi products to the line, configure the same settings for both modules.
• Specify the setting value of each timer on the connected device side so that the following formula is met. The
frequency of a communication error, such as a transmission timeout, may be higher if the timer values do not
meet the formula.
TCP ULP
timer value on
the connected device
Monitoring timer value of
the application software on
the connected device
TCP resend timer value
on the E71
TCP ULP timer value
on the E71
n *1
*1 "n" is the number of TCP segment transmission and is calculated by the following formula.
n = A value that
Message size sent by the E71
Maximum Segment Size
is rounded up to the nearest integer
Ex. The number of TCP segment transmission when communications are performed on the same line
The Maximum Segment Size is 1460 bytes on the same line (without a router) and the number of TCP
• n = 2 when the size of the message sent by the E71 is greater than 1460 bytes
Ex. The number of TCP segment transmission when communications are performed on a different line
The Maximum Segment Size is at least 536 bytes on another line (via a dialup router or other
communication device) and the number of TCP Segment transmission is as follows.
• n = 1 when the size of the message sent by the E71 is 536 bytes or less
• n = 2 when the size of the message sent by the E71 is greater than 536 bytes and no more than
1072 bytes
• n = 3 when the size of the message sent by the E71 is greater than 1072 bytes and no more than
1608 bytes
313
Appendix 4 Initial Process
Appendix 4.1 Setting the initial process
Segment transmission is as follows.
• n = 1 when the size of the message sent by the E71 is 1460 bytes or less
• When a communication failure occurs due to a problem such as noise, change the value so that the number
of retries may increase. The number of retries is obtained using the following formula. (When using the
default values, 3 = (60  20))
Number of retries = TCP ULP timer value TCP resend timer value
Ex. When the number of retries is three and data sending fails, a data sending error occurs at the timing
shown in the figure below (in communications using the fixed buffer).
BUFSND instruction
1 scan
BUFSND instruction
Completion device + 1
E71
Data
command
1st retry
A
2nd retry
A
3nd retry
A
TCP ULP timeout value
A: TCP resend timer value
(The time at which data are sent when ACK is not returned after data transmission)
• When not performing the above retry process (set 0 times), configure the setting so that the following
formula is met.
TCP ULP
timer value
=
TCP end
timer value
=
TCP resend
timer value
(Set the same value for the timer values.)
314
APPENDICES
Appendix 4.2
Reinitialization process
A
The reinitialization process sets the E71 to the status after startup without restarting the programmable controller (or
resetting the CPU module). Perform the reinitialization process using a program.
(1) The purpose of a reinitialization process
The purpose of a reinitialization process is described.
(a) To update address information of a connected device held by the E71
To prevent other devices from illegally accessing the programmable controller using the IP address of the
connected device with which communications are normally performed, the E71 holds the IP address of the
connected device and the corresponding MAC address.*1 If a module or the board of the connected device is
replaced due to a failure, the address information of the connected device held by the E71 must be cleared by
the reinitialization process.
*1
A MAC address is unique to a device. No devices share the same MAC address.
(b) To change the IP address of the E71 on the own station
When a system is changed, by only changing the own station IP address set by the programming tool,
communications with the connected device can be resumed.
(c) To change the Ethernet operation setting
By changing the communication conditions in the Ethernet operation setting set using the programming tool,
communications with the connected device can be resumed.
(d) To change the transmission speed and communication mode
can be resumed.
315
Appendix 4 Initial Process
Appendix 4.2 Reinitialization process
By changing the transmission speed and communication mode, communications with the connected device
(2) Program for the reinitialization process
Perform the reinitialization process using a program. The following shows the process timing and sample
programs.
(a) Process timing
Close process
Program
END
process
Scan
Initial normal completion
signal (X19)
Open completion signal
(address: 5000H)
Scan
END
process
Scan
END
process
Scan
END
process
Scan
1
2
UINI instruction
3
Completion device
Abnormally ended
Completion device + 1
Reinitialization specification
(address: 1FH (b15))
4
Internal process of the E71
5
Processing reinitialization
Requesting
reinitialization
Initializing the module
1
Check the normal completion of the initial process. (Initial normal completion signal (X19): ON)
2
Terminate all data communications with the connected devices and perform a close process on all
connections.
3
Execute the UINI instruction. Specify the parameters (such as the IP address of the own station and Ethernet
operation setting) using the control data of the dedicated instruction and initialize the E71.
4
When the E71 reinitialization request is completed, Initial normal completion signal (X19) turns off.
5
When the reinitialization processes are all completed, Reinitialization specification (address: 1FH (b15) turns
"0" and Initial normal completion signal (X19) turns on. If the reinitialization process fails, an error code is
stored in the initial error code storage area.
(b) Sample program
The following two methods are available:
• Using the dedicated instruction (UINI instruction)
• Writing directly to the buffer memory
Do not use the method using the dedicated instruction (UINI instruction) and the method by writing directly to the buffer
memory together.
316
APPENDICES
(c) Using the dedicated instruction (UINI instruction)
The following shows an example where the reinitialization process is performed using the UINI instruction and
A
the OPEN instruction is executed after the process is completed. (When the I/O signals of the E71 are X/Y00 to
X/Y1F)
Appendix 4 Initial Process
Appendix 4.2 Reinitialization process
Process upon completion
Process upon abnormal end
317
Process upon completion
Process upon abnormal end
Process upon completion
Communications enabled
Process upon abnormal end
318
APPENDICES
(d) Writing directly to the buffer memory
The following shows an example where the stored values in the TCP Maximum Segment Transmission setting
A
area and Communication condition setting (Ethernet Operation Setting) area is changed (when the I/O signals
of the E71 are X/Y00 to X/Y1F). Create a program with a contact (such as a flag for user) indicating the status
of the open completion signal storage area.
Set TCP segment transmission
not to be performed.
Set "ASCII Code".
Set "Use the KeepAlive".
Set "IEEE802.3".
Set "Enable Online Change".
Appendix 4 Initial Process
Appendix 4.2 Reinitialization process
Set "Always wait for OPEN".
Request a reinitialization process.
319
Process upon completion
Process upon abnormal end
Communications enabled
Remark
This is a sample program for communications using connection numbers 1 and 2. When using another connection number,
specify the corresponding signals and bits.
320
APPENDICES
A
(3) Precautions
(a) Buffer memory area settings
The following parameters operate according to the settings of the corresponding buffer memory areas
configured when a reinitialization process is performed. Therefore, do not change the settings of the buffer
memory areas.
• Timer setting of the initial setting
• Open setting
• Router relay parameter setting
• Station number <-> IP information setting
• FTP parameters setting
(b) Reinitialization process request
Do not request another reinitialization process while a reinitialization process is in progress.
Appendix 4 Initial Process
Appendix 4.2 Reinitialization process
321
Appendix 5
Line Status Check
The E71 line status, parameter settings, and progress of the initial process can be checked. The following two
methods can be used to check the line status.
• PING test
• Loopback test
Appendix 5.1
PING test
This section describes the PING test.
(1) Performing a test with direct connection to the E71
This test is to check the existence of an E71 that has completed the initial process on the same Ethernet network
using the programming tool or to check the existence of a connected device, such as a personal computer,
having a specified IP address.
Programming tool
Executing the PING test
Specifying the IP address
Ethernet
E71
(a) Applications
The line status between the programming tool (personal computer) and the E71 can be checked.
322
APPENDICES
(b) Operating procedure
A
Use the following procedure.
1.
Click the
button in the "Ethernet
Diagnostics" window.
[Diagnostics]
[Ethernet Diagnostics]
"Target Module Setting" under "Module No."
2.
Configure the settings and click the
button.
Click the
Appendix 5 Line Status Check
Appendix 5.1 PING test
3.
button.
323
4.
The test results are displayed.
(c) Action for abnormal end
If the test fails, check the following and perform the test again.
• Whether the E71 is properly connected
• Connection to the Ethernet network
• Parameter settings written in the CPU module
• Operating status of the CPU module (whether or not an error has occurred)
• IP addresses set in the programming tool and the PING test target station
• Whether the connected device has been reset after the E71 was replaced
324
APPENDICES
A
(2) Performing a test with direct connection to the CPU module
This test is to check the existence of an E71*1*2, that has completed the initial process on the same Ethernet
network where a station connected to the programming tool exists or to check the existence of a connected
device, such as a personal computer, having a specified IP address, by directly connecting the programming tool
and the CPU module.
Programming tool
CPU module
Specifying the station
executing the test
using the network No.
and station No.
PING test executing station
Specifying the target station
using the IP address
Ethernet
E71
(PING test target station)
*1
*2
This also applies to Q/QnA/A series modules. However, for an AJ71E71, AJ71E71-B2, and AJ71E71-B5, software
versions S and later are required.
The PING test cannot be executed on the own station.
(a) Applications
By specifying the execution station and the target station, the PING test can be executed from a remote device.
(b) Operating procedure
1.
Click the
Appendix 5 Line Status Check
Appendix 5.1 PING test
Use the following procedure.
button in the "Ethernet
Diagnostics" window.
[Diagnostics]
[Ethernet Diagnostics]
"Target Module Setting" under "Module No."
325
2.
Configure the settings and click the
button.
3.
Click the
4.
The test results are displayed.
button.
(c) Action for abnormal end
If the test fails, take the same action as that for the method using direct connection to the E71. (
322, Appendix 5.1 (1))
326
Page
APPENDICES
A
(3) Performing a test with the PING command
The PING test can be also executed using the PING command. The following shows an example of checking
whether the initial process has been completed by issuing a PING command to the E71 of the own station from a
connected device in the same Ethernet network.
[Specification method] ping IP Address
When the IP address of an E71 is 192.168.3.40
(Window upon normal completion)
(Window upon abnormal end)
(a) Action for abnormal end
If the test fails, check the following and perform the test again.
• Whether the E71 is properly connected
• Connection to the Ethernet network
• Parameter settings written in the CPU module
• Operating status of the CPU module (whether or not an error has occurred)
• IP address of the destination E71 specified using the PING command
Appendix 5 Line Status Check
Appendix 5.1 PING test
327
Appendix 5.2
Loopback test
This section describes the loopback test.
(1) Performing a test using a programming tool
This test is to check whether the initial process for each module has been completed. The test is executed on the
network of stations connected to the programming tool, and loopback test messages are sent sequentially to
each E71*1 on the network and in the station number range specified for the loopback test request designation.
Programming
tool
(Stations connected
to the programming tool)
Station No.1
Station No.3
E71
Station No.5
Station No.7
Station No.9
E71
E71
E71
E71
Network No.1
E71
The loopback test is executed
from the station No.1 through
the station No.5 on the network Station No.2
No.1.
*1
E71
E71
E71
Station No.4
Station No.6
Station No.8
Because the QJ71E71-100 of function version A and QnA/A series modules do not have a function for responding to this
request, the test results cannot be checked.
(a) Applications
The test can be executed only by specifying the network number for the test and target station number range.
For the E71-connected station subjected to the loopback test, do not specify the MELSOFT application transmission port
(UDP/IP) as a valid port for the password check. The loopback test cannot be executed.
328
APPENDICES
(b) Operating procedure
A
Use the following procedure.
1.
Click the
button in the "Ethernet
Diagnostics" window.
[Diagnostics]
[Ethernet Diagnostics]
"Target Module Setting" under "Module No."
2.
Configure the settings and click the
button to display the test results.
Appendix 5 Line Status Check
Appendix 5.2 Loopback test
If the same IP address or station number is assigned to multiple stations, only the results of the station that responds first are
displayed.
329
(c) Action for abnormal end
If the loopback test fails, "No response" or an error code is displayed.
Displayed test
Status of the
result
target E71
Cause
Action
Initial processing
IP address
normal completion
status (INIT. LED

Normal completion
turns on.)
Correct the following parameter settings.
The initial process for the target E71 has not
• Basic setting
been completed normally.
• Ethernet operation setting
• Initial setting
There is an error, such as cable
disconnection and line disconnection, in the
• Check the cable.
line connection to the target E71.
No error
The IP address of the target E71 is
incorrect. (The class or subnet address
differs from that of the E71.)
The same IP address has been set to
Correct the set values of the Ethernet
operation settings.
multiple target E71 modules.
No response
The same network number or station
number has been set to multiple target E71
modules.
Perform the PING test on the "No response"
module. When the test is completed
normally, correct the set values in the basic
settings.
The Ethernet line is heavily loaded
No error/Error exists
(including a case where an error equivalent
When the Ethernet line is not heavily
to the error codes C030H and C031H is
loaded, perform the test again.
occurring).
The routing parameter is not set (an error
Error exists
equivalent to the error code C080H is
occurring).
The MELSOFT application transmission
port (UDP/IP) for the target E71 is locked
No error
Error code
with the remote password.
Correct the set value of the routing
parameter.
Disable the remote password setting and
write the parameter to the CPU module.
The target E71 is a function version A
Check the module name and function
module.
version.
The Ethernet line is heavily loaded
No error/Error exists
(including a case where an error equivalent
When the Ethernet line is not heavily
to the error codes C030H and C031H is
loaded, perform the test again.
occurring).
For an E71 where the loopback test failed, check the error and take corrective action. Then restart the E71-connected
station. Restarting the E71 executes the initial process. To check whether the initial process has been completed in the E71,
perform the PING test. The PING test can be also performed on the "Loopback Test" window.
330
APPENDICES
A
(2) Performing a test using the MC protocol
The loopback test can be also executed using MC protocol communications. Note, however, that only the E71 in
the own station can be used. The test cannot be executed on E71 modules in other stations over the network. For
details, refer to the following.
MELSEC Communication Protocol Reference Manual
(Loopback test command sending station)
Ethernet
LCPU
E71
LCPU
E71
LCPU
E71
(Loopback test target station)
(a) Execution method
Execute the test using the MC protocol dedicated command (Loopback test: 0619).
When the user port on the E71 side is used to perform MC protocol communications, the line connection process is
necessary. Execute the open process for the connection used for the E71 side.
Appendix 5 Line Status Check
Appendix 5.2 Loopback test
331
Appendix 6
Self-Diagnostic Tests
This section describes the self-diagnostic tests to check data communications and hardware of an E71.
Appendix 6.1
Self-loopback test
Hardware including the E71 communication circuit is checked. Send the test message destined to the own station of
the E71 to the line. Then check whether the same message can be received over the network.
(1) Operating procedure
Use the following procedure.
1.
2.
3.
Connect the E71 to the line. *1
Set the switch on the CPU module to "STOP".
Select "Self-Loopback Test" under "Mode" and write
the parameter to the CPU module.
Project window
Parameter]
[Parameter]
[Network
[Ethernet/CC IE Field]
Select
"Ethernet" under "Network Type".
4.
Resetting the CPU module starts the test. Test time
is approximately five seconds. The RUN and OPEN
LEDs turn on during the test.
5.
Check the LED of the E71 after five seconds. When
the test is running normally, the RUN LED turns on.
If the test fails, the RUN and ERR. LEDs turn on.
*1
When the line is not connected, the self-loopback test is not performed and ends normally.
If an error is detected in the self-loopback test, the following causes are possible. The error information is stored
in Error log area (address: E5H) in the buffer memory.
• E71 hardware error
• Ethernet line error
There is no hardware-related problem even when the self-loopback test is executed while the destination is online. Because
a packet collision occurs when there are many packets on the line, the test may fail or may not be completed in five seconds.
In this case, execute the test after stopping data communications between other devices.
332
APPENDICES
Appendix 6.2
Hardware test (H/W Test)
A
The RAM and ROM of an E71 are checked.
(1) Operating procedure
Use the following procedure.
1.
2.
Set the switch on the CPU module to "STOP".
Select "H/W Test" under "Mode" and write the
parameter to the CPU module.
Project window
Parameter]
[Parameter]
[Network
[Ethernet/CC IE Field]
Select
"Ethernet" under "Network Type".
3.
Resetting the CPU module starts the test. Test time
is approximately five seconds. The RUN and OPEN
LEDs turn on during the test.
4.
Check the LED of the E71 after five seconds. When
If the test fails, the RUN and ERR. LEDs turn on.
If an error is detected in the hardware test (H/W test), the following cause is possible. The error information is
stored in Error log area (address: E5H) in the buffer memory.
• E71 RAM/ROM error
If the test fails, perform it again. If it fails again, there may be a hardware problem with the E71. Please consult your local
Mitsubishi representative.
333
Appendix 6 Self-Diagnostic Tests
Appendix 6.2 Hardware test (H/W Test)
the test is running normally, the RUN LED turns on.
Appendix 7
Differences from Ethernet Modules of Other
Series
This section describes the differences between an E71 and Ethernet modules of other series.
Appendix 7.1
Differences from a built-in Ethernet port LCPU
For comparison of the specifications and functions between an LJ71E71-100 and a Built-in Ethernet port LCPU, refer
to the following.
MELSEC-L CPU Module User's Manual (Built-In Ethernet Function)
Appendix 7.2
Differences from Q series modules
The functions of LJ71E71-100 are the same as those of QJ71E71-100, except for those listed below. A program of
QJ71E71-100 can be also used.
: Supported, : Not supported
Item
LJ71E71-100
QJ71E71-100


File password 32


Redundant system supporting function


AUTO MDI/MDI-X compatibility (automatic detection of a straight
cable and a cross cable)
Appendix 7.3
Differences from QnA/A series modules
This section provides the functional comparison between an E71 and QnA/A series modules and precautions for using
the same program. The QnA/A series modules are the following products.
Series
A series
Model name
Product name
AJ71E71
AJ71E71, A1SJ71E71-B2, A1SJ71E71-B5
AJ71E71-S3
AJ71E71-S3, A1SJ71E71-B2-S3, A1SJ71E71-B5-S3
AJ71E71N
AJ71E71N3-T, AJ71E71N-B5, AJ71E71N-B2, AJ71E71N-T, AJ71E71N-B5T, A1SJ71E71N3-T,
A1SJ71E71N-B5, A1SJ71E71N-B2, A1SJ71E71N-T, A1SJ71E71-B5T
AJ71QE71, AJ71QE71-B5, A1SJ71QE71-B2, A1SJ71QE71-B5, AJ71QE71N3-T, AJ71QE71N-B5,
QnA series
QE71(N)
AJ71QE71N-B2, AJ71QE71N-T, AJ71QE71N-B5T, A1SJ71QE71N3-T, A1SJ71QE71N-B5,
A1SJ71QE71N-B2, A1SJ71QE71N-T, A1SJ71QE71N-B5T
334
APPENDICES
A
(1) Functional comparison
The following table lists the functional comparison.
: Supported, : Not supported
Function
Initial process
Open process*1
AJ71E71
AJ71E71-S3,
AJ71E71N
QE71(N)
9706 or
9706B or
earlier
later
E71
Initial process with the program





Initial process with parameter settings





Open process with the program





Open process with parameter settings





Procedure Exist




*2
No Procedure




*2
Communications using a random access buffer





MC protocol communications




Communications using data link instructions



*4

Communications using a
fixed buffer
*3
*3










Send/receive with the program





Send with the auto notification function





File transfer (FTP server) function





Web function





Broadcast communications





Communications with the switch on the CPU module set to STOP





Selection of the communication data code (ASCII/binary)





CC-Link IE Controller Network, CC-Link IE Field Network,
MELSECNET/H, MELSECNET/10 relay communications



*4

E-mail function





Ping





KeepAlive










*5

 (Fixed)
 (Fixed)
 (Fixed)
 (Fixed)




Router relay function
Connected device alive
check
Pairing open
Unit of each timer setting
value for data
communications
500ms
Connection to
MELSOFT products
TCP/IP





UDP/IP





Installation of EEPROM




*6
TCP Maximum Segment Size Option transmission

*7

*7
*8
Hub connection status monitor function





IP address in use detection function





Communications using SLMP




*9
Data communications using the predefined protocol




*9
Module error collection function





2s
335
Appendix 7 Differences from Ethernet Modules of Other Series
Appendix 7.3 Differences from QnA/A series modules
BUFRCVS instruction
RECVS instruction
Interrupt process (upon
data receiving)
*1
*2
*3
*4
*5
*6
*7
*8
For the E71, the number of connections for the open process from the CPU module has increased to 16 connections.
Compatible with the I/O signal and QE71(N) buffer memory
Data of up to 960 words can be read from/written to an E71, and up to 480 words in a QE71(N).
Availability depends on the CPU module and programming tool version.
This applies to a module with the software version of Q or earlier.
No EEPROM is installed. Items registered in the EEPROM of a QE71(N) are set using the parameter settings of the
programming tool.
This applies to a module with the software version of E or later.
If the E71 cannot communicate data when combined with a certain connected device, the setting can be changed in the
buffer memory (address: 1EH). (
Page 35, Section 3.5.2)
After changing the setting, execute the reinitialization process.
*9
336
Availability depends on the E71 and a programming tool version (
Page 310, Appendix 3).
APPENDICES
A
The response performance of the E71 to connected devices is faster than that of the A/QnA series modules. When the E71
is used, the compatibility with the A/QnA series modules cannot be precisely maintained. If there is a problem due to the
performance of the connected device, create a timing similar to that of the existing system using the CPU module constant
scan setting.
(2) Precautions for using the same program
The QnA/A series modules used for data communications between a CPU module and the connected device on
the Ethernet network can be replaced by an E71. This section describes precautions for using the same program
used in QnA/A series modules.
(a) AJ71E71(-S3) and AJ71E71N
• Program of connected devices
The following communication function programs of connected devices for an AJ71E71(-S3) and
AJ71E71N can be used for communications with an E71. However, because the response speed of the
AJ71E71(-S3) and AJ71E71N is different from that of the E71, the program may not be used as is. Before
using the same program, check the operation.
E71
device 
connected
E71
device
Communications using a fixed buffer
("Procedure Exist")

Communications using a random
access buffer
Data read/write in the CPU module*1
AJ71E71(-S3),
E71AJ71E71(-S3),
AJ71E71NE71
AJ71E71N











: Communications allowed by using the program for an AJ71E71(-S3) and AJ71E71N on the connected device side, -: Not allowed to use
*1
Only A-compatible 1E frame commands can be used for data communications. To perform data communications using a
command other than the A-compatible 1E frame commands, create a new program.
• Program for an AJ71E71(-S3) and AJ71E71N in the own station
Because the assignment of the buffer memory areas for an E71 is different from that for an AJ71E71(-S3)
and AJ71E71N, a program for the AJ71E71(-S3) and AJ71E71N cannot be used for an E71. Create a new
program by referring to chapters that explain each function.
• Program using an I/O signal
Programs cannot be used together with parameter settings on the programming tool.
337
Appendix 7 Differences from Ethernet Modules of Other Series
Appendix 7.3 Differences from QnA/A series modules
Connected
Function
(b) QE71(N)
Program of connected devices
Programs of the connected devices for a QE71(N) can be used for communications with the E71 except for the
following programs.
• Program for file operation-related commands
• Program to access the data link system (A QCPU (Q Mode) cannot be connected to MELSECNET (II).)
However, because the response speed of an E71 is different from that of a QE71(N), the program may not be
used as is. Before using the same program, check the operation.
Program for a QE71(N) in the own station
When using a program for the initial process and the termination process, do not write the parameters of the
E71 (network parameters) set on the programming tool to the LCPU. Note the following when not using the
parameters of an E71 set on the programming tool.
• Because a QE71(N) operates with all of its communication condition setting switches off, set the
communication conditions using the reinitialization process.
• When MELSOFT products (such as a programming tool) are directly connected to an E71, the MELSOFT
products (such as a programming tool) cannot access an LCPU.
To set the parameters of an E71 using the programming tool, delete the programs for the initial process and the
termination process.
Programs for the QE71(N) in the own station can be used for communications with an E71 except for the
following programs.
• Program to access the data link system
• Program related to the EEPROM
• Connection number 8 pairing open setting
• Parameter setting program using the EPRSET instruction
However, because the response speed of an E71 is different from that of a QE71(N), the program may not be
used as is. Before using the same program, check the operation.
Program using an I/O signal
Programs cannot be used together with parameter settings on the programming tool.
● For an E71, set the operation mode and communication conditions using the programming tool. Settings cannot be
configured using a switch unlike QnA/A series modules. (There is no switch for settings.)
● For an E71, after the Passive open process is executed, the open request cannot be cancelled before open completion.
After the open completion, execute the close process.
338
APPENDICES
Appendix 8
Appendix 8.1
Operation Image and Data Structure of
Predefined Protocol
A
Operation image of each communication type of
protocol
In the predefined protocol function, communications with connected devices is performed through the communication
type "Send Only", "Receive Only", or "Send&Receive".
This section describes the operation images of each communication type.
(1) When the communication type is "Send Only"
The specified packet is sent once.
Send data
E71
Data
Header
Connected
device
The operation image of "Send Only" is as follows.
(a) When the instruction ends normally
ECPRTCL instruction
Appendix 8 Operation Image and Data Structure of Predefined Protocol
Appendix 8.1 Operation image of each communication type of protocol
Completion device
Completion device + 1
Waiting time to send
E71
Connected device
Send packet
Send packet
339
(b) When the instruction ends abnormally at TCP (timeout error)
An error has
occurred.
ECPRTCL instruction
Completion device
The device
turns on upon
abnormal end.
Completion device + 1
Waiting time
to send
t: TCP ULP timer
E71
Send packet
Connected device
The packet cannot be sent or
no response is received from
the connected device.
For an error occurred when the communication ends abnormally, refer to the error code stored in the buffer memory.
(
340
Page 273, Section 16.7.3)
APPENDICES
A
(2) When the communication type is "Receive Only"
The receive process completes when the data received from a connected device match the receive packet
(expected packet). If they do not match, the data are discarded.
E71
Receive data 1
Receive packet
(expected packet)
Not matched
Header
Discarded
Receive data 2
Data
Sixteen receive packets
can be specified.
Data
Matched
Header
Connected
device
Data
Received
The operation image of "Receive Only" is as follows.
(a) When the instruction ends normally
ECPRTCL instruction
Completion device
Completion device + 1
Appendix 8 Operation Image and Data Structure of Predefined Protocol
Appendix 8.1 Operation image of each communication type of protocol
E71
Receive data
The receive data matched
the receive packet
(expected packet).
Connected device
Receive data
341
(b) When the instruction ends abnormally (timeout error)
An error has
occurred.
ECPRTCL instruction
Completion device
The device
turns on upon
abnormal end.
Completion device + 1
t: waiting time to receive or the time specified
by the destination alive check timer*1
E71
The receive data
did not match the
receive packet
(expected packet).
Connected device
*1
Receive data
Receive data
When the receive packet (expected packet) is not matched to the data by the waiting time to receive or when the
existence of a connected device cannot be checked within the time specified by the destination alive check timer (the
time calculated based on the destination existence confirmation starting interval timer value, destination existence
confirmation interval timer value, and Destination existence confirmation resending time), the instruction ends
abnormally.
● When variables are included in receive packet (expected packet) elements, variable data are not verified.
● Receive packets (expected packets) can be specified up to 16.
● When multiple receive packets (expected packets) are specified, the received data are verified with the registered receive
packet (expected packet) in order of registration. When the receive packet (expected packet) is matched to the data, the
receive process is completed. The following verification is not performed.
● The receive packet number which is matched in the verification is stored in the control data of the ECPRTCL instruction
and the buffer memory.
● For the error occurred when the communication ends abnormally, refer to the error code stored in the buffer memory.
(
342
Page 273, Section 16.7.3)
APPENDICES
A
(3) When the communication type is "Send&Receive"
When the packet is sent once and the sending completes normally, the status of the E71 changes to the receive
wait status. The process completes when the data received from a connected device match the receive packet
(expected packet) and the receive process is performed.
E71
Send data
Data
Header
Receive data 1
Receive packet
(expected packet)
Not matched
Header
Discarded
Receive data 2
Data
Sixteen receive packets
can be specified.
Connected
device
Data
Matched
Header
Data
Received
The operation image of "Send&Receive" is as follows.
(a) When the instruction ends normally
ECPRTCL instruction
Appendix 8 Operation Image and Data Structure of Predefined Protocol
Appendix 8.1 Operation image of each communication type of protocol
Completion device
Completion device + 1
Waiting time
to send
E71
Waiting time
to receive
Send packet
Receive data
The receive data matched
the receive packet
(expected packet).
Connected device
Send packet
Receive data
343
(b) When the instruction ends abnormally (timeout error at sending)
An error has occurred.
ECPRTCL instruction
Completion device
The device turns on
upon abnormal end.
Completion device + 1
Waiting time
to send
E71
t: TCP ULP timer
Send packet
The packet cannot be
sent or no response is
received from the
connected device.
Connected device
Discarded
Receive data
(c) When the instruction ends abnormally (timeout error of waiting time to receive)
An error has
occurred.
ECPRTCL instruction
Completion device
The device
turns on upon
abnormal end.
Completion device + 1
t: waiting time to receive or the time
specified by the destination alive check timer*1
Waiting time
to send
E71
Send packet
Connected device
Send packet
Receive data
Receive data
The receive data did not
match the receive packet
(expected packet).
*1
When the receive packet (expected packet) is not matched to the data by the waiting time to receive or when the
existence of a connected device cannot be checked within the time specified by the destination alive check timer (the
time calculated based on the destination existence confirmation starting interval timer value, destination existence
confirmation interval timer value, and Destination existence confirmation resending time), the instruction ends
abnormally.
For the error occurred when the communication ends abnormally, refer to the error code stored in the buffer memory.
(
344
Page 273, Section 16.7.3)
APPENDICES
Appendix 8.2
Verification operation of receive packet
A
This section describes the verification operation for a receive packet (expected packet) when the E71 communicates
with a connected device with protocols whose communication type includes receiving.
(1) When received data are matched to a receive packet (expected packet)
The receive process is completed when the receive data are compared with the receive packet (expected
packet), and they are matched.
Receive packet
(expected packet)
Matched
Received
Receive data
(2) When multiple receive packets (expected packets) are specified
The predefined protocol support function enables to register up to 16 receive packets (expected packets).
When the data are received, the registered receive packet (expected packet) is verified in order of registration.
When the receive packet (expected packet) is matched to the data, the receive process is completed.
Receive packets
(expected packets)
No.1
No.2
No.16
Sixteen receive
packets can be
registered.
Matched
Received
Receive data
(3) When received data are not matched to all receive packets (expected packets)
The received data are discarded.
Receive packets
(expected packets)
No.1
Not matched
Receive data
No.2
No.16
When sixteen
receive packets
were registered
Not matched
Discarded
345
Appendix 8 Operation Image and Data Structure of Predefined Protocol
Appendix 8.2 Verification operation of receive packet
Not matched
No.3
Appendix 8.3
Data examples of packet elements
This section describes the procedures for the processing and practical data examples of each element placed in a
packet.
(1) Length
(a) Procedures
The E71 processes a Length element as follows.
[When sending]
Data flow
Forward direction
Sending
Connected device
30H
31H
32H
33H
Length calculating result
33H
123H
Reverse direction
32H
31H
"3210"
"0123"
"0123"
"3210"
"2301"
"1032"
30H
33H
Conversion to
ASCII
hexadecimal
32H
31H
"0"(30H)
30H
31H
32H
33H
32H
33H
30H
31H
30H
"1"(31H)
"2"(32H)
Byte swap
"3"(33H)
31H
30H
33H
32H
[When receiving]
Data flow
Forward direction
Length calculation result
30H
Conversion from ASCII hexadecimal to binary
31H
32H
"0123"
123H
"3210"
3210H
"1032"
1032H
33H
Connected device
Sending
Reverse direction
33H
"0123"
32H
33H
32H
31H
30H
31H
30H
Byte swap
31H
30H
33H
32H
346
APPENDICES
(b) Data flow
A
Data Flow is used to specify the order of send data and receive data.
"Forward Direction (Upper ByteLower Byte)", "Reverse Direction (Lower ByteUpper Byte)", and "Byte
Swap (by Word)" can be used as the Data Flow.
• Forward Direction and Reverse Direction: Available when the Data Length is 2 bytes or more.
• Byte Swap: Available only when the Data Length is 4 bytes.
(c) Calculating range for the length
The following shows the specification examples of calculating range for the length.
Packet format
Example 1
Example 2
Example 3
Packet
element 1
Packet
element 2
Packet
element 3
Packet
element 30
Packet
element 31
Packet
element 32
Static data
Length
Non-conversion
variable
Static data
Static data
Static data
Calculating
range for
the length
Calculating range for the length
Calculating range for the length
Example 1) Calculating range when its start is 3 and end is 3
Example 2) Calculating range when its start is 3 and end is 30
Example 3) Calculating range when its start is 1 and end is 32
Appendix 8 Operation Image and Data Structure of Predefined Protocol
Appendix 8.3 Data examples of packet elements
347
(2) Non-conversion Variable
(a) Procedures
The E71 processes a Non-conversion Variable element as follows.
When the setting for "Unit of Stored Data" is "Lower Byte + Upper Byte"
• When the data length of a send packet is an odd number, the upper byte (lower byte for "Byte Swap") of
the last device is not sent.
• When the data length of a receive packet is an odd number, the last data is stored with one byte of 00H.
Ex. When sending data whose length is an odd number
(Word)
Specified device
Data length storage area
+0
0005H
Data storage area
+1
0201H
+2
0403H
+3
0605H
Sending
Connected
device
Send data
No byte swap
06H
05H
04H
↑
Data are not sent.
↓
05H
06H
03H
03H
02H
01H
04H
01H
02H
Byte swap
Ex. When receiving data whose length is an odd number
(Word)
Specified device
Data length storage area + 0
0005H
Data storage area
+1
0201H
+2
0403H
+3
0005H
No byte swap
Send data
Receiving
(Word)
Specified device
Data length storage area + 0
0005H
Data storage area
+1
0102H
+2
0304H
+3
0500H
01H
02H
03H
04H
Connected
device
05H
Byte swap
When the setting for "Unit of Stored Data" is "Lower Bytes Only"
• Twice the size of the data length is occupied.
For the upper data, the E71 ignores the data at sending and adds 00H to the data at receiving.
348
APPENDICES
A
(3) Non-verified Reception
The following shows the usage example for a Non-verified Reception element.
Example of a packet format of the connected device
Necessary information for users
1 byte
2 bytes
2 bytes
5 bytes
5 bytes
STX
Identification
code
Country
code
Manufacturer
code
Product
code
Variable number of
characters
1 byte
EXT
Reading data
Non-verified reception is
set in the elements.
When the information is unnecessary
for users and the data
(including the number of characters)
are variable
Example of a packet setting
2 bytes
2 bytes
Variable number of characters
1 byte
Static data
Non-conversion
variable
Non-verified reception (variable number of characters)
Static data
Setting the packet format as above and setting the "Non-verified Reception" enable the followings.
• Only necessary information can be stored in a device of the CPU module or the buffer memory.
• Only one protocol (packet) is required even when the data that may change in each communication are
included in the receive packet.
Appendix 8 Operation Image and Data Structure of Predefined Protocol
Appendix 8.3 Data examples of packet elements
349
Appendix 9
Sample Program on the Connected Device
Side
The following shows a sample program for the connected device on the same Ethernet network as the E71. Each
program example describes only the minimum programming that is required to perform a communication test. Change
the IP address, port number and other values according to the system configuration used. Other processes such as a
process performed upon an error can be added.
(1) Receive process of the connected device
A receive processing example on the connected device side is shown below.
Communication process on the connected device
Request message/send process
Response message/receive process
Is the TCP connection open?
The TCP connection is closed.
Receive the remaining
response messages.
Were the data
received within the monitoring
timer value?
Timeout of the monitoring timer value
The received data size
is insufficient.
Check the received data size.
Response message process
If the response message to
the next request has been
received
Have all the received messages
been processed?
End
Error process
For Ethernet communications, the TCP socket functions are used inside the personal computer. However, these functions
do not have any limit. Therefore, when the "send" function is executed once to transmit data, the receiving side needs to
execute the "recv" function once or more to read the data ("send" and "recv" are not proportional to 1:1 execution). For this
reason, the receive process above is required.
350
APPENDICES
A
(2) When the receive process of the connected device is not supported
When the receive process of the connected device is not the one shown in (1), the following may occur when
"Enable TCP Maximum Segment Size Option transmission" is set for communications.
• When batch reading is executed from the connected device using the MC protocol, data cannot be normally
read.
• After replacing the E71 (which does not support the TCP Maximum Segment Size Option transmission
function) with the alternative module supporting the function, data cannot be normally read.
• Even though the value in Received TCP packet count (Address: 1B8H and 1B9H) in the buffer memory was
changed, data cannot be received.
If these errors occur, select "Disable TCP Maximum Segment Size Option transmission".
Appendix 9 Sample Program on the Connected Device Side
351
Appendix 9.1
When Visual C++(R).NET is used
This section describes the program execution environment, data communication details, and a sample program for
when Visual C++.NET is used on the program of a connected device.
(1) Execution environment of the program example
(a) CPU module side
Item
Description
A model name of the LCPU in the E71-connected station
L02CPU
E71 I/O signal
X/Y00 to X/Y1F
E71 IP address
C0.00.01.FDH (192.00.01.253)
E71 port number
2000H
Ethernet operation
setting
Programming tool setting
Open setting
Refer to Page 353, Appendix 9.1 (3) (a).
Refer to Page 353, Appendix 9.1 (3) (b).
(b) Connected device side
Item
Operation environment
Description
Microsoft
Windows
XP Professional Operating System
Ver.2002 Service Pack2
Ethernet interface board model name
WINSOCK compatible board
Library to link
WSOCK32.LIB
Software development environment
MAC address
Visual C++.NET 2003 manufactured by Microsoft
Corporation
This setting is not required because the ARP function can be
used.
IP address
Received upon an Active open
Port number
Received upon an Active open
(c) Communication protocol
TCP/IP is used.
(2) Outline of the program example
(a) Program on the CPU module side
Because parameters are set on the programming tool, no program is required.
(b) Program on the connected device side
Read/write data from/to the CPU module using the library described above.
• Write in word units (for five points from D0 to D4)
• Read in word units (for five points from D0 to D4)
352
APPENDICES
A
(3) Programming tool setting
Set the parameters using the programming tool as shown below.
(a) Ethernet operation setting
(b) Open setting
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.1 When Visual C++(R).NET is used
353
(4) Sample program on the connected device side
The program example of the connected device accessing the L02CPU in the E71-connected station is described.
When this program is executed, the contents of the following communication messages are displayed in order:
• Batch write command message in word units
• Batch write response message in word units
• Batch read command message in word units
• Batch read response message in word units
Remark
● The following is an outline of how to compile a program created using Microsoft Corporation Visual C++.NET.
• Start Visual C++.NET.
• Create a project. From [File][New][Project], select ".NET" in "Project Types" and "Empty Project" in
"Templates", and set the project name (e.g. AJSAMP) and location.
• Create a source file. Open Solution Explorer. Then right-click Source Files and select [Add][Add New Item]. Set
the file name (e.g. AJSAMP.cpp) and location, and create a program according to the program example.
• From the project setting window, get WSOCK32.LIB linked. Open Solution Explorer. Then right-click the project
name (AJSAMP) and select [Properties][Configuration Properties][Linker][Command Line]. Type
WSOCK32.LIB in Additional Options and press the OK button.
• On the Build menu, click Build Solution to create an execution file (AJSAMP.EXE).
• Exit Visual C++.NET.
• Execute AJSAMP.EXE.
● The following is an outline of how to implement a socket routine call.
Start
socket()
(Socket created)
bind()
(Bind)
Passive open
(Open)
Active open
listen()
UDP
connect()
accept()
(Communications)
send()/recv()
(Sending/reception disabled)
shutdown()
(Close)
closesocket
Completed
354
sendto()/recvfrom()
APPENDICES
A
/**************************************************************************/
/** Sample program (program name: AJSAMP.CPP) **/
/** **/
/** This program is a sample program to conduct a **/
/** connection test between the E71 and target device. **/
/** This program accesses the data register (D) of **/
/** the PLC CPU installed together with the E71 **/
/** **/
/** Copyright(C) 2005 Mitsubishi Electric Corporation **/
/** All Rights Reserved **/
/**************************************************************************/
#include <stdio.h>
#include <winsock.h>
#define FLAG_OFF
#define FLAG_ON
#define SOCK_OK
#define SOCK_NG
#define BUF_SIZE
0
1
2
3
4
5
6
7
// Completion flag OFF
// Completion flag ON
// Normal completion
// Abnormal completion
// Receive buffer size
// Initial error
// Socket creation error
// Bind error
// Connection error
// Send error
// Receive error
// Shutdown error
// Line close error
//Definitions for checking the receiving sizes
//#define RECV_ANS_1 4 // Receiving size of response message in reply to device write (1E frame)
#define RECV_ANS_1 22 // Receiving size of response message in reply to device write (3E frame)
//#define RECV_ANS_2 24 // Receiving size of response message in reply to device read (1E frame)
#define RECV_ANS_2 42 // Receiving size of response message in reply to device read (3E frame)
typedef struct sck_inf{
struct in_addr my_addr;
unsigned short my_port;
struct in_addr aj_addr;
unsigned short aj_port;
}sck_inf;
355
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.1 When Visual C++(R).NET is used
#define ERROR_INITIAL
#define ERROR_SOCKET
#define ERROR_BIND
#define ERROR_CONNECT
#define ERROR_SEND
#define ERROR_RECEIVE
#define ERROR_SHUTDOWN
#define ERROR_CLOSE
0
1
0
-1
4096
int nErrorStatus;
int Dmykeyin;
int Closeflag;
int socketno;
int main()
{
WORD wVersionRequested=MAKEWORD(1,1);
WSADATA wsaData;
int length;
unsigned char s_buf[BUF_SIZE];
unsigned char r_buf[BUF_SIZE];
int rbuf_idx;
int recv_size;
struct sck_inf sc;
struct sockaddr_in hostdata;
struct sockaddr_in aj71e71;
void Sockerror(int);
// Error information storage variable
// Dummy key input
// Connection completion flag
// Winsock Ver 1.1 request
// Communication data length
// Send buffer
// Receive buffer
// Receive data storage head index
// Number of receive data
// External device side data
// E71 side data
// Error handling function
unsigned long ulCmdArg ;
// Non-blocking mode setting flag
sc.my_addr.s_addr=htonl(INADDR_ANY);
sc.my_port=htons(0);
sc.aj_addr.s_addr=inet_addr("192.0.1.253");
sc.aj_port=htons(0x2000);
// External device side IP address
// External device side port number
// E71 side IP address (C00001FDH)
// E71 side port number
Closeflag=FLAG_OFF;
// Connection completion flag off
nErrorStatus=WSAStartup(wVersionRequested,&wsaData);
// Winsock Initial processing
if(nErrorStatus!=SOCK_OK) {
Sockerror(ERROR_INITIAL);
return(SOCK_NG);
}
// Error handling
printf("Winsock Version is %ld.%ld\n",HIBYTE(wsaData.wVersion), LOBYTE(wsaData.wVersion));
printf("AJ_test Start\n");
socketno=socket(AF_INET,SOCK_STREAM,0);
if(socketno==INVALID_SOCKET){
Sockerror(ERROR_SOCKET);
return(SOCK_NG);
}
356
// Create socket for TCP/IP
// Error handling
APPENDICES
A
hostdata.sin_family=AF_INET;
hostdata.sin_port=sc.my_port;
hostdata.sin_addr.s_addr=sc.my_addr.s_addr;
if(bind(socketno,(LPSOCKADDR)&hostdata,sizeof(hostdata))!=SOCK_OK){
// Bind
Sockerror(ERROR_BIND); // Error handling
return(SOCK_NG);
}
aj71e71.sin_family=AF_INET;
aj71e71.sin_port=sc.aj_port;
aj71e71.sin_addr.s_addr=sc.aj_addr.s_addr;
if(connect(socketno,(LPSOCKADDR)&aj71e71,sizeof(aj71e71))!=SOCK_OK){
// Connection (Active open)
Sockerror(ERROR_CONNECT); // Error handling
return(SOCK_NG);
}
Closeflag=FLAG_ON;
// Set to non-blocking mode
ulCmdArg = 1;
ioctlsocket(socketno, FIONBIO, &ulCmdArg);
//
// Connection completion flag ON
// Set to non-blocking mode
length = strlen((char *)(s_buf));
if(send(socketno, (char *)(s_buf), length, 0) == SOCKET_ERROR) {
// Data sending
Sockerror(ERROR_SEND); // Error handling
return (SOCK_NG);
}
printf("\n send data\n%s\n",s_buf);
357
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.1 When Visual C++(R).NET is used
strcpy((char *)(s_buf), "03FF000A4420000000000500112233445566778899AA");
// D0 to D4 batch write request (1E frame)
strcpy((char *)(s_buf),"500000FF03FF00002C000A14010000D
*0000000005112233445566778899AA");
// D0 to D4 batch write request (3E frame)
// Perform receiving size check and receiving processing simultaneously
rbuf_idx = 0;
// Receive data storage head index initialization
recv_size = 0;
// Initialize the number of receive data
while(1) {
length = recv(socketno, (char*) (&r_buf[rbuf_idx]), (BUF_SIZE - rbuf_idx), 0);
// Response data receiving
if(length == 0) { // Is connection cut off?
Sockerror(ERROR_RECEIVE);
// Error handling
return (SOCK_NG);
}
if(length == SOCKET_ERROR) {
nErrorStatus = WSAGetLastError();
if(nErrorStatus != WSAEWOULDBLOCK) {
Sockerror(ERROR_RECEIVE);
return (SOCK_NG);
} else {
continue;
}
} else {
rbuf_idx += length;
recv_size += length;
if(recv_size >= RECV_ANS_1)
break;
}
}
r_buf[rbuf_idx] = '\0' ;
// Error handling
// Repeat until messages are received
// Update the receive data storage
// position
// Update the number of receive data
// Have all response messages been
// received?
// Stop repeating as messages have
// been received
// Set NULL at the end of receive data
printf("\n receive data\n%s\n",r_buf);
//
strcpy((char *)(s_buf), "01FF000A4420000000000500");
// D0 to D4 batch read request
// (1E frame)
strcpy((char *)(s_buf), "500000FF03FF000018000A04010000D*0000000005");
// D0 to D4 batch read request
// (3E frame)
length = strlen((char *)(s_buf));
if(send(socketno, (char *)(s_buf), length, 0) == SOCKET_ERROR) {
// Data sending
Sockerror(ERROR_SEND);
// Error handling
return (SOCK_NG);
}
printf("\n send data\n%s\n",s_buf);
358
APPENDICES
A
// Perform receiving size check and receiving processing simultaneously
rbuf_idx = 0;
// Receive data storage head index
// initialization
recv_size = 0; // Initialize the number of receive data
while(1) {
length = recv(socketno, (char*)(&r_buf[rbuf_idx]), (BUF_SIZE - rbuf_idx), 0);
// Response data receiving
if(length == 0) {
// Is connection cut off?
Sockerror(ERROR_RECEIVE);
// Error handling
return (SOCK_NG);
}
if(length == SOCKET_ERROR) {
nErrorStatus = WSAGetLastError();
if(nErrorStatus != WSAEWOULDBLOCK) {
Sockerror(ERROR_RECEIVE);
return (SOCK_NG);
} else {
continue;
}
} else {
rbuf_idx += length;
recv_size += length;
if(recv_size >= RECV_ANS_2)
break;
// Repeat until messages are received
// Update the receive data storage
// position
// Update the number of receive data
// Have all response messages been
// received?
// Stop repeating as messages have
// been received
// Set NULL at the end of receive data
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.1 When Visual C++(R).NET is used
}
}
r_buf[rbuf_idx] = '\0' ;
// Error handling
printf("\receive data\n%s\n", r_buf);
if(shutdown(socketno,2)!=SOCK_OK){
Sockerror(ERROR_SHUTDOWN);
return(SOCK_NG);
}
if(closesocket(socketno)!=SOCK_OK){
Sockerror(ERROR_CLOSE);
return(SOCK_NG);
}
Closeflag=FLAG_OFF;
WSACleanup();
// Processing to disable
// sending/receiving
// Error handling
// Close processing
// Error handling
// Connection completion flag off
// Release Winsock.DLL
printf("\nAJ_test End.\n\n Normally completed. \n");
printf("Press any key to exit the program.\n");
Dmykeyin=getchar(); // Wait for key input
return(SOCK_OK);
}
359
void Sockerror(int error_kind) // Error handling function
{
if(error_kind==ERROR_INITIAL){
printf("Initial processing is abnormal.");
}
else{
nErrorStatus=WSAGetLastError();
switch(error_kind){
case ERROR_SOCKET:
printf("Failed to create socket.");
break;
case ERROR_BIND:
printf("Failed to bind.");
break;
case ERROR_CONNECT:
printf("Failed to establish connection.");
break;
case ERROR_SEND:
printf("Sending failed.");
break;
case ERROR_RECEIVE:
printf("Receiving failed.");
break;
case ERROR_SHUTDOWN:
printf("Failed to shutdown.");
break;
case ERROR_CLOSE:
printf("Failed to close normally.");
break;
}
}
printf("Error code is %d.\n", nErrorStatus);
if(Closeflag==FLAG_ON){
nErrorStatus=shutdown(socketno,2);
// Shutdown processing
nErrorStatus=closesocket(socketno);
// Close processing
Closeflag=FLAG_OFF;
// Connection completion flag off
}
printf("Press any key to exit the program.\n");
Dmykeyin=getchar();
WSACleanup();
return;
}
360
// Wait for a key input
// Release Winsock.DLL
APPENDICES
Appendix 9.2
When Visual Basic(R).NET is used
A
This section describes the program execution environment, data communication details, and a sample program for
when Visual Basic.NET is used on the program of the connected device.
(1) Execution environment of the program example
(a) CPU module side
Item
Description
A model name of the LCPU in the E71-connected station
L02CPU
E71 I/O signal
X/Y00 to X/Y1F
E71 IP address
C0.00.01.FDH (192.00.01.253)
E71 port number
2000H
Ethernet operation
setting
Programming tool setting
Open setting
Refer to Page 362, Appendix 9.2 (3) (a).
Refer to Page 362, Appendix 9.2 (3) (b).
(b) Connected device side
Item
Operation environment
Ethernet interface board model name
Software development environment
Windows
XP Professional Operating System
Ver.2002 Service Pack2
WINSOCK compatible board
Visual Basic.NET 2003 manufactured by Microsoft
Corporation
This setting is not required because the ARP function can be
used.
IP address
An arbitrary number is assigned.
Port number
An arbitrary number is assigned.
(c) Communication protocol
TCP/IP is used.
(2) Outline of the program example
(a) Program on the CPU module side
Because parameters are set on the programming tool, no program is required.
(b) Program on the connected device side
Data (D0 to D4) in the CPU module are read out.
361
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.2 When Visual Basic(R).NET is used
MAC address
Description
Microsoft
(3) Programming tool setting
Set the parameters using the programming tool as shown below.
(a) Ethernet operation setting
(b) Open setting
362
APPENDICES
A
(4) Sample program on the connected device side
The program example of the connected device accessing the L02CPU in the E71-connected station is described.
In this program, data of D0 to D4 (five points) in the L02CPU in the E71-connected station are read with an Acompatible 1E frame command (01: Batch read in word units). The following are basic operation procedures:
• Sending a command with the line disconnected (Connect the line. After completing the connection, the E71
sends a command.)
• Reconnecting the line with it connected (Disconnect the line. After the disconnection is completed, reconnect
it.)
Remark
The following is an outline of how to compile a program created using Microsoft Corporation Visual Basic.NET.
• Start Visual Basic.NET.
• Create a project. From [File][New][Project], select "Visual Basic Project" in "Project Types" and "Windows
Application" in "Templates", and set the project name (e.g. AJSAMP) and location.
• Create a form and a program. Use the toolbox "Button" to create the sample window shown below (Form1.vb) and
create a program referring to the sample program.
• On the Build menu, click Build Solution to create an execution file (AJSAMP.EXE).
• Exit the Visual Basic.NET.
• Execute the AJSAMP.EXE.
[Window example (Form 1.vb)]
(Object name)
Button1: Connects the station with the E71.
Button5:
Checks the connection status.
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.2 When Visual Basic(R).NET is used
Button2: Sends the A-compatible 1E frame command
(reading in units of words).
Button3: Cut off the line.
Button4: Ends the program.
363
[Sample program (Form 1.vb)]
Option Strict Off
Option Explicit ON
Imports System
Imports System.Text
Imports System.Net
Friend Class Form1
Inherits System. Windows. Forms. Form
#Region "Windows Form Designer generated code"
Public Sub New()
MyBase.New()
If m_vb6FormDefInstance Is Nothing Then
If m_InitializingDefInstance Then
m_vb6FormDefInstance = Me
Else
Try
‘For the start-up form, the first instance created is the default instance.
If System. Reflection. Assembly. GetExecutingAssembly. EntryPoint
.DeclaringType Is Me.GetType Then
m_vb6FormDefInstance = Me
EndIf
Catch
End Try
End If
End If
‘ This call is required by the Windows form designer.
InitializeComponent()
End Sub
364
APPENDICES
A
'Form overrides dispose to clean up the component list.
Protected Overloads Overrides Sub Dispose(ByVal Disposing As Boolean)
If Disposing Then
If Not components Is Nothing Then
components.Dispose()
End If
End If
MyBase.Dispose(Disposing)
End Sub
‘Required by the Windows Form Designer.
Private components As System.ComponentModel.IContainer
Public WithEvents Command5 As System.Windows.Forms.Button
Public WithEvents Command4 As System.Windows.Forms.Button
Public WithEvents Command3 As System.Windows.Forms.Button
Public WithEvents Command2 As System.Windows.Forms.Button
Public WithEvents Command1 As System.Windows.Forms.Button
Dim Ajsock As Sockets.Socket
Private State As Boolean = False
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.2 When Visual Basic(R).NET is used
'NOTE: The following procedure is required by the Windows Form Designer.
'It can be modified using the Windows Form Designer.
'Do not modify it using the code editor.
<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()
Me.Command5 = New System.Windows.Forms.Button
Me.Command4 = New System.Windows.Forms.Button
Me.Command3 = New System.Windows.Forms.Button
Me.Command2 = New System.Windows.Forms.Button
Me.Command1 = New System.Windows.Forms.Button
Me.SuspendLayout()
'
'Command5
'
Me.Command5.BackColor = System.Drawing.SystemColors.Control
Me.Command5.Cursor = System.Windows.Forms.Cursors.Default
Me.Command5.ForeColor = System.Drawing.SystemColors.ControlText
Me.Command5.Location = New System.Drawing.Point(64, 152)
Me.Command5.Name = "Command5"
Me.Command5.RightToLeft = System.Windows.Forms.RightToLeft.No
Me.Command5.Size = New System.Drawing.Size(72, 32)
Me.Command5.TabIndex = 4
Me.Command5.Text = "Connection status"
'
'Command4
'
365
Me.Command4.BackColor = System.Drawing.SystemColors.Control
Me.Command4.Cursor = System.Windows.Forms.Cursors.Default
Me.Command4.ForeColor = System.Drawing.SystemColors.ControlText
Me.Command4.Location = New System.Drawing.Point(144, 152)
Me.Command4.Name = "Command4"
Me.Command4.RightToLeft = System.Windows.Forms.RightToLeft.No
Me.Command4.Size = New System.Drawing.Size(73, 32)
Me.Command4.TabIndex = 3
Me.Command4.Text = "Close"
'
'Command3
'
Me.Command3.BackColor = System.Drawing.SystemColors.Control
Me.Command3.Cursor = System.Windows.Forms.Cursors.Default
Me.Command3.ForeColor = System.Drawing.SystemColors.ControlText
Me.Command3.Location = New System.Drawing.Point(64, 96)
Me.Command3.Name = "Command3"
Me.Command3.RightToLeft = System.Windows.Forms.RightToLeft.No
Me.Command3.Size = New System.Drawing.Size(152, 33)
Me.Command3.TabIndex = 2
Me.Command3.Text = "disconnect"
'
'Command2
'
Me.Command2.BackColor = System.Drawing.SystemColors.Control
Me.Command2.Cursor = System.Windows.Forms.Cursors.Default
Me.Command2.ForeColor = System.Drawing.SystemColors.ControlText
Me.Command2.Location = New System.Drawing.Point(64, 56)
Me.Command2.Name = "Command2"
Me.Command2.RightToLeft = System.Windows.Forms.RightToLeft.No
Me.Command2.Size = New System.Drawing.Size(152, 31)
Me.Command2.TabIndex = 1
Me.Command2.Text = "Sending a E71 command"
'
'Command1
'
Me.Command1.BackColor = System.Drawing.SystemColors.Control
Me.Command1.Cursor = System.Windows.Forms.Cursors.Default
Me.Command1.ForeColor = System.Drawing.SystemColors.ControlText
Me.Command1.Location = New System.Drawing.Point(64, 16)
Me.Command1.Name = "Command1"
Me.Command1.RightToLeft = System.Windows.Forms.RightToLeft.No
Me.Command1.Size = New System.Drawing.Size(152, 31)
Me.Command1.TabIndex = 0
Me.Command1.Text = "connect"
366
APPENDICES
A
'
'Form1
'
Me.AutoScaleBaseSize = New System.Drawing.Size(5, 12)
Me.BackColor = System.Drawing.SystemColors.Control
Me.ClientSize = New System.Drawing.Size(280, 214)
Me.Controls.Add(Me.Command5)
Me.Controls.Add(Me.Command4)
Me.Controls.Add(Me.Command3)
Me.Controls.Add(Me.Command2)
Me.Controls.Add(Me.Command1)
Me.Cursor = System.Windows.Forms.Cursors.Default
Me.Location = New System.Drawing.Point(329, 189)
Me.Name = "Form1"
Me.RightToLeft = System.Windows.Forms.RightToLeft.No
Me.StartPosition = System.Windows.Forms.FormStartPosition.Manual
Me.Text = "Form1"
Me.ResumeLayout(False)
End Sub
#End Region
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.2 When Visual Basic(R).NET is used
#Region "Upgrade Wizard support code"
Private Shared m_vb6FormDefInstance As Form1
Private Shared m_InitializingDefInstance As Boolean
Public Shared Property DefInstance() As Form1
Get
If m_vb6FormDefInstance Is Nothing OrElse m_vb6FormDefInstance.IsDisposed Then
m_InitializingDefInstance = True
m_vb6FormDefInstance = New Form1()
m_InitializingDefInstance = False
End If
DefInstance = m_vb6FormDefInstance
End Get
Set
m_vb6FormDefInstance = Value
End Set
End Property
#End Region
367
Private Sub Command1_Click(ByVal eventSender As System.Object, ByVal eventArgs
As System.EventArgs) Handles Command1.Click
'Connect to the Ethernet interface module.
Dim sock As New Sockets.Socket(Sockets.AddressFamily.InterNetwork, _
Sockets.SocketType.Stream, Sockets.ProtocolType.Tcp)
Ajsock = sock
Dim ip As IPAddress = Dns.Resolve("192.0.1.253").AddressList(0)
Dim ipend As IPEndPoint = New IPEndPoint(ip, "8192")
Me.Ajsock.Connect(ipend)
MsgBox("Connection Completed")
State = Me.Ajsock.Connected()
End Sub
Private Sub Command2_Click(ByVal eventSender As System.Object, ByVal eventArgs
As System.EventArgs) Handles Command2.Click
Dim SData As Byte()
Dim RData(256) As Byte
'Rend D0 to D4 (5 points) with the A-compatible 1E frame command.
SData = Encoding.ASCII.GetBytes("01FF000A4420000000000500")
'Read D0 to D4 (5 points) with the QnA-compatible 3E frame command.
'SData = Encoding.ASCII.GetBytes("500000FF03FF000018000A04010000D
*0000000005")
'Send the data.
Me.Ajsock.Send(SData)
MsgBox("Send completion", MsgBoxStyle.Information)
'Read the response from the PLC CPU.
Me.Ajsock.Receive(RData)
MsgBox(Encoding.ASCII.GetString(RData), MsgBoxStyle.Information)
End Sub
Private Sub Command3_Click(ByVal eventSender As System.Object, ByVal eventArgs
As System.EventArgs) Handles Command3.Click
'Close the TCP (UDP) connection socket (disconnect the line).
Me.Ajsock.Shutdown(Net.Sockets.SocketShutdown.Both)
Me.Ajsock.Close()
MsgBox("The disconnection was successful", MsgBoxStyle.Information)
State = Me.Ajsock.Connected()
End Sub
368
APPENDICES
A
Private Sub Command4_Click(ByVal eventSender As System.Object, ByVal eventArgs
As System.EventArgs) Handles Command4.Click
'End the program.
End
End Sub
Private Sub Command5_Click(ByVal eventSender As System.Object, ByVal eventArgs
As System.EventArgs) Handles Command5.Click
'Check the connection state.
If State Then
MsgBox("Connected")
Else
MsgBox("Closed")
End If
End Sub
End Class
Appendix 9 Sample Program on the Connected Device Side
Appendix 9.2 When Visual Basic(R).NET is used
369
Appendix 10 Checking the Serial Number, Function
Version, and MAC address
(1) Checking the serial number and function version
The serial number and function version can be checked on the rating plate or with the system monitor.
Refer to the following.
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)
(2) Checking the MAC address
The MAC address can be checked on the rating plate or with the Ethernet diagnostics.
For how to check the MAC address on the rating plate, refer to the following.
MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)
To use the Ethernet diagnostics, refer to Page 300, Section 16.8 in this manual.
370
APPENDICES
Appendix 11 External Dimension Diagram
A
90
45
4
This appendix provides the external dimension diagrams of an E71.
4
(45)
DIN rail center
4
95
28.5
(Unit: mm)
Appendix 11 External Dimension Diagram
371
Appendix 12 ASCII Code List
The following is the ASCII code table.
Higher 4 bits
Hexadecimal
Binary
Lower
4 bits
372
0
1
2
3
4
5
6
7
8–F
0000
0001
0010
0111
0100
0101
0110
0111
1000–1111
0
0000
NUL
DLE
(SP)
0
@
P
`
p
1
0001
SOH
DC1
!
1
A
Q
a
q
2
0010
STX
DC2
"
2
B
R
b
r
3
0011
ETX
DC3
#
3
C
S
c
s
4
0100
EOT
DC4
$
4
D
T
d
t
5
0101
ENQ
NAK
%
5
E
U
e
u
6
0110
ACK
SYN
&
6
F
V
f
v
G
W
g
w
7
0111
BEL
ETB
‘
7
8
1000
BS
CAN
(
8
H
X
h
x
9
1001
HT
EM
)
9
I
Y
i
y
A
1010
LF
SUB
*
:
J
Z
j
z
B
1011
VT
ESC
+
;
K
[
k
{
C
1100
FF
FS
,
<
L
\ (¥)
l
|
D
1101
CR
GS
-
=
M
]
m
}
E
1110
SO
RS
.
>
N
^
n
~
F
1111
SI
US
/
?
O
_
o
DEL
INDEX
0 to 9
100BASE-TX connection .
100Mbps hub . . . . . . . . .
10BASE-T connection . . .
10Mbps hub . . . . . . . . . .
4E frame . . . . . . . . . . . .
D
. . . . . . . . . . . . . . . . . . . 58
. . . . . . . . . . . . . . . . . . . 58
. . . . . . . . . . . . . . . . . . . 59
. . . . . . . . . . . . . . . . . . . 59
. . . . . . . . . . . . . . . . . . . 86
Data format . . . . . . . . . . . . . . . . . . . . . . . . 133,158
Data receiving using an interrupt program . . . . . . . 128
Data receiving using the main program . . . . . . . . . 125
Data transmission speed . . . . . . . . . . . . . . . . . . . . 27
Dedicated instruction. . . . . . . . . . . . . . . . . . . . . . 196
Default router IP address . . . . . . . . . . . . . . . . . . . 171
Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Differences from Ethernet modules of other series
Abnormal codes . . . . . . . . . . . . . . . . . . . . . . . . . 272
A-compatible 1E frame . . . . . . . . . . . . . . . . . . . . . 86
Active open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Alive check function . . . . . . . . . . . . . . . . . . . . . . 194
Always wait for OPEN (communication possible at
STOP time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Applicable software . . . . . . . . . . . . . . . . . . . . . . . . 60
Applicable systems . . . . . . . . . . . . . . . . . . . . . . . . 60
Application data . . . . . . . . . . . . . . . . . . . . . 133,159
ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
ASCII code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Auto-open UDP port . . . . . . . . . . . . . . . . . . . . . . 309
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
A
E71 . . . . . . . . . . . . . . . . . . .
E71-connected station. . . . . .
ECPRTCL . . . . . . . . . . . . . .
E-mail function . . . . . . . . . . .
Enable online change . . . . . .
End codes . . . . . . . . . . . . . .
ERRCLR . . . . . . . . . . . . . . .
Error code list . . . . . . . . . . . .
ERRRD . . . . . . . . . . . . . . . .
Ethernet diagnostics . . . . . . .
Ethernet operation setting . . .
External dimension diagram . .
. . . . . . . . . . . . . . . . 16
. . . . . . . . . . . . . . . . 16
. . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . . 30
. . . . . . . . . . . . . . . . 67
. . . . . . . . . . . . . . . 268
. . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . 258
. . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . 300
. . . . . . . . . . . . . . . . 67
. . . . . . . . . . . . . . . 371
F
Cascade connection . . . . . . . . . . . . . . . . . . . . . . . 27
CC-Link IE Controller Network, CC-Link IE Field
Network, MELSECNET/H, MELSECNET/10 relay
communications . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . 242
Checking the serial number, function version, and
MAC address . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Checking the status of the E71 with the system
monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Checking with the module error collection function
File transfer (FTP server) function .
Fixed buffer . . . . . . . . . . . . . . . . .
Fixed buffer communication . . . . . .
FTP. . . . . . . . . . . . . . . . . . . . . . .
Fullpassive. . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . 30
. . . . . . . . . . . 130
. . . . . . . . . . . 130
. . . . . . . . . . . . 16
. . . . . . . . . . . . 77
G
General specifications .
GP.ECPRTCL . . . . . .
Group No. . . . . . . . . .
GX Developer . . . . . .
GX Works2 . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Communication data code . . . . . . . . . . . . . . . . . . . 67
Communication procedure . . . . . . . . . . . . . . . . . . . 64
Communications using a fixed buffer . . . . . . . . . . . 120
Communications using a random access buffer . . . 154
Communications using an auto-open UDP port . . . 174
Communications using data link instructions . . . . . . 30
Compliance with EMC and Low Voltage Directives . . . 6
Connecting MELSOFT products and a GOT . . . . . . 82
Connection target . . . . . . . . . . . . . . . . . . . . . . . . . 83
4
E
. . . . . . . . . . . . . . . . . 29
. . . . . . . . . . . . . . . . . 66
. . . . . . . . . . . . . . . . . 63
. . . . . . . . . . . . . . . . 141
. . . . . . . . . . . . . . . . . 34
. . . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . . 196
C
4
Differences in functions according to the remote
password check status (enabled/disabled) . . . . . . 186
DIN rail hook . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Display unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Do not wait for OPEN (Communications impossible
at STOP time) . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
B
Basic functions . . . . . . . . . .
Basic setting . . . . . . . . . . . .
Bend radius . . . . . . . . . . . .
Broadcast communications .
Buffer memory . . . . . . . . . .
BUFRCV . . . . . . . . . . . . . .
BUFRCVS . . . . . . . . . . . . .
BUFSND . . . . . . . . . . . . . .
I
. . . . . . . . . . . . . . . . . . . . . 27
. . . . . . . . . . . . . . . . . . . . 206
. . . . . . . . . . . . . . . . . . . . . 66
. . . . . . . . . . . . . . . . . . . . . 16
. . . . . . . . . . . . . . . . . . 16,60
H
H/W test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Hardware test. . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Header . . . . . . . . . . . . . . . . . . . . . . . . . . . 133,158
How to turn off the COM.ERR. LED . . . . . . . . . . . 303
HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Hub connection status monitor function . . . . . . . . . 191
373
7
8
Open system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Other functiona . . . . . . . . . . . . . . . . . . . . . . . . . 169
I
ICMP . . . . . . . . . . . . . . . . . . . . . . .
Initial process . . . . . . . . . . . . . . . . .
Initial timing . . . . . . . . . . . . . . . . . . .
Input format . . . . . . . . . . . . . . . . . . .
Installation . . . . . . . . . . . . . . . . . . . .
Intelligent function module. . . . . . . . .
Internal current consumption (5VDC) .
Interrupt pointer setting . . . . . . . . . . .
Interrupt settings . . . . . . . . . . . . . . .
IP . . . . . . . . . . . . . . . . . . . . . . . . . .
IP address . . . . . . . . . . . . . . . . . . . .
IP address in use detection function . .
IP address setting . . . . . . . . . . . . . .
IP filter function . . . . . . . . . . . . . . . .
. . . . . . . . . . 16
. . . . . . . . . 311
. . . . . . . . 67,68
. . . . . . . . . . 67
. . . . . . . . . . 61
. . . . . . . . . . 16
. . . . . . . . . . 27
. . . . . . . . . 131
. . . . . . . . . 132
. . . . . . . . . . 16
. . . . . . . . . . 67
. . . . . . . . . 192
. . . . . . . . . . 67
. . . . . . . . . 175
P
Packing list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Pairing open . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Parameter list . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Part names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Passive open . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Performance specifications . . . . . . . . . . . . . . . . . . 27
Physical addresses . . . . . . . . . . . . . . . . . . . . . . 167
PING command . . . . . . . . . . . . . . . . . . . . . . . . . 327
PING test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
POP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Port numbers used for the E71 . . . . . . . . . . . . . . 309
Predefined protocol support function . . . . . . . . . . . 17
Procedure exist . . . . . . . . . . . . . . . . . . . . . . . . . 120
Procedures before operation . . . . . . . . . . . . . . . . . 55
Processing time . . . . . . . . . . . . . . . . . . . . . . . . . 304
Programming tool . . . . . . . . . . . . . . . . . . . . . . . . 17
L
Line status check . . . . . . . . . . .
List of buffer memory addresses
List of dedicated instructions . . .
List of I/O signals . . . . . . . . . . .
Lock process . . . . . . . . . . . . . .
Logical addresses . . . . . . . . . .
Loopback test . . . . . . . . . . . . .
. . . . . . . . . . . . . 322
. . . . . . . . . . . . . . 35
. . . . . . . . . . . . . 196
. . . . . . . . . . . . . . 32
. . . . . . . . . . . . . 182
. . . . . . . . . . . . . 167
. . . . . . . . . . . . . 328
MAC address. . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Maximum segment length . . . . . . . . . . . . . . . . . . . 27
Maximum station-to-station distance (maximum cable
length) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
MC protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
MC protocol communications . . . . . . . . . . . . . . . . 85
MELSECNET/10 . . . . . . . . . . . . . . . . . . . . . . . . . 16
MELSECNET/H . . . . . . . . . . . . . . . . . . . . . . . . . . 16
MELSECNET/H remote I/O station . . . . . . . . . . . . 16
MELSOFT application transmission port (TCP) . . . 309
MELSOFT application transmission port (UDP) . . . 309
MELSOFT connection . . . . . . . . . . . . . . . . . . . . . 83
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Module joint lever . . . . . . . . . . . . . . . . . . . . . . . . . 25
MRECV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
MSEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
MX component . . . . . . . . . . . . . . . . . . . . . . . . . . 16
N
Network components . . . . . . . . .
Network No. . . . . . . . . . . . . . . .
Network parameter. . . . . . . . . . .
Network type . . . . . . . . . . . . . . .
No procedure. . . . . . . . . . . . . . .
Number of connectable modules .
Number of occupied I/O points . .
. . . . . . . . . . . . . 58
. . . . . . . . . . . . . 66
. . . . . . . . . . . . . 65
. . . . . . . . . . . . . 66
. . . . . . . . . . . . 120
. . . . . . . . . . . . . 60
. . . . . . . . . . . . . 27
O
374
QnA-compatible 3E frame. . . . . . . . . . . . . . . . . . . 86
R
M
Offline . . . . .
Online . . . . .
OPEN . . . . .
Open setting
Q
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
. . . . . . . . . . . . . . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RECV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RECVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reinitialization process . . . . . . . . . . . . . . . . . . .
Relevant manuals . . . . . . . . . . . . . . . . . . . . . .
Remote password . . . . . . . . . . . . . . . . . . . . . .
Remote password check . . . . . . . . . . . . . . . . .
Remote password setting processes (unlock and
lock processes) . . . . . . . . . . . . . . . . . . . . . . . .
REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RJ45 connector . . . . . . . . . . . . . . . . . . . . . . . .
Router information . . . . . . . . . . . . . . . . . . . . . .
Router IP address . . . . . . . . . . . . . . . . . . . . . .
Router relay function . . . . . . . . . . . . . . . . . . . .
. 196
. 196
. 196
. 315
... 7
. 181
. 183
. 182
. 196
. . 58
. 171
. 173
. 169
S
Sample program on the connected device side . . . 350
Self-diagnostic tests . . . . . . . . . . . . . . . . . . . . . . 332
Self-loopback test . . . . . . . . . . . . . . . . . . . . . 66,332
SEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Send frame setting. . . . . . . . . . . . . . . . . . . . . . . . 67
Setting parameters required for communications . . . 65
Shielded twisted pair cable (STP) . . . . . . . . . . . . . 58
SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Special functions . . . . . . . . . . . . . . . . . . . . . . . . . 30
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SREAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Start I/O No. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Station No. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Straight cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Subnet address . . . . . . . . . . . . . . . . . . . . . . . . . 171
Subnet mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Subnet mask pattern . . . . . . . . . . . . . . . . . . . . . 170
SWRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
System configuration . . . . . . . . . . . . . . . . . . . . . . . 57
T
TCP existence confirmation setting . .
TCP/IP communications . . . . . . . . .
Terms . . . . . . . . . . . . . . . . . . . . . .
Transmission method . . . . . . . . . . .
Transmission specifications . . . . . . .
Troubleshooting . . . . . . . . . . . . . . .
Troubleshooting by symptom . . . . . .
. . . . . . . . . . . 67
. . . . . . . . . . . 72
. . . . . . . . . . . 16
. . . . . . . . . . . 27
. . . . . . . . . . . 27
. . . . . . . . . . 239
. . . . . . . . . . 245
UDP/IP communications . . . . . . . . .
UINI. . . . . . . . . . . . . . . . . . . . . . . .
Unlock process . . . . . . . . . . . . . . . .
Unpassive . . . . . . . . . . . . . . . . . . .
Unshielded twisted pair cable (UTP) .
Use with other functions. . . . . . . . . .
. . . . . . . . . . . 79
. . . . . . . . . . 196
. . . . . . . . . . 182
. . . . . . . . . . . 77
. . . . . . . . . . . 59
. . . . . . . . . . . 31
I
4
U
4
W
Web function . . . . . . . . . . . . . .
When using data link instructions
Wiring . . . . . . . . . . . . . . . . . . .
WRITE . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . 30
. . . . . . . . . . . . . 197
. . . . . . . . . . . . . . 62
. . . . . . . . . . . . . 196
7
8
Z
Z.BUFRCVS . .
ZNRD . . . . . .
ZNWR . . . . . .
ZP.BUFRCV . .
ZP.BUFSND . .
ZP.CLOSE . . .
ZP.ERRCLR . .
ZP.ERRRD. . .
ZP.OPEN . . . .
ZP.UINI . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . 224
. . . . . . . . . . . . . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . . . . . . . . . . . . 196
. . . . . . . . . . . . . . . . . . . . . . . . . . 220
. . . . . . . . . . . . . . . . . . . . . . . . . . 216
. . . . . . . . . . . . . . . . . . . . . . . . . . 203
. . . . . . . . . . . . . . . . . . . . . . . . . . 226
. . . . . . . . . . . . . . . . . . . . . . . . . . 230
. . . . . . . . . . . . . . . . . . . . . . . . . . 199
. . . . . . . . . . . . . . . . . . . . . . . . . . 233
375
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print date
*Manual number
February 2013
SH(NA)-081105ENG-A
Revision
First edition
June 2013
SH(NA)-081105ENG-B
Revision due to the support for data communications using the predefined
October 2014
SH(NA)-081105ENG-C
Error correction
April 2015
SH(NA)-081105ENG-D
Revision due to the support for Receive buffer full detection signal
July 2016
SH(NA)-081105ENG-E
Revision due to the support for the IP filter function
Japanese Manual Version SH-081104-F
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.
 2013 MITSUBISHI ELECTRIC CORPORATION
376
WARRANTY
Please confirm the following product warranty details before using this product.
1. Gratis Warranty Term and Gratis Warranty Range
If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the product
within the gratis warranty term, the product shall be repaired at no cost via the sales representative or Mitsubishi Service
Company.
However, if repairs are required onsite at domestic or overseas location, expenses to send an engineer will be solely at
the customer's discretion. Mitsubishi shall not be held responsible for any re-commissioning, maintenance, or testing
on-site that involves replacement of the failed module.
[Gratis Warranty Term]
The gratis warranty term of the product shall be for one year after the date of purchase or delivery to a designated place.
Note that after manufacture and shipment from Mitsubishi, the maximum distribution period shall be six (6) months, and
the longest gratis warranty term after manufacturing shall be eighteen (18) months. The gratis warranty term of repair
parts shall not exceed the gratis warranty term before repairs.
[Gratis Warranty Range]
(1) The range shall be limited to normal use within the usage state, usage methods and usage environment, etc., which
follow the conditions and precautions, etc., given in the instruction manual, user's manual and caution labels on the
product.
(2) Even within the gratis warranty term, repairs shall be charged for in the following cases.
1. Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused
by the user's hardware or software design.
2. Failure caused by unapproved modifications, etc., to the product by the user.
3. When the Mitsubishi product is assembled into a user's device, Failure that could have been avoided if functions
or structures, judged as necessary in the legal safety measures the user's device is subject to or as necessary by
industry standards, had been provided.
4. Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the
instruction manual had been correctly serviced or replaced.
5. Failure caused by external irresistible forces such as fires or abnormal voltages, and Failure caused by force
majeure such as earthquakes, lightning, wind and water damage.
6. Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi.
7. Any other failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.
2. Onerous repair term after discontinuation of production
(1) Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.
Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.
(2) Product supply (including repair parts) is not available after production is discontinued.
3. Overseas service
Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA
Center may differ.
4. Exclusion of loss in opportunity and secondary loss from warranty liability
Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation to:
(1) Damages caused by any cause found not to be the responsibility of Mitsubishi.
(2) Loss in opportunity, lost profits incurred to the user by Failures of Mitsubishi products.
(3) Special damages and secondary damages whether foreseeable or not, compensation for accidents, and
compensation for damages to products other than Mitsubishi products.
(4) Replacement by the user, maintenance of on-site equipment, start-up test run and other tasks.
5. Changes in product specifications
The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.
377
TRADEMARKS
Microsoft, Microsoft Access, Excel, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, Windows NT,
Windows Server, Windows Vista, and Windows XP are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Ethernet is a registered trademark of Fuji Xerox Corporation in Japan.
The company names, system names and product names mentioned in this manual are either registered trademarks or
trademarks of their respective companies.
In some cases, trademark symbols such as '' or '' are not specified in this manual.
378
SH(NA)-081105ENG-E
SH(NA)-081105ENG-E(1607)MEE
MODEL:
LJ71E71-U-KI-E
MODEL CODE: 13JZ73
HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN
NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN
When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.
Specifications subject to change without notice.