Q Corresponding Ethernet Interface Module User's Manual (Basic)

Q Corresponding Ethernet Interface Module
User's Manual (Basic)
-QJ71E71-100
-QJ71E71-B5
-QJ71E71-B2
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention
to safety to handle the product correctly.
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".
Indicates that incorrect handling may cause hazardous conditions,

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

CAUTION resulting in minor or moderate injury or property damage.
Under some circumstances, failure to observe the precautions given under " CAUTION" may lead to
serious consequences.
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 manuals relevant to the
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.
● 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 in the system area of the buffer memory in the intelligent function module. Also,
do not use any use prohibited signals as an output signal from the programmable controller CPU to
the intelligent function module. Doing so may cause malfunction of the programmable controller
system.
[Design Precautions]
CAUTION
● Do not bundle the control wires and the communication cables with the main circuit and the power
wires, and do not install them close to each other. They should be installed at least 100 mm away from
each other. Failure to do so may generate noise that may cause malfunctions.
● 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.
[Security Precautions]
WARNING
● To maintain the security (confidentiality, integrity, and availability) of the programmable controller and
the system against unauthorized access, denial-of-service (DoS) attacks, computer viruses, and other
cyberattacks from external devices via the network, take appropriate measures such as firewalls,
virtual private networks (VPNs), and antivirus solutions.
2
[Installation Precautions]
CAUTION
● Use the programmable controller in an environment that meets the general specifications in the user's
manual for the CPU module used. Using the programmable controller in any other operating
environments may cause electric shocks, fires or malfunctions, or may damage or degrade the
module.
● While pressing the installation lever located at the bottom of module, insert the module fixing tab into
the fixing hole in the base unit until it stops. Then, securely mount the module with the fixing hole as a
supporting point. If the module is not installed properly, it may cause the module to malfunction, fail or
fall off. Secure the module with screws especially when it is used in an environment where constant
vibrations may occur.
● Be sure to tighten the screws using the specified torque. If the screws loose, it may cause the module
to short-circuit, malfunction or fall off. If the screws are tightened excessively, it may damage the
screws and cause the module to short-circuit, malfunction or fall off.
● Shut off the external power supply (all phases) used in the system before mounting or removing the
module. Failure to do so may cause product damage.
● Do not directly touch any conductive part or electronic component of the module. This may cause the
module to malfunction or fail.
[Wiring Instructions]
CAUTION
● Connectors for external devices and coaxial cables must be crimped or pressed with the tool specified
by the manufacturer, or must be correctly soldered. Incomplete connections may cause short circuit,
fire, or malfunction.
● Shut off the external power supply (all phases) used in the system before connecting the AUI cable.
● 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.
● Tighten the terminal screws using the specified torque. If the terminal screws are loose, it may cause
the module to short-circuit, malfunction or fall off. If the terminal screws are tightened excessively, it
may damage the screws and cause the module to short-circuit, malfunction or fall off.
● When disconnecting the cable from the module, do not pull the cable by the cable part. For the cable
with connector, hold the connector part of the cable. For the cable connected to the terminal block,
loosen the terminal screw. Pulling the cable connected to the module may result in malfunction or
damage to the module or cable.
● Be careful not to let any foreign matter such as wire chips get inside the module. They may cause fire,
as well as breakdowns and malfunctions of the module.
● 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. 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. Remove it for heat
dissipation before system operation.
3
[Setup and Maintenance Precautions]
WARNING
● Do not touch any terminal while power is on. Doing so will cause electric shock or malfunction.
● Shut off the external power supply (all phases) used in the system before cleaning the module or
retightening the terminal screws, connector screws, or module fixing screws. Failure to do so may
result in electric shock or cause the module to fail or malfunction.
[Setup and Maintenance Precautions]

CAUTION
● Do not disassemble or modify the modules. 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.
● After the first use of the product, do not mount/remove the module to/from the base unit more than 50
times (IEC 61131-2 compliant). Exceeding the limit of 50 times may cause malfunction.
● Always make sure to touch the grounded metal to discharge the electricity charged in the body, etc.,
before touching the module. Failure to do so may cause a failure or malfunctions of the module.
[Precautions When Disposing of This Product]

CAUTION
● Dispose of this product as an industrial waste.
4
CONDITIONS OF USE FOR THE PRODUCT
(1) MELSEC 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 ELECTRIC 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 ELECTRIC USER'S, 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 Electric 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 Electric 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 Electric representative in your region.
(3) Mitsubishi Electric shall have no responsibility or liability for any problems involving programmable controller trouble and
system trouble caused by DoS attacks, unauthorized access, computer viruses, and other cyberattacks.
5
INTRODUCTION
Thank you for purchasing the Mitsubishi Electric MELSEC-Q series programmable controllers. This manual describes
the operating procedure, system configuration, parameter settings, functions, programming, and troubleshooting of the
Ethernet interface modules: QJ71E71-100, QJ71E71-B5, and QJ71E71-B2 (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-Q series programmable controller to handle the product correctly.
When applying the program examples introduced in this manual to the actual system, ensure the applicability and
confirm that it will not cause system control problems.
Please make sure that the end users read this manual.
COMPLIANCE WITH THE EMC AND LOW VOLTAGE

DIRECTIVES
(1) For programmable controller system

To ensure that Mitsubishi Electric programmable controllers maintain the EMC and Low Voltage Directives or
other regulations when incorporated into other machinery or equipment, certain measures may be necessary.
Please refer to one of the following manuals.
• QCPU User's Manual (Hardware Design, Maintenance and Inspection) (SH-080483ENG)
• Safety Guidelines (IB-0800423)
Certification marks on the side of the programmable controller indicate compliance with the relevant regulations.
(2) For the product

To ensure that this product maintains the EMC and Low Voltage Directives or other regulations, please refer to
one of the manuals listed under (1).
6
RELEVANT MANUALS
This manual describes the basic specifications, functions, and usage of the E71.
(1) E71 relevant manual
Manual name
Description
<manual number, model code>
MELSEC-Q/L Ethernet Interface Module User's E-mail function, communication function (communications via CC-Link IE
Manual (Application) Controller Network, CC-Link IE Field Network, MELSECNET/H, or
MELSECNET/10, and communications by using the data link instructions), and file
<SH-080010, 13JL89> transfer (FTP server) function of the E71
MELSEC-Q/L Ethernet Interface Module User's
Manual (Web function) Web function of the E71
<SH-080180, 13JR40>
MELSEC Communication Protocol Reference Manual Details of MELSEC communication protocol (MC protocol) that is used for data
<SH-080008, 13JF89> communication between a target device and a CPU module
(2) Operating manual
Manual name
Description
<manual number, model code>
GX Works2 Version1 Operating Manual (Common) System configuration, parameter settings, and online operations (common to
<SH-080779, 13JU63> Simple project and Structured project) of GX Works2
GX Works2 Version 1 Operating Manual (Intelligent
Parameter settings for intelligent function modules, monitoring operations, and the
Function Module)
predefined protocol support function of GX Works2
<SH-080921, 13JU69>
GX Developer Version 8 Operating Manual Operating methods of GX Developer, such as programming, printing, monitoring,
<SH-080373, 13JU41> and debugging
7
CONTENTS
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
MANUAL PAGE ORGANIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
TERM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
PACKING LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
CHAPTER 1 FEATURES 20
CHAPTER 2 PART NAMES 26
CHAPTER 3 SPECIFICATIONS 28
3.1 General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.2 Performance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3 Function List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.1 Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.2 Use with other functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.4 List of I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.5 Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5.1 Configuration of the buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5.2 List of buffer memory addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
CHAPTER 4 PROCEDURES BEFORE OPERATION 63
CHAPTER 5 SYSTEM CONFIGURATION 65

5.1 Configuration of an E71-mounted System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.1.1 Applicable modules and base units, and the number of connectable modules . . . . . . . . . . . 65
5.1.2 For use with a Basic model QCPU or safety CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
5.1.3 For use in a multiple CPU system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.1.4 For use in a redundant system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
5.1.5 For use in a MELSECNET/H remote I/O station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.2 Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

5.2.1 Configuration devices used for 100BASE-TX/10BASE-T connection . . . . . . . . . . . . . . . . . . 74
5.2.2 Configuration devices used for 10BASE5 connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.2.3 Configuration devices used for 10BASE2 connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
CHAPTER 6 INSTALLATION AND WIRING 78

6.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
6.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.2.1 Wiring with the QJ71E71-100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
6.2.2 Wiring with the QJ71E71-B5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
6.2.3 Wiring with the QJ71E71-B2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
8
CHAPTER 7 COMMUNICATION PROCEDURE 84
7.1 Setting Parameters Required for Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.1 Parameter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.1.2 Basic setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.1.3 Ethernet Operation Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.1.4 Open Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.2 TCP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.2.1 Establishing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2.2 Communication process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.2.3 Active open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.2.4 Passive open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.3 UDP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

7.3.1 Communication process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.3.2 Open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
CHAPTER 8 CONNECTING MELSOFT PRODUCTS AND A GOT 102

8.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
8.2 Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
CHAPTER 9 MC PROTOCOL COMMUNICATIONS 105

9.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
9.2 Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.4 Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
CHAPTER 10 SLMP COMMUNICATIONS 109

10.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10.5 Available command list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL 114

11.2 Communication Type of Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
11.3 Packet Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
11.4 Execution Condition of Predefined Protocol Communication . . . . . . . . . . . . . . . . . . . . . . . . . 127
11.5 Example of Predefined Protocol Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.5.1 System configuration example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.5.2 Parameter Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
11.5.3 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
9
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER 141
12.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
12.1.1 Differences between the "Procedure Exist" and "No Procedure" control methods . . . . . . . 141

12.3 Data Sending Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
12.4 Data Receiving Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
12.4.1 Data receiving using the main program (BUFRCV instruction) . . . . . . . . . . . . . . . . . . . . . . 146
12.4.2 Data receiving using an interrupt program (BUFRCVS instruction) . . . . . . . . . . . . . . . . . . . 149

12.5.1 Parameter setting when using an interrupt program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
12.6 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

12.6.1 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
12.6.2 Application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
12.7 Pairing Open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

12.7.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
12.7.2 Parameter setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
12.8 Broadcast Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

12.8.1 Sending/receiving procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
12.8.3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
12.9 Example of Communications Using a Fixed Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

12.9.1 System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
12.9.3 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER 176

13.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
13.2.1 How data is read from a connected device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
13.2.2 How a connected device writes data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

13.4 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
13.4.1 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
13.4.2 Application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
13.4.3 Examples of command and response formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
13.5 Precautions when Creating Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

13.6 Physical and Logical Addresses of a Random Access Buffer. . . . . . . . . . . . . . . . . . . . . . . . . 189
13.7 Example of Communications Using a Random Access Buffer . . . . . . . . . . . . . . . . . . . . . . . . 190
CHAPTER 14 OTHER FUNCTIONS 191

14.1 Router Relay Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
14.1.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
14.1.2 Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
10
14.2 Communications Using an Auto-open UDP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
14.2.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
14.3 IP Filter Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

14.3.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
14.3.2 Setting method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
14.3.3 Program example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
14.3.4 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
14.4 Remote Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

14.4.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
14.4.2 Remote password setting processes (unlock and lock processes) . . . . . . . . . . . . . . . . . . . 204
14.4.3 Remote password check procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
14.4.4 Comparison of functions according to the remote password check status (enabled/disabled)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
14.4.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
14.5 Hub Connection Status Monitor Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

14.6 IP Address in Use Detection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
14.7 Redundant System Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
14.7.1 System switching request to the control system CPU module. . . . . . . . . . . . . . . . . . . . . . . 216
14.7.2 Communication path bypass function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
14.7.4 Data communications in a redundant system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
14.8 Alive Check Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
CHAPTER 15 DEDICATED INSTRUCTIONS 238

15.1 List of Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
15.2 Parameter Settings for Using Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
15.2.1 When using data link instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
15.3 Precautions for Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

15.4 Organization of the Dedicated Instruction Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
15.5 ZP.OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
15.6 ZP.CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
15.7 GP.ECPRTCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
15.8 ZP.BUFSND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
15.9 ZP.BUFRCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
15.10 Z.BUFRCVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
15.11 ZP.ERRCLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
15.12 ZP.ERRRD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
15.13 ZP.UINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CHAPTER 16 TROUBLESHOOTING 285

16.1 Before Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
16.2 Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
16.3 Checking with the Module Error Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
11
16.4 Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
16.4.1 If the RUN LED turns off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
16.4.2 If the ERR. LED or COM.ERR. LED turns on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
16.4.3 If the SD LED does not flash when data is sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
16.4.4 If data cannot be received with the RD LED off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
16.5 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

16.5.1 Communications cannot be performed with the connected device.. . . . . . . . . . . . . . . . . . . 290
16.5.2 The E71 frequently fails to receive a message sent from the connected device. . . . . . . . . 291
16.5.3 A dedicated instruction is not completed.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
16.5.4 MC protocol communications cannot be performed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
16.5.5 Communications using SLMP cannot be performed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
16.5.6 Communications using the predefined protocol cannot be performed. . . . . . . . . . . . . . . . . 293
16.5.7 The protocol setting data cannot be read or written. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
16.5.8 Data cannot be sent with communications using a fixed buffer. . . . . . . . . . . . . . . . . . . . . . 295
16.5.9 Data cannot be received with communications using a fixed buffer. . . . . . . . . . . . . . . . . . . 296
16.5.10 Communications using a random access buffer cannot be performed. . . . . . . . . . . . . . . . . 297
16.5.11 The access cannot be allowed/denied correctly by the IP filter.. . . . . . . . . . . . . . . . . . . . . . 297
16.5.12 An e-mail cannot be sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
16.5.13 An e-mail cannot be received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
16.5.14 Communications using data link instructions cannot be performed. . . . . . . . . . . . . . . . . . . 300
16.5.15 Communications cannot be performed during OPS connection in a redundant system. . . . 300
16.5.16 Systems cannot be switched in a redundant system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
16.6 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

16.6.1 End codes returned to a connected device during data communications . . . . . . . . . . . . . . 312
16.6.2 Abnormal codes returned during communications using an A-compatible 1E frame. . . . . . 315
16.6.3 Error codes stored in the buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
16.7 Ethernet Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

16.8 How to Turn Off the COM.ERR. LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
APPENDICES 343
Appendix 1 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Appendix 2 Port Numbers Used for the E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Appendix 3 New and Improved Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Appendix 4 Initial Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Appendix 4.1 Setting the initial process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Appendix 4.2 Reinitialization process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Appendix 5 Line Status Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Appendix 5.1 PING test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Appendix 5.2 Loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Appendix 6 Self-Diagnostic Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Appendix 6.1 Self-loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Appendix 6.2 Hardware test (H/W Test). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Appendix 7 Differences from Ethernet Modules of Other Series . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Appendix 7.1 Comparison with a Built-in Ethernet port QCPU . . . . . . . . . . . . . . . . . . . . . . . 378
Appendix 7.2 Comparison with QnA/A Series Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
12
Appendix 8 Operation Image and Data Structure of Predefined Protocol . . . . . . . . . . . . . . . . . . . . 382
Appendix 8.1 Operation image of each communication type of protocol. . . . . . . . . . . . . . . . . 382
Appendix 8.2 Verification operation of receive packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Appendix 8.3 Data examples of packet elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Appendix 9 Usage example of MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

Appendix 9.1 How to create a program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Appendix 9.2 Sample Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Appendix 10 Sample Program on the Connected Device Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Appendix 10.1 When Visual C++®.NET is used (single CPU system) . . . . . . . . . . . . . . . . . . . 401
Appendix 10.2 When Visual C++®.NET is used (redundant system) . . . . . . . . . . . . . . . . . . . . 410
Appendix 10.3 When Visual Basic®.NET is used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Appendix 11 Checking the Serial Number and Function Version . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Appendix 11.1 Compatible software versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Appendix 12 External Dimension Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

Appendix 13 ASCII Code List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
INDEX 436
REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
13
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 shows notes that

reference pages. requires attention.
shows useful
information.
*1 The mouse operation example 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. Project window [Parameter]

[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
14
TERM
Unless otherwise specified, this manual uses the following terms.
Term Description
ACPU A generic term for the AnNCPU, AnACPU, and AnUCPU
A generic term for the A2ACPU, A2ACPU-S1, A2ACPUP21/R21, A2ACPUP21/R21-S1, A3ACPU,
AnACPU
and A3ACPUP21/R21
A generic term for the A1NCPU, A1NCPUP21/R21, A2NCPU, A2NCPU-S1, A2NCPUP21/R21,
AnNCPU
A2NCPUP21/R21-S1, A3NCPU, and A3NCPUP21/R21
AnUCPU A generic term for the A2UCPU, A2UCPU-S1, A2ASCPU, A2ASCPU-S1, A3UCPU, and A4UCPU
An abbreviation for Address Resolution Protocol. This protocol is used to obtain the MAC address
ARP
of Ethernet from an IP address.
BUFRCV An abbreviation for ZP.BUFRCV
BUFRCVS An abbreviation for Z.BUFRCVS
BUFSND An abbreviation for ZP.BUFSND
CLOSE An abbreviation for ZP.CLOSE
C24 Another name for the Q series serial communication module
An abbreviation for Domain Name System. This system is mainly used to convert host names on
DNS
the Internet or domain names used for e-mails to IP addresses.
ECPRTCL An abbreviation for GP.ECPRTCL
ERRCLR An abbreviation for ZP.ERRCLR
ERRRD An abbreviation for ZP.ERRRD
A generic term for the Q03UDVCPU, Q03UDECPU, Q04UDVCPU, Q04UDPVCPU,
Q04UDEHCPU, Q06UDVCPU, Q06UDPVCPU, Q06UDEHCPU, Q10UDEHCPU, Q13UDVCPU,
Built-in Ethernet port QCPU
Q13UDPVCPU, Q13UDEHCPU, Q20UDEHCPU, Q26UDVCPU, Q26UDPVCPU, Q26UDEHCPU,
Q50UDEHCPU, and Q100UDEHCPU
E71 A generic term for the Ethernet interface modules: QJ71E71-100, QJ71E71-B5, and QJ71E71-B2
E71-mounted station An abbreviation for the station where the E71 is mounted
An abbreviation for File Transfer Protocol. This protocol is used to transfer data files over a
FTP
network.
GX Developer
The product name of the software package for the MELSEC programmable controllers
GX Works2
An abbreviation for Hyper Text Transfer Protocol. This protocol is used to send and receive
HTTP
content, such as HTML files, between a Web browser and a Web server.
An abbreviation for Internet Control Message Protocol. This protocol is used to exchange
ICMP
messages of errors in an IP network or other information related to an Ethernet network.
IP An abbreviation for Internet Protocol
A unique identifier assigned to each external device on a network. This address is also known as
MAC address
an Ethernet hardware address.
An 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/H An abbreviation for a MELSECNET/H network system
MELSECNET/H remote I/O station A generic term for the QJ72LP25-25, QJ72LP25G, and QJ72BR15
MELSECNET/10 An abbreviation for a MELSECNET/10 network system
MRECV An abbreviation for ZP.MRECV
MSEND An abbreviation for ZP.MSEND
MX Component An abbreviation for MX Component (SW0D5C-ACT-E or later)
OPEN An abbreviation for ZP.OPEN
15
Term Description
A generic term for the partner products with built-in EZSocket that supports a redundant system.
OPS
The E71 communicates with an OPS using a connection specified by a user.
An abbreviation for Post Office Protocol Ver.3. This protocol is used to transfer e-mails from a mail
POP3
server to a local computer.
A generic term for the Basic model QCPU, High Performance model QCPU, Process CPU,
QCPU
Redundant CPU, and Universal model QCPU
QCPU-mounted station An abbreviation for the programmable controller where the QCPU is mounted
A generic term for the Q2ACPU, Q2ACPU-S1, Q2ASCPU, Q2ASCPU-S1, Q2ASHCPU,
QnACPU
Q2ASHCPU-S1, Q3ACPU, Q4ACPU, and Q4ARCPU
READ An abbreviation for JP.READ and GP.READ
RECV An abbreviation for JP.RECV and GP.RECV
RECVS An abbreviation for Z.RECVS
REQ An abbreviation for J.REQ, JP.REQ, G.REQ, and GP.REQ
SEND An abbreviation for JP.SEND and GP.SEND
An 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.
An abbreviation for Simple Mail Transfer Protocol. This protocol is used to transfer e-mails over the
SMTP
Internet.
SREAD An abbreviation for JP.SREAD and GP.SREAD
SWRITE An abbreviation for JP.SWRITE and GP.SWRITE
UINI An abbreviation for ZP.UINI
WRITE An abbreviation for JP.WRITE and GP.WRITE
ZNRD An abbreviation for J.ZNRD and JP.ZNRD
ZNWR An abbreviation for J.ZNWR and JP.ZNWR
A module that has functions other than an input or output, such as an A/D converter module and
Intelligent function module
D/A converter module
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
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.
Device A device (X, Y, M, D, or others) in a CPU module
High Performance model QCPU A generic term for the Q02(H)CPU, Q06HCPU, Q12HCPU, and Q25HCPU
A memory in an intelligent function module, where data (such as setting values and monitoring
Buffer memory
values) exchanged with a CPU module are stored
An address that indicates the storage location of data assigned to the buffer memory in an
Buffer memory address
intelligent function module
Programming tool A generic term for GX Works2 and GX Developer
Process CPU A generic term for the Q02PHCPU, Q06PHCPU, Q12PHCPU, and Q25PHCPU
Basic model QCPU A generic term for the Q00(J)CPU and Q01CPU
A generic term for the Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU,
Q03UDVCPU, Q03UDECPU, Q04UDHCPU, Q04UDVCPU, Q04UDEHCPU, Q06UDHCPU,
Universal model QCPU Q06UDVCPU, Q06UDEHCPU, Q10UDHCPU, Q10UDEHCPU, Q13UDHCPU, Q13UDVCPU,
Q13UDEHCPU, Q20UDHCPU, Q20UDEHCPU, Q26UDHCPU, Q26UDVCPU, Q26UDEHCPU,
Q50UDEHCPU, and Q100UDEHCPU
Redundant CPU A generic term for the Q12PRHCPU and Q25PRHCPUU
Safety CPU Another name for the QS001CPU
16
Term Description
Dedicated Instruction An instruction that simplifies programming for using functions of intelligent function modules
17
PACKING LIST
The following items are included in the package of this product. Before use, check that all the items are included.
QJ71E71-100
QJ71E71-100 Before Using the Product
QJ71E71-B5
QJ71E71-B5 Before Using the Product
18
QJ71E71-B2
QJ71E71-B2 Before Using the Product
19
CHAPTER 1 FEATURES
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
Provider Provider
Own station 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
20
CHAPTER 1 FEATURES
(1) Connection with MELSOFT products and a GOT 1

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) 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 105, 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.
( Page 109, CHAPTER 10)
21
(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 114, CHAPTER 11)
1) Setting protocols 2) Writing protocols

Protocols can be set easily using the Write the set protocols in the flash ROM of
predefined protocol support function of GX the E71.
Works2.
GX Works2
Sending
Connected device E71 Connected device

Receiving
3) Executing protocols
Data can be communicated
Execute protocols by dedicated instructions. with protocols appropriate to
Multiple protocols can be executed by one dedicated each connected device.
instruction.
22
CHAPTER 1 FEATURES
(5) Exchange of data with connected devices (communications using a fixed 1

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 141, CHAPTER 12)
Sending/receiving Sending/receiving
Another station 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). ( Page 176, CHAPTER 13)
Reading/writing Reading/writing
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 197, 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.
( Page 203, Section 14.4)
23
(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-mails
Mail server Mail server
E71
Connected device
24
CHAPTER 1 FEATURES
(9) Data sending/receiving using the Web function 1

The system administrator can monitor a CPU module in a remote location via the Internet using a commercially
available Web browser. For details, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)
HTTP MC protocol
header (command message)
HTTP
MC protocol HTTP
(response message) header
E71
Web server Connected device
Web browser
HTML
Display of
requests/
ASP results
Communication
library
25
CHAPTER 2 PART NAMES
This chapter describes the E71 parts.
1) 1) 1)
3)
4)
2)
5)
6) 6) 6)
No. Name Application

1) LED indicator Refer to (1) in this chapter.
10BASE-T/100BASE-TX connector A connector to connect the E71 to the 10BASE-T or 100BASE-TX network (The E71
2)
(RJ45)*1 determines whether to use 10BASE-T or 100BASE-TX according to the hub.)
A connector to connect the E71 to the 10BASE5 network (for connecting a 10BASE5 AUI
3) 10BASE5 connector
cable (transceiver cable))
A connector to connect the E71 to the 10BASE2 network (for connecting a 10BASE2
4) 10BASE2 connector
coaxial cable)
A power supply terminal for supplying power to a transceiver in the 10BASE5 network
5) External power supply terminal
(13.28VDC to 15.75VDC)
6) Serial number display A display indicating the serial number printed on the rating plate
*1 The LED on the connector does not turn on. Depending on the serial number, the connector orientation is left-right
reversal.
26
CHAPTER 2 PART NAMES
(1) LED indication
QJ71E71-100 QJ71E71-B5 QJ71E71-B2 2

RUN ERR. RUN ERR. RUN ERR.
INIT. COM.ERR. INIT. COM.ERR. INIT. COM.ERR.
OPEN 100M OPEN OPEN
SD RD SD RD SD RD
LED name Description

RUN Indicates operating status.
ON In normal operation
OFF An error has occurred. ( Page 288, Section 16.4.1)

INIT. Indicates initial process status.
ON Normal completion
OFF Not processed
OPEN*1 Indicates open process status.

ON An open process normally completed (connection open)
OFF An open process not completed (no connection)
SD Indicates whether data is being sent.
Flashing Data being sent
OFF Data not sent ( Page 289, Section 16.4.3)
ERR. Indicates whether the setting is correct.
ON The setting is incorrect. ( Page 288, Section 16.4.2)
OFF Correct setting
*2 Indicates whether a communication failure has occurred.
COM.ERR.
ON A communication failure has occurred. ( Page 288, Section 16.4.2)
OFF Normal communications in progress
100M Indicates a transmission speed.
ON 100Mbps
OFF 10Mbps or a cable not connected
RD Indicates whether data is being received.
ON Data being received
OFF Data not received ( Page 289, Section 16.4.4)
*1 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.)
*2 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". ( Page 342, Section 16.8)
27
CHAPTER 3 SPECIFICATIONS
This chapter describes the performance specifications, functions, CPU module I/O signals, and buffer memory areas
of an E71.
3.1 General Specifications
For the general specifications of an E71, refer to the following.

"Safety Guidelines", the manual included with the CPU module or base unit
28
3.2 Performance Specifications
The following table lists the performance specifications of an E71.
Specifications
Item QJ71E71-100 QJ71E71-B5 QJ71E71-B2
100BASE-TX 10BASE-T*9 10BASE5 10BASE2 3
100Mbps
Data transmission speed (Full-duplex/Half- 10Mbps (Half-duplex)
duplex)
Full-duplex: None*8
Half-duplex: Back
Flow control Back pressure congestion control (Half-duplex)
pressure
congestion control
Interface RJ45 (Fixed to MDI) AUI BNC
Transmission method Base band
Transmission
Maximum node-to-node
specifications - 2500m 925m
distance
100m
Maximum segment length*6 500m 185m
(length between a hub and node)*7
Cascade Cascade
Maximum number of connection connection 100 modules/ 30 modules/
nodes/connection *6 (maximum of 2 (maximum of 4 segment segment
1 1
levels* ) levels* )
Minimum interval between
- 2.5m 0.5m
nodes*6
3.2 Performance Specifications

Number of simultaneous
16 connections (Connections usable on a program)
open connections
Sending/receiving Fixed buffer 1K word × 16
data storage
Random access buffer 6K words × 1
memory
Attachment 6K words × 1
E-mail
Main text 960 words × 1
Number of occupied I/O points 32 points per slot (I/O assignment: Intelligent 32 points)
Internal current consumption (5VDC) 0.50A 0.50A 0.60A*2
12VDC external power supply capacity
- *3 -
(Transceiver)
External dimensions 98 (H) × 27.4 (W) × 90 (D) [mm]
Weight 0.11kg 0.12kg 0.13kg*2
29
Specifications
Item QJ71E71-100 QJ71E71-B5 QJ71E71-B2
100BASE-TX *9 10BASE5 10BASE2
10BASE-T
Attachment 6K words × 1
Data size
Main text 960 words × 1
When sending: Send either a file as attachment or main text (select one).
Data transfer method
When receiving: Receive a file as attachment.
Subject Us-ASCII format or ISO-2022-JP (Base64)
Attachment format MIME format
MIME Version 1.0
Can be selected from binary, ASCII, and CSV.
Data of attachment format File name: XXXX.bin (binary), XXXX.asc (ASCII), XXXX.csv (CSV)
(CSV: Comma Separated Value)
Transmission
Division of attachment Cannot be divided (Only one file can be sent/received.)*4
specifications
Subject: Base64/7 bits
sending/receiving
When sending (encode) Main text: 7 bits
data
Attachment: Base64
Subject: (Does not decode)
When receiving (decode) Main text: (Cannot be received)
Attached file: Base64/7 bits/8 bits/Quoted Printable*5
Encryption None
Compression None
Communications with a mail SMTP (sending server) Port number = 25,
server POP3 (receiving server) Port number = 110
®
Microsoft Corporation Internet Explorer 5.0 (Outlook Express 5.5/Outlook Express 5)
Operation check mailer
Netscape® Communications Corporation Netscape® 4.05
*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.
*2 As described below, a module with a serial number (first five digits) of "05049" or earlier has a different 5VDC internal
current consumption value and weight.
• Internal current consumption (5VDC): 0.70A
• Weight: 0.14kg
*3 The specifications of the transceiver and the AUI cable need to be met. ( Page 76, Section 5.2.2)
*4 If divided files are received, only the first file is received and the remaining files are discarded.
*5 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.
*6 The following figure shows segment lengths and node intervals.
Segment length
Node Transceiver
Terminating resistor
Repeater Repeater
Segment length
Segment length
Node Node
Maximum
node-to-node
distance
Node Node
*7 For the maximum segment length (the length between hubs), consult the manufacturer of the hub used.
*8 The QJ71E71-100 does not support the flow control of the IEEE802.3x.
*9 When using the QJ71E71-100 with a serial number (first six digits) of "210214" or later, regard 10BASE-T as 10BASE-
Te.
30
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 Description Reference
Connecting with MELSOFT An E71 can be connected with MELSOFT products, such as a programming tool and Page 102,
products and a GOT MX Component, and a GOT. CHAPTER 8
CPU module data can be read/written from/to connected devices. Access to files can Page 105,
MC protocol communications
be also performed. CHAPTER 9
The connected device can read/write data from/to the buffer memory or device of an
Communications using SLMP SLMP supporting device connected to the shared network with the E71. In addition, Page 109,
(only QJ71E71-100) the connected device can read/write data from/to the device of the CPU module CHAPTER 10
where an E71 is mounted.
Data communications using the Data can be sent/received with protocols appropriate to each connected device.
Page 114,
predefined protocol The connected device side protocol can be easily selected, or created/edited from
CHAPTER 11
(only QJ71E71-100) the Predefined Protocol Library of GX Works2.
Procedure
Any data is sent/received between a CPU module and connected devices using the Page 141,
exists
fixed buffer of an E71. CHAPTER 12
No procedure
3.3.1 Function list

3.3 Function List
Communications
Paring receiving/sending connections enables data communications with two Page 160,
using a fixed Pairing open
connections by performing the open process for one port. Section 12.7
buffer
Broadcast communications are enabled with all E71-mounted stations in the same
Broadcast Page 162,
Ethernet network that is connected to the E71 when "No Procedure"
communications Section 12.8
communications using a fixed buffer are performed using UDP/IP.
Communications using a random Data is read/written from multiple connected devices to the random access buffer of Page 176,
access buffer an E71. CHAPTER 13
Data communications are performed through a router and a gateway. This function Page 191,
Router relay function
is not the function where an E71 operates as a router. Section 14.1
Communications using an auto- Communications are enabled without the open/close processes after an E71- Page 196,
open UDP port mounted station is started up. Section 14.2
The IP address of the connected device to be allowed or denied access is set in the Page 197,
IP filter function
buffer memory, and access from connected devices is restricted. Section 14.3
Page 203,
Remote password Unauthorized remote access to a CPU module is prevented.
Section 14.4
Hub connection status monitor The current connection status and transmission speed of an E71 and a hub and the Page 213,
function (only QJ71E71-100) number of times that the E71 detected disconnection can be checked. Section 14.5
IP address in use detection function If different stations in the same network use the same IP address, the address in use Page 214,
(only QJ71E71-100) can be detected. Section 14.6
Network configuration in a Page 216,
A network can be configured in a redundant system.
redundant system Section 14.7
Whether a connected device is normally operating after a connection is established Page 236,
Alive check function
(open process) can be checked. Section 14.8
31
Function Description Reference
An error that has occurred in an E71 can be stored in the CPU module as error
Module error collection function history. The history data can be stored on a memory with the backup power feature; Page 287,
(only QJ71E71-100) therefore error details are held even if the CPU module is reset or the system is Section 16.3
powered off.
32
(2) Special functions

The following special functions are also available. For the functions, refer to the following.
Function Description
Data are sent/received using an e-mail.
E-mail function
• Data sent/received by a CPU module 3
• Data sent using the programmable controller CPU monitoring function
(automatic notification function)
CC-Link IE Controller Network, CC-Link IE Field
Data are communicated over multiple network systems where Ethernet and other
Network, MELSECNET/H, MELSECNET/10 relay
networks exist together or network systems that relay multiple Ethernet networks.
communications
Data of a CPU module in other stations can be read/written over Ethernet using
Communications using data link instructions
data link instructions.
Data can be read/written in files from connected devices using an exclusive FTP
File transfer (FTP server) function
command.
(3) Web function

This function allows data to be read/written from/to a remote CPU module over the Internet using a commercially
available Web browser. For the function, refer to the following.
MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)
3.3.1 Function list

3.3 Function List
33
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
Communication
Network, CC-Link IE Field Router Alive Communications
function Pairing IP filter Remote Broadcast
Network, MELSECNET/H, relay check using an auto-open
(Communication open function password communications
MELSECNET/10 relay function function UDP port
method)
communications
MC protocol
communications *1 *2 × *1 *1 *3
(TCP/IP, UDP/IP)
Communications using
a fixed buffer × × *3 *4
(TCP/IP, UDP/IP)
SLMP × × *3
(TCP/IP, UDP/IP)
Data communications
using the predefined
× × *3
protocol
(TCP/IP, UDP/IP)
a random access
× × × ×
buffer
(TCP/IP, UDP/IP)
E-mail function
× × × × × ×
(TCP/IP)
data link instructions × × ×
(UDP/IP)
File transfer (FTP
server) function × × × × ×
(TCP/IP)
Web function
× × × ×
(TCP/IP)
*1 These functions cannot be used with an A-compatible 1E frame.

*2 The auto-open UDP port is excluded.
*3 These functions can be used only for UDP/IP communication.
*4 These functions cannot be used for communications using a fixed buffer in the "Procedure Exist" control method.
34
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 (the module is mounted on the slot 0 of a main base unit) is listed below.
Device Device
number
Signal name
number
Signal name
3
For fixed buffer communication of connection No.1 (ON:
Connection No.1 (ON: At sending request or reception
X0 Sending normal completion or reception completion, Y0
complete confirmation signal, OFF: -)
OFF: -)
For fixed buffer communication of connection No.1 (ON: Connection No.2 (ON: At sending request or reception
X1 Y1
Detection of sending error or reception error, OFF: -) complete confirmation signal, OFF: -)
OFF: -)
X3 Y3
OFF: -)
X5 Y5
OFF: -)
X7 Y7
3.4 List of I/O Signals

Connection No.1
(ON: Open request, OFF: -)
OFF: -)
For fixed buffer communication of connection No.5 (ON: Connection No.2
X9 Y9
Detection of sending error or reception error, OFF: -) (ON: Open request, OFF: -)
Connection No.3
XA Sending normal completion or reception completion, YA
OFF: -)
XB YB
Connection No.5
XC Sending normal completion or reception completion, YC
OFF: -)
XD YD
Connection No.7
XE Sending normal completion or reception completion, YE
OFF: -)
XF YF
Open completed for connection No.1
X10 Y10 Use prohibited
(ON: Open completion signal, OFF: -)
35
Device Device
Signal name Signal name
number number
Open completed for connection No.8 COM.ERR. LED Off request
X17 Y17
(ON: Open completion signal, OFF: -) (ON: At off request, OFF: -)
Open abnormal detection signal
(ON: At off request, OFF: -)
Initial normal completion signal Initial request signal
X19 Y19
(ON: Normal completion, OFF: -) (ON: At request, OFF: -)
Initial abnormal end signal
X1A Y1A Use prohibited
(ON: Abnormal end, OFF: -)
X1B Use prohibited Y1B Use prohibited
COM.ERR. LED lit confirmation
X1C Y1C Use prohibited
(ON: lit, OFF: -)
Predefined protocol ready
X1D Y1D Use prohibited
(ON: Ready, OFF: -)
X1E Use prohibited Y1E Use prohibited
Watchdog timer error detection
X1F Y1F Use prohibited
(ON: Watchdog timer error, OFF: -)
● Do not use any use prohibited signal as I/O signals to the CPU module. Doing so may cause malfunction of the
programmable controller system.
● Do not turn off the Open request signal (Y8 to YF) and turn on the COM.ERR. LED Off request (Y17) with the same
sequence scan.
Remark
The I/O signals listed in this section are mainly applied when QnA series module programs are used. For the Q 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.
For details on I/O signals, refer to the following.
For QnA Ethernet Interface Module User's Manual
36
3.5 Buffer Memory
This section describes the E71 buffer memory.
3.5.1 Configuration of the buffer memory 3

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.
3.5.1 Configuration of the buffer memory

3.5 Buffer Memory
(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.
37
3.5.2 List of buffer memory addresses
The following table lists the buffer memory addresses of an E71.
Address Initial value Programming

Decimal Application Name Hexadecimal tool setting
(Hexadecimal) (Decimal) applicability*2
0 and 1
Own station E71 IP address C00001FEH
(0H and 1H)
2 and 3
System area - -
(2H and 3H)
Special function settings

• Router relay function (b5, b4)
00: Do not use (default)
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 (default)
4
01: IP address computation system 0100H
(4H)
10: Table exchange system
11: Use-together system
• FTP function setting (b9, b8)
00: Do not use
01: Use (default)
Bits other than those described above are reserved for

system use.
5 to 10 Initial process
System area - -
(5H to AH) parameter setting
11 area 3CH
TCP ULP timer value
(BH) (Setting time = setting value × 500 ms) (60)
12 TCP zero window timer value 14H

(CH) (Setting time = setting value × 500 ms) (20)
13 TCP resend timer value 14H
(DH) (Setting time = setting value × 500 ms) (20)
14 TCP end timer value 28H
(EH) (Setting time = setting value × 500 ms) (40)
15 IP assembly timer value AH
(FH) (Setting time = setting value × 500 ms) (10)
Monitoring timer
16 Response monitoring timer value 3CH
(10H) (Setting time = setting value × 500 ms) (60)
Destination existence confirmation
17 4B0H
starting interval timer value
(11H) (1200)
(Setting time = setting value × 500 ms)
Destination existence confirmation
18 14H
interval timer value
(12H) (20)
(Setting time = setting value × 500 ms)
19 Destination existence confirmation 3H
(13H) resending time (3)
38

20
Initial process Auto-open UDP port number 1388H ×
(14H)
parameter setting
21 to 29
area System area - -
(15H to 1DH)
TCP Maximum Segment Transmission setting area

0H: Enable TCP Maximum Segment Size Option 3
transmission
30
8000H: Disable TCP Maximum Segment Size 8000H ×
(1EH)
Option transmission
Re-initialization makes the set value effective.

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
Initial process 1: Use the KeepAlive
parameter setting • Send frame setting (b5)
area (For 0: Ethernet
reinitialization) 1: IEEE 802.3
• Setting of write enable/disable at RUN time (b6)
31 0: Disable
0H
(1FH) 1: Enable
• Initial timing setting (b8)
0: Do not wait for OPEN

3.5 Buffer Memory
(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.
39
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)
32
0: TCP/IP 0H
(20H)
1: UDP/IP
• Fixed buffer communication procedure
(b10, b9)
00: Procedure exists
01: No procedure
10: Predefined protocol
Communication Connection • Open system (b15, b14)
parameter setting usage setting 00: Active open or UDP/IP
area area 10: Unpassive open
11: Fullpassive open
Bits other than those described above are

reserved for system use.
33
Connection No.2 (The bit configuration is the same as Connection No.1.)
(21H)
34
(22H)
35
(23H)
36
(24H)
37
(25H)
38
(26H)
39
(27H)
40

40
Own station port No. 0H
(28H)
41 and 42
Destination IP address 0H
(29H and 2AH) Connection
43 No.1
(2BH)
Destination Port No. 0H 3
44 to 46
Destination MAC address FFFFFFFFFFFFH ×
(2CH to 2EH)
47 to 53
(2FH to 35H)
Communication
54 to 60
Communication address setting Connection No.3 (The bit configuration is the same as Connection No.1.)
(36H to 3CH)
parameter setting area
61 to 67
area Connection No.4 (The bit configuration is the same as Connection No.1.)
(3DH to 43H)
68 to 74
(44H to 4AH)
75 to 81
(4BH to 51H)
82 to 88
(52H to 58H)
89 to 95
(59H to 5FH)
96 to 102
System area - -
(60H to 66H)

3.5 Buffer Memory
103 and 104
System area - -
(67H and 68H)
105
Initial error code 0H ×
(69H)
106 and 107

Own station IP address 0H ×
(6AH and 6BH)
108 to 110
Own station MAC address 0H ×
(6CH to 6EH)
111 to 115 Communication

System area - -
(6FH to 73H) status storage
area Area for the initial
116
process Auto-open UDP port number 0H ×
(74H)
117
System area - -
(75H)
Station number (b0 to b7)

118
Network number of the own station (b8 to 0H ×
(76H)
b15)
119
Own station group number 0H ×
(77H)
41
120
Own station port No. 0H ×
(78H)
121 and 122

Destination IP address 0H ×
(79H and 7AH)
123
Destination Port No. 0H ×
(7BH)
124
Open error code 0H ×
(7CH)
125 Fixed buffer sending error

0H ×
(7DH) code
Connection
126 No.1
Connection end code 0H ×
(7EH)
Fixed buffer
127
communication time 0H ×
(7FH)
(Maximum value)
Fixed buffer
128
Communication communication time 0H ×
(80H) Connection
status storage (Minimum value)
information area
area Fixed buffer
129
(81H)
(Current value)
130 to 139
(82H to 8BH)
140 to 149
(8CH to 95H)
150 to 159
(96H to 9FH)
160 to 169
(A0H to A9H)
170 to 179
(AAH to B3H)
180 to 189
(B4H to BDH)
190 to 199
(BEH to C7H)
42

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)
3
0: OFF
1: ON (connection open processing
200
completed) 0H ×
(C8H)
• [ERR.]LED (b3)
0: OFF
1: ON (setting error)
• [COM.ERR.]LED (b4)
0: OFF
1: ON (communication error)

Communication reserved for system use.
Area for module
status storage
status Hub connection status area
area
• Communication mode (b9)
0: Half duplex
1: Full duplex
• Hub connection status (b10)
0: Hub not connected/disconnected
201
1: Hub connected 0H ×
(C9H)
• Data transmission speed (b14)
0: Operating at 10BASE-T

3.5 Buffer Memory
1: Operating at 100BASE-TX

Switch status
• Operational mode setting (b1)
202 0: Online
0H
(CAH) 1: Offline
2: Self-loopback test
3: Hardware test
43
Status of settings with a programming tool

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 sequence
program)
1: Parameter setting (start up
according to the parameters)
0: Use the Ping
1: Use the KeepAlive
• Send frame setting (b5)
203 Module status 0: Ethernet
0H
(CBH) area 1: IEEE 802.3
• Setting of write enable/disable at RUN
time (b6)
0: Disable
1: Enable
0: Do not wait for OPEN
Communication
(Communications impossible at
status storage
STOP time)
area
1: Always wait for OPEN
(Communication possible at STOP
time)

204
System area - -
(CCH)
205
RECV instruction execution request 0H ×
(CDH)
206
System area - -
(CEH)
Area for
207
sending/receiving ZNRD instruction 0H ×
(CFH)
instructions
208 Data link
System area - -
(D0H) instruction
209 execution
ZNWR instruction 0H ×
(D1H) result
210 to 223
System area - -
(D2H to DFH)
224 to 226
System area - -
(E0H to E2H)
227
Error log area Number of errors 0H ×
(E3H)
228
Error log write pointer 0H ×
(E4H)
44

229
Error code/end code 0H ×
(E5H)
230
Subheader 0H ×
(E6H)
231
(E7H)
Command code 0H × 3
232
Connection No. 0H ×
(E8H) Error log
233 block 1
(E9H)
234 and 235

Destination IP address 0H ×
(EAH and EBH)
236
(ECH)
237
System area - -
(EDH)
238 to 246
Error log block 2 (The bit configuration is the same as Error log block 1.)
(EEH to F6H)
247 to 255
(F7H to FFH)
256 to 264
(100H to 108H)
265 to 273 Error log block

Error log area Error log block 5 (The bit configuration is the same as Error log block 1.)
(109H to 111H) area

3.5 Buffer Memory
274 to 282
(112H to 11AH)
283 to 291
(11BH to 123H)
292 to 300
(124H to 12CH)
301 to 309
(12DH to 135H)
310 to 318
(136H to 13EH)
319 to 327
(13FH to 147H)
328 to 336
(148H to 150H)
337 to 345
(151H to 159H)
346 to 354
(15AH to 162H)
355 to 363
(163H to 16BH)
364 to 372
(16CH to 174H)
45
373 to 375
System area - -
(175H to 177H)
376 and 377

Received IP packet count 0H ×
(178H and 179H)
Received IP packet count

378 and 379
discarded due to sumcheck 0H ×
(17AH and 17BH)
error
380 and 381
Sent IP packet total count 0H ×
(17CH and 17DH) IP
382 to 397
System area - -
(17EH to 18DH)
398 and 399 Simultaneous transmission

0H ×
(18EH and 18FH) error detection count
400 to 407
System area - -
(190H to 197H)
408 and 409 Received ICMP packet

0H ×
(198H and 199H) count
Received ICMP packet
410 and 411
count discarded due to 0H ×
(19AH and 19BH)
sum check error
412 and 413 Sent ICMP packet total
Status for each 0H ×
(19CH and 19DH) Error log area count
protocol
414 and 415 Echo request total count of
0H ×
(19EH and 19FH) ICMP received ICMP packets
416 and 417 Echo reply total count of
0H ×
(1A0H and 1A1H) sent ICMP packets
418 and 419 Echo request total count of
0H ×
(1A2H and 1A3H) sent ICMP packets
420 and 421 Echo reply total count of
0H ×
(1A4H and 1A5H) received ICMP packets
422 to 439
System area - -
(1A6H to 1B7H)
440 and 441 Received TCP packet

0H ×
(1B8H and 1B9H) count
Received TCP packet
442 and 443
(1BA H and 1BBH)
TCP sum check error
444 and 445 Sent TCP packet total
0H ×
(1BCH and 1BDH) count
446 to 471
System area - -
(1BEH to 1D7H)
46

472 and 473 Received UDP packet

0H ×
(1D8H and 1D9H) count
Received UDP packet
474 and 475
(1DAH and 1DBH)
UDP sum check error
476 and 477 Sent UDP packet total 3
0H ×
(1DCH and 1DDH) count
478 to 481
System area - -
(1DEH to 1E1H)
Status for each
482 to 491 Error log area
protocol System area - -
(1E2H to 1EBH)
492 and 493

Framing error count 0H ×
(1ECH and 1EDH)
494 and 495 Receiving

Overflow count 0H ×
(1EEH and 1EFH) error
496 and 497
crc error count 0H ×
(1F0H and 1F1H)
498 to 511
System area - -
(1F2H to 1FFH)
512 and 513

Sub-net mask 0H
(200H and 201H)
514 and 515

Default router IP address 0H
(202H and 203H)
516
Number of registered routers 0H

3.5 Buffer Memory
(204H)
517 and 518

Sub-net address 0H
(205H and 206H)
Router 1
519 and 520
Router IP address 0H
(207H and 208H)
521 to 524
Router 2 (The bit configuration is the same as Router 1.)
(209H to 20CH)
Router relay
525 to 528
parameter Router 3 (The bit configuration is the same as Router 1.)
(20DH to 210H)
setting area
529 to 532
(211H to 214H)
533 to 536
(215H to 218H)
537 to 540
(219H to 21CH)
541 to 544
(21DH to 220H)
545 to 548
(221H to 224H)
549
System area - -
(225H)
47
550 and 551

System area - -
(226H and 227H)
552
Number of conversion table data 0H
(228H)
Communication request
553 and 554
destination/source stations network 0H
(229H and 22AH)
number and station number
Conversion
555 and 556 External station Ethernet module IP
information No.1 0H
(22BH and 22CH) address
Station No.
557 and 558
<-> IP System area - -
(22DH and 22EH)
information
559 to 564 Conversion information No.2
setting area
(22FH to 234H) (The bit configuration is the same as Conversion information No.1.)
to to
931 to 936 Conversion information No.64
(3A3H to 3A8H) (The bit configuration is the same as Conversion information No.1.)
Net mask pattern for CC-Link IE Controller Network, CC-Link
937 and 938
IE Field Network, MELSECNET/H, and MELSECNET/10 0H
(3A9H and 3AAH)
routing
939 to 943
System area - -
(3ABH to 3AFH)
944 to 949
FTP login name "QJ71E71"
(3B0H to 3B5H)
950 to 953
Password "QJ71E71"
(3B6H to 3B9H)
954
FTP setting area Command input monitoring timer 708H
(3BAH)
955
Programmable controller CPU monitoring timer AH
(3BBH)
956 to 1663
System area - -
(3BCH to 67FH)
48

1664
Data length 0H ×
(680H)
Fixed buffer No.1
1665 to 2687
Fixed buffer data 0H ×
(681H to A7FH)
2688 to 3711
(A80H to E7FH)
Fixed buffer No.2 (The bit configuration is the same as Fixed buffer No.1.) 3
3712 to 4735
Fixed buffer No.3 (The bit configuration is the same as Fixed buffer No.1.)
(E80H to 127FH)
4736 to 5759 Fixed buffer data

(1280H to 167FH) area
5760 to 6783
(1680H to 1A7FH)
6784 to 7807
(1A80H to 1E7FH)
7808 to 8831
(1E80H to 227FH)
8832 to 9855
(2280H to 267FH)
9856 to 16383 Shared area for

Shared area for random access buffers and e-mail buffers 0H ×
(2680H to 3FFFH) random access
16384 to 18431 buffers and
e-mail buffers System area - -
(4000H to 47FFH)
Send/receive
area for
18432 to 20479

3.5 Buffer Memory
predefined Send/receive area for predefined protocol support function 0H
(4800H to 4FFFH)
protocol support
function
49
Open completion signal

0: Open incomplete
1: Open completed
20480
• Connection No.1 (b0) 0H ×
(5000H)
• Connection No.2 (b1)
to
20481
System area - -
(5001H) Connection
status Open request signal
information area 0: No open request
1: Open being requested
20482
(5002H)
to
Connection
20483 and 20484
status storage
(5003H and System area - -
area
5004H)
Fixed buffer reception status signal

0: Data not received
1: Data being received
20485 Fixed buffer
(5005H) information area
to
Remote password status
0: Unlock status/no remote password
setting
Remote
20486 1: Lock status
password status 0H ×
(5006H) • Connection No.1 (b0)
storage area
to
Remote password status
0: Unlock status/no remote password
setting
1: Lock status
Remote
20487 System port • Auto-open UDP port (b0)
password status 0H ×
(5007H) information area • MELSOFT application transmission
storage area
port (UDP) (b1)
• MELSOFT application transmission
port (TCP) (b2)
• FTP transmission port (b3)
50

System port use prohibited designation

0: Use allowed
1: Use prohibited
20488 • Auto-open UDP port (b0)
System port use 0H ×
(5008H) System port • MELSOFT application transmission
prohibited
information area
designation area
port (UDP) (b1)
• MELSOFT application transmission
3
port (TCP) (b2)
20489 to 20591
System area - -
(5009H to 506FH)
Remote password mismatch notification

accumulated count designation (For user
20592 open port)
1H ×
(5070H) 0: No designation
1 or higher: Notification accumulated
count
Remote password mismatch notification
accumulated count designation (For
auto-open UDP port, MELSOFT
20593 application transmission port (TCP/ UDP)
2H ×
(5071H) and FTP transmission port)
0: No designation
1 or higher: Notification accumulated
count
Accumulated count of
20594
unlock process normal 0H ×
(5072H)
completion

3.5 Buffer Memory
Accumulated count of
20595
Remote unlock process abnormal 0H ×
(5073H)
password end
Monitoring area Connection
20596 function No.1 Accumulated count of lock
0H ×
(5074H) monitoring area process normal completion
20597 Accumulated count of lock
0H ×
(5075H) process abnormal end
20598 Accumulated count of lock
0H ×
(5076H) process based on close
20599 to 20603
(5077H to 507BH)
20604 to 20608
(507CH to 5080H)
20609 to 20613
(5081H to 5085H)
20614 to 20618
(5086H to 508AH)
20619 to 20623
(508BH to 508FH)
20624 to 20628
(5090H to 5094H)
51
20629 to 20633
(5095H to 5099H)
20634 to 20638
(509AH to 509EH)
20639 to 20643
(509FH to 50A3H)
20644 to 20648
(50A4H to 50A8H)
20649 to 20653
(50A9H to 50ADH)
20654 to 20658
(50AEH to 50B2H)
20659 to 20663
Remote Connection No.14 (The bit configuration is the same as Connection No.1.)
(50B3H to 50B7H)
password
20664 to 20668 Monitoring area
function Connection No.15 (The bit configuration is the same as Connection No.1.)
(50B8H to 50BCH)
monitoring area
20669 to 20673
(50BDH to Connection No.16 (The bit configuration is the same as Connection No.1.)
50C1H)
20674 to 20678 Auto-open UDP port

(50C2H to 50C6H) (The bit configuration is the same as Connection No.1.)
20679 to 20683
MELSOFT application transmission port (UDP)
(50C7H to
(The bit configuration is the same as Connection No.1.)
50CBH)
20684 to 20688
MELSOFT application transmission port (TCP)
(50CCH to
(The bit configuration is the same as Connection No.1.)
50D0H)
20689 to 20693 FTP transmission port

(50D1H to 50D5H) (The bit configuration is the same as Connection No.1.)
52

20694 to 20736
System area - -
(50D6H to 5100H)
20737
Error log pointer 0H ×
(5101H)
20738 Log counter

(5102H) (HTTP response code 100 to 199)
0H × 3
20739 Log counter
0H ×
20740 Log counter
0H ×
20741 Log counter
0H ×
20742 Log counter
0H ×
20743
System area - -
(5107H)
20744
HTTP response code 0H ×
(5108H)
20745 and 20746

(5109H and Error log block 1 Destination IP address 0H ×
510AH)
20747 to 20750
Error time 0H ×
(510BH to 510EH)
HTTP status
20751 to 20757
storage area

3.5 Buffer Memory
(510FH to 5115H)
20758 to 20764
(5116H to 511CH)
20765 to 20771
(511DH to 5123H)
20772 to 20778
(5124H to 512AH)
20779 to 20785
(512BH to 5131H)
20786 to 20792
(5132H to 5138H)
20793 to 20799
(5139H to 513FH)
20800 to 20806
(5140H to 5146H)
20807 to 20813
(5147H to 514DH)
20814 to 20820
(514EH to 5154H)
20821 to 20827
(5155H to 515BH)
20828 to 20834
(515CH to 5162H)
53
20835 to 20841
(5163H to 5169H)
20842 to 20848 Status storage

(516AH to 5170H) area
20849 to 20855
(5171H to 5177H)
20856 to 20991
System area - -
(5178H to 51FFH)
"Issue system switch in cable disconnection timeout"

20992
0: Not set 1H
(5200H)
1: Set
"Issue system
20993 switching request Disconnection detection monitoring time
4H
(5201H) at disconnection Set time = set value × 500ms (setting range: 0 to 60)
20994 detection" status
System area - -
(5202H) storage area
20995
Disconnection detection count 0H ×
(5203H)
20996 to 21007
System area - -
(5204H to 520FH)
"System switching settings when communication error

occurs" (user connection)
0: Not set
21008 1: Set
0H
(5210H) • Connection No.1 (b0)
"System • Connection No.2 (b1)
switching settings to
when • Connection No.16 (b15)
communication "System switching settings when communication error
error occurs" occurs" (system connection)
status storage 0: Not set
area 1: Set
21009
• Auto-open UDP port (b0) 0H
(5211H)
• MELSOFT application transmission port (UDP) (b1)
• MELSOFT application transmission port (TCP) (b2)
• FTP transmission port (b3)
• HTTP port (b4)
21010 to 21055
System area - -
(5212H to 523FH)
Receive buffer Receive buffer full detection signal

21056
status storage 0: Receive buffer not full 0H ×
(5240H)*1
area 1: Receive buffer full
21057 to 21119
System area - -
(5241H to 527FH)
54

Same IP address detection flag

21120
0: Unique IP addresses 0H ×
(5280H)
1: Same IP address for multiple stations
The MAC address of the station that has been already
21121 to 21123 IP address status
connected to the network (The address is stored in the station FFFFFFFFFFFFH ×
(5281H to 5283H) storage area
with the same IP address.) 3
The MAC address of the station with the IP address used for
21124 to 21126
another station (The address is stored in the station that has FFFFFFFFFFFFH ×
(5284H to 5286H)
been already connected to the network.)
21127 to 21279
System area - -
(5287H to 531FH)
21280 to 21283
System area - -
(5320H to 5323H)
21284
Protocol No. 0H ×
(5324H)
21285
Setting type 0H ×
(5325H) Protocol setting data error
21286 information
Packet No. 0H ×
(5326H) Protocol setting
21287 data check area
Element No. 0H ×
(5327H)
21288
Number of registered protocols 0H ×
(5328H)
21289 to 21295
System area - -
(5329H to 532FH)

3.5 Buffer Memory
21296 to 21311
Protocol registration 0H ×
(5330H to 533FH)
21312 to 21695
System area - -
(5340H to 54BFH)
55
21696
Protocol execution status 0H ×
(54C0H)
21697
System area - -
(54C1H)
21698 to 21713 Received data verification result (receive

Connection No.1 0H ×
(54C2H to 54D1H) packet No.1 to 16)
21714
Number of protocol executions 0H ×
(54D2H)
21715
Protocol cancellation specification 0H
(54D3H)
21716 to 21735 Predefined

protocol support Connection No.2 (The bit configuration is the same as Connection No.1.)
(54D4H to 54E7H)
function
21736 to 21755
execution status Connection No.3 (The bit configuration is the same as Connection No.1.)
(54E8H to 54FBH)
check area
21756 to 21775
(54FCH to 550FH)
21776 to 21795
(5510H to 5523H)
21796 to 21815
(5524H to 5537H)
21816 to 21835
(5538H to 554BH)
21836 to 21855
(554CH to 555FH)
21856 to 21875
(5560H to 5573H)
21876 to 21895
(5574H to 5587H)
21896 to 21915
(5588H to 559BH)
21916 to 21935 Predefined

protocol support Connection No.12 (The bit configuration is the same as Connection No.1.)
(559CH to 55AFH)
function
21936 to 21955
execution status Connection No.13 (The bit configuration is the same as Connection No.1.)
(55B0H to 55C3H)
check area
21956 to 21975
(55C4H to 55D7H)
21976 to 21995
(55D8H to 55EBH)
21996 to 22015
(55ECH to 55FFH)
22016 to 22271
System area - -
(5600H to 56FFH)
56

Use of IP filter settings

22272 (5700H) • 0: Do not use 0H ×
• 1: Use
IP filter function type setting
22273 (5701H) • 0: Allow 0H ×
• 1: Deny 3
22274 to 22275
Start IP address 0H ×
(5702H to 5703H) IP address
22276 to 22277 setting 1
End IP address 0H ×
(5704H to 5705H)
22278 to 22281 IP address setting 2 (The bit configuration

0H ×
(5706H to 5709H) is the same as IP address setting 1.)
22282 to 22285 IP filter settings
IP address setting 3 (The bit configuration
0H ×
(570AH to 570DH) is the same as IP address setting 1.)
IP filter function
22286 to 22289 area IP address setting 4 (The bit configuration
0H ×
(570EH to 5711H) is the same as IP address setting 1.)
0H ×
0H ×
0H ×
(571AH to 571DH) is the same as IP address setting 1.)
0H ×
(571EH to 5721H) is the same as IP address setting 1.)

3.5 Buffer Memory
22306 to 22307 Number of access denied by the IP filter
0H ×
(5722H to 5723H) IP filter function
22308 to 22309 monitoring area
IP address denied by the IP filter function 0H ×
(5724H to 5725H)
22310 to 22559
System area - -
(5726H to 581FH)
57
22560
(5820H)
22561 and 22562

(5821H and Destination IP address 0H ×
5822H)
22563
(5823H)
222564
Open error code 0H ×
(5824H)
22565 Fixed buffer sending error

Connection 0H ×
(5825H) code
No.9
22566
Connection end code 0H ×
(5826H)
Fixed buffer
22567
(5827H)
(Maximum value)
Fixed buffer
22568 Communication
Connection communication time 0H ×
(5828H) status storage
information area (Minimum value)
area
Fixed buffer
22569
(5829H)
(Current value)
22570 to 22579
(582AH to 5833H)
22580 to 22589
(5834H to 583DH)
22590 to 22599
(583EH to 5847H)
22600 to 22609
(5848H to 5851H)
22610 to 22619
(5852H to 585BH)
22620 to 22629
(585CH to 5865H)
22630 to 22639
(5866H to 586FH)
58

22640
Number of mails remaining on the server 0H ×
(5870H)
22641 Dedicated instruction normal completion

0H ×
(5871H) count
22642
(5872H)
Dedicated instruction abnormal end count 0H × 3
22643
Normal receiving count 0H ×
(5873H)
22644
Attached file receiving count 0H ×
(5874H)
22645
Server inquiry count 0H ×
(5875H)
22646
Server communication error count 0H ×
(5876H) E-mail status
Receive
22647 storage area
Error log write count 0H ×
(5877H)
22648
Receiving error log write pointer 0H ×
(5878H)
22649
Error code 0H ×
(5879H)
22650
Command code 0H ×
(587AH)
22651 to 22658 Error log

From 0H ×
(587BH to 5882H) block 1

3.5 Buffer Memory
22659 to 22662
Date 0H ×
(5883H to 5886H)
22663 to 22692
Subject 0H ×
(5887H to 58A4H)
59
22693 to 22736
(58A5H to 58D0H)
22737 to 22780
(58D1H to 58FCH)
22781 to 22824
(58FDH to 5928H)
22825 to 22868
(5929H to 5954H)
22869 to 22912
(5955H to 5980H)
22913 to 22956
(5981H to 59ACH)
22957 to 23000
(59ADH to Error log block 8 (The bit configuration is the same as Error log block 1.)
59D8H)
23001 to 23044
(59D9H to 5A04H) Receive
23045 to 23088
(5A05H to 5A30H)
23089 to 23132
(5A31H to 5A5CH)
23133 to 23176
(5A5DH to 5A88H)
E-mail status
23177 to 23220
storage area Error log block 13 (The bit configuration is the same as Error log block 1.)
(5A89H to 5AB4H)
23221 to 23264
(5AB5H to Error log block 14 (The bit configuration is the same as Error log block 1.)
5AE0H)
23265 to 23308
(5AE1H to Error log block 15 (The bit configuration is the same as Error log block 1.)
5B0CH)
23309 to 23352
(5B0DH to 5B38H)
23353 Dedicated instruction normal completion

0H ×
(5B39H) count
23354
Dedicated instruction abnormal end count 0H ×
(5B3AH)
23355
Number of mails normally completed 0H ×
(5B3BH)
23356
Send Attached file sending count 0H ×
(5B3CH)
23357
Sending to the server count 0H ×
(5B3DH)
23358
Number of mails abnormally completed 0H ×
(5B3EH)
23359
Error log write count 0H ×
(5B3FH)
60

23360
Sending error log write pointer 0H ×
(5B40H)
23361
Error code 0H ×
(5B41H)
23362
(5B42H)
Command code 0H × 3
23363 to 23370
To 0H ×
(5B43H to 5B4AH) Error log
23371 to 23374 block 1
(5B4BH to Date 0H ×
5B4EH)
23375 to 23404
(5B4FH to Subject 0H ×
5B6CH)
23405 to 23448
(5B6DH to 5B98H)
Send
23449 to 23492
E-mail status Error log block 3 (The bit configuration is the same as Error log block 1.)
(5B99H to 5BC4H)
storage area
23493 to 23536
(5BC5H to Error log block 4 (The bit configuration is the same as Error log block 1.)
5BF0H)
23537 to 23580
(5BF1H to Error log block 5 (The bit configuration is the same as Error log block 1.)
5C1CH)

3.5 Buffer Memory
23581 to 23624
(5C1DH to Error log block 6 (The bit configuration is the same as Error log block 1.)
5C48H)
23625 to 23668
(5C49H to 5C74H)
23669 to 23712
(5C75H to Error log block 8 (The bit configuration is the same as Error log block 1.)
5CA0H)
23713 to 24575
(5CA1H to System area - -
5FFFH)
61
24576
Data length 0H ×
(6000H)
Fixed buffer No.9
24577 to 25599
Fixed buffer data 0H ×
(6001H to 63FFH)
25600 to 26623
(6400H to 67FFH)
26624 to 27647
(6800H to 6BFFH)
27648 to 28671 Fixed buffer data

(6C00H to 6FFFH) area
28672 to 29695
(7000H to 73FFH)
29696 to 30719
(7400H to 77FFH)
30720 to 31743
(7800H to 7BFFH)
31744 to 32767
(7C00H to 7FFFH)
*1 Available only for the QJ71E71-100.
Availability depends on the QJ71E71-100 version. ( Page 353, Appendix 3)
*2 " " means area which is reflected values of network parameters set by the programming tool and "×" means area which
is not reflected them.
62
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 84, CHAPTER 7)
Checkbox
System planning
Page 28, CHAPTER 3,
Page 65, CHAPTER 5
4
Plan the system configuration of the E71.
Mounting
Page 26, CHAPTER 2,
Mount the E71 on the base unit. Page 78, Section 6.1
Wiring
Page 74, Section 5.2,
Connect an Ethernet cable to the E71. Page 79, Section 6.2
Setting parameters
Page 86, Section 7.1.2,
Set the following parameters, which are required to start up Page 87, Section 7.1.3
the E71, on a programming tool.
Basic setting
Ethernet operation setting
Restarting the CPU module

QCPU User's Manual
Reflect the parameter settings by powering off and on the CPU (Hardware Design,
module or resetting the CPU module. Maintenance and
Inspection)
Network diagnostics
Page 366, Appendix 5
Check that the cables are connected properly or that
communications are performed normally with the set
parameters. (PING test, loopback test)
Continued to COMMUNICATION PROCEDURE
63
Memo
64
CHAPTER 5 SYSTEM CONFIGURATION
This chapter describes the system configuration of an E71.
5.1 Configuration of an E71-mounted System
This section describes the configuration of the system where an E71 is mounted.
5.1.1 Applicable modules and base units, and the number of 5

connectable modules
(1) Connecting an E71 to a CPU module

For the CPU modules and base units that can be used for an E71 and the number of connectable modules, refer
to the following.
User’s Manual (Hardware Design, Maintenance and Inspection) for the CPU module used.
(2) Connecting an E71 in a MELSECNET/H remote I/O station

For the base units that can be used for an E71 and the number of connectable modules, refer to the following.
Q Corresponding MELSECNET/H Network System Reference Manual (Remote I/O network)
5.1.1 Applicable modules and base units, and the number of connectable modules
65
5.1.2 For use with a Basic model QCPU or safety CPU
When an E71 is mounted to a Basic model QCPU or a safety CPU, the available functions are restricted as follows.
: Available, ×: Not available
Availability
Function Basic model
Safety CPU
QCPU
Connection with MELSOFT products and a GOT
MC protocol communications
Communications using SLMP
Data communications using the predefined protocol ×
Communications using a fixed buffer *2
Receive process using an interrupt program *1 ×
Pairing open
Broadcast communications
Communications using a random access buffer ×
IP filter function
Remote password *1
Communications using an auto-open UDP port
Connected device alive check function
E-mail function *1 ×
CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H,
×
MELSECNET/10 relay communications
Communications using data link instructions *3 *3
Receive process using an interrupt program *1 ×
File transfer (FTP server function) ×
Web function ×
*1 This function can be used in a Basic model QCPU with the function version B or later. For the version of a programming
tool, check the corresponding software version. ( Page 432, Appendix 11.1)
*2 The connection numbers 1 to 8 only can be specified. If the specified value is out of range, an "OPERATION ERROR"
(error code: 4101) occurs.
*3 When the target station of the SREAD/SWRITE instructions is a Basic model QCPU or safety CPU, the read notification
device to the target station set to the argument (D3) is ignored. The operation of the SREAD/SWRITE instructions is the
same as that of the READ/WRITE instructions. For the SREAD/SWRITE instructions, refer to the following.
66
5.1.3 For use in a multiple CPU system
When using an E71 in a multiple CPU system, refer to the following.

QCPU User's Manual (Multiple CPU System)
(1) Precautions
Note the following precautions for when using an E71 in a multiple CPU system.
(a) Writing network parameters

Configure network parameters only on the control CPU of an E71.
(b) Accessing an E71 non-control CPU from a connected device

When accessing a non-control CPU in a multiple CPU system, use an E71 with the function version B or later.
5
E71
Non-control CPU Connected device
Control CPU
(c) Accessing other stations

A control CPU and non-control CPU in a station to be accessed are accessible even when a relay station or
station to be accessed is configured in a multiple CPU system. To access a non-control CPU, use modules of
the function version B or later in the own station and all relay stations and for all relay modules in stations to be
5.1.3 For use in a multiple CPU system

accessed and CPU modules.
Ex. When the relay modules are CC-Link IE Controller Network modules
Own
station
Programming tool CC-Link IE Connected device

Controller Network
Relay
station
CC-Link IE
Controller Network
Station to be
accessed
67
5.1.4 For use in a redundant system
When using an E71 in a redundant system, refer to the following.

QnPRHCPU User's Manual (Redundant System)
(1) Mounting an E71 on the main base unit of a redundant system

This section provides information on mounting an E71 on the main base unit of a redundant system.
(a) Basic system configuration

Access can be performed from a connected device to the control system and standby system of a redundant
system.
(b) System configuration with a communication path backed up

Access can be performed from a connected device to the control system and standby system of the redundant
system in the communication path 1 or communication path 2.
Ex. If a communication error occurs during access to the control system through the communication path 1
(1) in the figure below), the control system can be accessed through the communication path 2 (2) in the
figure below). If a communication error also occurs in the communication path 2, the system switches
between the control system and the standby system, enabling communications with the new system (3) in
the figure below).
Connected device
Ethernet Ethernet
network No.1 network No.2
Control system 1) 2) Standby system 3)
Tracking cable
: Communication path 1
: Communication path 2
68
(c) Restrictions on the use of the functions

When an E71 is mounted on a main base unit, the available functions are restricted as follows.
Function Availability
MC protocol communications *1
Data communications using the predefined protocol
Communications using a fixed buffer *1
Pairing open
Broadcast communications *1
Communications using a random access buffer *1 5

IP filter function
Remote password
E-mail function *1
CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10 relay *1

communications
Communications using data link instructions *1
File transfer (FTP server function) *1
Web function
5.1.4 For use in a redundant system

*1 Available with restrictions. For the restrictions, refer to the functions that can be used in a redundant system.
( Page 226, Section 14.7.4)
69
(2) Mounting an E71 on the extension base unit of a redundant system
This section provides information on mounting an E71 on the extension base unit of a redundant system.
(a) System configuration

The following shows the system configuration.
Control system Standby system
Tracking cable
Extension cable
Extension base unit
Ethernet
Connected device
(b) Restrictions on the use of the functions

Restrictions are the same as those of when an E71 is mounted on a main base unit, except for the following
restrictions.
• Because an E71 does not issue a system switching request to the control system CPU module, the
system switching does not continue communications. To continue communications even when the E71
experiences a communication error or when the cable is disconnected, mount the E71 on a main base
unit.
• Dedicated instructions cannot be used. To use dedicated instructions, mount the E71 on a main base unit.
• The following restrictions apply to communications via modules mounted on an extension base unit.
• An access destination that can be specified (a control system CPU module or standby system
CPU module or a system A CPU module or system B CPU module) varies according to the MC
protocol dedicated command.
• If systems are switched during MC protocol communications or communications using dedicated
instructions from other stations, a communication timeout may occur.
70
5.1.5 For use in a MELSECNET/H remote I/O station
This section provides information on using an E71 in a MELSECNET/H remote I/O station.
(1) System configuration

The following shows the system configuration.
Remote master station Remote I/O station
MELSECNET/H remote I/O network

Connected device
5
Remote I/O station
(2) Parameter settings

Configure the network parameters as follows.
(a) Ethernet operation setting

Select "Always wait for OPEN" for the initial timing setting.
(b) Open setting

Select "Unpassive" or "Fullpassive" in the open system for the TCP/IP communication. An auto-open UDP port
can be also used for UDP/IP communication.
(3) Open/close processes

Perform the open/close processes on the connected device side.
71
(4) Restrictions on the use of the functions
The available functions are restricted as follows.
Function Availability
Program setting ×
Initial process
Network parameter setting
Program setting ×
Open/close processes
Network parameter setting
MC protocol communications (Refer to clause (5).)

Data communications using the predefined protocol ×
Communications using a fixed buffer ×
Pairing open ×
Broadcast communications ×
Communications using a random access buffer
IP filter function
Remote password *1

E-mail function ×
CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H,
MELSECNET/10 relay communications
Communications using data link instructions × (Can be relayed)
File transfer (FTP server function) ×
Web function ×
*1 This function can be used in a MELSECNET/H remote I/O station with the function version D or later. For the version of
a programming tool, check the corresponding software version. ( Page 432, Appendix 11.1)
72
(5) Access using MC protocol communications

Access to a MELSECNET/H remote I/O station using the MC protocol and access to other stations via a
MELSECNET/H remote I/O station are described below.
(a) Compatible frames

Use a QnA-compatible 3E frame or 4E frame for communications. (An A-compatible 1E frame cannot be used.)
(b) Available functions

The following functions can be used in MELSECNET/H remote I/O stations.
• Reading/writing of device memory*1 *2
• Reading/writing of buffer memory*2
• Reading/writing of intelligent function module buffer memory
5
*1 For accessible MELSECNET/H remote I/O station devices, refer to the following.
MELSEC Communication Protocol Reference Manual
*2 This function cannot be used in QnA/A series-compatible MELSECNET/10 remote I/O stations.
(c) Access to other stations through MELSECNET/H remote I/O stations

A MELSECNET/H remote master station and MELSECNET/H remote I/O stations can be accessed.
Ex. The MELSECNET/H remote master station and MELSECNET/H remote I/O stations can be accessed
from a connected device.
Remote master station

Connected device
1) MELSECNET/H remote I/O network
Access allowed
Access not allowed
2)
The following methods cannot be used to access other stations through MELSECNET/H remote I/O
stations.
• Access to other stations from a MELSECNET/H remote master station via the E71 connected in
a MELSECNET/H remote I/O station (1) in the figure above)
• Access to other stations through two E71 modules (2) in the figure above)
73
5.2 Network Components
This section describes the devices used for Ethernet.
5.2.1 Configuration devices used for 100BASE-TX/10BASE-T

connection
A QJ71E71-100 is used for 100BASE-TX and 10BASE-T connections. An E71 determines whether to use 10BASE-T
or 100BASE-TX and the full-duplex or half-duplex transmission mode according to the hub. For connection to the 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.
Connected device
E71
Hub
Configuration device Description

Straight cable A Category 5 or higher straight cable is usable.
System operation using connection with a cross cable is not
Shielded twisted pair
guaranteed. Note, however, that a Category 5 or 5e cross cable can be
cable (STP) Cross cable
used for data communications with an E71 (between QJ71E71-100
modules) or connection with a GOT.
Connector RJ45 connector -
Hub 100Mbps hub Up to two levels of cascade connection can be configured.*1
(a) Precautions for using a hub

The QJ71E71-100 does not support the flow control of the IEEE802.3x.
Therefore, for the connection using an IEEE802.3x-compatible hub, the data sent from the QJ71E71-100 may
be lost and the execution of the dedicated instruction may be timed out if the Ethernet line is heavily loaded.
If the phenomenon mentioned above occurs, reduce the load on the line taking mesures such as adding hubs.
74
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
describes 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. ( Page 279,
Section 15.13)
5
Remark
Consult a network specialist for required devices.
(2) 10BASE-T connection

To configure a system for 10BASE-T connection, use devices that meet the IEEE 802.3 10BASE-T standards.
Connected device
E71
5.2.1 Configuration devices used for 100BASE-TX/10BASE-T connection

Hub

Straight cable A Category 3 to 5e straight cable is usable.
Unshielded twisted
System operation using connection with a cross cable is not
pair cable (UTP) or
guaranteed. Note, however, that a Category 3 to 5e cross cable can be
shielded twisted pair Cross cable
used for data communications with an E71 (between QJ71E71-100
cable (STP)
modules) or connection with a GOT.
Connector RJ45 connector -
Hub 10Mbps hub Up to four levels of cascade connection can be configured.*1
Remark
75
5.2.2 Configuration devices used for 10BASE5 connection
A QJ71E71-B5 is used for 10BASE5 connection. Use devices that meet the IEEE 802.3 10BASE5 standards.
N-type terminating N-type terminating

resistor resistor
Coaxial cable
Transceiver
Connected device E71
DC power supply

10BASE5 coaxial cable
N-type terminating resistor The Ethernet standards need to be satisfied.
AUI cable (transceiver cable)
The Ethernet standards need to be satisfied. The SQE TEST (Signal Quality
Transceiver
Error TEST) or the heartbeat needs to be supported.
DC power supply (power supply for a
The specifications of the transceiver and the AUI cable need to be satisfied.
transceiver)
● The transceiver electrical characteristics are as follows. The power supply for the transceiver needs to be 13.28VDC to
15.75VDC.
• Input terminal voltage: 12VDC-6% to 15VDC+5%
• AUI cable direct resistance: 40/km or less, maximum length 50m (164ft.)
• Maximum current consumption: 500mA or less
The voltage drop (V) of the power supply for the transceiver is calculated as follows.
Voltage drop (V) = AUI cable direct current resistance (/m) × AUI cable length (m) × 2 (both directions) × transceiver
current consumption (A)
Ex. 2.0(VDC) = 0.04(/m) × 50(m) × 2 × 0.5(A)

In this case, the recommended power supply for the transceiver is more than 13.28VDC.
13.28(VDC) = 12VDC-6% × (11.28VDC) + 2.0(VDC)
● A communication error may occur due to high-frequency noise from devices other than a programmable controller in a
given installation environment. The following describes countermeasures to be taken on the E71 side to avoid high-
frequency noise influence.
• Install a ferrite core. ( Page 80, Section 6.2.2)
• Increase the number of retries of communications for TCP/IP communication.
Remark
76
A QJ71E71-B2 is used for 10BASE2 connection. Use devices that meet the IEEE 802.3 10BASE2 standards.
Terminating Terminating
resistor resistor
Coaxial cable
T-type
connector
Connected device E71

5
RG58A/U or RG58C/U (coaxial cable 50) -
Product equivalent to 221629-4 manufactured by Tyco Electronics
BNC-type terminating resistor
AMP K.K.
Product equivalent to UG-274/U(15) manufactured by Hirose
T-type connector
Electric Co., Ltd.
Remark

77
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 details on installation of the E71, refer to the following.
QCPU User's Manual (Hardware Design, Maintenance and Inspection)
(2) Handling precautions

The precautions for handling the E71 are described below.
• Do not drop or apply strong shock to the E71 case since it is made from resin.
• Tighten screws such as module fixing screws within the following range.
Screw Tightening torque range
*1 0.40N•m
External power supply terminal screw (M2.5)
*2 0.36 to 0.48N•m
Module fixing screw (M3)
*1 This terminal is an external power input terminal for supplying power to a transceiver when the E71 is connected to the
10BASE5 network.
*2 A module can be easily fixed onto the base unit using the hook at the top of the module. However, it is recommended to
secure the module with the module fixing screw if the module is subject to significant vibration.
78
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 65, CHAPTER 5)
6.2.1 Wiring with the QJ71E71-100
The following describes connection and disconnection of the Ethernet cable.
6.2.1 Wiring with the QJ71E71-100

6.2 Wiring
(1) Connecting the cable
1. Check the orientation of the connector and insert the Ethernet cable connector into the E71 until it
clicks into place.
(2) Disconnecting the cable

1. While holding down the Ethernet cable tab, pull out the cable.
79
6.2.2 Wiring with the QJ71E71-B5
The following describes connection and disconnection of the AUI cable and connection of the external power supply
terminal.
Retainer
A
B
AUI cable
External power supply terminal

(DC power supply for a transceiver)

1. Slide the retainer in the orientation A and insert the AUI cable connector all the way in.
2. Slide the retainer in the orientation B and make sure that the AUI cable is securely locked into
place.
3. Connect the external power supply terminal (DC power supply for a transceiver).
Strip the cable jacket by 13mm.*1 The applicable cable size is 0.13mm2 to 2.5mm2 (26 to 14 AWG).
13mm
4. Loosen the terminal screw and insert the cable into the terminal.
5. Tighten the terminal screw within the torque range listed in Section 6.1 (2).
*1 If the wire strip length is too long, the conductive part is exposed and it may increase the risk of electric shock or short-
circuit between the adjacent terminals. If the wire strip length is too short, it may result in poor contact.
80
To prevent the influence of high-frequency noise using ferrite cores, install them on the E71 side, connected device side, and
transceiver side on the AUI cable. (Ferrite core used for the tests conducted by Mitsubishi Electric Corporation: ZCAT 2032-
0930 from TDK Corporation)
QJ71E71-B5
AUI cable
10BASE5 coaxial cable

Ferrite core
Transceiver
6

1. Slide the retainer in the orientation A, hold the connector on the AUI cable, and pull out the cable.
2. Slide the retainer in the orientation B.

6.2 Wiring
81
The following describes connection and disconnection of the coaxial cable.
[2]
[1]

1. Align the groove [1] with the groove [2] and push the connector in.
2. While pushing the connector in, rotate it one-quarter clockwise until it securely locks into place.
3. Check that the connector is locked.

1. Rotate the connector one-quarter counterclockwise and pull out the connector.
82
Remark
● The following shows the composition of the BNC connector and coaxial cable.
• Parts comprising the BNC connector • Structure of the coaxial cable
External conductor
Outer sheath Insulator
Nut Washer Gasket
Internal conductor
Plug shell
Clamp Contact
● The following shows how to attach the BNC connector and the coaxial cable.
1. Cut off the outer sheath of the coaxial cable by the length shown in 6
10mm
the figure to left. Take care not to damage the external conductor.
Cut off this portion of the outer sheath.
Clamp
2. Fix the nut, washer, gasket, and clamp to the coaxial cable as
shown in the figure to left and unfasten the external conductor.
Nut
Washer
Gasket

6.2 Wiring
Insulator
Internal conductor
3. Cut the external conductor, insulator, and internal conductor by the
length shown in the figure to left. Cut off the external conductor to
5mm the same length as that of the tapered section of the clamp, and
7mm smooth it down to the clamp.
Clamp and external conductor
4. Solder the contact to the internal conductor. Note the following.

• Make sure that the soldered part does not swell.
Solder the contact.
• Make sure that there is no gap between the connector and the
cable insulator and they do not cut into each other.
• To prevent the insulator from deformation, solder the contact
quickly.
5. Insert the contact assembled in the step 4. into the plug shell
and screw the nut into the plug shell.
83
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
Parameter settings
Set parameters other than the basic setting and Ethernet Page 85, Section 7.1,
operation setting when required. Parameter setting of each
function
Starting the CPU module

QCPU User's Manual
Update the settings by powering off and on the CPU module (Hardware Design,
or resetting the CPU module. Maintenance and Inspection)
Initial process
The process is automatically performed with default settings
of the parameters.
Open process
Establish connections with connected devices. Page 99, Section 7.3
Data communications
using each function
Close process
Disconnect (cancel) connections with the connected devices Page 99, Section 7.3
where connections have been established by the open process.
84
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.
Configure settings to use the E71 as a network
Basic setting Network No. Page 86, Section 7.1.2
module.
Station No.
Mode
Configure the settings, such as an IP address, to
Operation Setting Page 87, Section 7.1.3
connect the E71 to Ethernet.
Initial Setting Set a data communication timer value. Page 356, Appendix 4.1 7
Page 89, Section 7.1.4,
Open Setting Configure connection settings. Parameter setting of each
function
Configure settings to communicate with connected
Router Relay Parameter
devices on Ethernet via a router and a gateway.
Configure settings (e.g. network number and
Station No. <-> IP Information station number) to communicate with other network
7.1.1 Parameter list

MELSEC-Q/L Ethernet
modules. Interface Module User's
Network Configure the settings of the file transfer (FTP) Manual (Application)
FTP Parameters
Parameter function.
Configure the settings of the e-mail function and the
E-mail Setting
automatic notification function.
Set the control number (SI) on the E71 side to
Interrupt Settings Page 152, Section 12.5.1
request an interrupt to the CPU module.
Configure settings to use the E71 on the main base
Redundant settings Page 223, Section 14.7.3
unit in a redundant system.
MELSEC-Q/L Ethernet
Set the communication path to communicate with a
Routing Parameters Interface Module User's
station having a different network number.
Manual (Application)
When two communication paths are configured
between the connected device and the E71 on the QnPRHCPU User's
Group Settings main base unit in a redundant system, configure Manual (Redundant
settings to disable system switching even if an error System)
occurs in either communication path.
Select a relay module when an access request with
Valid Module During Other Station
no network number specified is issued from -
Access
another station.
The connected device side protocol can be easily
Predefined Protocol Support Function selected, or created/edited from the Predefined Page 114, CHAPTER 11
Protocol Library of GX Works2.
Select the connection protected by a remote
Remote Password Page 203, Section 14.4
password.
85
7.1.2 Basic setting
Set items, such as a network number and station number.
Project window [Parameter] [Network Parameter] [Ethernet/CC IE/MELSECNET] Select

"Ethernet" under "Network Type".
Item Description Setting range

Network Type Select "Ethernet". -
Within the number of I/O points of the
Start I/O No. Set the start I/O number of the E71 in units of 16 points.
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
• Offline
Mode Select the operation mode of the E71.
• Self-Loopback Test
• H/W Test
Remark
For settings to use the E71 in a redundant system, refer to the parameter settings for the redundant system function.
86
7.1.3 Ethernet Operation Setting
Configure the settings, such as an IP address, to connect the E71 to Ethernet.

"Ethernet" under "Network Type". "Operation Setting"
7
• Binary Code
Communication Data Code Select the communication data code for the connected device.
• ASCII Code
• Do not wait for OPEN
(Communications impossible at
7.1.3 Ethernet Operation Setting

STOP time)
Initial Timing Page 88, Section 7.1.3 (1)
• Always wait for OPEN
(Communication possible at
STOP time)
• DEC
Input Format Select the IP address input format.
• HEX
Set the IP address of the own station. Make sure that the E71 on the
IP Address
own station and the connected device to be communicated with have
Setting
IP Address the same class and subnet address. Consult with the network 0H to FFFFFFFFH
administrator for the IP address setting.
Page 88, Section 7.1.3 (2)
Select the frame of the Ethernet header for the data link layer to be • Ethernet(V2.0)
Send Frame Setting
sent by the E71. • IEEE802.3
Select whether to enable connected devices to write data in MC • Selected: Enable
Enable Online Change
protocol communications while the CPU module is in RUN. • Not selected: Disable
TCP Existence Confirmation • Use the KeepAlive
Select an alive check method in TCP/IP communications.
Setting*1 • Use the Ping
*1 Do not use a programming tool that supports this setting together with one not supporting the setting. (Doing so may
change the setting to "Use the Ping".) This setting is ignored if the E71 does not support the alive check function using
KeepAlive. (The PING command is used for alive check.)
Remark
For settings to use the E71 in a redundant system, refer to the parameter settings for the redundant system function.
87
(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 89, 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
88
7.1.4 Open Setting
Configure settings to open connections for data communications with connected devices.

"Ethernet" under "Network Type". "Open Setting"

IP Address/Port No. Input • DEC
Select the input format for the IP address and port number.
Format • HEX
Select the communication protocol for the connected device. • TCP
7.1.4 Open Setting

Protocol
( Page 91, Section 7.2, Page 99, Section 7.3) • UDP
• Active
• Unpassive
Set this item when "TCP" is selected under "Protocol".
Open System • Fullpassive
( Page 92, Section 7.2.2, Page 93, Section 7.2.3, Page 95, Section 7.2.4)
• MELSOFT
Connection
For communications using a fixed buffer, select whether to use the buffer for
sending or for receiving in a connection to the connected device. When not • Send
Fixed Buffer
performing communications using a fixed buffer, select "Send". ( Page 141, • Receive
CHAPTER 12)
• Procedure Exist
Select a communication method for communications using a fixed buffer.
Fixed Buffer Communication • No Procedure
• Predefined protocol
Configure the pairing open setting for communications using a fixed buffer. • Disable
Pairing Open
( Page 160, Section 12.7) • Enable
• No Confirm
Existence Confirmation Select whether to use the alive check function. ( Page 236, Section 14.8)
• Confirm
401H to 1387H,
Host Station Port No. Set the E71 connection port numbers.
138BH to FFFEH*1
Destination IP Address Set the IP address of the connected device. 0H to FFFFFFFFH
Destination Port No. Set port numbers for connections of connected devices. 1H to FFFFH*2
*1 1388H to 138AH cannot be specified. ( Page 352, Appendix 2)

*2 The range of 1H to 400H is available only for the QJ71E71-100 with the serial number (first five digits) of "15042" or later.
89
● 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
E71 When connecting multiple connected devices, set multiple

own station port numbers.
Connected device
Connected device When connecting multiple connected devices, set a single

own station port number. (However, connections need to be
E71
opened by the number of connections.) ×
Connected device This setting cannot be configured when the own station is
Unpassive.
E71 Connected device When connecting multiple ports on a connected device, set
multiple port numbers of the E71.
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
Unpassive.
When connecting the same port on a connected device, set

E71 Connected device
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.
90
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
7
Open request
Response
E71 Connected device
Passive open Connection Active open
(passive) (active)
7.2.1 Establishing a connection

91
7.2.2 Communication process
This section describes the process from establishing a connection to terminating communications.
Server Client
E71
After the server performs Connected device
Passive open, it will wait
for an open request from
the client. Passive open When the client sends
an Active open request
Open request
Active open and the server accepts it,
a connection is established
between the client and the
Response server.
Connection established Connection established
Data sending The client requests data

Data sending
sending and sends data.
Response The client receives the response

Receive process
to the data.
Data sending
Data sending The client receives data and sends
back the response to the data.
Response
Receive process
Close request
Close process
Response
Close request
Close request The packet to stop communications is
exchanged then the connection is
disconnected.
Response
Closed Closed
After the connected device sends a close request to the E71, wait for 500ms or more before performing an open process
again.
92
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 238, CHAPTER 15)
Ex. Open/close processes for the connection number 1
Parameter communications
Power-on completed
Open status 1
Open enable status

(closed)
Closed status
Initial normal completion

signal X19
2
OPEN instruction
1 scan 7
OPEN instruction
completion device
OPEN instruction Abnormally ended
completion device + 1
Open abnormal detection Abnormally ended
signal X18
5
7.2.3 Active open procedure

CLOSE instruction
1 scan
CLOSE instruction
completion device
Abnormally
CLOSE instruction ended

(address: 5000H)
Open request signal

(address: 5002H)
SYN ACK FIN ACK
3 6 7
SYN + ACK FIN + ACK
93
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
*1 If the E71 sends an SYN and the connected device returns a RST, Open abnormal completion (X18) turns on
immediately and the open process terminates. (Open abnormal end)
*2 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)
94
7.2.4 Passive open procedure
The E71 has the following two connection methods for Passive open.
• Unpassive: 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.
• Fullpassive: 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" 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
communications
Power-on completed 1
Open status
Open enable status (closed)

*1
7
(Active open acceptance enabled)
Closed status

signal X19
4

(address: 5000H)
Open request signal
(address: 5002H) SYN + ACK FIN + ACK
2 3
SYN ACK FIN ACK
95
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.
2 The E71 starts the open process upon receiving the open request (SYN) from the connected device. When the
open 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 acceptance enable status.
*1 An open request (SYN) received after the normal completion of an initial process and before the E71 is in the open
acceptance enable 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.
96
(2) When "Do not wait for OPEN" 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 238, CHAPTER 15)
Parameter
communications
Power-on completed
Open status 1
Open enable status (closed) *1

(Active open acceptance enabled)
Closed status

signal X19
2
OPEN instruction
1 scan
7
OPEN instruction
completion device
Abnormally
OPEN instruction ended
Open abnormal detection Abnormally ended
signal X18

5
CLOSE instruction
1 scan
CLOSE instruction
completion device Abnormally
ended
CLOSE instruction
(address: 5000H)
Open request signal
(address: 5002H) SYN + ACK FIN + ACK
3 4
SYN ACK FIN ACK
97
3 The E71 starts the open process upon receiving the open request (SYN) from the connected device. When
the open 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 An open request (SYN) received after the normal completion of an initial process and before the E71 is in the open
acceptance enable status will cause an error, and the E71 sends a connection forced close (RST).
● 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.
98
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.
Unlike TCP/IP communications, UDP/IP communications do not require connections to be established with connected
devices.
Server Client
E71
Connected device
7
The client opens
Open Open
the port.
Data sending The client specifies

Data sending request
the destination and
sends data to it.

The server requests
data reception and Receive process (reading)
reads the received data.
Data sending
Data sending request
Receive process (reading)
Close Close The client performs

the close process.
After the connected device sends a close request to the E71, wait for 500ms or more before performing an open process
again.
99
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" is selected for the Ethernet operation setting
After the E71-mounted station has been 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, even if "Always wait for OPEN"
has been selected for the Ethernet operation setting, all open/close processes after the connection to the connected device
is established must be performed in a program.
100
(2) When "Do not wait for OPEN" 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 238, CHAPTER 15)
Parameter
communications
Power-on completed
Open status 1
Open enable status (closed)
Closed status
7
signal X19
2
OPEN instruction
1 scan
OPEN instruction
completion device
OPEN instruction Abnormally ended

5
7.3.2 Open procedure

CLOSE instruction
1 scan
CLOSE instruction
completion device
Abnormally
CLOSE instruction ended

(address: 5000H) 3 4 6 7
Internal process Internal process
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.
101
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.
102
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 (GX Works2) over Ethernet
1. Write the parameter settings ( Page 89, Section

7.1.4) in the CPU module.
In the following cases, the open setting is not required.
• Only one product is connected in the TCP/IP
communications.
One product can be connected without the open
setting using the dedicated system connection.
• The network is running in the UDP/IP communications.
Multiple products can be connected without the
open setting using the dedicated system
connection.
To connect multiple products in the TCP/IP
communications, set the connection for the second
product or more in the open setting.
2. Set the connection target in the programming tool.
8
Connection destination window [Connection1]
3. Select "Ethernet Board" under "PC side I/F" and

double-click the item. The window shown to left
appears. Set the network number according to the
network parameter of the E71. Assign a unique
station number.
103
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.)
104
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.
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.
(3) Remote control of a CPU module
9.1 Applications
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.
105
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
Application data
Header
Subheader Text (command)
Ethernet
Response message
Application data
Header
Subheader Text (command)
The frames that can be used with an E71 are as follows.

• 4E frame
• QnA-compatible 3E frame
• A-compatible 1E frame
Remark
When the connected device is a personal computer, using a separately sold communication support tool (MX Component)
allows a communication program for the connected device to be created without considering the MC protocol message
format or sending/receiving procedures. ( Page 393, Appendix 9)
106
CHAPTER 9 MC PROTOCOL COMMUNICATIONS
9.3 Data Communication Procedure 9

The following is a data communication procedure for MC protocol communications.
1. Set the parameters. ( Page 108, Section 9.4)

2. Perform the open process and establish a connection between the E71 and the connected device.
( Page 91, Section 7.2, Page 99, Section 7.3)
3. Once the connection is established, the connected device sends an MC protocol message.
4. 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 204, 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
107
9.4 Parameter Setting
Set the following parameters for MC protocol communications.

• Basic setting ( Page 86, Section 7.1.2)
• Ethernet operation setting ( Page 87, Section 7.1.3)
• Open setting ( Page 89, Section 7.1.4)

Select the communication method for communications using a fixed buffer. For
Fixed Buffer Communication Procedure Exist
MC protocol communications, select "Procedure Exist".
108
CHAPTER 10 SLMP COMMUNICATIONS

SLMP is a protocol that enables connected devices to access SLMP supporting devices over Ethernet.
10
SLMP communications are available among devices that can receive/send messages in the SLMP control procedure.
This function is available only in the QJ71E71-100 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 mounted and intelligent function
module buffer memory. This allows a connected device to monitor the operation of the CPU module where an
E71 is mounted, 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 mounted.
(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.
109
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
Server Connected device
E71
Request message
Access
Header Subheader Command
destination
Ethernet
Response message
Header Subheader Response data
The following is a data communication procedure for SLMP communications.
1. Set the parameters. ( Page 111, Section 10.4)

2. Perform the open process and establish a connection between the E71 and the connected device.
( Page 91, Section 7.2, Page 99, Section 7.3)
3. Once the connection is established, the connected device sends an SLMP message.
4. 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 204, Section
14.4.2)
• When the connection for data communications with the connected device is to be subjected to the remote
password check
110
Set the following parameters for SLMP communications.

• Basic setting ( Page 86, Section 7.1.2) 10

Select the communication method for communications using a fixed buffer. For
Fixed Buffer Communication Procedure Exist
SLMP communications, select "Procedure Exist".
111
10.5 Available command list
The following table lists the commands that can be executed from a connected device to the E71.
The  part in the Subcommand column varies depending on the specified device.
For details on each command, refer to the following.
Item
Command Subcommand Description
Type Operation
Reads values in 1-point units from bit devices (consecutive device
001
numbers).
Read 0401 • Reads values in 16-point units from bit devices (consecutive device
numbers).
000
• Reads values in 1-word units from word devices (consecutive device
numbers).
001 Writes values to bit devices (consecutive device numbers) in 1-point units.
• Writes values to bit devices (consecutive device numbers) in 16-point
Write 1401 units.
000
• Writes values to word devices (consecutive device numbers) in 1-word
units.
Specifies a device number to read the device value. Discrete device
numbers can be used.
Read Random 0403 000
• Reads bit devices in 16- or 32-point units.
Device • Reads word devices in 1- or 2-word units.
Specifies a device number in 1-point units to write a value to a bit device.
001
Discrete device numbers can be used.
Write Random 1402 • Specifies a device number in 16-point units to write a value to a bit
device. Discrete device numbers can be used.
000
• 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).
Reads the value of the device registered by Entry Monitor Device
Execute Monitor 0802 0000
(command: 0801).
Specifies n points (1 point: 16 bits) of word or bit devices as one block, and
Read Block 0406 000
reads multiple blocks of data. Discrete device numbers can be used.
Specifies n points (1 point: 16 bits) of word or bit devices as one block, and
Write Block 1406 000
writes multiple blocks of data. Discrete device numbers can be used.
Read 0613 0000 Reads buffer memory data of the E71.
Memory
Write 1613 0000 Writes data to the buffer memory of the E71.
Read 0601 0000 Reads buffer memory data of the intelligent function module.
Extend Unit
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 mounted.
Remote Stop 1002 0000 Executes remote STOP to the CPU module where an E71 is mounted.
Remote Pause 1003 0000 Executes remote PAUSE to the CPU module where an E71 is mounted.
Remote
Control Remote Latch Clear 1005 0000 Executes remote latch clear to the CPU module where an E71 is mounted.
Remote Reset 1006 0000 Executes remote RESET to the CPU module where an E71 is mounted.
Reads the model name and code of the CPU module where an E71 is
Read Type Name 0101 0000
mounted.
Specifies the remote password to disable the communication with other
Lock 1631 0000
Remote devices. (The locked state is activated from the unlocked state.)
Password Specifies the remote password to enable communication with other
Unlock 1630 0000
devices. (The unlocked state is activated from the locked state.)
112
Item
Command Subcommand Description
Type Operation
Read Directory/File 1810 0000 Reads file list information from the CPU module where an E71 is mounted.
Reads the file number of the specified file from the CPU module where an
Search Directory/File 1811 0000
E71 is mounted.
Reserves storage area for the specified file of the CPU module where an
10
New File 1820 0000
E71 is mounted.
Delete File 1822 0000 Deletes a file in the CPU module where an E71 is mounted.
Copy File 1824 0000 Copies the specified file in the CPU module where an E71 is mounted.
Changes the attributes of the file in the CPU module where an E71 is
File Change File State 1825 0000
mounted.
Changes the creation date of the file in the CPU module where an E71 is
Change File Date 1826 0000
mounted.
Locks a file so that the data of the file is not changed by other devices in
Open File 1827 0000
the CPU module where an E71 is mounted.
Read File 1828 0000 Reads the data of a file from the CPU module where an E71 is mounted.
Write File 1829 0000 Writes the data to a file in the CPU module where an E71 is mounted.
Close File 182A 0000 Cancels the file lock by the open process.
Tests whether the communication with the E71 is normally performed or

Self Test 0619 0000
not.
Clear Error 1617 0000 Turns off the COM.ERR. LED on the E71.
10.5 Available command list
113
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.
1) Setting protocols 2) Writing protocols

Protocols can be set easily using the predefined Write the set protocols in the flash ROM of the E71.
protocol support function of GX Works2.
GX Works2
Sending
Connected device E71 Connected device

Receiving
3) Executing protocols
Data can be communicated
Execute protocols by dedicated instructions.
with protocols appropriate to
Multiple protocols can be executed by one dedicated each connected device.
instruction.
For the protocol setting method, refer to the following.

GX Works2 Version 1 Operating Manual (Intelligent Function Module)
114
CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL
● 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. 11
For details, refer to the following.
● From Connection No.1 to 16 are available.
● The Communication Data Code becomes Binary Code regardless of the setting.
115
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]

[Ethernet Module...]
2. Create a new file.
[File] [New...] "Add"
3. Select "Predefined Protocol Library" or "Add New"

in the "Add Protocol" window.
When "Predefined Protocol Library" is selected,
select the protocol from Predefined Protocol Library
registered 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.
116
4. Set the items required for the data communications.

• Set communication parameters in the "Protocol Detailed
Setting" window.
"Protocol Detailed Setting" window Select a

protocol [Edit] [Protocol Detailed Setting...]
11
• Set the configuration of packets to be sent and received in

the "Packet Setting" window.
"Protocol Detailed Setting" window [Variable

Unset] or [Element Unset]

↓
117
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
*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).)
● When writing the data to the Redundant CPU, pay attention to the followings:
• To write the data, connect directly to the CPU module or connect via an intelligent function module on a main base
unit; connection via an intelligent function module on an extension base is not available.
• Select "Not specified" for Target System in the Transfer Setup of GX Works2. When the Target System is
specified, an error occurs in the CPU module.
• A system switching during data writing may cause the data not to be written to the flash ROM.
Change the operation mode of the Redundant CPU to separate mode before writing to prevent such situation from
occurring.
If a system switching has occurred during data writing, write the data to the flash ROM again.
● 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.
Execute the protocol written to the flash ROM by using
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.
118
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
389, Appendix 8.3.
(a) TCP/IP
11
Maximum data length: 1514 bytes

Header
Destination Sender's MAC

Type: IP: TCP:
MAC address: address: Data
2 bytes 20 bytes 20 bytes
6 bytes 6 bytes
Ethernet header TCP/IP header

40 to 1500 bytes
(b) UDP/IP
Maximum data length: 1514 bytes

Header
Destination Sender's
Type: IP: UDP:
MAC address: MAC address: Data
2 bytes 20 bytes 8 bytes
6 bytes 6 bytes
Ethernet header UDP/IP header
11.2 Communication Type of Protocols

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 382,
Appendix 8.1.
Communication type name Description

Send Only Sends a send packet once.
Receive Only Receives a packet if it matches any of up to 16 defined receive packets.
Sends a send packet, then receives a packet if it matches any of up to 16
Send&Receive
defined receive packets.
119
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 389, Appendix 8.3.
(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 Description Remark

Element Name Set name of the element. -
Select a data type of the setting value.
Code Type -
ASCII String/ASCII Control Code/HEX
Set data within 1 to 50 bytes.
Code type and setting range are as follows: Setting example
• ASCII String: 20H to 7FH ASCII String: "ABC"
Setting Value
ASCII Control Code: STX
• ASCII Control Code: Control code of 00H to 1FH and 7FH
HEX: FFFF
• HEX: Hexadecimal data of 00H to FFH
120
(2) Length
11
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.

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.
When sending: The calculated Length is sent from the
Forward Direction
upper byte.

(Upper ByteLower Byte)
When receiving: The data is received from the upper byte.
When sending: The calculated Length is sent from the
Reverse Direction
lower byte. Not settable when Data
Data Flow (Lower ByteUpper Byte)
When receiving: The data is received from the lower byte. Length is 1 byte
When sending: The calculated Length is sent swapping
the upper byte and lower byte by word.
Byte Swap (by Word)*1
When receiving: The data is received swapping the upper
byte and lower byte by word.
Select the start element number of the calculating range.
Start
Calculating The range is 1 to 32.
-
Range Select the end element number of the calculating range.
End
*1 Available only when the Data Length is 4 bytes.
121
● 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 Non-
conversion Variable or Non-verified Reception.
● 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.
122
(3) Non-conversion Variable
11
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.
Item Description
Element Name Set name of the element.
Fixed Length Sends and receives the data whose length is fixed.
When sending: The data length at the time of the protocol execution is
Fixed Length/Variable Length
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.)
When sending: Each one word (2 bytes) data in the data storage area is sent in
the order of the lower byte to the upper byte.
Lower Byte + 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.
The E71 ignores data in the upper byte.
Lower Bytes Only 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.
123
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)
Latch relay (L)
Data Storage Area Link relay (B)
Specification 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: Do not set local devices.
*2: 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.)
• When "Lower Bytes Only" is selected, twice the size of the data length is occupied.
(Word) Specified device
+0
Send Data storage area

packet
Send packet: The user stores the send data.

Data storage area Receive packet: The E71 stores the receive data.
Receive Data storage area

packet
+n
124
(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.)
11
• When "Lower Bytes Only" is selected, twice size of the data length + one word (length for the data length
storage area) are occupied.
+0 Data length storage area*

+1
Send Data storage area

packet
Send packet: The user stores the send data.

Data storage area
Receive packet: The E71 stores the receive data.
Receive Data storage area

packet
+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 Non-
conversion 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.
125
(4) Non-verified Reception
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.

0 (Variable number of Set this item when the number of characters not to
characters) be verified varies in each communication.
Data Length -
1 to 2046 (Specified number Set the number of characters not to be
of characters) verified.
● Multiple Non-verified Reception elements can be placed in a packet.

● 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.
126
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).
11
(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
11.4 Execution Condition of Predefined Protocol Communication

Checking the
E71
protocol setting data
X1D turns on when the

check result is normal.

(X1D)
Protocol setting data

The number of registered protocols and information
check area about whether protocols have been registered are stored.
(address: 5320H to 533FH)
127
(b) If an error has occurred in the protocol setting data
Power on/reset
Check result error
Checking the
E71
protocol setting data
X1D stays off.

(X1D)

check area 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).
(a) If the protocol setting data is set correctly
Start to write
the protocol setting data.
Check result normal
E71 Writing the protocol Checking the protocol

setting data setting data

protocol setting data has been X1D turns on when the
X1D turns off.
set correctly before data write. check result is normal.

(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 The number of registered protocols and
check area information about whether protocols have
(address: 5320H to 533FH) been registered are stored.
128
(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 Checking the protocol

setting data setting data

11
protocol setting data has X1D turns off.
been set correctly before
data write.
X1D stays off.

(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.
check area 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
11.4 Execution Condition of Predefined Protocol Communication

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.
129
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
(1) System configuration
QCPU-1 QCPU-2
GX Works2
(192.0.1.100) (192.0.1.101)
Ethernet
130
11.5.2 Parameter Setting
(1) Sending side (QCPU-1 side)

The following is an example of the parameter settings of the sending side (QCPU-1 side).
(a) Basic setting

The following is an example of the basic setting. 11
(b) Ethernet operation setting

The following is an example of the Ethernet operation setting.
131
(c) Open setting
The following is an example of the open setting.
132
(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]
11
[Packet Setting]
• Send Packet (Request)

133
• Receive Packet (Normal response)
• Receive Packet (Error response)
134
(2) Receiving side (QCPU-2 side)

The following is an example of the parameter settings of the receiving side (QCPU-2 side).
(a) Basic setting

The following is an example of the basic setting.
11

135
(c) Open setting
136
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

11
(a) Sending side (QCPU-1 side)
<<Open process program>>

137
<<Program for predefined protocol communications>>
138
11

139
<<Close process program>>
140
CHAPTER 12 COMMUNICATIONS USING A FIXED BUFFER
CHAPTER 12 COMMUNICATIONS USING A FIXED

BUFFER
This chapter describes communications using a fixed buffer.
12.1 Applications
12
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.
12.1.1 Differences between the "Procedure Exist" and "No Procedure" control methods
12.1 Applications
Difference
Item
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.
connected device.
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
Data code
binary code or ASCII code. code.
Data length specified using a
Specified by the number of words. Specified by the number of bytes.
dedicated instruction
Amount of application data per
Maximum of 1017 words Maximum of 2046 bytes
communication
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.
141
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
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 No.1
No.2
No.3
BUFRCV instruction No.4
CPU module
Connected device
No.16
(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 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

Connected device 1
Connected device 8
Connected device 28
142
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.
● 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 12
• 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 and 5038H to 506FH) corresponding to the fixed buffer number n.*1
(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 In case of 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.
143
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
Initial normal completion 1

signal X19
Open completion signal 2

(address: 5000H [b0])
BUFSND instruction 3
completion device 1 scan
BUFSND instruction
Sending data
Response
ACK ACK
(TCP only) (TCP only)
4 5
1 Confirm the normal completion of the initial process. (Initial normal completion signal (X19): ON)
2 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 When the connected device receives the data from the E71, the connected device sends a response to the E71.
6 When the E71 receives the response from the connected device, the E71 stops sending data. If a response is 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. ( Page 356, Appendix
4.1)
● 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.
144
(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
signal X19
12
2
completion device
1 scan
BUFSND instruction
Sending data
ACK
(TCP only)
12.3 Data Sending Procedure

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.
145
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)
A receive process in the main program is performed using the BUFRCV instruction.

The following is the data receive process performed in the fixed buffer number 1 area for the connection number
1.
Initial process Open process Receiving data Sending a response

signal X19

BUFRCV instruction 4
completion device 1 scan
BUFRCV instruction

(Address: 5005H [b0])
Response
Receiving data
ACK ACK
3 5
3 Receive data from the destination.
• Fixed buffer reception status signal (address: 5005H (b0)): ON
4 Execute the BUFRCV instruction to read the receive data length and receive data from the fixed buffer number 1.
• Fixed buffer reception status signal (address: 5005H (b0)): OFF
5 When the receive data length and the receive data are completely read out, a response is sent to the destination.
6 End the receive process. If the data receive process is abnormally ended, execute the BUFRCV instruction again
to repeat the receive process.
146
● 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.
(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
12
1
signal X19
2
completion device
1 scan
BUFRCV instruction
12.4.1 Data receiving using the main program (BUFRCV instruction)

(Address: 5005H [b0])
Receiving data
ACK
(TCP only)
147
3 Receive data from the connected device.
4 Execute the BUFRCV instruction to read the receive data length and receive data from the fixed buffer 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.
● 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.
148
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 152, Section 12.5.1)
• Interrupt pointer setting
• Interrupt settings
(1) Procedure exists 12

Initial Open
process process Receiving data Sending a response

signal X19

BUFRCVS instruction 4
In interrupt process 6
12.4.2 Data receiving using an interrupt program (BUFRCVS instruction)

Receiving data
Response
ACK ACK
3 5
Cycle Cycle
Program END Interrupt process END

Scan process Scan Scan process
• 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 2.
5 When the receive data length and the receive data are completely read out, a response is sent to the
destination.*1
6 End the interrupt program to restart the main program.
*1 If the data receive process is abnormally ended, the E71 does not return a response.
149
(2) No procedure
Initial Open
process process Receiving data

signal X19

BUFRCVS instruction 4
In interrupt process 5
Receiving data
ACK
(TCP only)
Cycle Cycle
Program END Interrupt process END

Scan process Scan Scan process
• 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.
150
Set the following parameters to perform communications using a fixed buffer.

12
12.4.2 Data receiving using an interrupt program (BUFRCVS instruction)

Select whether to use the fixed buffer for connection with the connected • Send
Fixed Buffer
device for sending or receiving. • Receive
• Procedure Exist
Fixed Buffer Communication Select the communication method for communications using a fixed buffer.
• No Procedure
Select whether to disable or enable the pairing open for communications using • Disable
Pairing Open
a fixed buffer. ( Page 160, Section 12.7) • Enable
Select whether or not to use the alive check function. ( Page 236,
Section 14.8) • No Confirm
Existence Confirmation
Select "No Confirm" to send data by broadcast communications during "No • Confirm
Procedure" communications using a fixed buffer.
151
12.5.1 Parameter setting when using an interrupt program
Configure the parameter setting on a programming tool to start up an interrupt program.
E71 CPU module
Control <Program>
Connection No.1
number Interrupt
Connection No.2 interrupt pointer Ixx
(SI) No. (Ixx) Z.BUFRCVS
Setting Setting
of (2) 0 of (1) 50
to
to
15 255
Connection No.16
(1) Interrupt pointer setting

The following is a setting example.
Project window [Parameter] [PLC Parameter] [PLC System] button

Set the start number of the interrupt pointer used in a
Interrupt Pointer Start No. 50 to 255
PLC Side program.
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 Among maximum 16 interrupt (SI) numbers (control numbers
Side 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.
152
(2) Interrupt settings

The following is a setting example.
Project window [Parameter] [Network Parameter] [Ethernet/CC

IE/MELSECNET] [Interrupt Settings]
12

Input Format The input format of each data is decimal number only. -
Device Code Select a device code. Select "Fixed Buffer" in this setting. Fixed Buffer
12.5.1 Parameter setting when using an interrupt program

Set the connection number of the fixed buffer to trigger the
Channel No./Connection No. 1 to 16
interrupt program.
Set the interrupt control number for the E71 for when an interrupt
Interrupt (SI) No. 0 to 15
request is issued from the E71 to the CPU module.*1
*1 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.
153
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.
(1) Detailed header sizes
(a) TCP/IP
Ethernet IP TCP
(14 bytes) (20 bytes) (20 bytes)
(b) UDP/IP
Ethernet IP UDP
12.6.2 Application data
This section describes the application data configuration.

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/MELSECNET] "Operation Setting"
154
(a) Format
• Communications using a binary code
Application data area

(command message)
Maximum of
2 bytes 2 bytes 1017 words
Communication Subheader Data length Text

request source setting (command)
L H L H
12
Communication Subheader End code
request destination
1 byte 1 byte

(Response)
• Communications using an ASCII code

(command message)
Maximum of
4 bytes 4 bytes 1016 words
Communication Subheader Data length Text

request source setting (command)
H - - L H - - L

12.6 Data Format
Communication Subheader End code
request destination
H L H L
2 bytes 2 bytes

(Response)
155
(b) Subheader
Because an E71 automatically adds and deletes a header, the user setting is not required.
Command Response
b7 to b0 b7 to b0
0 1 1 0 0 0 0 0 1 1 1 0 0 0 0 0
Communications using 60H 00H E0H

a binary code
Subheader Subheader
b7 to b0 b7 to b0
0 1 1 0 0 0 0 0 1 1 1 0 0 0 0 0
"6" 6H "0" 0H "E" EH "0" 0H
Communications using 36H 30H 30H 30H 45H 30H

an ASCII code
Subheader 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
156
(d) Text (command)

The following is the format of a command/response.
Command format
Maximum of 1017 words
60H 00H (L) (H) (L) (H) (L) (H) (L) (H) (L) (H)
Subheader
Data specifying/
storing device for sending/
receiving instructions 12
Data length
n setting
n+1 (H) (L)
n+2 (H) (L)

Send/
n+3 (H) (L)
receive data
n + setting data length (H) (L)
1 word (2 bytes)

Command format

12.6 Data Format
36H30H30H30H (H) to (L) (H) to (L) (H) to (L) (H) to (L)
Subheader
Data specifying/
storing device for sending/
ASCII-binary conversion
receiving instructions
n Data length
setting
n+1 (H) (L)
n+2 (H) (L)

Send/
receive data
n + setting data length (H) (L)

1 word (2 bytes)
157
(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.
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
Correct the subheader specified in the application data.
device to the E71 is incorrect.
158
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.
12
Data sent from the connected device Data processed by the E71
(1st data) (2nd data)
Subheader 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 storage
area.)

12.6 Data Format
(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.
159
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
process for one port. MC protocol communications and communications using a random access buffer can be also
performed using paring-opened connections.
(TCP/IP or UDP/IP communications)

E71
Send data
Connection No.1 Fixed buffer (to receive data) Port Connected device
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).
160
12.7.2 Parameter setting
The following is the pairing open setting.
12

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.

12.7 Pairing Open
When "Yes" 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 (dedicated for receiving) and the fixed buffer of the
next connection (dedicated 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.)
161
12.8 Broadcast Communications
Broadcast communications mean that the same data is sent to all E71-mounted 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
● 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
over the Ethernet network.
(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.
162
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 NO

own station E71 the same as that of the
receive data request destination?
12
YES Is the network
address (subnet address)
in the IP address of the own station
E71 the same as the network address (subnet NO
address) of the received data?
Are all the bits of the host address
of the received data 1?
YES
Is Destination
IP address FFFFFFFFH? NO*1
(Simultaneous Broadcast)
Is Destination NO
YES IP address the same as that of the receive
(Simultaneous Broadcast) data request source?
12.8.1 Sending/receiving procedures

YES
NO
Is Destination Port No. FFFFH?
Is Destination NO
YES Port No. the same as that of the receive
(Simultaneous Broadcast) data request source?
YES
The application data of the received data is stored

in the fixed buffer.
Fixed buffer reception status signal (address: The received data is ignored (discarded)
5005H) turns on.) because it has not been sent to the own station.
*1 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".
163
The following is the parameter setting for broadcast communications.
(1) When sending data

The following is the parameter setting for data sending.

Protocol Select "UDP/IP". -
Fixed Buffer Select "Send". -
Fixed Buffer Communication Select "No Procedure". -
Existence Confirmation Select "No Confirm". -
Destination IP Address Set FFFFFFFFH. -
164
(2) When receiving data

The following is the parameter setting for data receiving.
12

Protocol Select "UDP/IP". -
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. -
165
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
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.
166
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. 12

QCPU-1 QCPU-2
(10.97.85.222) (10.97.85.223)
Ethernet
This section describes a parameter setting example.
12.9.1 System configuration

(1) Sending side (QCPU-1 side)
The following is an example of the parameter settings of the sending side (QCPU-1 side).
(a) Basic setting

167
(c) Open setting

168
(2) Receiving side (QCPU-2 side)

The following is an example of the parameter settings of the receiving side (QCPU-2 side).
(a) Basic setting

12


169
(c) Open setting
170
12.9.3 Program
(1) Sample program procedures

This section describes the procedures for a sample program.
(a) Sending side (QCPU-1 side)

The following describes how communications are processed on the sending side (QCPU-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 confirm that the initial process is completed. 12
2. Perform the open process (Active open) of the connection number 1.
3. 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 (QCPU-2 side)

The following describes how communications are processed on the receiving side (QCPU-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 confirm 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. Perform communications using a fixed buffer from the CPU module using the BUFRCV
instruction.
3.
12.9.3 Program
Data received in the corresponding fixed buffer data area in the E71 is read to the CPU
module.
171
(2) Sample program
(a) Program on the sending side (QCPU-1 side)

The following is a program on the sending side (QCPU-1 side).
<<Open process program>>
172
<<Fixed buffer No.1 send program>>
12
Process upon completion
12.9.3 Program
Process upon abnormal end
173
<<Close processing program>>
174
(b) Receiving side (QCPU-2 side)

The following is a program on the receiving side (QCPU-2 side).
<<Fixed buffer No.1 receive program>>

\
12
\
12.9.3 Program
● 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.
● 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.
175
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 Writing Writing Connected

device device
Reading Random Reading

access
Writing buffer Writing
Connected Connected
device Reading Reading device
Writing 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.)
176
CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER
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
13
CPU module Random
access Read request Connected
buffer device
Reading data
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.

(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
177
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.
2 Read request (command)

CPU module E71
ACK (TCP only)
Random access
1 Writing using buffer 3 Response/reading data
the TO instruction
ACK (TCP only) Connected device
1 Write data in the random access buffer of the E71 using the TO instruction.
2 Asynchronously with the process 1 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 Writing data (command)

CPU module E71
ACK (TCP only)
Random access
Reading using buffer
3 2 Response
the FROM instruction
Connected device
ACK (TCP only)
1 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 1 and 2 above, the data written in the random access buffer is read
using the FROM instruction.
178
CHAPTER 13
Set the following parameters to perform communications using a random access buffer.
13

Fixed Buffer Communication Select the communication method for communications using a fixed buffer.
Procedure Exist
Procedure Select "Procedure Exist" for communications using a random access buffer.
179
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 IP TCP
(b) UDP/IP
Ethernet IP UDP
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/MELSECNET] "Operation Setting"
180
CHAPTER 13
(1) Format

(command message data)
Maximum of
2 bytes 2 bytes 2 bytes 1017 words
Text
Communication Data length (command)
Subheader Start address
request setting (none at read
source H 00H L H L H request)
Text
Communication (response)
Subheader End code
request (none at write
13
destination request)
1 byte 1 byte Maximum of

1017 words

(response)

(command message)
Maximum of
4 bytes 4 bytes 4 bytes 1016 words
Text
Data length (command)
Communication Subheader Start address
setting (none at read
request source
request)

13.4 Data Format
H L 30H 30H H - - L H - - L
Text
Communication (response)
request destination Subheader End code
(none at write
H L H L request)
2 bytes 2 bytes Maximum of

1016 words
(response)
181
(2) Subheader
Because an E71 automatically adds and deletes a header, the user setting is not required.
b7 b6 b5 b4 b3 b2 b1 b0
1 1 0 0 0 0 1 00H
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) Response (from the E71 to the connected device)
b7 to b0 b7 to b0
0 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1
Communications using 61H 00H E1H

a binary code
Subheader Subheader
b7 to b0 b7 to b0
0 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1
"6" 6H "1" 1H "E" EH "1" 1H
Communications using 36H 31H 30H 30H 45H 31H

an ASCII code
Subheader Subheader
182
CHAPTER 13
(3) Start address

Use a logical address to set the start address of a random access buffer that reads/writes data. ( Page 189,
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.

Specify the number of words using a binary value. (Maximum of 1017 words)

13.4 Data Format
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
183
(5) Text
Text is a data written to and read from a random access buffer.

Data length (maximum of 1017 words)
(L) (H) (L) (H) (L) (H) (L) (H)
Random access
buffer
Specified n (H) (L)
address
n+1 (H) (L)
n+2 (H) (L)
n + set number of
(H) (L)
words to be read
1 word (2 bytes)

Data length 2 (maximum of 1016 words)
(H) to (L) (H) to (L) (H) to (L)
Random access
buffer
Specified
n (H) (L)
address
n+1 (H) (L)
n + set number of
words to be read (H) (L)
(Maximum of 508 words)
Ex.
(H) (L)
n 12H 34H
n+1 56H 78H
31H 32H 33H 34H 35H 36H 37H 38H
(H) to (L) (H) to (L)
184
CHAPTER 13
(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.
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
13
device

• Command format (from the connected device to the E71)
Subheader Start address Data length Text (10 words)

(L) (H) (L) (H) (L) (H) (L) (H) (L) (H) (L) (H)
62H 00H 00H 00H 0AH 00H 34H 12H 78H 56H BCH 9AH BCH 9AH
Random access buffer
Physical address (H) (L) Logical address

13.4 Data Format
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 End code

E2H 00H
185
Subheader Start address Data length

(H) - - (L) (H) - - (L)
36H 32H 30H 30H 00H 00H 00H 00H 00H 00H 00H 41H
Text (20 words)

(H) - - (L) (H) - - (L) (H) - - (L) (H) - - (L)
31H 32H 33H 34H 35H 36H 37H 38H 39H 41H 42H 43H 39H 41H 42H 43H

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)
Subheader End code
45H 32H 30H 30H
186
CHAPTER 13
(2) Reading data from a random access buffer upon a read request from a
connected device


(L) (H) (L) (H)
61H 00H 14H 00H 0AH 00H
Subheader End code Text (10 words)
(L) (H) (L) (H) (L) (H) (L) (H) 13

E1H 00H 34H 12H 78H 56H BCH 9AH BCH 9AH
2680H( 9856) 0H( 0)
2694H( 9876) 12H 34H 14H( 20)

13.4 Data Format
2695H( 9877) 56H 78H 15H( 21)
2696H( 9878) 9AH BCH 16H( 22)
269DH( 9885) 9AH BCH 1DH( 29)
(10 words)
3E7FH(15999) 17FFH(6143)
187

(H) - - (L) (H) - - (L)
36H 31H 30H 30H 00H 00H 31H 34H 00H 00H 00H 41H
Subheader End code

45H 31H 30H 30H
Text (20 words)

(H) - - (L) (H) - - (L) (H) - - (L) (H) - - (L)
31H 32H 33H 34H 35H 36H 37H 38H 39H 41H 42H 43H 39H 41H 42H 43H
2680H( 9856) 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) 17FFH(6143)
188
CHAPTER 13
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 189,
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
in commands.
13.5 Precautions when Creating Programs

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 item in the command
Physical address Buffer memory areas

680H( 1664)
Fixed buffer
267FH( 9855) Logical address

2680H( 9856) 0H( 0)
Random access
buffer
3E7FH(15999) 17FFH(6143)
189
13.7 Example of Communications Using a Random Access
Buffer
The following figure shows an example of a write operation from a connected device.
Connected
CPU module E71 device
Device memory
R20000 11710
Data received Data received
11719
R20009 11720 1 1
Receive process program Receive completion flag

\ \
1 The receive completion flag is provided at the end of the received data.
2 The receive completion flag is monitored.
3 When the receive completion flag turns on, the data is transmitted from the random access buffer to the CPU
module.
190
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
14
gateway. This function does not allow the E71 to operate as a router. One default router and up to eight routers can be
set.
14.1.2 Parameter settings
Configure the settings in the following window.
Project window [Parameter] [Network Parameter] [Ethernet/CC IE/MELSECNET]
14.1.1 Applications
Select "Ethernet" under "Network Type". "Operation Setting"
191
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
A value other than 00000000H and

Default Router IP Address Refer to (2) in this section.
FFFFFFFFH
Input Format Select the input format of router information. DEC/HEX

A value other than 00000000H and
Sub-net Address Refer to (3) (a) in this section.
Router FFFFFFFFH
Information A value other than 00000000H and
Router IP Address Refer to (3) (b) in this section.
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
81H 05H 2FH 01H

IP address
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
FFH FFH FCH 00H

Subnet mask
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 Host address
81H 05H 2FH 01H

IP address
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.)
192
(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
(a) Subnet address 14

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 2: The host address bits are all "0".
*1 If the class (network address) of the E71 on the own station differs from that of the connected device, set the network
*2 If the class (network address) of the E71 on the own station is the same as that of the connected device, set the subnet

Own station E71
Class B
IP address: 81052F01H (129.5.47.1)
Subnet mask: FFFFFC00H (255.255.252.0)
Ethernet 4
Router 1 Router 2 Router 3
Ethernet 1 Ethernet 2 Ethernet 3
Setting example 1 Setting example 2 Setting example 3

Connected device 1 Connected device 2 Connected device 3
Class B Class A Class B
IP address: 81044001H IP address: 71044001H IP address: 81052902H
(129.4.64.1) (113.4.64.1) (129.5.41.2)
193
Ex. When the network addresses differ between the E71 on the own station and the connected device
Network address
Own station E71 81H 05H 2FH 01H

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
Connected device 1 81H 04H 40H 01H

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


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
Set the network address of

Network address
71H 00H 00H 00H

Subnet address setting value
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

FFH FFH FCH 00H

Subnet mask
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

Set the subnet address of
Subnet address
Subnet address 81H 05H 28H 00H

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
194
(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 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

195
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-mounted 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. ( Page 356, Appendix 4)
196
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
External device
Access permitted IP address: 192.168.1.2
E71
Access permitted External device

IP address: 192.168.1.3
14.3.1 Application
Access prohibited
External device
IP address: 192.168.1.5
Remark
When a network other than Ethernet is used as the communication path, access cannot be restricted.
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.)
197
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. Confirm 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. Write the settings in the buffer memory areas, IP filter settings (address: 5700H to 5721H).
4. Perform reinitialization process. ( Page 360, Appendix 4.2)
5. 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.
198
(2) Buffer memory areas used

The following buffer memory areas are used for IP filter settings.
Address
Buffer memory name Decimal Description
(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)
• 0H: Ethernet
Communication condition setting
31 (1FH) • 1H: IEEE 802.3
(Ethernet Operation Setting) area
Setting of write enable/disable at RUN time (b6)
• 0H: Disable 14
• 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

stored.
Initial error code 105 (69H)
• 0H: Normal completion
14.3.2 Setting method

• Other than 0H: Abnormal end (error code)
Set when using the IP filter function.

Use of IP filter settings 22272 (5700H) • 0H: Do not use (default)
• 1H: Use
Select whether to allow or deny the access from the IP addresses

specified in IP address setting 1 to 8.
IP filter function type setting 22273 (5701H)
• 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
range.
22274 to 22275 22274 (5702H): Third octet, fourth octet
Start IP address
(5702H to 5703H)
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.
22276 to 22277 22276 (5704H): Third octet, fourth octet
End IP address
(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)
22278 to 22305
IP address setting 2 to 8 The configuration is the same as IP address setting 1.
(5706H to 5721H)
199
Address
Buffer memory name Decimal Description
(Hexadecimal)
The number of times an access is denied by the IP filter function.
• 0H: None (default)
Number of access denied by the IP 22306 to 22307
• 1H to FFFFFFFFH (1 to 4294967295): Number of access denied (When
filter function (5722H to 5723H)
this value exceeds 4294967295, it returns to "1" and starts counting
again.)
The latest IP address denied by the IP filter function is stored.
22308 (5724H): Third octet, fourth octet
IP address denied by the IP filter 22308 to 22309
22309 (5725H): First octet, second octet
function (5724H to 5725H)
• 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
200
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".

Set the end IP address to "192.168.3.5".
201
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.
202
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 Application 14
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 QCPU
• C24
14.4.1 Application
203
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.
204
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 mounted on the QCPU station, the E71 checks a
remote password for communication requests listed below.
• 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) 14
• Communication request from the connected device (including the programming tool connected to
the CPU module on the own station) to send data to another station upon request from the CPU
module
E71
QCPU
Remote password Remote password Path checked using

check a remote password
(Own station)
2) Path not checked using
(Another station) 3) a remote password
3)
Programming tool
QCPU
Remote Remote password

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
212, Section 14.4.6)
205
(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 QCPU 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 QCPU 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
QCPU E71
Network No.1 Ethernet
Station 1-1 1) 2) Station 3-2 1)

Remote Remote
password password
check QCPU E71
Station B
QCPU E71 E71
Programming tool
Ethernet Network No.2 Network No.3 Ethernet
Station 2-1 1) Station 2-2 1) 2) Station 3-1 1)
QCPU E71 QCPU E71 E71 QCPU E71
Station C Station D
*1 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 Target programmable controller station (request destination)

*2
device Station 1-2 Station 2-1 Station 2-2 Station 3-1 Station 3-2
Station 1-1 QCPU
(request source) QCPU QCPU QCPU QCPU QCPU
Station A ● ● ● ● ●
Station B
Station C
Station D
*2 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.
206
Ex. When a remote password and the remote password check have been set in multiple QCPU stations
Station 1-2 1)
Station A
QCPU E71
Network No.1 Ethernet
Station 1-1 1) 2) Station 3-2 1)

Remote Remote Remote Remote
password password password password
check check
Station B
QCPU E71 E71 QCPU E71
Programming tool
Ethernet Network No.2 Network No.3 Ethernet
14
Station 2-1 1) Station 2-2 1) 2) Station 3-1 1)
Remote Remote
password password
QCPU E71 check QCPU E71
Station C QCPU E71 E71 Station D
*1 The following are the connected devices that can perform unlock/lock processes.
•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,
: Stations that can be accessed from the connected device without performing the remote password unlock process,
×: Stations that cannot be accessed from the connected device
Connected Target programmable controller station (request destination)

*2
device Station 1-2 Station 2-1 Station 2-2 Station 3-1 Station 3-2
Station 1-1 QCPU
(request source) QCPU QCPU QCPU QCPU QCPU
Station A ● ● × × ×
Station B × × ×
Station C ● ● ×
Station D ●
*2 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.
207
14.4.4 Comparison of 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).
Remote password check setting

Function
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,
After an open process is completed, communications are enabled from the time
User open port
communications are enabled. that the unlock command is received until the
MC protocol lock command is received.
communications After an initial process is completed,
Auto-open UDP After an initial process is completed, communications are enabled from the time
port communications are enabled. that the unlock command is received until the
lock command is received.
After an open process is completed, Use MC protocol to communicate with the
User open port
Communications communications are enabled. CPU module where a remote password is set
using SLMP After an initial process is completed, because SLMP does not have unlock and lock
Auto-open UDP port
communications are enabled. commands.
Communications using the predefined After an open process is completed, After an open process is completed,
protocol communications are enabled. communications are enabled.*1
After the remote password is entered,
After an initial process is completed, communications are enabled. The remote
Communications using the predefined
communications are enabled by password lock process is automatically
protocol support function
establishing a connection in GX Works2. performed when the protocol setting data are
closed.
communications are enabled from the time
Procedure exists
Communications that the unlock command is received until the
using a fixed buffer lock command is received.
After an open process is completed, After an open process is completed,
No procedure
communications are enabled. communications are enabled.*1
Communications using a random access communications are enabled from the time
buffer that the unlock command is received until the
After an initial process is completed, data After an initial process is completed, data
E-mail function
sending and receiving are enabled.*2 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, performed when the Web browser is closed.
CC-Link IE Controller Network, CC-Link IE communications are enabled.
Field Network, MELSECNET/H, and After an initial process is completed,
MELSECNET/10 relay communications communications are enabled.*3
Communications using data link instructions
208
Remote password check setting

Function
Disabled Enabled
Within Ethernet, communications are
communications are enabled from the time
File transfer (FTP server) function enabled with the connected device that
that the unlock command is received until the
has completed an open process.
*1 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.
*2 Remote password check is not performed against the e-mail function.
*3 If a remote password has been set to the CPU module on the relay station or station to be accessed where the E71 is
mounted, access to another station may not be performed.
14
14.4.4 Comparison of functions according to the remote password check status (enabled/disabled)
209
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. (CPU number 1 in a multiple CPU system).
(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.
210
(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
memory areas. 14
• 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
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
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. ( Page 342,
Section 16.8)
● The accumulated counts stored in the following buffer memory areas can be cleared.
• Accumulated count of unlock process abnormal end (address of Connection No.1: 5072H)
• Accumulated count of lock process abnormal end (address of Connection No.1: 5074H)
211
The remote password setting of the E71 is described.
Project window [Parameter] [Remote Password]

Enter a password set for the CPU
Password Setting -
module.
Select the module model that checks
an entered remote password against
Model Name QJ71E71
Remote the remote password set for the CPU
Password module.
Password Active
Setting Set the start address of the module
Module Setting
Start XY that checks an entered remote 0000H to 0FE0H
password.
Opens the "Remote Password Detail
Condition -
Setting" window.
User Connection No. Connection 1 to Connection 16
Auto Open UDP Port
FTP Transmission Port (TCP/IP)
Remote
MELSOFT Application Transmission Port Specify a connection where an
Password
(TCP/IP) entered remote password is -
Detail System Connection
MELSOFT Application Transmission Port checked.
Setting
(UDP/IP), Dedicated Instruction, CC-Link
IE, NET/10(H) Relay Transmission Port
HTTP Port, HTTP Protocol
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.
212
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 38, Section 3.5.2)
This function is available only for the QJ71E71-100.
Buffer memory area Description

Stores the current connection status and transmission speed
Hub connection status area (address: C9H)
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
213
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.
This function is available only in the QJ71E71-100 with the serial number (first five digits) of "12062" or later. 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
The station that has been already station cannot be connected to the network.
connected to the network continues (The COM.ERR. LED turns on, and COM.ERR.
communications even if the station LED lit confirmation (X1C) turns on.)
with the same IP address is connected.
The module
connected later
This station cannot

be connected to
the network,
resulting in
an error.
IP address: IP address: IP address: IP address:
10.97.24.1 (Already in use) 10.97.24.2 10.97.24.3 10.97.24.1 (Already in use)
MAC address: MAC address: MAC address: MAC address:
00 26 92 89 2E 89 00 26 92 45 16 CC 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
Buffer memory area Description
address
Destination IP address (stored in the station with the same IP 234 (EAH) The third and fourth octets of the IP address
address connected to the network later.) 235 (EBH) The first and second octets of the IP address
The MAC address of the station that has 21121 (5281H) The fifth and sixth octets of the MAC address
been already connected to the network
21122 (5282H) The third and fourth octets of the MAC address
(stored in the station with the same IP
IP address status address connected to the network later). 21123 (5283H) The first and second octets of the MAC address
storage area The MAC address of the station with the 21124 (5284H) The fifth and sixth octets of the MAC address
same IP address connected to the network 21125 (5285H) The third and fourth octets of the MAC address
later (stored in the station that has been
already connected to the network). 21126 (5286H) The first and second octets of the MAC address
214
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 14
in the station with the same IP address (station connected to the network later).
[Diagnostics] [Ethernet Diagnostics...]
14.6 IP Address in Use Detection Function
215
14.7 Redundant System Function
This section describes functions used when the E71 is mounted on the main base unit in a redundant system.
Remark
When the E71 is mounted on an extension base unit, skip this section.
14.7.1 System switching request to the control system CPU module
This function issues a system switching request to the control system CPU module if the E71 mounted with the control
system CPU module in a redundant system detects a communication error or disconnection.
Connected device
A communication
error occurred.
Control system (system A) Standby system (system B)
Tracking cable
System switching request
(1) Conditions under which a system switching request is issued

The E71 issues a system switching request when the following conditions are satisfied.
Condition Description
After a connection is opened, the existence of the connected device cannot be
Alive check
Communication error confirmed.
detection An ACK response is not returned from the connected device within the TCP ULP timer
ULP timeout
time.
Disconnection detection The cable connected to the E71 has been disconnected (the QJ71E71-100 only).
In the following cases, system switching is not performed even if the E71 issues a system switching request.
• When the standby system has already been in error status (due to such as power-off, reset operation, and stop
error)
• The network module redundant group settings have been configured for the E71 and either one is operating
normally.
216
(2) Issuing a system switching request upon communication error

The E71 mounted with the control system CPU module monitors communications with the connected device on
each connection. If the E71 detects a communication error, it issues a system switching request to the control
system CPU module. The following table lists a communication error that triggers a system switching request.
Communication error Description

Alive check After a connection is opened, the existence of the connected device cannot be confirmed.
ULP timeout An ACK response is not returned from the connected device within the TCP ULP timer time.
(a) Target connection

The E71 detects communication errors in the connections selected in the redundant settings. The following
table lists connections that can be monitored.
Target connection
User Connection No. Connection 1 to Connection 16
Auto Open UDP Port 14
FTP Transmission Port (TCP/IP)
MELSOFT Application Transmission Port (TCP/IP)
System Connection
MELSOFT Application Transmission Port (UDP/IP), Dedicated Instruction, CC-Link IE,
NET/10(H) Relay Transmission Port
HTTP Port, HTTP Protocol

217
(b) System switching request operation
The E71 monitors communications with the connected device for an error using the alive check function and
TCP ULP timer.
1. During normal communications

Connected device
The system A is operating as a control system, and the
system B as a standby system.
Normal
The connected device is communicating with the E71
communications
mounted with the control system CPU module. (By
connecting the connected device to the E71 mounted
with the standby system CPU module in TCP/IP, an
error in the standby system CPU module can be
Control system (system A) Standby system (system B) detected.)
Tracking cable
2. At error detection*1
Connected device If a communication error has occurred between the
connected device and the E71, and the E71 mounted
with the control system CPU module detects an error, a
system switching request is issued to the control system
CPU module.*2
A communication
error occurred.
Tracking cable
3. After system switching

Connected device
The system A operates as a standby system, and the
system B as a control system.
Normal
The connected device changes the destination and
communications
communicates with the E71 mounted with the control
system CPU module (system B).
Tracking cable
218
*1 The following shows the timing of issuing the system switching request.
• System switching timing when an alive check is used
When the E71 has not communicated with the connected device where a connection is open for a certain
period of time, it performs an alive check. If the E71 cannot receive a response message from the
connected device, it closes the corresponding connection and issues a system switching request to the
control system CPU module. (The following figure shows an example where an alive check message is
resent twice.)

(address: 5000H)
A response message cannot be received from
the connected device.
E71
Alive check Alive check Alive check
The last communications
resent resent
(1st time) (2nd time)
Destination existence Destination Destination Destination
confirmation starting existence existence existence
interval timer value confirmation confirmation confirmation A request for system switching
interval timer interval timer interval timer to the control system CPU
module is issued.
14
• System switching timing when a ULP timeout is used
If ACK is not returned from the connected device within the TCP ULP timer time when the connection is
open in TCP/IP or data is sent, a sending error occurs and the E71 issues a system switching request to
the control system CPU module. (The following figure shows an example where the number of retries is set
twice.)
BUFSND instruction
BUFSND instruction

ACK is not returned from
E71
Data 1st retry 2nd retry
command
TCP resend TCP resend TCP resend

timer value timer value timer value
A request for system
TCP ULP timer value switching to the control
system CPU is issued.
*2 Set whether to issue the system switching request in the redundant settings of the programming tool. ( Page 223,
Section 14.7.3)
219
(3) Issuing a system switching request upon disconnection detection
The E71 mounted on the control system CPU module monitors the connection status of the cable connected to
the E71, and on detection of disconnection, it issues a system switching request to the control system CPU
module. Disconnection is detected in the following cases.
• Disconnection between the E71 and a hub
• Cable removal from the hub side connector
• Hub power-off
• Cable removal from the E71 side connector
Remark
This function is available for the QJ71E71-100 only.
(a) System switching request operation

The E71 always monitors the connected cable for disconnection.
Connected device
1. Disconnection monitoring
The E71 always monitors the connected cable for
disconnection.*1 The monitoring result is stored to the
buffer memory area, Hub connection status area
(address: C9H).
Disconnected
Tracking cable
2. Upon disconnection detection*2

Connected device If the E71 mounted with the control system CPU module
detects disconnection, it performs a disconnection
status time check. If the disconnected status continues
for the period of the disconnection detection monitoring
time, the E71 issues a system switching request to the
control system CPU module.
Tracking cable
220
3. After system switching

Connected device
The system A operates as a standby system, and the
system B as a control system.
Tracking cable
*1 When the cable is not connected from the start, the E71 does not determine it as disconnection. (Disconnection is 14
detected only when normal status turns to abnormal.)
*2 The following shows the timing of issuing the system switching request.
• System switching timing at disconnection detection
The E71 starts disconnection detection after initial process completion. On detection of disconnection, the
E71 performs a disconnection status time check, and when disconnected status continues for the period of
the disconnection detection monitoring time, the E71 issues a system switching request to the control
system CPU module. When the disconnected status returns to normal within the disconnection detection
monitoring time, the E71 does not issue a system switching request.
Disconnected Cable connected Disconnected

(link down) (link up) (link down)
Detection for Disconnected Disconnected

disconnection is
E71 started after the initial
process is completed.
Disconnection detection Disconnection detection

monitoring time monitoring time
A request for system switching to

the control system CPU is issued.
221
14.7.2 Communication path bypass function
When any of the following redundant system supported applications is used, the path where a communication error
has occurred is automatically bypassed to continue communications if an error occurs in communications with the
E71. The communication path needs not to be changed manually.
• Application that operates on the OPS (except the MELSOFT products such as GX Developer)
• GX Works2
• GX Developer
• PX Developer monitor tool
(1) Operation example of a redundant system supported application at a

communication error
The following provides an example of redundant system supported application operation if an error occurs during
communications with the control system CPU module.
1. During normal communications

Connected device
The station number 1 is operating as a control system,
and the station number 2 as a standby system. The
redundant system supported application is
Normal
communications
communicating with the control system CPU module.
Control system (station No.1) Standby system (station No.2)
Tracking cable
2. Upon a communication error

Connected device
The station number 1 is operating as a control system,
Redundant system
supported and the station number 2 as a standby system. (Without
application
system switching)
[Operation of the redundant system supported

application]
(1)
Because a communication error has occurred between
A communication the redundant system supported application and the
error occurred.
E71 mounted with the control system CPU module, the
Control system (station No.1) Standby system (station No.2)
redundant system supported application automatically
changes the communication path and communicates
with the control system CPU module through the
standby system CPU module.
(2) Tracking cable
[Operation of the standby system CPU module]
(1) The connected device accesses the control system CPU
module around the path. Because the received data is addressed to the control
(2) Communications with the control system CPU module is system CPU module, data is relayed to the control
continued via a tracking cable.
system CPU module through the tracking cable.
222
This section describes the parameter settings for using the E71 in a redundant system. The following settings are
required:
• Basic setting
• Ethernet operation setting
• Open setting (if necessary) ( Chapter for each function)
• Redundant settings
(1) Basic setting

Only the settings for a redundant system that differ from those for a single CPU system are listed.
14


Network Type Select "Ethernet (Main Base)". -
Set the station number of the E71 in the system A. Set the
Station No. station number of the E71 in the system B in the 1 to 64
Redundant Setting.
• Online
Select the operation mode of the E71 in the system A. Set
• Offline
Mode the operation mode of the E71 in the system B in the
• Self-Loopback Test
Redundant Setting.
• H/W Test
(2) Ethernet operation setting

The IP address configured in the Ethernet operation setting becomes the IP address of the E71 in the system A.
Set the IP address of the E71 in the system B in the redundant settings.
223
(3) Redundant settings
Configure the settings of the system B and issue of a system switching request.

Station Station No.
Number and
Displays the settings configured in the basic setting. -
Mode Setting Mode
(System A)
Station Station No.
Set the station number and mode of the system B. Set a different
System B Number and
station number from that of the system A. Set the same mode as the Same as system A
Setting Mode Setting Mode
system A.
(System B)
Input Format Select an input format. Same as system A
IP Address System A Displays the settings configured in the Ethernet operation setting. -
Setting Set the IP address of the system B. Set a different IP address from
System B Same as system A
that of the system A.
Issue system switch in Cable disconnection Select whether a system switching request is issued upon detection of Selected/not
timeout disconnection. selected
Cable Disconnection Timeout Set the time from when disconnection is detected until the system
0.0s to 30.0s
Setting switching request is issued to the control system CPU module.
Select whether a system switching request is issued upon a Selected/not
Issue system switch in communication error
communication error. selected
System switching settings when Set the target connection where a communication error will cause a
Target connection
communication error occurs system switching request to be issued.
224
*1 The settings of the auto-open UDP port and MELSOFT application transmission port (UDP) are enabled when the
following conditions are satisfied. When the following conditions are not satisfied, the system switching request is not
issued even if a communication error occurs in the target connection.
• The remote password setting is enabled.
• The remote password is unlocked.
*2 Do not set the connection with any of the following settings as the target connection. If set, the system may be
consecutively switched in the redundant system if a communication error occurs due to cable disconnection or power-off
of the connected device.
• "Initial timing" in the Ethernet operation setting: "Always wait for OPEN (Communication possible at STOP time)"
• "Protocol" in the open setting: "UDP"
• "Existence confirmation" in the open setting: "Confirm"
*3 It is recommended that the connection set to "MELSOFT connection" under "Open system" of the open setting is not set
as the target connection. Doing so may set all the MELSOFT products connected to the network as the target
connections, therefore; the connected device (target MELSOFT product) cannot be specified.
● When using a redundant system in the backup mode, set the mode of the system B same as that of the system A. If the
mode differs between them, an error will occur in the Redundant CPU.
● Configure "Cable disconnection timeout setting" from several seconds to several ten seconds. If the value is shorter than
that, a system switching request may occur due to such as noise.
14

225
14.7.4 Data communications in a redundant system
This section describes data communications using the E71 mounted on the main base unit in a redundant system.
Processes other than those described in this section are the same as those in a single CPU system.
(1) Initial process
(a) Reinitialization process

When performing a reinitialization process, do not change the settings, such as the own station IP address and
Ethernet operation setting. Doing so may cause a communication error.
• When using the UINI instruction
Execute the instruction after specifying "0H" for Specification of changed item ((S1)+2) of the control data.
• When directly writing to the buffer memory
Write "1" to the bit 15 of Communication condition setting (Ethernet Operation Setting) area (address: 1FH)
without changing the value stored in the buffer memory area.
(b) Initial process using I/O signals

Because the output signal (Y) turns off in the standby system CPU module, an initial process cannot be
performed using I/O signals. To perform an initial process, set the network parameters using a programming
tool.
(2) Open/close processes
(a) Communications in TCP/IP

Place the E71 in open wait status (Passive open) and perform an open/close process from the connected
device. If an Active open process is performed from the E71, the close process is performed from the E71 after
data communications, but if the system is switched before execution of the close process, the process cannot
be performed.
(b) When using a user connection to communicate with the standby system (for MC
protocol communications or communications using a random access buffer)
Set "Always wait for OPEN (Communication possible at STOP time)" under "Initial timing".
• Open setting
In TCP/IP communications, set "Unpassive or Fullpassive" under "Open system".
Setting connections for communications with the system A and communications with the system B is recommended. This
facilitates communications with the other system if a communication error has occurred in the own system or when the
system is switched. A maximum of 16 user connections can be registered in the E71.
(c) Open/close processes using I/O signals

Because the output signal (Y) turns off in the standby system CPU module, open/close processes cannot be
performed using I/O signals. To perform the processes, set "Always wait for OPEN (Communication possible at
STOP time)" under "Initial timing" in the Ethernet operation setting or use dedicated instructions
(OPEN/CLOSE instructions).
226
(3) Using MC protocol communications

The QnA-compatible 3E frame or 4E frame can be used to access the control system/standby system or system
A/system B.
(a) Operation performed for access to the control system/standby system or the system
A/system B
Ex. When the system is switched (example of access to the control system CPU module)
Connected device
1. Connect the connected device to the E71
QnA-compatible 3E frame mounted with the control system CPU module
Request destination module I/O number:
Access to 03D0H to access the control system CPU module.
the control system Network number: 00H
Personal computer number: FFH
14
Tracking cable
Connected device
2. When the system is switched, the connected
QnA-compatible 3E frame device automatically continues access to the
Access to the control
Request destination module I/O number:
system is continued
03D0H control system through the tracking cable.
via a tracking cable. Network number: 00H
However, if the communication line with the
Personal computer number: FFH

connection destination is faulty or the
standby system is powered off, for example,
the destination must be changed on the
Standby system (system A) Control system (system B) connected device.
Tracking cable
Ex. For access to the system that is not the connection destination (example of connection to the control
system and access to the standby system CPU module)
3. To access the standby system CPU module,

Connected device QnA-compatible 3E frame
Request destination module I/O number: the connected device connects to the E71
Access to
03D1H mounted with the control system CPU module
Network number: 00H
the standby system Personal computer number: FFH through the tracking cable. This enables
access even if the communication line
Even if an error occurs in the communication line,
it is possible to access the standby system. between the connected device and standby
system becomes faulty.
Tracking cable
227
(b) Communication procedure example for access to the control system CPU module in
a redundant system
The following shows a communication procedure example. Place the E71 in open wait status and perform
open/close processes from the connected device.
Example of a communication procedure
Perform the open process to the system A.
Perform the open process to the system B.
ON: The system A is

the control system.
Is SM1515
(operating system status) on?
OFF: The system A is the standby system.
Is SM1516 The TRK.CABLE ERR. has occurred.

OFF
(operating system status) on? For details, refer to the QnPRHCPU User's
Manual (Redundant System).
ON: The system A is the standby system.
ON: The system B is

the control system.
Is SM1515
OFF: The system B is

the standby system.
Is SM1516 OFF
ON: The system B is

the standby system.
A command message is sent. A command message is sent.

I/O No. of the request destination module: 03D0H I/O No. of the request destination module: 03D0H
Was the response NO NO Was the response

message normally sent? message normally sent?
YES YES
YES YES
Is this process repeated? Is this process repeated?
NO NO
Perform the close process to the system A. Perform the close process to the system B.
Perform the close process to the system A. Perform the close process to the system B.
End
228
(c) Precautions for writing a parameter file or program file

• Write the same file to the system A and system B. If different files are written to the systems, or a file is
written to only one system, an error will result.
• Write the file while the switch on the CPU module is set to STOP.
• Write the file in the following procedure.
Start
Perform the remote STOP to the control system CPU module. A continuation error occurs in the
standby system CPU module.
Perform the remote STOP to the standby system CPU module.
Write the file to the control system CPU module.

Write the file to the standby system CPU module.
*1
14
Perform the remote RUN to the standby system CPU module.
Perform the remote RUN to the control system CPU module.
Clear the error in the standby system CPU module.*2
End
*1 After writing the parameter file, reset the both CPU modules.

*2 When the operating status of the control system CPU module is switched from STOP to RUN, check the error status of
the standby system CPU module. If an error has occurred, set the error code (6010H) to SD50 then turn on SM50 to
clear the error.
(4) Communicating using a fixed buffer
(a) Receive process in a standby system

When data is sent to the E71 mounted with the standby system CPU module, the data received by the E71 is
discarded, and the receive process is not performed. (Fixed buffer reception status signal does not turn on.)
(b) Receive process in an interrupt program

When the control system is switched to the standby system by system switching before execution of an
interrupt program, the interrupt factor is held. When the system is switched again and the standby system is
switched to the control system, the interrupt program is executed by the held interrupt factor. (The interrupt
factor is not transferred to the other system.)
229
(c) When data is sent from the connected device
• When using the "Procedure exist" method
If a response timeout to the E71 occurs, change the connection destination to the other system and send the
data.
• When using the "No procedure" method
Send the same data to both the control system and standby system.
The following shows an example of the sending procedure for sending data to a redundant system using the
"Procedure exist" method.
Fixed buffer communication procedure

(Procedure exist)
Data is sent to the system A.
YES
Did a timeout occur?
NO
A response is received from

Data is sent to the system B.
the system A.
YES
Did a timeout occur?
NO
A response from the system B

An error has occurred.
is received.
Take care of the following when performing a resend process at system switching.
• When performing communications while synchronizing sending and receiving, system switching may occur during
the communications, and the system may be switched with the sending and receiving not synchronized. To
perform system switching, restart communications after initializing the synchronization for safety.
• After executing the WRITE instruction, execute it again because it is difficult to determine that the instruction has
been completed. However, note that the same instruction may be executed twice.
(5) Communicating using a random access buffer

The buffer memory of the E71 is not tracked. Therefore, when writing data to the random access buffer, write the
same data to the control system and standby system.
230
(6) Using the e-mail function
(a) Receiving e-mails

• After the E71 receives an e-mail, send a response mail to the mail sending source so that the mail sending
source may recognize the arrival of the e-mail. If the receiving cannot be recognized, send the e-mail
again.
• After the MRECV instruction is executed, the read e-mail is deleted from the mail server. Therefore, when
system switching occurs during execution of the MRECV instruction, the mail may not be received by the
new control system CPU module after system switching even if the MRECV instruction is re-executed.
(The e-mail has been deleted from the mail server.)
(b) E-mail receiving program

In the following program, turning on X21 allows the E71 mounted on the slot where the I/O signals of X/Y00 to
X/Y1F are assigned to receive an e-mail by execution of the MRECV instruction and send a response mail to
the sending source by execution of the MSEND instruction.
14
Specify inquires to the server.
Specify the first mail reading.
Specify the matching to the data

length of a received mail.
Specify the matching to the header
data length of the received mail.
Read the received mail.

Normal receiving of the e-mail
Failure in the receiving of the e-mail
Text data (normal)
Text data (error)
Specify the text.
Specify the sending destination No.
Specify the send data length.
Specify the Subject length.
Specify the Subject.
Send an e-mail.
Completion
Abnormal end
231
(c) Using the notification function
Because a notification mail may be sent from both the control system and standby system in either of the
following conditions, perform the process that discards the same e-mail that is received later on the receiving
side personal computer.*1
• The CPU operating status has been set as the notification condition.
• The device data set as the notification condition is being tracked.
*1 By setting the following SM devices as notification conditions, the system mode in the redundant system can be
identified with a notification mail. The devices can be used as conditions for identifying the system having the same
e-mail.
• SM1511 (System A identification flag)
• M1512 (System B identification flag)
• SM1515, SM1516 (operating system status)
(7) Communicating over CC-Link IE Controller Network, CC-Link IE Field Network,

MELSECNET/H, and MELSECNET/10
(a) When a redundant system is in the network

When performing access through a redundant system, change the routing parameter settings on the request
source station or relay station using the RTWRITE instruction at system switching.
(b) When performing access through a redundant system

To access another station through Ethernet using the CC-Link IE Controller Network, CC-Link IE Field Network,
MELSECNET/H, and MELSECNET/10 relay communications, set the routing parameters on the request
source station or relay station. To perform access through a redundant system, set the station that becomes a
control system as a routing station.
Request source station Network parameter setting

Transfer destination Relay destination Relay
E71 destination
QCPU network No. network No. station No.
Station
No.3 1 2 1
Network No.2
Control system Standby system

E71 E71 E71 E71
QnPRH QnPRH
Station Station Station Station
CPU CPU
No.1 No.1 No.2 No.2
Network No.1
Request
destination station
E71
QCPU Station
No.3
232
If system switching occurs, change the routing parameter settings using the RTWRITE instruction so that the
request source station or relay station accesses the destination through the station of the new control system
after system switching.
Request source station Network parameter setting

Transfer destination Relay destination Relay
E71 destination
Station network No. network No. station No.
QCPU
No.3 1 2 1 2
Network No.2 Change the parameter

setting using the RTWRITE
instruction.
Standby system Control system
E71 E71 E71 E71
QnPRH QnPRH
Station Station Station Station
CPU CPU
No.1 No.1 No.2 No.2
Network No.1
Request
destination station
E71 14
QCPU Station
No.3
(8) When the CPU module accesses a programmable controller on another station
using data link instructions
(a) Redundant system supported data link instructions

• By specifying the destination in Target station CPU type of the control data in any of the following data link
instructions, access can be performed to the control system/standby system or system A/system B.

• READ/SREAD instructions
• WRITE/SWRITE instructions
• REQ instruction
• Operation performed for access to the control system/standby system or the system A/system B (example
of executing the READ instruction)
When the target station is the standby system, because the received command is addressed to the control
system CPU module (Target station CPU type: 3D0H), data is relayed to the control system CPU module
through the tracking cable to read the data in the control system CPU module.
QCPU E71
READ
Channel 3
(Own station)
Device
Control system Standby system (target station)
Device
Tracking cable
233
(b) Process at abnormal end
When a data link instruction is executed for the specified control system CPU module or standby system CPU
module in a redundant system, the data link instruction may result in an error if system switching occurs in the
target station (error codes: 4244H, 4248H). If a data link instruction results in an error with either of the
aforementioned error codes, execute the data link instruction again.
(c) SEND instruction

• When the target station is in a redundant system, the communication request source station must identify
that the target station is the control system to execute the SEND instruction. When the target station is the
standby system, the target station storage channel cannot be used since the RECV instruction is not
executed at the target station after data is sent by the SEND instruction. (Channel being used)
• When a redundant system exists on the network where a broadcast is performed, the storage channel
cannot be used since the RECV instruction is not executed for the standby system. (Channel being used)
(d) RECV instruction and interrupt program (RECVS instruction)

When the SEND instruction is executed for the redundant system, the process of the RECV instruction or
interrupt program (RECVS instruction) changes depending on the following conditions.
• When system switching occurs between execution of the SEND instruction for the control system and
execution of the RECV instruction or interrupt program
When the control system is switched to the standby system before execution of the RECV instruction or
interrupt program, it holds the buffer memory area data, RECV instruction execution request (address:
CDH) and the interrupt factor (interrupt pointer) of the interrupt program. When system switching occurs
again and the standby system is switched to the control system, the RECV instruction and interrupt
program are executed using the data held in the buffer memory area, RECV instruction execution request
and the interrupt factor of the interrupt program.
• When the SEND instruction is executed for the standby system
When the standby system receives data from the sending station, it holds data in the buffer memory area,
RECV instruction execution request (address: CDH) and the interrupt factor (interrupt pointer) of the
interrupt program. When system switching occurs and the standby system is switched to the control
system, the RECV instruction and interrupt program are executed using the data held in the buffer memory
area, RECV instruction execution request area and the interrupt factor of the interrupt program.
234
(9) Using the file transfer (FTP server) function
(a) Precautions for writing a parameter file or program file

• Write the same file to the system A and system B. If different files are written to the systems, or a file is
written to only one system, an error will result.
• Write the file while the switch on the CPU module is set to STOP.
• Write the file in the following procedure.
Start
Log in the E71 mounted on the main base unit of the system A CPU module.
Log in the E71 mounted on the main base unit of the system B CPU module.
Perform the remote STOP to the system A CPU module. A continuation error occurs in
Perform the remote STOP to the system B CPU module. the standby system CPU module.
14
Write the file to the system A CPU module.
Write the file to the system B CPU module.
*1
Perform the remote RUN to the system A CPU module.

Perform the remote RUN to the system B CPU module.
Log out from the E71 mounted on the main base unit of the system A CPU module.
Log out from the E71 mounted on the main base unit of the system B CPU module.

Clear the error in the standby system CPU module. *2
End
*1 After writing the parameter file, reset the both CPU modules.
*2 When the operating status of the control system CPU module is switched from STOP to RUN, check the error status of
the standby system CPU module. If an error has occurred, set the error code (6010H) to SD50 then turn on SM50 to
clear the error.
(10)Using dedicated instructions

If system switching occurs during execution of the dedicated instruction, the dedicated instruction may not be
completed. Execute the dedicated instruction again from the new control system CPU module after system
switching.
235
14.8 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.
In TCP/IP communications, the following methods can be selected in the Ethernet operation setting. ( Page
87, 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 command. (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 an
alive check 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.*2
*2 The connection may be disconnected if the connected device does not support the TCP KeepAlive function (response to
a KeepAlive ACK message).
236
(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
Open completion signal forced close
(address: 5000H) (error code: C035H)
E71 14
The last Alive check Alive check Alive check
RST sending
communications Alive check resent resent resent
(TCP only)
(1st time) (2nd time) (3rd time)
Destination Destination Destination Destination
Destination existence existence existence existence existence
confirmation starting confirmation confirmation confirmation confirmation
interval timer interval timer interval timer interval timer
interval timer value value value value value
*1 The values of the number of retries and timers can be changed in the initial setting. ( Page 356, Appendix 4.1)
14.8 Alive Check Function
237
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 Description Reference

Establishes (opens) a connection with the connected device to perform data
OPEN Page 243, Section 15.5
communications.
Disconnects (closes) a connection with the connected device performing
CLOSE Page 247, Section 15.6
data communications.
Executes the protocols registered in the flash ROM of the E71 using the
ECPRTCL Page 250, Section 15.7
Predefined Protocol Support Function of GX Works2.
Sends data to the connected device through communications using a fixed
BUFSND Page 261, Section 15.8
buffer.
Reads data received from the connected device through communications
BUFRCV Page 265, Section 15.9
using a fixed buffer (used in the main program).
Reads data received from the connected device through communications
BUFRCVS Page 269, Section 15.10
using a fixed buffer (used in an interrupt program).
Turns off LEDs of the E71 or clears error information stored in the buffer
ERRCLR Page 272, Section 15.11
memory.
ERRRD Reads error information stored in the buffer memory of the E71. Page 275, Section 15.12
UINI Re-initializes the E71. Page 279, Section 15.13
238
(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.
Function Instruction Description

MRECV Reads the received e-mails.
E-mail function
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.)
Performs remote RUN/STOP to CPU modules on other stations.
REQ
Reads/writes the clock data of other stations.
SEND Sends data to other stations.
data link instructions
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).
15
ZNWR Writes word device data to other stations (ACPU).
15.1 List of Dedicated Instructions
239
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.

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. (For safety CPUs, the following measures cannot be applied.)
• Execute the COM instruction.
• Reserve time for a communication process for 2 to 3 ms.
• For a Basic model QCPU, High Performance model QCPU, Process CPU, and Redundant CPU, set
the service processing time in Time reserved for communication processing (SD315).
• For a Universal model QCPU, configure "Service Processing Setting" in the "PLC System" tab of the
PLC parameter window.
240
15.4 Organization of the Dedicated Instruction Sections
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.
15
Descriptions Setting side
of setting data User: A device value is set by the user.
and data type System: A device value is set
by the CPU module.
15.4 Organization of the Dedicated Instruction Sections

(1) Instruction execution conditions
Instructions can be executed under the following conditions.
Any time During on On the rising edge During off On the falling edge
No symbol
241
(2) Available devices
The following devices can be used.
Internal device Constant

File register
Bit*1 Word K, H $
X, Y, M, L, F, V, B T, ST, C, D, W R, ZR K, H $
*1 For bit data, a bit-specified word device can be used. For example, 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).
For details on each device, refer to the following.

User's manual for the CPU module used (function explanation, program fundamentals)
(3) Data type

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
242
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)
*1
Available device
Internal device Link direct device Intelligent
Index Constant
Setting data*2 (system, user) File J\ function module
register Others
register device
Bit Word Bit Word Zn K, H $
U\G
(S1) - - - -
(S2) - - - - -
(D1) - - - -
*1 If the own station is a Basic model QCPU (function version B or later), Universal model QCPU, or safety CPU, " " (double
15
quotation) of the first argument can be omitted.
*2 The file registers set for each local device and program cannot be used.
(1) Setting data
15.5 ZP.OPEN
Setting data Description Set by Data type
Start I/O number of the E71 (00 to FEH: The first two digits Character string/BIN
"Un"/Un
of the three-digit I/O number) User 16-bit
(S1) *1 BIN 16-bit

Connection number (1 to 16)
(S2) Start number of the device that stores control data 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.
*1 For safety CPUs, only connection numbers 1 to 8 can be specified. If the specified value is out of range, "OPERATION
ERROR" (error code: 4101) occurs.
243
(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 the settings stored in the following
Execution control data starting from (S2)+2. 0000H,
(S2)+0 User
type/completion type 0000H: Use the parameter settings of the 8000H
programming tool.
8000H: Use the settings of control data starting
from (S2)+2.
Stores the status at completion.
0000H: Normal completion
(S2)+1 Completion status - System
Values other than 0000H (error code): Abnormal
end
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
1: Enable
As described in
(S2)+2 Usage setting area • Communication method (protocol) (b8) User
the left
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
401 H to 1387H,
(S2)+3 Own station port No. Specify the port number of the own station. User
138BH to FFFEH
1H to FFFFFFFFH
(S2)+4 Destination IP
Specify the IP address of the connected device. (FFFFFFFFH: User
(S2)+5 address
broadcast)
1H to FFFFH*1
Specify the port number of the connected
(S2)+6 Destination port No. (FFFFH: User
device.
broadcast)
(S2)+7
Destination MAC Specify the MAC address of the connected 000000000000H to
(S2)+8 User
address device. FFFFFFFFFFFFH
(S2)+9
*1 The range of 1H to 400H is available only for the QJ71E71-100 with the serial number (first five digits) of "15042" or later.
244
(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.
• Completion device Turns on at the END process of the scan where the OPEN instruction is
(D1)+0: completed and turns off at the next END process.
• Completion device Turns on and off depending on the completion status of the OPEN instruction.
(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]
END END END

Program Scan process Scan process Scan process
OPEN instruction Executed

15
Completion device
Completion device + 1 Abnormally ended
Connection
opened
• The ZP.OPEN instruction is executed on the rising edge (OFF ON) of the open command.
15.5 ZP.OPEN
Do not perform an open 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.
245
(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 Necessary when the open setting of the programming tool is used. (In this case, the program marked with *2 is
unnecessary.)
*2 Necessary when the open setting of the program is used. (In this case, the program marked with *1 is unnecessary.)
For safety CPUs, data stored in the buffer memory of the intelligent function module cannot be used. The program must be
modified using the I/O signals of the intelligent function module corresponding to the buffer memory.
For use with safety CPUs, refer to the following.
QSCPU User's Manual (Function Explanation, Program Fundamentals)
246
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)
*1
Available device
Index Constant
register Others
register device
U\G
(S1) - - - -
(S2) - - - - -
(D1) - - - -
15
(1) Setting data
15.6 ZP.CLOSE
"Un"/Un
(S1) *1 BIN 16-bit

(S2) Start number of the device that stores control data Device name
System
(D1) turns on for one scan upon completion of the instruction. Bit
(2) Control data

(S2)+0 System area - - -
Values other than 0000H (error code):
Abnormal end
247
(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.
• Completion device Turns on at the END process of the scan where the CLOSE instruction is
• Completion device Turns on and off depending on the completion status of the CLOSE instruction.
(D1)+1:
the CLOSE instruction is completed and turns off
at the next END process.
[Operation while the CLOSE instruction is being executed]
END END END

CLOSE instruction Executed
Completion device
Connection
closed
• The ZP.CLOSE instruction is executed on the rising edge (OFF ON) of the close command.
Do not perform a close process using I/O signals and using the dedicated instruction together for the same connection.
(4) Errors
248
(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
249
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
Internal device Link direct Intelligent
Index Constant
Setting data*1 (system, user) File deviceJ\ function module
register Others
register device
U\G
n1 - - -
n2 - - -
(S) - - - -
(D) - - - -
(1) Setting data

Start I/O number of the E71 (00 to FEH: The first two digits
Un BIN 16-bit
of the three-digit I/O number)
BIN 16-bit
n1 Connection number (1 to 16) User
Device name
BIN 16-bit
n2 Number of consecutive protocol executions (1 to 8)
Device name
(S) Start number of the device that stores control data User/system Device name
(D) turns on for one scan upon completion of the instruction. System Bit
(D)+1 also turns on if the instruction ends abnormally.
250
(2) Control data

Stores the number of protocols which are
executed by using the ECPRTCL instruction.
(S)+0 Execution count result Protocols with errors are included in the count. 0, 1 to 8 System
When settings of the setting data or control data
contain an error, "0" is stored.
When multiple protocols are executed, the
status of the protocol executed at last is stored.
(S)+1 Completion status - System
Abnormal end
Execution protocol
(S)+2 Set the first protocol number to be executed. 1 to 128 User
number specification 1
Execution protocol Set the second protocol number to be
(S)+3 0, 1 to 128 User
number specification 2 executed.
Execution protocol
(S)+4 Set the third protocol number to be executed. 0, 1 to 128 User
number specification 3 15
Execution protocol
(S)+5 Set the fourth protocol number to be executed. 0, 1 to 128 User
Execution protocol
(S)+6 Set the fifth protocol number to be executed. 0, 1 to 128 User
Execution protocol
(S)+7 Set the sixth protocol number to be executed. 0, 1 to 128 User
Execution protocol Set the seventh protocol number to be
15.7 GP.ECPRTCL
(S)+8 0, 1 to 128 User
number specification 7 executed.
Execution protocol
(S)+9 Set the eighth protocol number to be executed. 0, 1 to 128 User
When the communication type of the first
protocol executed includes receiving, the
matched receive packet number is stored.
Matched receive packet
(S)+10 When the communication type is "Send Only", 0, 1 to 16 System
No.1
"0" is stored.
If an error occurs to the first protocol executed,
"0" is stored.
When the communication type of the second
When the communication type is "Send Only",
(S)+11 "0" is stored. 0, 1 to 16 System
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.
251
When the communication type of the third
No.3
If an error occurs to the third protocol executed,
"0" is stored.
When the communication type of the fourth
No.4
If an error occurs to the fourth protocol
When the communication type of the fifth
No.5
If an error occurs to the fifth protocol executed,
"0" is stored.
When the communication type of the sixth
No.6
If an error occurs to the sixth protocol executed,
"0" is stored.
When the communication type of the seventh
No.7
If an error occurs to the seventh protocol
When the communication type of the eighth
No.8
If an error occurs to the eighth protocol
252
(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 Connection No. that can be specified by n1
When the communication type of all protocols executed (up

• A connection where "Send" is selected in the open setting 15
(no paring open setting)
to eight protocols) is "Send Only"
• A connection where paring open is set*1*2
• A connection where "Receive" is selected in the open
When the communication type of all protocols executed (up
setting (no paring open setting)
to eight protocols) is "Receive Only"
• A connection where paring open is set*1*2
When the communication type of any protocol executed (up
15.7 GP.ECPRTCL
to eight protocols) is "Send&Receive"
A connection where paring open is set*1*3
When the communication types of protocols executed (up to
eight protocols) are "Send Only" and "Receive Only"
*1 To specify a connection where paring open is set, either of pairing-opened connections can be specified.
*2 When a pairing-opened connection is specified, an extra connection is used.
*3 When the protocols executed include the communication type of "Send&Receive" or "Send Only" and "Receive Only",
pairing open setting is required.
253
• Completion of the ECPRTCL instruction can be checked with Completion device (D) and (D1)+1.
• Completion device Turns on at the END process of the scan where the ECPRTCL instruction is
(D)+0: completed and turns off at the next END process.
• Completion device Turns on and off depending on the completion status of the ECPRTCL
(D)+1: instruction.
the ECPRTCL instruction is completed and turns
off at the next END process.
[Operation while the ECPRTCL instruction is being executed]
Program Scan END Scan END Scan END Scan END Scan END Scan
process process process process process
ECPRTCL instruction Instruction executed
Completion device
Completion device + 1 At abnormal end
Protocol executed*2
Protocol execution status

(Execution status) (5: Completed)
(address: 54C0H*1)
*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
254
● 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
high-speed 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 15
completed until the data specified in the protocol setting is received.
15.7 GP.ECPRTCL
255
(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 130, 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)).
User
Connection No.n
Protocol cancellation specification 1: Cancellation request 2: Cancel completed
(54D3H (when the value of n is 1))
The E71 cancels the

E71 protocols being executed
in connection No.n.
256
(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
protocols
(S)+0 Execution count result
(When cancel request is executed to the second
protocol, 2 is stored.)
(S)+1 Completion status Protocol cancel request error (error code: C404H)
Matched receive packet number of the executed

(S+10) to (S+17) Matched receive packet No.1 to 8
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. 15
● 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.
15.7 GP.ECPRTCL
● When Protocol cancellation specification (address: 54D3H (Connection No.1)) is "1: Cancellation request", the next
ECPRTCL instruction cannot be executed.
257
(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
The E71 cancels the sending and terminates the dedicated instruction
1: Waiting for transmission
forcibly.
The E71 terminates the dedicated instruction forcibly at sending
2: Sending
completion.
The E71 cancels the receiving and terminates the dedicated instruction
3: Waiting for data reception
forcibly.
The E71 terminates the dedicated instruction forcibly at receiving
4: Receiving
completion.
The E71 terminates the dedicated instruction when protocols are executed
5: Completed
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
Completion device
The device turns on
upon abnormal end.
Completion device + 1
Connection No.n
Waiting time The E71 does not send a send

to send
packet to the connected device
Cancel even when a receive data or a
E71 protocol exists.
Send packet
Connected device
Send packet
258
• 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.
Connection No.n
Protocol cancellation specification 1: Cancel request 2: Cancel completed
Waiting time
to send t: TCP ULP timer
E71
Send packet
The E71 does not send a
Packet sending in progress is send packet to the connected
completed without interruption. device even when a receive
data or a protocol exists.
15
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)
15.7 GP.ECPRTCL
ECPRTCL instruction
Completion device
The device
turns on upon
Completion device + 1 abnormal end.
Connection No.n
Protocol cancellation specification 1: Cancellation 2: Cancel
(54D3H (when the value of n is 1)) request completed
Waiting time
E71
Send packet
The E71 does not send a

send packet to the connected
Cancel device even when a receive
Connected device data or a protocol exists.
Send packet
259
• 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.
Connection No.n
Protocol cancellation specification 1: Cancellation request 2: Cancel completion
t: waiting time to receive or the time specified The E71 does not send a
by the destination alive check timer send packet to the connected
device even when a receive
E71 data or a protocol exists.
Cancel
Connected device
• When the cancel request is performed during receiving (when "4" (Receiving) is set in Protocol execution
status (address: 54C0H))
ECPRTCL instruction
Completion device
The device turns on
upon abnormal end.
Connection No.n
t: waiting time to receive or the time specified The E71 does not send a
by the destination alive check timer send packet to the connected
device even when a receive
E71 data or a protocol exists.
Receiving
The E71 interrupts the verification and

Cancel general data processing and forcibly
Connected device terminates the dedicated instruction.
Receive data
260
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)
*1
Available device
Index Constant
register Others
register device
U\G
(S1) - - - -
(S2) - - - - -
(S3) - - - - -
(D1) - - - - 15
*1 If the own station is a Basic model QCPU (function version B or later), Universal model QCPU, or safety CPU, " Page
243, Section 15.5" (double quotation) of the first argument can be omitted.
(1) Setting data
15.8 ZP.BUFSND
"Un"/Un
(S1) Connection number (1 to 16)*1 BIN 16-bit

(S2) Start number of the device that stores control data System Device name
(S3) Start number of the device that stores send data User Device name
(2) Control data

Abnormal end
261
(3) Send data

Specify send data length. (Depending on the procedure of
fixed buffer communications, the data length is the -
number of words or the number of bytes.)
Procedure exists (communications using a binary
Send data 1 to 1017
(S3)+0 code): Number of words User
length
Procedure exists (communications using an ASCII
1 to 508
code): Number of words
No procedure (communications using a binary code):
1 to 2046
Number of bytes
(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 E71
Fixed buffer data area
(S3) Send data length No.1
Send data :
BUFSND
: No.n Connected device
: :
Send data No.16
262
• Completion of the BUFSND instruction can be checked with Completion device (D1)+0 and (D1)+1.
• Completion device Turns on at the END process of the scan where the BUFSND instruction is
• Completion device Turns on and off depending on the completion status of the BUFSND
(D1)+1: instruction.
the BUFSND instruction is completed and turns off
[Operation while the BUFSND instruction is being executed]
END END END

BUFSND instruction Executed
Completion device
Sending data
15
• 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.
15.8 ZP.BUFSND
(5) Errors
263
(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).
264
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)
*1
Available device
Index Constant
register Others
register device
U\G
(S1) - - - -
(S2) - - - - -
(D1) - - - - - 15
(D2) - - - -
15.9 ZP.BUFRCV
(1) Setting data

"Un"/Un
(S1) *1 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 Device name
The start number of the bit device in the own station that System
(D2) turns on for one scan upon completion of the instruction. Bit
(2) Control data

Abnormal end
265
(3) Receive data
Setting
Device Item Setting data Set by
range
Stores the data length of the data read from the fixed
buffer data area. (Depending on the procedure of fixed
-
buffer communications, the data length is the number of
words or the number of bytes.)
Receive data Procedure exists (communications using a binary
(D1)+0 1 to 1017 System
length code): Number of words
1 to 508
No procedure (communications using a binary
1 to 2046
code): Number of bytes
(D1)+1
Stores the data read from the fixed buffer data area
to Receive data - System
starting from the smallest address.
(D1)+n
(4) Functions
• This instruction reads the receive data (for fixed buffer communications) of the connection specified by (S1)
CPU module E71

(D1) Receive data length No.1
Receive data :
BUFRCV
: No.n
: :
Receive data No.16
266
• Completion of the BUFRCV instruction can be checked with Completion device (D2)+0 and (D2)+1.
• Completion device Turns on at the END process of the scan where the BUFRCV instruction is
• Completion device Turns on and off depending on the completion status of the BUFRCV
the BUFRCV instruction is completed and turns off
[Operation while the BUFRCV instruction is being executed]
END END END

BUFRCV instruction Executed
Completion device
Receiving data Storing the receive data

15
• 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.
15.9 ZP.BUFRCV
● When receive data is read from the same connection, the BUFRCVS instruction (for an interrupt program) cannot be
used together.
(5) Errors
267
(6) Program example
The following shows a sample program that reads the receive data from the fixed buffer of connection number 1
268
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) (D2)
*1
Available device
Index Constant
register Others
register device
U\G
(S1) - - - -
(D1) - - - - -
*1 If the own station is a Basic model QCPU (function version B or later) or Universal model QCPU, " " (double quotation) of 15
the first argument can be omitted.
(1) Setting data
15.10 Z.BUFRCVS
"Un"/Un
(S1) Connection number (1 to 16) BIN 16-bit
(D1) Start number of the device that stores receive data System Device name
(2) Receive data
Setting
Device Item Setting data Set by
range
Stores the data length of the data read from the fixed
buffer data area. (Depending on the procedure of fixed
-
buffer communications, the data length is the number of
words or the number of bytes.)
Receive data Procedure exists (communications using a binary
(D1)+0 1 to 1017 System
length code): Number of words
1 to 508
No procedure (communications using a binary
1 to 2046
code): Number of bytes
(D1)+1
Stores the data read from the fixed buffer data area
to Receive data - System
starting from the smallest address.
(D1)+n
269
(3) Functions
• This instruction reads the receive data (for fixed buffer communications) of the connection specified by (S1)
CPU module E71
(D1) Receive data length No.1
Receive data :
BUFRCVS
: No.n
: :
Receive data No.16
[Operation while the BUFRCVS instruction is being executed]
Program Scan END process
Interrupt program
BUFRCVS instruction Executed
Storing
Receiving data the receive data
• The Z.BUFRCVS instruction is executed in an interrupt program, and the process is completed within one
scan.
● To read receive data using an interrupt program, configure both the interrupt settings and interrupt pointer setting
parameters of the programming tool. ( Page 152, 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.
270
(5) Program example

The following shows a sample program that reads the receive data from the fixed buffer of connection number 2
Enable the interrupt

program.
Execute the BUFRCVS

instruction.
15
15.10 Z.BUFRCVS
271
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)
*1
Available device
Index Constant
register Others
register device
U\G
(S1) - - - - -
(D1) - - - -
*1 If the own station is a Basic model QCPU (function version B or later) or Universal model QCPU, " " (double quotation) of
the first argument can be omitted.
(1) Setting data

"Un"/Un User
of the three-digit I/O number) 16-bit
272
(2) Control data

Abnormal end
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
Clear target 0101H: Communication status - status for each As described in
(S1)+2 User
specification protocol the left
0102H: Communication status - e-mail
receiving status
0103H: Communication status - e-mail sending
status
FFFFH: Clears all of the above 15
Specify the function to be cleared.
Clear function 0000H,
(S1)+3 0000H: COM.ERR LED off, error code clear User
specification FFFFH
FFFFH: Error log clear
(S1)+4
to System area - - -
(S1)+7
15.11 ZP.ERRCLR
(3) Functions
• This instruction turns off the COM.ERR. LED and clears error information listed below for the module
specified by Un.
Target Function
Error information to be cleared
Item specification specification
(buffer memory)
(S1)+2 (S1)+3
• Initial error code (address: 69H)
Initial error 0000H 0000H
• COM.ERR. LED off
• Open error code for a connection with the
Open error 0001H to 0010H 0000H
connected device (address: 7CH, 86H…)
Error log 0100H FFFFH Error log (address: E3H to 174H)
Status for each Clears communication status.

0101H FFFFH
protocol (address: 178H to 1FFH)
Communication E-mail receiving E-mail receiving

0102H FFFFH
status status (address: 5871H to 5B38H)
E-mail sending E-mail sending

0103H FFFFH
status (address: 5B39H to 5CA0H)
All FFFFH FFFFH Clears all of the above.
273
• Completion of the ERRCLR instruction can be checked with Completion device (D1)+0 and (D1)+1.
• Completion device Turns on at the END process of the scan where the ERRCLR instruction is
• Completion device Turns on and off depending on the completion status of the ERRCLR
the ERRCLR instruction is completed and turns off
[Operation while the ERRCLR instruction is being executed]
END END END

ERRCLR instruction Executed
Completion device
Clearing the error
• The ZP.ERRCLR instruction is executed on the rising edge (OFF ON) of the clear command.
(4) Errors
(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 error code of

the connection No.1.
Specify the error code clear.
Execute the ERRCLR instruction.

(Error information is cleared.)
274
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)
*1
Available device
Index Constant
register Others
register device
U\G
(S1) - - - - -
(D1) - - - -
the first argument can be omitted. 15
(1) Setting data
15.12 ZP.ERRRD
"Un"/Un User
275
(2) Control data

(S1)+1 Completion status 0000H: Normal completion - System
Values other than 0000H (error code): Abnormal end
Specify error information to be read.

Read information 0000H: Initial error code 0000H,
(S1)+2 User
specification 0001H to 0010H: Open error code for a connection 0001H to 0010H
with the connected device
Read target
Specify whether to read the latest error information.
(S1)+3 information 0000H User
0000H: Reads the latest error information.
specification
Stores the error information that has been read.
(S1)+4 Error information 0000H: No error - System
(S1)+5
to System area - - -
(S1)+7
276
(3) Functions
• This instruction reads the error information of the module specified by Un.
Target specification Function Error information to be read

Item
(S1)+2 specification (S1)+3 (buffer memory)
Initial error 0000H 0000H Initial error code (address: 69H)
Open error code for a connection with the

Open error 0001H to 0010H 0000H
connected device (address: 7CH, 86H…)
• Completion of the ERRRD instruction can be checked with Completion device (D1)+0 and (D1)+1.
• Completion device Turns on at the END process of the scan where the ERRRD instruction is
• Completion device Turns on and off depending on the completion status of the ERRRD instruction.
(D1)+1:
the ERRRD instruction is completed and turns off
15
[Operation while the ERRRD instruction is being executed]
END END END

ERRRD instruction Executed
Completion device
15.12 ZP.ERRRD
Reading the
error information
• The ZP.ERRRD instruction is executed on the rising edge (OFF ON) of the read command.
(4) Errors
277
(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 error code of

the connection No.1.
Specify the latest error information.
Execute the ERRRD instruction.

(Error information is read.)
278
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)
*1
Available device
Index Constant
register Others
register device
U\G
(S1) - - - - -
(D1) - - - -
the first argument can be omitted. 15
(1) Setting data
15.13 ZP.UINI
"Un"/Un User
279
(2) Control data
Completion
(S1)+1 0000H: Normal completion - System
status
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
Specification 1: Change 0000H
(S1)+2 of changed • Specification of the Ethernet operation setting change (b1): Specify to User
item whether to change the Ethernet operation setting. 5000H
(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
00000001H
(S1)+3 Own station
Specify the IP address of the own station. to User
(S1)+4 IP address FFFFFFFEH
Specify the Ethernet operation setting.

0: Binary Code
1: ASCII Code
0: Use the Ping
1: Use the KeepAlive
Ethernet • Send frame setting (b5)
As described in
(S1)+5 operation 0: Ethernet User
the left
setting 1: IEEE 802.3
• Setting of write enable/disable at RUN time (b6)
0: Disable
1: Enable
0: Do not wait for OPEN (Communications impossible at STOP
time)
1: Always wait for OPEN (Communications possible at STOP time)
*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.)
280
(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.
• Completion device Turns on at the END process of the scan where the UINI instruction is
• Completion device Turns on and off depending on the completion status of the UINI instruction.
(D1)+1:
the UINI instruction is completed and turns off at
the next END process.
[Operation while the UINI instruction is being executed]
Close process
END END END END

Program Scan Scan Scan Scan Scan
process process process process

signal (X19)
15
(address: 5000H)
Executed
UINI instruction
Completion device
15.13 ZP.UINI
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
re-initialize 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.)
• In a redundant system, do not change parameters such as IP address and Ethernet operation setting using the
UINI instruction. If changed, normal communications cannot be performed. Change the parameters using a
programming tool.
281
(4) Errors
(5) Program example

The following pages show sample programs that change the following setting items using the UINI instruction.
• 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. ( Page 360, Appendix
4.2)
282
(a) Changing the Ethernet operation setting

The following shows 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.
Enable writing
during RUN.
15
15.13 ZP.UINI
Communications enabled
modified using the I/O signals of the intelligent function module corresponding to the buffer memory. For use with safety
CPUs, refer to the following.
283
(b) Changing the transmission speed and communication mode
The following shows a sample program that changes the transmission speed to 10Mbps and the
communication mode to half-duplex (when the I/O signals of the E71 are X/Y00 to X/Y1F).
Change the settings

to 10Mbps and
half-duplex.
284
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
16
1. Connect the CPU module to a programming tool,
and open the "System Monitor" window.
16.1 Before Troubleshooting

[Diagnostics] [System Monitor]
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.
285
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
• Troubleshooting by symptom
286
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 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
287
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 is stored in Area for module status (address:
C8H) of the buffer memory. ( Page 38, Section 3.5.2)
16.4.1 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 mounted properly? Securely mount the E71 on the base unit.
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 377, Appendix 6.2)
• Self-loopback test ( Page 376, Appendix 6.1)
16.4.2 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 285, Section 16.2)
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". ( Page 342, Section 16.8)
288
16.4.3 If the SD 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 Action

Is the ERR. LED or COM.ERR. LED on? 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 there
Are the cables properly connected? is a problem with the cable connection and the Ethernet line.
( Page 366, Appendix 5)
Is the program correct? Correct the send program of the E71.
16.4.4 If data cannot be received with the RD LED off
The following table lists the items to be checked and the actions to be taken when an E71 cannot receive data with the
RD LED off.
16
Check item Action
16.4.3 If the SD LED does not flash when data is sent

16.4 Checking the LEDs
Is the ERR. LED or COM.ERR. LED on? 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 there
Are the cables properly connected? is a problem with the cable connection and the Ethernet line.
Correct the IP address, router setting, and subnet mask setting of the own
Are the parameter settings correct?
station.
Is the program correct? Correct the send program of the connected device.
289
16.5 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. ( Page 285, Section 16.2)
16.5.1 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 RUN LED on the E71, the
Is the RUN LED of the E71 on? 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? ( Page 65, CHAPTER 5)
• Securely lock the cable.

Is the cable securely connected?
• Check the wiring. ( Page 79, Section 6.2)
Set the network parameter mode to "Online".

Is the network parameter mode set to "Online"?
If the data code settings do not match, data cannot be sent or received because the connected device
Does the communication data code (ASCII or binary) cannot normally decode commands.*2 Set the same data code as that of the connected device in
setting match with that of the connected device? "Communication Data Code" of the Ethernet operation setting.
• If Initial normal completion signal (X19) is off, perform the initial process. ( Page 366,
Has the initial process been completed normally? (Is Appendix 5)
Initial normal completion signal (X19) on?) • 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 Restart all the devices on the line.*1
same IP address?
Power off the E71-mounted station and ground the LG and FG terminals of the power supply module.
When the E71 is connected to 10BASE2, are the LG
and FG terminals of the power supply module ( User's manual (hardware design, maintenance and inspection) for the CPU module used)*3
grounded? After grounding the terminals, start the E71 to perform communications with the connected device
again.
If the access from the connected device is denied by the IP filter function, correct the values in IP filter
Is the access from the connected device set to be settings (address: 5700H to 5721H) and perform IP filter setting by the reinitialization process again.
denied by the IP filter function?
*1 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.
*2 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 158, Section 12.6.2 (1) (e), Remark)
*3 If the LG and FG terminals of the power supply module of the E71-mounted 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. ( Page 292, Section 16.5.4 to Page 301, Section 16.5.16)
290
16.5.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
Check item Action

Are there many detected errors in Simultaneous
There may be a heavy load on the Ethernet line due to data sending and
transmission error detection count (address: 18EH and
receiving between connected devices.
18FH)? • Taking action such as separating networks or decreasing the number of data
Has the error code C0C7H been stored in Error code/end sending reduces the load on the Ethernet line.
code (address: E5H ) in the error log block? • 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. ( Page 146, Section 12.4.1)
(address: 5240H)?*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 175, 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. 16
*1 Available only for the QJ71E71-100.
16.5.2 The E71 frequently fails to receive a message sent from the connected device.
Availability depends on the QJ71E71-100 version. ( Page 353, Appendix 3)
16.5.3 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"?
(If a dedicated instruction is executed in the "Offline" mode, no error occurs but
the instruction is not completed.)
291
16.5.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
because the connected device cannot normally decode commands.*2 Use
Does the communication data code (ASCII or binary) setting
the same setting of "Communication Data Code" in the Ethernet operation
match with that of the connected device?
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,
Correct the command format.
device, address, and others?
Check the checkbox next to "Enable Write at RUN time" in the Ethernet
Is the write operation during RUN enabled?
operation setting.
Has an open or initial error occurred in the error log area? Check and correct the error.
*1 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.
*2 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 158, Section 12.6.2 (1) (e), Remarks)
292
16.5.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.
16.5.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

• Check if the open/close processes for I/O signals and the OPEN/CLOSE
Has the connection with the connected device been opened? instructions are not used together for the same connection. If so, correct
(Check the corresponding bit of 5000H in the buffer memory.) 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 Protocol in the open setting match with that of the
connected device (TCP/IP or UDP/IP)?
Check and correct the settings if they are unmatched.
16
• Set "Predefined protocol" to Fixed Buffer Communication in the open
setting.
Is "Predefined protocol" set to Fixed Buffer Communication
• Configure the setting so that the fixed buffer setting (Send or Receive) in
in the open setting?
16.5.5 Communications using SLMP cannot be performed.

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.
Check the error code in the ECPRTCL instruction completion status area
Was the ECPRTCL instruction completed normally?
and correct the error.
Is the execution protocol number set to the control data of Set the execution protocol number to the control data of the ECPRTCL
the ECPRTCL instruction? instruction.
Is the communication status of the connected device
Correct the error in the connected device.
normal?
*1 For details on the settings, refer to Page 253, Section 15.7 (3).
293
16.5.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 Action

Are the values in Protocol setting data error information
Write the protocol setting data to the E71 because they have not been
(address: 5324H to 5327H) and Number of registered
written.
protocols (address: 5328H) set to 0?
(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.
294
16.5.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

• 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.
Check the error code in the BUFSND instruction completion status area
Was the BUFSND instruction completed normally?
Has the data length of the send data been set in the control
Write the data length. 16
data?
Correct the error in the connected device.
normal?
16.5.8 Data cannot be sent with communications using a fixed buffer.

295
16.5.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

If the amount of the actually received data is smaller than the receive data
Does the receive data length match with the amount of data
length, receive the remaining data. If it is larger than the receive data
actually received?
length, receive the excess data as the next request message or discard it.
Is the reception completion signal of the corresponding fixed
Data was not sent from the connected device. Check the connected device
buffer on? (Check the corresponding bit of 5005H in the
on the sending side and correct the error.
buffer memory.)
• 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.
Check the error code in the BUFSND instruction completion status area
Was the BUFRCV instruction completed normally?
• 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.
296
16.5.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

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 memory.) 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 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.
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
Correct the buffer memory address and send the command again.
command?
Has data been set in the specified address of the random
Write the data.
access buffer?
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
16.5.10 Communications using a random access buffer cannot be performed.

16.5.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.
297
16.5.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 Action

Was the MSEND instruction executed? Correct the execution conditions of the MSEND instruction.
Check the error code in the MSEND instruction completion status area and
Was the MSEND instruction completed normally?
the e-mail sending error log to correct the error.
Check with the system administrator that the following settings are correct:
Is the error response received from the mail server using the
• DNS setting
MRECV instruction?
• 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 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.
• Correct the following so that the monitoring condition disable time
becomes longer than the value set in "PLC Inquiry Interval".
• PLC Inquiry Interval
• Condition Device
Were the second and subsequent sendings performed using
• Correct the following so that the sending time of the SMTP server and the
the programmable controller CPU monitoring function?
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?
298
16.5.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 Action

Was the MRECV instruction executed? Correct the execution conditions of the MSEND instruction.
Check the error code in the MRECV instruction completion status area and
Was the MRECV instruction completed normally?
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.
• Check and correct the e-mail parameter settings.
Is the receive data value incorrect? (Are the characters in the
• Check if the mail server system is down.
subject garbled?)
• 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
station.
Is a device other than the E71 sending the data?
For Outlook Express, select "Properties"  "Details". In the header
information, check that the setting is
"Content-Type:text-plain:charset=iso-2022jp". If charset of header
information is "EUC-jp" or "SHIFT-JIS", correct it to "iso-2022jp".
Because the E71 does not decode received data, it cannot receive an
Is the E71 sending the data?
e-mail normally. Try to send an e-mail from a device other than the E71. 16
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.
16.5.13 An e-mail cannot be received.

Did the sending device send the e-mail in the ASCII code or • When the destination is a personal computer, use another mailer. If the
convert the ASCII code further into the ASCII code? 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.
299
16.5.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

Correct the error of the connected device.
normal?
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
Check and correct the arrival monitoring time.
increased?
Does an error occur even after the setting value in "TCP
Check and correct the setting value in "TCP Resend Timer".
Resend Timer" in the initial setting is increased?
Are the routing parameter settings correct? 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))
16.5.15 Communications cannot be performed during OPS

connection in a redundant system.
The following table lists how to troubleshoot the problem when an E71 cannot perform communications during OPS
connection in a redundant system.
Check item Action

Is "OPS connection" set under "Open system" of the open
Set "OPS connection" under "Open system" of the open setting.
setting?
Is the own station port number of the E71 correct? Correct the own station port number of the E71.
Is the IP address of the OPS correct? Correct the IP address of the OPS.
The MELSOFT connection and MC protocol cannot be used together for a connection set for the OPS connection. In
addition, a port set for the OPS connection can be connected using EZSocket only.
If the action above does not solve the problem, there may be other causes or the connected device may be in failure.
300
16.5.16 Systems cannot be switched in a redundant system.
The following table lists how to troubleshoot the problem when systems cannot be switched in a redundant system.
Check item Action

• Use SD1590 of the control system CPU module to check if the E71 has
Has the E71 issued a system switching request to the issued a system switching request.
control system CPU module? • Check Error log area (address: E3H to 174H) of the E71 connected to the
control system CPU module. Then correct the error.
Has "Issue system switch in communication error" been Select "Issue system switch in communication error" in the "Redundant
selected in "Redundant settings"? settings".
Has the correct number been selected in "System switching
Select the correct number in "System switching settings when
settings when communication error occurs” in "Redundant
communication error occurs" in the "Redundant settings".
settings"?
Do the settings of the programming tool match those of the After writing the parameters to the CPU module, power off and on the CPU
buffer memory? module or reset the system.
Has disconnection been detected? Check if the communication target is faulty.
Has "Issue system switch in Cable disconnection timeout" Select "Issue system switch in Cable disconnection timeout" in "Redundant
been selected in "Redundant settings"? settings".
Is the disconnection detection monitoring time setting
Check and correct the disconnection detection monitoring time setting.
correct?
Is the setting value in "TCP ULP Timer" in the initial setting
Check and correct the setting value in "TCP ULP Timer".
correct?
16
Has "Confirm" been selected in "Existence Confirmation" in
Select "Confirm".
the open setting?
Is the setting value in "Dest. Confirmation Start Interval" in
Check and correct the setting value in "Dest. Confirmation Start Interval".
the initial setting correct?
16.5.16 Systems cannot be switched in a redundant system.

Is the setting value in "Dest. Confirmation Interval" in the
Check and correct the setting value in "Dest. Confirmation Interval".
initial setting correct?
Is "Broadcast Communications" displayed in "Transmission Set the IP address of the communication target station in "Transmission
target device IP address" in the open setting? target device IP address".
Is the connection open? Open the connection.
Has the group setting been configured? Check the connected CPU module.
Is the power supply module of the standby system on? Power on the power supply module of the standby system.
Is the RESET/L.CLR switch of the standby system CPU
Set the RESET/L.CLR switch to the central position (reset clear).
module set to the central position (reset clear)?
Is the tracking cable connected properly? Connect the tracking cable properly.
Is the standby system CPU module operating normally? Check and correct the error of the standby system CPU module.
Is the connected CPU module the control system? Set the connected CPU module as the control system.
Is there any cause, such as a standby system CPU module
Remove the cause of the system switching failure.
stop error, which disables system switching even when the
E71 issues a system switching request?
Is the CPU module in the backup mode? Change it from the separate mode to the backup mode.
301
16.6 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.
Buffer memory area that stores the

Error type Description
error code
• Setting value error

Errors occurring in the initial process Page 303, Section 16.6 (1)
• Initial process error
• Setting value error
Errors occurring in the open process Page 303, Section 16.6 (2)
• Open process error
Errors occurring in communications using a
• Specified data error Page 303, Section 16.6 (3),
fixed buffer (sending) with the connected
• Sending error Page 303, Section 16.6 (4)
device
• Specified data error
Errors occurring in communications using a • Communication error (excluding errors occurring in
Page 303, Section 16.6 (4)
fixed buffer with the connected device communications using a fixed buffer (sending) with
the connected device)
• Errors returned in communications using a fixed
buffer (end code)
-
Errors returned to the connected device when • Errors returned in communications using a random
communicating with it access buffer (end code)
Errors returned in communications using the MC End code or error code for each
protocol command
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
Page 304, Section 16.6 (5)
"Description" column), and whose error codes communications
are stored in the error log area • Errors that have occurred in communications using
a random access buffer
Errors occurring in data communications • Setting data error Page 305, Section 16.6 (6)
using the predefined protocol • Receiving error Page 307, Section 16.6 (7)
Errors (response commands) occurring in Refer to the QnUCPU User's
communications with the destination using the Manual (Communication via
• Communication error
file transfer (FTP server) function Built-in Ethernet Port).
Errors occurring in communications using the
Communication error Page 308, Section 16.6 (8)
Web function
• Setting data error
Errors occurring when an e-mail is received Page 309, Section 16.6 (9) (a)
• Receiving error
• Setting data error
Errors occurring when an e-mail is sent Page 311, Section 16.6 (9) (b)
• Sending error
Errors occurring in communications using Not stored (stored in the
data link instructions from the CPU module of complete status area of the
• Communication error
the own station instructions)
Errors occurring in communications using the Not stored (stored in the
dedicated instructions from the CPU module complete status area of the
• Communication data error
of the own station instructions)
302
(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
connection with the connected device are stored in binary. Process the end codes in the responses according to

the destination.
303
(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. ( Page 38, Section 3.5.2)
Buffer memory name Address Description

The number of errors registered in the error log block area is stored. When the number of
Number of errors E3H
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
Error An error code indicating error details is stored. The subheader code of the error message is
code/end E5H stored in bits 0 to 7 of the corresponding area. (Bits 8 to 15 store 0.) For errors below the
code TCP/IP or UDP/IP level, 0 is stored.
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.
b15 to b0 b15 to b8 b7 to b0
Command
E7H Command code or Subrequest type Request type
code
0 is stored in the following cases:
Error log • For messages not containing a command code
block • For errors below the TCP/IP or UDP/IP level (because their commands are unknown)
Connection The number of the error connection is stored in bits 0 to 7 of the corresponding area. (Bits 8
E8H
No. to 15 store 0.) For errors below the TCP/IP or UDP/IP level, 0 is stored.
Own station The port number of the error own station is stored. For errors below the TCP/IP or UDP/IP
E9H
port No. level, 0 is stored.
The IP address of the error connected device is stored. 0 is stored in the following cases:
Destination
EAH and EBH • For errors below the IP level
IP address
• When an error response was sent through the CPU module
Destination The IP address of the error connected device is stored. For errors below the TCP/IP or
ECH
Port No. UDP/IP level, 0 is stored.
The number of occurrences of the corresponding status of each protocol is stored. When the
Status for each protocol 178H to 1FFH
count value by the E71 exceeds two words, the count stops at FFFFFFFFH (4294967295).
*1 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
*2 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-mounted 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.
304
(6) Protocol setting data check area (address: 5320H to 533FH)

The following table lists the details of the protocol setting data check area.

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.
(Valid when the Protocol No. value is 1 to 128)
Setting type 5325H
• 0: Packet setting or element setting
• 1: Protocol detailed setting
Protocol • 65535: Unidentified*1
setting data When an error is detected in the protocol setting data, the packet No. where an error has
error been detected is stored.
information The send packet is checked first, then receive packet (expected packet) is checked from the
lowest packet No. and the first packet No. where an error has been detected is stored.
Packet No. 5326H
(Valid when the Setting type value is 0)
• 0: Send packet
• 1 to 16: Receive packet 16
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
Element No. 5327H error has been detected is stored.
(Valid when the Setting type value is 0)
• 1 to 32: Element No.
Number of registered protocols in the protocol setting data is stored.
Number of registered When the check results include any error, 0 is stored.
5328H
protocols • 0: No registration
• 1 to 128: Number of registrations
305
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 Registration status of

protocol No.16 protocol No.1
b15 b14 b13 to b2 b1 b0
Buffer memory address 5330H to
5331H to
0 (OFF): Not registered
1 (ON): Registered
5330H to
Protocol registration
533FH
5337H to
Registration status of Registration status of

protocol No.128 protocol No.113
5338H to
Unused
(reserved)
533FH to
*1 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)
306
(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. ( Page 38, Section 3.5.2)

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 Verification result of receive packet No.1 is stored. ( Page 307, Section 16.6 (7) (a))
result (receive packet 54C2H • b0 to b7: Element No. where the verification result did not match
No.1) • b8 to b15: The cause of mismatch (verification result code)
Received data verification
54C3H to
result (receive packet No.2 The bit configuration is the same as receive packet No.1.
54D1H
to 16)
The number of protocol executions in Connection No.1 is stored.
Number of protocol • 0: No protocol execution
54D2H
executions • 1 to 65535: Number of executions (When the number exceeds 65535, the value remains 16
65535.)
Cancels the protocol executed in Connection No.1.
Protocol cancellation • 0: No cancellation specification
54D3H
specification • 1: Cancellation request (set by user)

• 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
307
(b) The cause of mismatch (verification result code) (b8 to b15)
Stored
Description Cause
value
00H Normal -
The total packet size of receive data is smaller than that set in protocol
01H Insufficient receive data
data.
10H Data not matched The receive data do not match the value set in protocol data.
When "ASCII Hexadecimal" is set in Code Type, data not in ASCII
11H ASCII-binary conversion error
code are received.
12H Data length error The received Length value exceeded 2046 bytes.
The Length value received from the connected device does not match
30H Data length size error
the actual length.
FFH Verification not performed -
(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. ( Page 38, Section 3.5.2)

The number of the error log block where the latest error log is registered is stored.
• 1 or more: The number of the error log block where the latest error log is registered.
Error log pointer 5101H
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
The number of times the HTTP response code was returned from the E71 to the Web browser
Log counter 5101H to 5106H
is stored.
HTTP
5108H The HTTP response code in case of an error is stored.
response code
Destination IP
5109H to 510AH The IP address of the server in case of an error is stored.
address
The time when the error occurred is stored in the BCD code.
Error b15 to b8 b7 to b0
log Month (01H to 12H) Year (00H to 99H): Last two digits of the year
block b15 to b8 b7 to b0
Error time 510BH to 510EH Hour (00H to 23H) Day (01H to 31H)
b15 to b8 b7 to b0
Second (00H to 59H) Minute (00H to 59H)
b15 to b8 b7 to b0
Year (00H to 99H): First two digits of the year Day of the week (0 to 6)
*1 An error log block area consists of 16 error log blocks that have the same data order.
308
(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.
(a) Receive area

The number of remaining e-mails returned when the E71 inquired the receive mail
server is stored.
Number of mails remaining on the
5870H • 0: No received mail in the server
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 stored.
Dedicated instruction normal • 0: The MRECV instruction has not been executed or no executions have resulted
5871H
completion count 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
stored.
Dedicated instruction abnormal
completion count
5872H • 0: The MRECV instruction has not been executed or no executions have resulted
in abnormal end.
16
• 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 area is stored.

Normal receiving count 5873H
• 0: No mail has been transferred.
• 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 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 setting is stored.
Server inquiry count 5875H
• 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 receive mail server is stored.
Server communication error count 5876H
• 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.
• 1 or more: The number of the error log block where the latest error log is
Receiving error log write pointer 5878H 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
309
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
communications with the mail server are stored in the ASCII code.
From 587BH
(Example) If the sender's e-mail address is "[email protected]",
"[email protected]" is stored in the ASCII code.
The date and time when the e-mail was received are stored in the BCD code.
b15 to b8 b7 to b0
Month (01H to 12H) Year (00H to 99H): Last two digits of the year
Error log block
b15 to b8 b7 to b0
Date 5883H Hour (00H to 23H) Day (01H to 31H)
b15 to b8 b7 to b0
Second (00H to 59H) Minute (00H to 59H)
b15 to b8 b7 to b0
Year (00H to 99H): First two digits of the year Day of the week (0 to 6)
The first 30 words of the e-mail subject are stored. A subject is not stored
Subject 5887H successfully if it contains characters other than alphanumeric and ASCII code
characters.
*1 A receiving error log block area consists of 16 error log blocks that have the same data order.
310
(b) Send area

The cumulative number of normal completions of the dedicated instruction (MSEND) is
stored.
Dedicated instruction normal
5B39H • 0: The MSEND instruction has not been executed or no executions have resulted in normal
completion count
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 stored.
Dedicated instruction • 0: The MSEND instruction has not been executed or no executions have resulted in
5B3AH
abnormal completion count 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 server is
Number of mails normally stored.
5B3BH
completed • 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 stored.
Sending to the server count 5B3DH • 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 requests to the
Number of mails abnormally send mail server is stored.
completed
5B3EH
• 0: No communication error between servers or no e-mail sent
16
• 1 or more: The cumulative number of communication errors
The cumulative number of registrations in the send error log block area is stored.
Error log write count 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 is
registered.
Sending error log write pointer 5B40H
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 communications
with the mail server are stored in the ASCII code.
To 5B43H
Error log (Example) If the sender's e-mail address is "[email protected]",
block "[email protected]" is stored in the ASCII code.
The date and time when the e-mail was sent are stored in the BCD code (similar to 5883H of
Date 5B4BH
(a)).
The first 15 words of the e-mail subject are stored. A subject is not stored successfully if it
Subject 5B4FH
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.
311
16.6.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 Communications Communications
Error description Action MC protocol
code using a fixed using a random
communications
buffer access buffer
• When each communication
00H • Normal completion is normally completed, the
error code 00H is stored.
• Check and correct the

• The device range destination of devices
02H specified start device and
to be read/written from/to is incorrect.
the number of points.
• Codes for the command/response type of
a subheader are not within the
specifications. • Check and correct the
• MC protocol communications: 00H to 3CH command/response type set
for the connected device.
• Communications using a fixed buffer: 60H
(Because the E71
• Communications using a random access
automatically adds the
50H buffer: 61H, 62H
command/response type,
• In communications using a fixed buffer, if the user setting is not
the data length setting is smaller than the required.)
actual data amount, the remaining data is • Check and correct the data
processed as the second data. In this length.
case, a subheader undefined command
type error may occur.
• In communications using a random
access buffer, the start address specified • Check and correct the
51H
by a connected device has been set specified start address.
outside the range from 0 to 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 • Check and correct the start
connected device exceeds the range from address and the number of
52H 0 to 6143. data words.
• Data by the number of words specified • Correct the number of
(text) cannot be sent in one frame. (The read/write points.
data length value or the amount of the text
sent/received are not in the allowable
range.)
• When "ASCII Code" has been selected in
the communication data code setting in
• Check and correct the data
the Ethernet operation setting, ASCII
54H sent from the connected
code data which cannot be converted into
device.
binary code data has been sent from the
connected device.
• Enable (select) "Enable
• When "Enable Online Change" was Online Change" in the
disabled (or not selected) in the Ethernet Ethernet operation setting
operation setting, the connected device and write data. (However, a
requested a data write while the CPU parameter, program, or
55H module was running. microcomputer program
• While the CPU module was running, the cannot be written while the
connected device requested for writing a CPU module is running.)
parameter, program, or microcomputer • Set the switch on the CPU
program. module to STOP and write
the data.
312

communications
• The connected device specified a wrong • Correct the device
56H
device. specification.
• 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 • Correct the specified points
process. or the start address (device
• Addresses from the start address (start number and step number).
device number and start step number) to
the specified number of 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
• Check the data length of the
specifications.
57H command and set the data
• When data is written, the set number of
again.
write data points is different from the
specified number of points.
• A monitor request was issued even • Register the monitoring
though monitoring data is not registered. data.
• Data cannot be read
• For data read/write in a microcomputer
from/written to an area with
program, an address after the last
an address after the last
address that can be set in the parameter
address. Correct the
setting has been specified.
specified address. 16
• In the block number specification of the
extension file register, a block number
• Correct the block number.
exceeding the range of the corresponding
memory cassette size has been specified.
16.6.1 End codes returned to a connected device during data communications

• The start address (start device number
and start step number) of a command
specified by a connected device has been
set outside the range that can be • Correct the value to the one
specified. within the range that can be
• For data read/write in a microcomputer specified for each process.
program or file register, values exceeding
the CPU module parameter setting range
has been specified.
58H • A block number specified for an extension

• Correct the block number.
file register does not exist.
• Correct the device
• A file register cannot be specified.
specification.
• A word device has been specified for the
command for bit devices.
• The start number of bit devices has been • Correct the command or
specified using a value other than a specified device.
multiple of 16 in the command for word
devices.
• An extension file register cannot be • Correct the device
59H
specified. specification.
• The CPU module and the E71 cannot
• Check the error code
communicate.
5BH appended to the end code
• The CPU module cannot process a
request from a connected device.
• The communication time between the
• Increase the CPU
60H CPU module and the E71 exceeded the
monitoring timer value.
CPU monitoring timer value.
313
communications
• After unlocking the remote
password using the MC
protocol, perform
communications using a
• In communications using a fixed buffer,
fixed buffer.
63H the remote password of the port for the
• Exclude ports used for
destination E71 is in the lock status.
communications using a
fixed buffer from the targets
of the remote password
check.
A0H
• The error details and how to troubleshoot the problem are the same as those for the error code stored in the buffer memory. ( Page 316,
to
FFFFH Section 16.6.3)
314
16.6.2 Abnormal codes returned during communications using an

A-compatible 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 code Error Error description Action

The PC number specified with a command is Change the PC number to FFH of the own
not FF of the own station or not the station station or not the station number set using the
10H PC number error
number set with the MELSECNET link link parameter to perform communications
parameters. again.
After the E71 receives a request from the
connected device normally, communications Perform communications again. If the error
11H Mode error cannot be normally performed between the E71 occurs again, check for noise and other causes
and the CPU module due to some causes such and/or replace the E71.
as noise.
The specified intelligent function module
number has not been assigned to an intelligent Change the specified data contents in the
16
Intelligent function
function module that has the buffer memory and control procedure or change the mounting
12H module designation
where communications can be performed. (For position of the intelligent function module. Then
error
example, the specified module is an I/O module perform communications again.
16.6.2 Abnormal codes returned during communications using an A-compatible 1E frame

or the specified slot is empty.)
Check if the remote STOP/PAUSE has been
The remote RUN/STOP cannot be executed.
already executed from another module. Then
18H Remote error (The remote STOP/PAUSE has been already
cancel the operation to perform
executed from another module.)
communications again.
• Correct the specified device.
1FH Device error Invalid device specification
• Do not access a device which does not exist.
Check if the CPU module of the station number
The CPU module of the request destination has set for the PC number has been disconnected.
20H Link error
been disconnected from the data link. Then remove the cause of the disconnection to
perform communications again.
Memory access to the intelligent function
module cannot be performed due to the There is a hardware problem with the CPU
Intelligent function following causes: module, base unit, intelligent function module,
21H
module bus error • The control bus to the intelligent function or the E71. Please consult your local Mitsubishi
module is faulty. representative.
• The intelligent function module is in failure.
315
16.6.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.
Error
Error description Action
code
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
0056H in data communications. ( Page 312, Section 16.6.1)
0057H
0058H
0059H
005BH
0060H
0063H
This request cannot be specified in connection with the • Correct the request details.
00A0H
connected device. • Correct the open setting.
Contents of the request cannot be analyzed because • Check and correct the text length or request data length of the Qn
00A1H
the text length or request data length is too short. header. Then send data to the Ethernet module again.
00A2H This request cannot be processed. • Correct the request details and command.
3E8H • Refer to the troubleshooting section of the user's manual
to (Errors detected by a programmable controller CPU) (hardware design, maintenance and inspection) for the CPU
4FFFH module used, and take corrective action.
7000H
(Errors detected by a module such as a serial • Refer to a manual such as a serial communication module user's
to
communication module) manual, and take corrective action.
7FFFH
B000H
• Refer to the CC-Link System Master/Local Module User's Manual,
to (Errors detected by a CC-Link module)
and take corrective action.
BFFFH
• The IP address setting value of the E71 for the initial

process is incorrect. • Correct the IP address. Set the class to A/B/C.
C001H
• The setting value of the subnet mask field for the • Correct the subnet mask.
router relay function is incorrect.
Some of the various timer setting values for the initial
C002H • Check and correct each timer setting value for the initial process.
process are outside the allowable range.
The setting value of the auto-open UDP port number for
C003H • Check and correct the auto-open UDP port number.
the initial process is outside the allowable range.
C004H The setting value of the subnet mask field is incorrect. • Correct the subnet mask and perform the initial process again.
316
Error
code
• The setting value of the default router IP address for
the router relay function is incorrect. • Correct the default router IP address and perform the initial
• The network address (network address after the process again.
C005H
subnet mask) of the default router IP address is • Set the same network address as that of the IP address of the
different from that of the IP address of the Ethernet Ethernet module in the own station.
module in the own station.
The setting value of the subnet address for the router
C006H • Correct the subnet address and perform the initial process again.
relay function is incorrect.
• The setting value of the router IP address for the
router relay function is incorrect.
• Correct the router IP address and perform the initial process again.
• The network address (network address after the
C007H • Change the IP address of the Ethernet module in the own station
subnet mask) of the router IP address is different from
to the same address as the network address.
that of the IP address of the Ethernet module in the
own station.
The setting value in IP filter function type setting Correct the value in IP filter function type setting (address: 5701H)
C008H
(address: 5701H) is not correct. 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). Correct the values in IP address setting 1 to 8 (address: 5702H to
C009H • In IP address setting 1 to 8 (address: 5702H to 5721H) and perform IP filter setting by the reinitialization process
5721H), the value of start IP address is greater than again.
the end IP address.
The send/receive process has been executed while the Do not execute the send/receive process while executing the IP
C00EH
IP address in use detection function is being executed. address in use detection function.
16
• 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).
The setting value of the Ethernet module port number

C010H • Correct the port number.
for the open process is incorrect.
The setting value of the port number of the connected
C011H • Correct the port number.
device for the open process is incorrect.
The port number set is used in a connection already • Correct the port numbers of the Ethernet module and the
C012H
opened in TCP/IP. connected device.
The port number used in a connection already opened
C013H • Correct the port number of the Ethernet module.
is set for the open process in UDP/IP.
The initial process or open process of the Ethernet
C014H • Perform the initial process or open process.
module is not completed.
The setting value of the IP address of the connected
C015H • Correct the IP address. Set the class to A/B/C.
device for the open process is incorrect.
The open process of the connection (or the next • Check that none of the connections targeted for pairing open has
C016H connection) specified for pairing open has been already been opened.
completed. • 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 parameters.
A connection could not be established in the open • Correct the port number of the Ethernet module, the IP address
C017H
process of the TCP connection. and port number of the connected device, and the open setting.
• Check if the cable is disconnected.
• Check if there is a problem with the connection to the transceiver
or terminating resistor.
317
Error
code
The setting value of the IP address of the connected
C018H • Correct the IP address.
device is incorrect.
• Correct the data length.
C020H The data length exceeds the allowable range. • When the amount of data to be sent exceeds the limit, divide the
data into smaller chunks to send it.
An abnormal end response was received for • Read the response end code from the connection end code or
C021H
communications using a fixed buffer. error log area and perform the required action.
• 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.
C022H
• The connection with the connected device was closed • Check the open status of the connection with the connected
while waiting for a response. device.
• The connection with the connected device has not
been opened.
C023H • Open the connection with the connected device.
• The connection with the connected device has been
closed.
• When "Predefined protocol" is set in "Fixed Buffer
• Correct the connection number of
Communication" setting, communications using a
BUFSND/BUFRCV/BUFRCVS/ECPRTCL instructions.
fixed buffer or a random access buffer are executed.
C024H • Correct the "Fixed Buffer Communication" setting (Procedure
• When "Procedure Exist" or "No Procedure" is set in
Exist/No Procedure/Predefined protocol) of the corresponding
"Fixed Buffer Communication" setting, a predefined
connection.
protocol is executed.
• When starting the open by using the OPEN instruction, correct the
There is an error in the usage setting area when starting
usage setting area of the control data.
C025H the open process by the OPEN instruction or
• When starting the open by input/output signals, correct the
input/output signals.
connection usage setting area of the buffer memory.
• Check that connection cable with the engineering tool is not
disconnected and read/write/verify the predefined protocol setting
An error has occurred when reading/writing/verifying the
C026H data again.
predefined protocol setting data.
• Do not write data simultaneously when writing protocol setting data
from multiple engineering tools.
• Check the operation of the transceiver and connected device.
* Use a transceiver which can perform the SQE test.
• 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.
• Check the operation of the transceiver and connected device.
* Use a transceiver which can perform the SQE test.
C031H A sending error has occurred. • Check if the cable is disconnected.
Ethernet module.
318
Error
code
• Correct the TCP ULP timeout value and perform the initial process
again.
A TCP ULP timeout error has occurred in the TCP/IP
C032H communication. (The connected device does not send
an ACK response.)
• Correct the IP address of the connected device and the Ethernet
address.
• Use the default value (FFFFFFFFFFFFH ) if the connected device
has the ARP function. If it does not have the function, set the MAC
address.
There is no connected device with the IP address that
C033H • Check the operation of the connected device.
has been set.
On the ARP table, there is no connected device with the
C034H • Decrease the number of communication destinations.
IP address that has been set.
• Correct the settings of the alive check.
The existence of the connected device could not be
C035H
checked within the response monitoring timer value.
• Check if the cable is disconnected. 16

Because a cable is not connected or disconnected, the or terminating resistor.
C036H
send process cannot be executed. • Perform the loopback test to check for an error in the line.
Ethernet module.
• Not all the data could be received within the response
monitoring timer value.
• Correct the data length of the communication data.
• Sufficient data for the data length could not be
• Because there may be congestion of packets on the line, correct
C040H received.
the settings of the initial process.
• The remaining part of the message divided at the
• Send the same data from the connected device again.
TCP/IP level could not be received within the
response monitoring timer value.
• Correct the checksum value sent from the connected device and
send the correct value.
There is an error in the checksum of the receive data
C041H • Check the situation of the line, such as noise, the distance
when TCP is used.
between the line and power cable, and the grounding of each
device.
There is an error in the checksum of the receive data
when UDP is used.
device.
The checksum in the header of the IP packet received is
incorrect.
device.
319
Error
code
C044H An error packet of ICMP was received.
• If an alive check timeout occurs, correct the IP assembly timer
value of the connected device.
An error packet of ICMP was received. (An IP assembly • Check if the cable is disconnected.
C04AH
timeout error has occurred in the connected device.) • Check if there is a problem with the connection to the transceiver
• If an alive check timeout occurs, correct the IP assembly timer
value 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.)
• Correct the IP assembly timer value and perform the initial process
again.
Because there is no space in the internal buffer, such as
C04CH • Send the same data again and check the receipt of a response.
the IP header buffer, data cannot be sent.
• In communications using an auto-open UDP port or
communications using a fixed buffer in the "No
• Correct the data length.
Procedure" control method, there is an error in the
C04DH • Correct the text size so that the text data size is within the receive
data length specified in the application data of the
buffer memory size.
message received by the Ethernet module.
• Not all the receive data can be stored.
320
Error
code
When "ASCII Code" has been selected in the
• Select "Binary Code" in the Ethernet operation setting. Then
communication data code setting in the Ethernet
restart the Ethernet module to perform communications again.
C050H operation setting, ASCII code data which cannot be
• Check and correct the data sent from the connected device and
converted into binary code data has been sent from the
send it again.
connected device.
The number of read/write points is outside the allowable • Correct the number of read/write points and send the data to the
C051H
range. Ethernet module again.
C052H
C053H
C054H
The number of file data read/write points is outside the • Correct the number of read/write points (or the number of bytes)
C055H
allowable range. and send the data to the Ethernet module again.
• Correct the start address or the number of read/write points and
• The read/write request exceeds the largest address.
C056H send the data to the Ethernet module again. (Make sure that the
• The address is 0.
request does not exceed the largest address.)
The request data length does not match with the • Check and correct the text or requested data length of the Qn
C057H
number of data in the character (a part of text). header. Then send the data to the Ethernet module again.
The request data length after the ASCII/binary
• Check and correct the text or requested data length of the Qn
C058H conversion does not match with the number of data in
header. Then send the data to the Ethernet module again.
the character (a part of text).
16
Incorrect designation of the command and
C059H • Correct the request details.
subcommand
The Ethernet module cannot read/write data from/to the
C05AH • Check the device for read/write.
specified device.

The Ethernet module cannot read/write data from/to the
C05BH • Check the device for read/write.
specified device.
Incorrect request (For example, a request for data • Correct the request details and send it to the Ethernet module
C05CH
read/write in bit units has been issued to a word device.) again. (For example, change the subcommand.)
C05DH The monitor registration is not performed. • Register the monitoring data and perform monitoring.
• Increase the CPU monitoring timer value.
• Check that the programmable controller CPU is operating
normally.
The communication time between the Ethernet module
• Correct the network number or PC number.
C05EH and the programmable controller CPU exceeded the
• If the destination is a station with a different network number,
CPU monitoring timer value.
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.
This request cannot be executed to the target • Correct the network number or PC number.
C05FH
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 module
C060H
specified for bit devices.) again. (For example, correct the data.)
The request data length does not match with the • Check and correct the text or requested data length of the Qn
C061H
number of data in the character (a part of text). header. Then send the data to the Ethernet module again.
When writing was prohibited while the CPU was
• To write data to the remote I/O station using the MC protocol (with
running, data has been written to the remote I/O station
C062H a QnA-compatible 3E frame or 4E frame), select "Enable Write at
using the MC protocol (with a QnA-compatible 3E frame
RUN time" in the Ethernet operation setting.
or 4E frame).
321
Error
code
• Read/write data without the device memory set for extension.
The device memory cannot be extended for the target • Device memory can be extended only in an Ethernet
C070H
station. module-connected station and a Q/QnACPU via CC-Link IE
Controller Network, MELSECNET/H, or MELSECNET/10.
The number of device points for data read/write set for • Correct the number of device points for data read/write and send
C071H
modules other than a Q/QnACPU is too large. the data to the Ethernet module again.
• Check whether the data can be requested to the target
Incorrect request (For example, a request for data programmable controller CPU.
C072H
read/write in bit units has been issued to a word device.) • 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
target programmable controller CPU. (For example, the
C073H • Correct the request details.
number of double word access points cannot be
specified for modules other than a Q/QnACPU.)
This request cannot be executed to the target • Correct the network number or PC number.
C074H
programmable controller CPU. • Correct the read/write request details.
The destination IP address could not be obtained during
• Set the Station No. <-> IP information in the Ethernet module.
CC-Link IE Controller Network, CC-Link IE Field
• Change the conversion method for the CC-Link IE Controller
C080H Network, MELSECNET/H, MELSECNET/10 relay
Network, CC-Link IE Field Network, MELSECNET/H, and
communications or communications using data link
MELSECNET/10 relay communication parameters.
instructions.
The termination process for the Ethernet module is in
• Finish all the communications to perform the termination process
C081H process, and whether communications using data link
of the Ethernet module.
instructions have reached cannot be checked.
• Check if the relay station/connected station is operating normally.
(If the communication is alive, no action for this error is required.)
• Check if there is an error with the cable connection between the
The communication process was abnormally ended in own station and the connected station.
the following communications. • If the line is heavily loaded, reduce the load.
• Communications with a programming tool (UDP/IP) • Increase the number of resends for the data link instructions.
C082H
• CC-Link IE Controller Network, CC-Link IE Field • Increase the time reserved for the communication process.
Network, MELSECNET/H, MELSECNET/10 relay • For a Basic model QCPU, High Performance model QCPU,
communications Process CPU, or Redundant CPU, use Time reserved for
communication process (SD315).
• For a Universal model QCPU, configure 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.)
• 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.
The communication process was abnormally ended in • Increase the number of resends for the data link instructions.
C083H
communications using data link instructions. • Increase the time reserved for the communication process.
• For a Basic model QCPU, High Performance model QCPU,
Process CPU, or Redundant CPU, use Time reserved for
322
Error
code
• Check if the own station/relay station/connected station is running
normally.
• Check if there is a problem with the cable connection between the
own station and the connected station.
• Increase the TCP resend timer value.
The communication process was abnormally ended in
C084H • Increase the time reserved for the communication process.
communications using data link instructions.
• For a Basic model QCPU, High Performance model QCPU,
Process CPU, or Redundant CPU, use Time reserved for
The own station's channel specified by another station
C085H in communications using data link instructions is • Execute the request from another station again.
currently in use.
A message exceeding the receive message size was
C086H • Correct the send message size of the request source.
received.
There is an error in the IP address set in the Station No. • In the Station No.<->IP information setting, set the IP addresses
<-> IP information setting for CC-Link IE Controller for the CC-Link IE Controller Network, CC-Link IE Field Network,
C087H
Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/H, and MELSECNET/10 relay communication target
MELSECNET/10 relay communications. devices.
• Increase the request interval.
There is no insufficient space in the receive buffer of the
• Decrease the number of request nodes.
relay station PC number for MELSOFT connection or
C0B2H • Wait for a response to the previous request before sending the
data link instructions, or the communication request
destination station. (Receive buffer full error)
next request. 16
• Correct the timeout value.
A request that cannot be processed was issued from • Correct the request details.
C0B3H
the programmable controller CPU. • Correct the network number or PC number.

Data that cannot be processed by the programmable • Correct the request details.
C0B5H
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.
• Change the channel number.
C0B7H A channel number currently in use was specified. • Perform communications again after the current communications
are completed.
• The network number or PC number is outside the
allowable range. • Correct the network number or PC number.
C0B8H
• A response from the programmable controller CPU is • Check the programmable controller CPU operation.
faulty.
• Perform the open process.
The open process of the TCP connection has not been
C0B9H • After sending a close request (FIN) from the connected device to
completed.
the E71, perform the open process again and wait for 500ms or
more.
Because the close process is in process using the
C0BAH • Perform the open process and send the request.
CLOSE instruction, a send request cannot be accepted.
• Follow the procedure below.
(1) Check if each module is properly mounted on the base unit.
(2) Check if the operating environment of the Ethernet module
conforms to the general specifications of the CPU module.
C0BBH 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.
323
Error
code
• Open the communication line.
C0BCH The specified communication line is closed.
• Correct the target connection number.
Requests have been accepted successively and cannot • Check if requests have been sent successively without waiting for
C0BDH
be sent. a response.
C0BEH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
C0BFH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
The open process of the UDP connection has not been • Perform the open process.
C0C0H
completed. • Check the operation of the connected device.
• Check if a send request is being repeatedly issued.
C0C1H The transmission interval of UDP is too short.
• Increase the send interval.
C0C2H System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
each module.
The UINI instruction has been executed during
C0C4H • Execute the UINI instruction after closing all connections.
communications.
• Enable the router relay function and perform the initial process.
• A send request was issued to the connected device • Set the correct data in the router relay parameter.
with the class/network address different from those of • Correct the IP address of the connected device and perform the
C0C5H the own station when the router relay function is not open process.
used. • Check if the network address is correct.
• The setting of the router relay parameter is incorrect. • After changing the network address, perform the initial process
again.
324
Error
code
each module.
• 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 the
Ethernet line.
C0C7H An Ethernet module system error has occurred.
Ethernet module.
each module.
16

each module.
C0CAH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
Another send request was issued before the send • Wait for completion of transmission before sending the next send
C0CBH
process has not been completed. request.
C0CCH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
325
Error
code
C0CFH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
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 destination.
The number of relay stations in CC-Link IE Controller
• Correct the settings in the Station No. <-> IP information for the
C0D3H Network, CC-Link IE Field Network, MELSECNET/H,
stations between the own station and the communication
and MELSECNET/10 exceeded the allowable range.
destination.
• Check the specified value for the communication destination.
The number of relay stations in CC-Link IE Controller
• Correct the settings in the Station No. <-> IP information for the
C0D4H Network, CC-Link IE Field Network, MELSECNET/H,
stations between the own station and the communication
and MELSECNET/10 exceeded the allowable range.
destination.
C0D5H The number of retries is incorrect. • Correct the number of retries.
• Correct the settings for the communication destination.
C0D6H The network number or station number is incorrect.
• Correct the specified value for the communication destination.
• Set the parameters with the programming tool and write them to
the CPU module. Then perform communications with the
C0D7H Data were sent without the initial process completed. 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 module
A response to the PING test could not be received where the PING test is executed.
C0DAH
within the time of the communication time check. • Enable the Ethernet module where the PING test is executed to
perform communications. (Complete the initial process.)
The IP address and host name of the Ethernet module • Correct the IP address and host name of the Ethernet module to
C0DBH
for the PING test are incorrect. perform the PING test.
C0DCH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
326
Error
code
C0DDH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
• Correct the specified arrival monitoring time.
Data could not be received within the specified arrival
C0DEH • Correct the specified channel number.
monitoring time.
• Check the status of the send source station and relay station.
C0DFH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
• Check that the CPU module and each intelligent function module
are properly mounted on the base unit.
An error was detected in the programmable controller

• Check that the programmable controller CPU is not in the reset
status.
16
C0E0H
CPU. • 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.
An error was detected in the programmable controller status.
C0E1H
C0E2H
C0E3H
327
Error
code
C0E4H
C0E5H
C0E6H
C0E7H
C0E8H
C0E9H
328
Error
code
C0EAH
C0EBH
C0ECH
16
C0EDH

C0EEH
C0EFH
• Perform the hardware test again. If an error occurs again, the
An Ethernet module RAM error was detected in the
C0F0H Ethernet module may have a hardware error. Please consult your
hardware test (H/W test).
• Perform the hardware test again. If an error occurs again, the
An Ethernet module ROM error was detected in the
C0F1H Ethernet module may have a hardware error. Please consult your
hardware test (H/W test).
329
Error
code
A system error (major error) was detected in the CPU
C0F3H • Remove the error cause of the CPU module in the own station.
module.
C0F4H System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
each module.
each module.
data from the connected device after a certain period of time.
C0F7H An error has occurred in the self-loopback test. • Check if there is a problem with the connection to the transceiver
C100H System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
• Check the address of the DNS server.
• Check if communications with the DNS server can be performed
using the PING command.
C101H A response could not be received from the DNS client.
• 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.)
330
Error
code
• Check if the SMTP server name has been registered in the DNS.
• Delete the SMTP server name and change the setting to the IP
C102H A response from the SMTP layer could not be received. address setting. Then check the operation.
• Check if communications with the SMTP server can be performed
each module.
• If the actions above do not solve the problem, please consult your
each module.
16

each module.
each module.
each module.
• 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
331
Error
code
• Check if the POP3 server name has been registered in the DNS.
• Delete the POP3 server name and change the setting to the IP
C112H A response from the POP3 layer could not be received. address setting. Then check the operation.
• Check if communications with the POP3 server can be performed
• 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 destination of the
An e-mail without an attachment was received. (This MSEND instruction.
C113H
error occurs when an attachment is not read normally.) • 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.
• Check if the file extension of the attachment is "bin" or "asc" on the
sending side.
An e-mail that was received has an attachment with an • Check that the e-mail is not compressed or encrypted.
C114H
invalid name. • Check the destination of the MSEND instruction.
each module.
each module.
each module.
332
Error
code
each module.
• Read Mail information storage area (address: 2682H) of the buffer
C119H There is no received mail.
memory and read received e-mails remaining on the server.
• Check that the e-mail is not compressed or encrypted.
• Check if the e-mail specifications, such as the encoding/decoding
C11AH The received mail failed to be converted. style and file format, on the sending side are the same as those for
• Check if the sending side has not divided the file.
(The received mail is stored in the mail buffer.)
An e-mail was sent and an error mail was received from
C11BH • Check if the portion before "@" is correct in the mail address
the mail server of the destination.
setting in the parameter settings.
• Check if the portion before "@" has been registered on the
destination mail server.
C11DH The attachment size exceeded the allowable size.

• Check if the attachment size is 6K words or less. 16
• 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

Communications cannot be performed with the SMTP
C121H • Check if the SMTP server is busy.
server. (Error response)
server. (Abort)
server. (Reset response)
• Check for an error in the SMTP server.
C124H A response from the SMTP server timed out.
• Check if the network is heavily loaded.
C125H Forcefully disconnected from the SMTP server
C126H The SMTP server could not be closed.
C127H Closing the SMTP server gave an error response.
The communication channel is closed because the
C130H • Check the status of the SMTP server.
service is not available.
• Check that a user name not registered in the server has not been
The SMTP server is in process, and an error response
C131H specified.
was received.
• Send the e-mail again after a certain period of time.
was received. (Local error)
was received. (Insufficient memory area)
333
Error
code
each module.
each module.
each module.
each module.
The SMTP server is in process, and an error response • Check if the mail address of the Ethernet module has been
C138H
was received. (Mailbox not found) correctly set.
each module.
C13AH was received. (Exceeded the allocation of the memory • Check the status of the SMTP server.
area)
The SMTP server is in process, and an error response • Check if the mail address of the Ethernet module has been
C13BH
was received. (Illegal mailbox name) correctly set.
334
Error
code
C13CH System error (The OS detected an error.) (3) Check if the power capacity is sufficient.
each module.
• Check that the port number of the POP3 server is 110. (The port
number of the Ethernet module is fixed to 110.)
C140H The POP3 server could not be opened.
• Check if communications with the POP3 server can be performed
Communications cannot be performed with the POP3
C141H • Check if the POP3 server is busy.
server. (Error response)
server. (Abort)
server. (Reset response)
A response from the POP3 server could not be • Check for an error in the POP3 server.
C144H
received. • Check if the network is heavily loaded.
C145H Forcefully disconnected from the POP3 server • Check for an error in the POP3 server.
C146H The POP3 server could not be closed.

• Check for an error in the POP3 server.
16
C147H Closing the POP3 server gave an error response. • Check for an error in the POP3 server.
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 and
C151H parameter) is different from the account name in the
correct the account of the mailbox set in the Ethernet module.
mailbox on the server side.
The Ethernet module's password (e-mail setting
• Check the password on the server side and correct the password
C152H parameter) is different from the password on the server
of the Ethernet module.
side.
An error has occurred in acquisition of the received mail
• Reset the server inquiry time to the default value and restart the
C153H list. (The list of the mail that arrived at the POP3 server
CPU module of the own station.
failed to be acquired.)
• Check that the e-mail is not compressed or encrypted.
An error has occurred upon receiving a mail. (An e-mail • Check if the e-mail specifications, such as the encoding/decoding
C154H
cannot be read from the POP3 server.) style and file format, on the sending side are the same as those for
A response was received from the DNS server after • Check if the network is heavily loaded.
C160H
timeout. • Check the status of the DNS server.
C161H A response from the DNS server could not be received.
• Check the status of the DNS server.
each module.
335
Error
code
each module.
• Check if the IP address of the DNS server is correct.
• Check if the mail server names (SMTP server names and POP
C171H An error was returned from the DNS server. server names) are correct.
• Check with the network administrator if the DNS function of the
server specified in the DNS setting is properly operating.
336
Error
code
C17AH An error was returned from the DNS server. server names) are correct.
C17BH An error was returned from the DNS server. server names) are correct.
C17CH An error was returned from the DNS server. server names) are correct.
C17DH An error was returned from the DNS server. server names) are correct.
C17EH An error was returned from the DNS server. server names) are correct.
• Check with the network administrator if the DNS function of the 16
C17FH An error was returned from the DNS server. server names) are correct.

The device specified in "Condition Device" in "News • Correct the device settings in the PLC parameter window and
C180H Setting" is outside the range set in the [Device] tab of specify the condition devices within the range of the device
the PLC parameter window. 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.
• Specify the connection number within the range of 1 to 16.
C1A6H The specified connection number is incorrect. • 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.
337
Error
code
• Correct the specified send/receive data length and header length
The send/receive data length and header length are to values within the allowable ranges.
C1AEH
incorrect. • The send/receive data length needs to be equal to or longer than
the header length.
C1AFH The specified port number is incorrect. • Correct the specified port number.
The open process of the specified connection has been
C1B0H • Perform the close process before the open process.
already completed.
The open process of the specified connection has not
C1B1H • Perform the open process.
been completed.
The OPEN or CLOSE instruction is being executed in
C1B2H • Try again after the OPEN or CLOSE instruction is completed.
the specified connection.
Another send or receive instruction is being executed in • Change the channel number.
C1B3H
the specified channel. • Try again after the send or receive instruction is completed.
• Set the arrival monitoring time to a value within the allowable
C1B4H The specified arrival monitoring time is incorrect.
range.
Data could not be received within the specified arrival
C1B5H • Correct the specified arrival monitoring time.
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 setting.
A reading operation was executed while no receiving • If there is a mail received in the mail information, execute the
C1B7H
e-mail was stored in the mail buffer data area. MRECV instruction.
The RECV instruction was executed for the channel that • Correct the execution condition of the RECV instruction.
C1B8H
had not received data. • Correct the channel number.
The OPEN instruction cannot be executed for the
C1B9H • Correct the connection number.
specified connection.
The dedicated instruction was executed with the • Execute the dedicated instruction after the initial process is
C1BAH
initialization not completed. completed.
C1BBH The target station CPU type is incorrect. • Correct the specified target station CPU type.
• Correct the remote password, and unlock/lock the remote
C200H The remote password is incorrect.
password again.
The remote password status of the port used for
C201H • After unlocking the remote password, perform communications.
communications is in the lock status.
• When accessing another station, do not set the remote password
When another station was accessed, the remote
C202H on the relay station or access station or do not execute the remote
password could not be unlocked.
password check on them.
each module.
• Request the lock process of the remote password from the
The device is different from the one requesting the
C204H connected device that requested the unlock process of the remote
remote password unlock.
password.
• When accessing another station, do not set the remote password
When another station was accessed, the remote
C205H on the relay station or access station or do not execute the remote
password could not be unlocked.
password check on them.
338
Error
code
each module.
C207H 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.
C300H
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 protocol
again.
C401H Protocol unregistered error
• Register the corresponding protocol to the specified protocol
number.
C402H Protocol setting data error • Correct the protocol setting data and register it again.
• Do not execute dedicated instructions which do not support
simultaneous execution.
16
C403H Simultaneous dedicated instructions execution error
• Correct the specified connection number and execute the
dedicated instruction again.
• Check the canceled protocol in the control data of the ECPRTCL

C404H Protocol cancel request error instruction (execution count result) and eliminate the cause of the
cancellation.
• Correct the specified protocol number and execute the protocol
C405H Protocol number setting error
again.
• Correct the number of protocols to be executed continuously and
C406H Continuous protocol execution count setting error
execute the protocol again.
• Correct the specified connection number and execute the protocol
again.
C407H Connection number setting error
• Correct the connection setting of the specified connection number
and execute the protocol again.
• 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.
339
Error
code
• Write the data again.
C420H Flash ROM write error
• If an error still occurs even after rewriting, replace the module.
• Replace the module because the number of writes exceeded the
C421H Flash ROM write count over limit error
limit.
Protocol setting data writing during the ECPRTCL • If the ECPRTCL instruction is under execution, cancel the
C430H
instruction execution instruction and write the protocol setting data.
Connection close during the ECPRTCL instruction • Check the connection open status with the connected device.
C431H
execution • Open the connection with the connected device again and execute
the instruction.
D000H
to (Errors detected by CC-Link IE Field Network) • Refer to the manual for each module.
DFFFH
E000H
to (Errors detected by CC-Link IE Controller Network) • Refer to the manual for each module.
EFFFH
F000H
(Errors detected by the MELSECNET/H and • Refer to the MELSECNET/H or MELSECNET/10 network system
to
MELSECNET/10 network system) reference manual, and take corrective action.
FFFFH
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.
340
16.7 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...]
16
Item Description
16.7 Ethernet Diagnostics

Specify the E71 to be monitored. The number of other network modules is not
Target Module Setting (Module No.)
included.
Parameter Status 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 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
Status of 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. ( Page 342, Section 16.8)
Remark
For each window and detailed explanations, refer to the following.
Operating manual for the programming tool used
341
16.8 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 signal (Y17). An off request continues to
be issued while COM.ERR. LED OFF request signal (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 272, Section 15.11) This method can
also clear the error information (initial error code, open error code) or the error log.
(3) In the "Ethernet Diagnostics" window

Turn off the COM.ERR. LED by clicking the 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 341, Section 16.7)
(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.
342
APPENDICES
APPENDICES A
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
QJ71E71-100 QJ71E71-B5, QJ71E71-B2

TCP/IP UDP/IP TCP/IP UDP/IP

Item
communications communications communications communications
Ke Kdf Ke Kdf Ke Kdf Ke Kdf

Communications using a binary code 12 0.0065 10 0.0069 25 0.020 20 0.019
Communications using an ASCII code 12 0.030 10 0.029 25 0.068 21 0.068
(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
QJ71E71-100 QJ71E71-B5, QJ71E71-B2

Item
Ke Kdf Ke Kdf Ke Kdf Ke Kdf

[Calculation example]
The time between the QJ71E71-B5 sending 1017-word data of a binary code and it completing the sending
when the QJ71E71-B5 communicates with another QJ71E71-B5 in TCP/IP by 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.
63.34 (ms) 10 + 25 + (0.020 × 1017) + 8
343
(2) Minimum processing time of communications using a random access buffer
Trs = Kr + (Kdr × Df) + ACK processing time of a connected device (added only for TCP/IP communications)
• Trs : The time between the E71 receiving request data from a personal
computer 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
connected device completed and the connected device returning ACK
QJ71E71-100 QJ71E71-B5, QJ71E71-B2

Item
Kr Kdr Kr Kdr Kr Kdr Kr Kdr

Communications using a binary code 3.1 0.004 2.1 0.005 9.4 0.008 6.6 0.008
Reading Communications using an ASCII
3.1 0.016 2.2 0.016 9.1 0.030 6.5 0.030
code
Communications using a binary code 3.1 0.006 2.1 0.005 9.5 0.014 6.6 0.012
Writing Communications using an ASCII
3.2 0.017 2.2 0.015 9.6 0.042 6.7 0.036
code
[Calculation example 1]
The time between the QJ71E71-B5 receiving request data from a personal computer and it completing reading
when the QJ71E71-B5 communicates with the personal computer in TCP/IP and reads 508-word data of a binary
code from a random access buffer (unit: ms)
13.46 + ACK processing time of the connected device (ms) 9.4 + (0.008 × 508) + ACK processing time of the
connected device
The time between the QJ71E71-B5 receiving request data from a personal computer and it completing writing
when the QJ71E71-B5 communicates with the personal computer in TCP/IP and writes 508-word data of a binary
code to a random access buffer (unit: ms)
16.61 + ACK processing time of the connected device (ms) 9.5 + (0.014 × 508) + ACK processing time of the
connected device
344
APPENDICES
(3) Minimum processing time of MC protocol communications (batch reading and A

batch writing)
Tfs = Ke + (Kdt × Df) + Scr × number of scans required for the process + ACK processing time of the connected
device
• Tfs : The time between the E71 receiving request data from a personal computer and it
completing the process (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)
• Scr : CPU module processing time
(a) When the target station is the QCPU
• Own station access: E71-mounted station scan time
• Another station access over MELSECNET/10: Transmission delay time +
E71-mounted station scan time
(b) When the target station is in a redundant system and data is sent through a
tracking cable*2
• Own station access: Control system CPU module scan time + tracking transfer
time
• Another station access over MELSECNET/10: Transmission delay time + control
system CPU module scan time + tracking transfer time
QJ71E71-100 QJ71E71-B5, QJ71E71-B2

Item

Ke Kdt Ke Kdt Ke Kdt Ke Kdt
Batch
Communications using an ASCII
reading 18 0.015 13 0.017 23 0.020 18 0.020
code
Batch
Communications using an ASCII
writing 16 0.027 14 0.027 22 0.037 20 0.033
code
*1 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 ACK Response ACK
message (TCP only) message (TCP only)
E71
Step 0 Step 0
END END
CPU module scan time
Tfs
*2 When data is sent through the tracking cable of a redundant system, add the tracking transfer time. For data transfer
time of when the tracking cable is used, refer to the following.
345
The time between the QJ71E71-B5 receiving request data from a personal computer and it completing reading
when the QJ71E71-B5 communicates with the personal computer in TCP/IP and reads 100-point data of an
ASCII code from the data register (D) in the own station (unit: ms)
Assume that the scan time of the QJ71E71-B5-mounted station is 10ms, the command data length is 21 words,
and the response data length is 211 words.
37.64 + ACK processing time of the connected device (ms) 23 + (0.020 × (21 + 211)) + 10 × 1 + ACK
processing time of the connected device
The time between the QJ71E71-B5 receiving request data from a personal computer and it completing writing
when the QJ71E71-B5 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 QJ71E71-B5-mounted station is 10ms, the command data length is 221 words,
the response data length is 11 words, and writing during RUN is enabled.
40.58 (ms) 22 + (0.037 × (221 + 11)) + 10 × 1
346
APPENDICES
(4) Processing time of the dedicated instructions A

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.
(a) QJ71E71-100
Processing time (unit: ms)

Number of access QnHCPU,
Universal model Instruction
Instruction points Basic model QCPU Q02CPU Process CPU,
QCPU execution
name Redundant CPU
condition
Condition Condition
For 1) For 2) For 1) For 2) For 1) For 2) For 1) For 2)
1) 2)
A UDP/IP
OPEN 4.2 3.8 3.0 2.9 transmission port
is open.
1 port
A UDP/IP
CLOSE 4.2 3.3 3.2 3.2 transmission port
is closed.
BUFSND 14.0 23.5 12.8 19.2 11.5 18.1 8.2 15.7 TCP/IP
BUFRCV 2.2 5.8 1.3 1.8 0.9 1.4 0.7 1.1 communications,
binary code
1017 communications,
1 word
words and fixed buffer
BUFRCVS 0.8 2.9 0.5 0.9 0.3 0.7 0.2 0.6 communications
(procedure
exists)
All error information is
ERRCLR 3.4 2.2 2.0 1.7 -
cleared.
An initial error code is

ERRRD 2.4 1.2 0.8 0.7 -
read.
960 words 16.4 15.7 15.4 15.4
SEND 11.5 7.9 7.5 7.5
480 words 16.8 11.2 10.8 10.8
960 words 6.8 4.3 3.8 3.8
RECV 1.8 2.1 2.0 2.0
480 words 4.3 3.2 2.9 2.9
960 words 1.5 0.9 0.7 0.6
RECVS 0.8 0.6 0.3 0.2 Communications
480 words 1.2 0.8 0.5 0.4
between
1 word
READ, 960 words 24.3 28.8 28.2*1 19.2 E71-mounted
14.7 17.2 17.1*1 9.9 stations
SREAD 480 words 20.9 22.7 21.7*1 13.9
WRITE, 960 words 24.4 28.8 28.4*1 18.9

14.5 17.3 17.0*1 9.7
SWRITE 480 words 19.8 23.0 *1 13.7
22.2
ZNRD 12.1 14.1 14.4 17.1 13.8 16.6 9.8 11.8
230 words
ZNWR 12.0 14.8 14.2 17.5 13.9 16.4 9.8 12.0
Time between
the UINI
instruction
UINI - 26.9 26.7 26.7 26.7 accepted and a
reinitialization
process
completed
ECPRTCL *2 -
*2 The processing time of the ECPRTCL instruction differs depending on a connected device or a protocol.
347
(b) QJ71E71-B5, QJ71E71-B2
Processing time (unit: ms)

Number of access QnHCPU,
Universal model Instruction
Instruction points Basic model QCPU Q02CPU Process CPU,
QCPU execution
name Redundant CPU
condition
Condition Condition
For 1) For 2) For 1) For 2) For 1) For 2) For 1) For 2)
1) 2)
A UDP/IP
OPEN 5.2 4.3 3.3 3.0 transmission
port is open.
1 port
A UDP/IP
CLOSE 6.0 4.5 4.5 2.9 transmission
port is closed.
BUFSND 28.2 50.0 27.6 45.3 24.5 45.0 12.9 23.7 TCP/IP
BUFRCV 2.3 5.8 1.9 2.4 1.2 1.6 0.7 1.1 communications
, binary code
communications
1 word 1017 words
, and fixed-buffer
BUFRCVS 0.8 2.9 0.5 0.9 0.3 0.7 0.2 0.6 communications
(procedure
exists)
All error information is
ERRCLR 3.4 2.7 2.2 1.8 -
cleared.
An initial error code is
ERRRD 2.5 1.7 1.1 0.7 -
read.
960 words 38.8 39.4 37.9 22.3
SEND 22.8 21.4 20.3 11.0
480 words 30.8 30.4 29.1 16.1
960 words 11.1 7.9 7.4 4.4
RECV 5.3 5.3 5.2 2.4
480 words 8.2 6.6 6.3 3.3
960 words 1.6 1.0 0.7 0.6
RECVS 0.8 0.6 0.3 0.2 Communications
480 words 1.2 0.8 0.5 0.4
between
1 word
READ, 960 words 50.1 52.1 52.3*1 25.9 E71-mounted
27.7 30.1 27.7*1 12.5 stations
SREAD 480 words 38.9 41.1 *1 18.3
40.0
WRITE, 960 words 47.6 53.6 52.4*1 25.4

28.2 30.0 29.4 *1 12.9
SWRITE 480 words 37.9 41.8 40.9*1 18.2
ZNRD 27.8 33.2 29.0 34.3 29.0 34.7 12.6 15.3

230 words
ZNWR 27.6 33.4 29.7 36.4 29.4 35.2 12.9 15.6
Time between
the UINI
instruction
UINI - 26.8 26.7 26.7 26.7 accepted and a
reinitialization
process
completed
348
APPENDICES
(5) System switching time of a redundant system A

The following shows the system switching time required when the E71 mounted with the control system CPU
module in a redundant system issues a system switching request to the control system CPU module at
communication error or disconnection detection. The system switching time is the time from when a
communication error or disconnection is detected until the control system CPU module is switched to the standby
system CPU module.
(a) When a communication error is detected

• For alive check errors
Tnc = Tsi + Ti × Tr + St + Tsw
• Tnc : System switching time

• Tsi : Destination existence confirmation starting interval timer value
• Ti : Timer value of the alive check
• Tr : Destination existence confirmation resending time
• St : One scan time
• Tsw : CPU system switching time*1
The following shows the timing for system switching operation if an alive check error occurs.
Connected device

A communication
error occurred.

QJ71E71-100 QJ71E71-100
Station No.1 Station No.2
System switching Tracking cable

request
Communications have not been performed with

the connected device for a fixed period.
(Tr = 3)
Operating as
QJ71E71-100 (station No.1) Operating as a control system a standby system
Tsi Ti Ti Ti
Issuing a system
switching request
Scan time of the system A CPU
System A Control system Standby system

Tsw
System B Standby system Control system
Scan time of the system B CPU
Operating as
QJ71E71-100 (station No.2) Operating as a standby system a control system
Tnc
*1 For details on CPU system switching time, refer to the following.

349
• When a ULP timeout occurs
Tnc = Ttu + St + Tsw

• Ttu : TCP ULP timer value
The following shows the system switching operation timing if a ULP timeout occurs.
Connected device
A communication
error occurred.

QJ71E71-100 QJ71E71-100
System switching Tracking cable

request
No response from the connected device
QJ71E71-100 (station No.1) Operating as a control system Operating as a standby system
Ttu
Issuing a system
switching request

Tsw
QJ71E71-100 (station No.2) Operating as a standby system Operating as a control system

Tnc

350
APPENDICES
(b) When disconnection is detected

Tnc = Td + St + Tsw
A

• Td : Disconnection detection monitoring time
The following shows the system switching operation timing if disconnection is detected.
Connected device
Disconnected

QJ71E71-100 QJ71E71-100
Tracking cable

Disconnected
QJ71E71-100 (station No.1) Operating as a control system Operating as a standby system
Td
Issuing a system
switching request

Tsw
QJ71E71-100 (station No.2) Operating as a standby system Operating as a control system

Tnc

351
Appendix 2 Port Numbers Used for the E71
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).
352
APPENDICES
Appendix 3 New and Improved Functions A

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
Version of E71 Version of Version of GX Version of GX
Function Reference
QJ71E71-100 QJ71E71-B5 QJ71E71-B2 CPU module Developer Works2
Function
Page 87,
version B or Version 7
Support for IEEE 802.3 frame Section
later of or later
7.1.3
"03102"
Function
Reinitialization Page 360,
version B or
process with Appendix
Function later of
the program 4.2
version B or "03061"
Reinitialization later of Function
"03102" Page 279,
process with version B or
Section
the UINI later of
15.13
instruction "03102"
Reinitialization
process of the Changing the
E71 transmission Function
Page 279,
speed and the version D or
× × Section
communication later of
15.13
mode with the "11012"
UINI instruction
Function Function
TCP Maximum Page 360,
version B or version B or
Appendix 3 New and Improved Functions

Segment Appendix
later of later of
transmission 4.2
"05051" "05051"
Function Function
Page 93,
Re-open process of the E71*1 Section
later of later of
7.2.3
"05051" "05051"
Function Function
Page 87,
Alive check Check using version B or version B or Version 8.05F
Section
function KeepAlive later of later of or later
7.1.3
"05051" "05051"
Function
Connection up to 17 MELSOFT
version B or Version 6.05F Page 102,
products in TCP/IP
later of or later CHAPTER 8
communications
"02122"
Easy access to
Easy other stations Function Function
connection with Access to the version B or version B or Page 102,
MELSOFT station with the later of later of CHAPTER 8
products same station "05051" "05051"
number
Monitoring of Page 285,
various E71 CHAPTER
status 16
Version 6
PING or later
Function Function
Ethernet test/loopback Page 366,
version B or version A or
diagnostics test via Appendix 5
later later of "02092"
Ethernet board
PING test Page 369,
Version 7
through a CPU Appendix
or later
module 5.1 (2)
353
Function Reference
QJ71E71-100 QJ71E71-B5 QJ71E71-B2 CPU module Developer Works2
Specification of station numbers Universal

Function
65 to 120 for data link instructions model QCPU
version D or
(for access to CC-Link IE × × with function
later of
Controller Network and CC-Link version B or MELSEC-Q/
"09042"
IE Field Network) later of "09042" L Ethernet
Interface
Target station CPU type Function Function Function
Module
specification for data link version D or version D or version D or
User's
instructions later later later
Manual
Function Function Function (Application)
Expansion of data length for data
version D or version D or version D or
link instructions (from 480 to 960
later of later of later of
words)
"07082" "07082" "07082"
Sending an Function
Version 6
attachment as version B or
or later
a CSV file later
Function
Sending the version B or Version 7
main text later of or later
"03102"
Function Function
Support for
encoding/
E-mail function later of later of
decoding
"03102" "03102"
Sending
character
strings as the
Function Function Function
main text in an
version D or version D or version D or Version 8.27D
e-mail using the
later of later of later of or later
programmable
"07082" "07082" "07082"
controller CPU
monitoring
MELSEC-Q/
function
L Ethernet
Function Interface
Support of a multiple CPU system Function
version B or Module
by the file transfer (FTP server) version B or
later of User's
function later
"03102" Manual
(Application)
Support of 4E frame data in MC version D or version D or version D or
protocol communications later of later of later of
"07082" "07082" "07082"
Universal
Access to the link direct device of Function
model QCPU
LW10000 or later in MC protocol version D or
× × with function
communications (4E frame and later of
version B or
QnA-compatible 3E frame only) "09042"
later of "09042"
Access to the extended data
Universal
register of D65536 or later and the Function
model QCPU
extended link register of W10000 version D or
× × with function
or later in MC protocol later of
version B or
communications (4E frame and "09042"
later of "09042"
QnA-compatible 3E frame only)
Function
version B or
Web function
later of
"05051"
Function Function
Version 6 Page 203,
Remote password check version B or Version A or
or later Section 14.4
later later of "02092"
Function
Hub connection status monitor Page 213,
version D or × ×
function Section 14.5
later
354
APPENDICES

Function Reference
CPU module Developer Works2
QJ71E71-100
Function
QJ71E71-B5 QJ71E71-B2
A
IP address in use detection version D or Page 214,
× ×
function later of Section 14.6
"12062"
MELSEC-Q/
Setting the arrival monitoring time L Ethernet
Function
of the dedicated instruction in Interface
version D or
100ms increments (the READ, × × Module
later of
SREAD, WRITE, and SWRITE User's
"12062"
instructions only) Manual
(Application)
Function
Page 109,
version D or
Communications using SLMP × × × CHAPTER
later of
10
"15042"
Function
Page 114,
Data communications using the version D or
× × × CHAPTER
predefined protocol later of
11
"15042"
Universal
Function
model QCPU
version D or Version 1.492N Page 287,
Module error collection function × × with function ×
later of or later Section 16.3
version B or
"15042"
later of "11043"
Setting range extension of the Function
Page 89,
communication destination port version D or
× × × Section
number (Port number 1H to 400H later of
7.1.4
can be set.) "15042"
Function
Page 38,
Receive buffer full detection signal version D or
× × Section
(address: 5240H) later of
3.5.2
"17032"
Appendix 3 New and Improved Functions

version D or version D or version D or Page 197,
IP filter function
later of later of later of Section 14.3
"18072" "18072" "18072"
*1 The operations of the E71 has been changed for the case where an Active open request from the connected device is
received again during open completion status in TCP/IP.
355
Appendix 4 Initial Process
The initial process is for enabling data communications with connected devices by setting the minimum number of
parameters for the E71. For the Q Series, a program for the initial process is not required because the initial process is
automatically performed.
(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 abnormal end signal

Initial process INIT. LED
signal (X19) (X1A)
At normal completion ON ON OFF
At 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".
Project window [Parameter] [Network Parameter] [Ethernet/CC IE/MELSECNET]

Select "Ethernet" under "Network Type". Initial Setting
356
APPENDICES
Item Description Setting range A

TCP ULP Timer Set Time to Live during packet sending in TCP/IP. 2 to 32767
Window indicates the receive buffer on the recipient. If the
receive buffer on the recipient has no free space (window size
= 0), data sending is waited until the recipient has free receive
TCP Zero Window Timer 2 to 32767
buffer space. At this time, the sender sends packets for
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
Timer Setting and the connection is forcibly closed.
The communication data may be divided at the IP level before
being sent due to the buffer limitation of the sending station or
IP Assembly Timer 1 to 32766
the receiving station. Set the waiting time for the divided data
in such a case.
Set the following waiting time.
• Time for waiting a response after a command is sent
Response Monitoring Timer 2 to 32767

• For receiving divided messages, time until the last message
is received after the first message is received
Set the time until starting the alive check after
communications with the connected device of the connection
Dest. Confirmation Start Interval 1 to 32767
that has been opened where the alive check target exists is
lost.
For the connection that is opened where the alive check target
exists, set the interval to perform the alive check again when a
Dest. Confirmation Interval 1 to 32767
response from the connected device as the alive check target
is not received.
For the connection that has been opened where the alive
check target exists, set the number of times that the alive
Dest. Confirmation Resend 1 to 32767
check is performed again when a response from the
connected device as the alive check target is not received.
Input Format Select an input format. DEC/HEX
IP Address of DNS Server1
*1 IP Address of DNS Server2
DNS Setting
Set the IP address of each DNS server. -
*1 The DNS setting is configured for using the e-mail function. For details, refer to the following.
357
(1) Precautions for settings
• Specify the setting value of each timer on the E71 side so that the following formula is met.
Response TCP IP
TCP ULP TCP end
monitoring resend assembly
timer value timer value
TCP
TCP zero window
resend = timer value
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
TCP resend timer value
timer value on
on the E71
the connected device
Monitoring timer value of

the application software on TCP ULP timer value n *1
the connected device on the E71
*1 "n" is the number of TCP segment transmission and is calculated by the following formula.
Message size sent by the E71

n = A value that is rounded up to the nearest integer
Maximum Segment Size
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
Segment transmission is as follows.
• n = 1 when the size of the message sent by the E71 is 1460 bytes or less
• 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
358
APPENDICES
• 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 A
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
E71
Data 1st retry 2nd retry 3nd retry
command
A A 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 TCP end TCP resend

= =
(Set the same value for the timer values.)
359
Appendix 4.2 Reinitialization process
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) 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 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

By changing the transmission speed and communication mode, communications with the connected device
can be resumed.
360
APPENDICES
(2) Reinitialization processing program A

Perform the reinitialization process using a program. The following shows the process timing and sample
programs.
(a) Process timing
Close process
END END END END

Program Scan process Scan process Scan process Scan process Scan

1
signal (X19)

(address: 5000H)
3
UINI instruction
Completion device
Reinitialization specification
(address: 1FH (b15))
4 5
Processing reinitialization
Internal process of the E71 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.
361
(c) Using the dedicated instruction (UINI instruction)
The following shows an example where the reinitialization process is performed using the UINI instruction and
the OPEN instruction is executed after the process is completed. (When the I/O signals of the E71 are X/Y00 to
X/Y1F)
(To the next page)
362
APPENDICES
A

363
(d) Writing directly to the buffer memory
The following shows an example where the stored values in the TCP Maximum Segment Transmission setting
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 "Disable TCP Maximum

Segment Size Option
transmission".
Set "ASCII Code".
Set "Use the KeepAlive".
Set "IEEE 802.3".
Set "Enable" for Setting of

write enable/disable at
RUN time.
Set "Always wait for OPEN".
Reinitialization process
request
364
APPENDICES
Remark A
This is a sample program for communications using connection numbers 1 and 2. When using another connection number,
specify the corresponding signals and bits.
(3) Precautions
(a) MELSOFT products supporting TCP Maximum Segment transmission

To set "Enable TCP Maximum Segment Size Option transmission" in the reinitialization process, use the
following MELSOFT products together.
MELSOFT product Supported version

GX Works2 Version 1.15R or later
GX Developer Version 8.07H or later
MX Component Version 3.03D or later
MX Links Version 3.08J or later
To perform communications over Ethernet using a MELSOFT product other than those listed above, select
"Disable TCP Maximum Segment Size Option transmission" or use UDP/IP communications. When "Enable
TCP Maximum Segment Size Option transmission" is selected, the program may not be normally read/written.
(b) 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
(c) Reinitialization process request

Do not request another reinitialization process while a reinitialization process is in progress.
365
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) Method using direct connection to the E71

This test is to check the existence of an E71*1 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
*1 This also applies to QnA/A series modules. However, for an AJ71E71, AJ71E71-B2, and AJ71E71-B5, software
versions S and later are required.
(a) Applications
The line status between the programming tool (personal computer) and the E71 can be checked.
366
APPENDICES
(b) Operating procedure

Use the following procedure.
A
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.

3. Click the button.
367
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 mounted on the base unit
• 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
368
APPENDICES
(2) Method using direct connection to the CPU module A

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 PING test executing station
using the network No. Specifying the target station
and station No. using the IP address Ethernet
E71
(PING test target station)
*1 This also applies to QnA/A series modules. However, for an AJ71E71, AJ71E71-B2, and AJ71E71-B5, software
versions S and later are required.
*2 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.



369
button.
3. Click the button.
4. The test results are displayed.

If the test fails, take the same action as that for the method using direct connection to the E71. ( Page 368,
Appendix 5.1 (1) (c))
370
APPENDICES
(3) Method using the PING command A

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

[Sample program] IP Address of an E71(10.97.85.223)
(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 mounted on the base unit
• 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
371
Appendix 5.2 Loopback test
This section describes the loopback test.
(1) Method using the 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 (Stations connected

tool to the programming tool)
Station No.1 Station No.3 Station No.5 Station No.7 Station No.9
E71 E71 E71 E71 E71

Network No.1
The loopback test is executed E71 E71 E71 E71

from the station No.1 through
the station No.5 on the network Station No.2 Station No.4 Station No.6 Station No.8
No.1.
*1 Because the E71 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-mounted 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.
372
APPENDICES

A



button to display the test results.

If the same IP address or station number is assigned to multiple stations, only the results of the station that responds first are
displayed.
373
If the loopback test fails, "No response" or an error code is displayed.
Displayed test Status of the target

Cause Action
result E71
Initial processing
normal completion
IP address Normal completion -
status (INIT. LED
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
• Check the cable.
disconnection and line disconnection, in the
• Check the transceiver.
line connection to the target E71.
The IP address of the target E71 is
No error
incorrect. (The class or subnet address
Correct the set values of the Ethernet
differs from that of the E71.)
operation settings.
The same IP address has been set to
No response multiple target E71 modules.
Perform the PING test on the "No response"
The same network number or station
module. When the test is completed
number has been set to multiple target E71
normally, correct the set values in the basic
modules.
settings.
The Ethernet line is heavily loaded
(including a case where an error equivalent When the Ethernet line is not heavily
No error/Error exists
to the error codes C030H and C031H is loaded, perform the test again.
occurring).
The routing parameter is not set (an error
Correct the set value of the routing
Error exists equivalent to the error code C080H is
parameter.
occurring).
The MELSOFT application transmission
Disable the remote password setting and
port (UDP/IP) for the target E71 is locked
write the parameter to the CPU module.
No error with the remote password.
The target E71 is a function version A Check the module name and function
Error code module. version.
The Ethernet line is heavily loaded
(including a case where an error equivalent When the Ethernet line is not heavily
No error/Error exists
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-mounted 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.
374
APPENDICES
(2) Method using the MC protocol A

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.
(Loopback test command sending station)
Ethernet
QCPU E71 QCPU E71 QCPU 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.

375
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

1. Connect the E71 to the line.*1

2. Set the switch on the CPU module to "STOP".
3. Select "Self-Loopback Test" under "Mode" and write
the parameter to the CPU module.
Project window [Parameter]

[Network Parameter]
[Ethernet/CC IE/MELSECNET]
"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 For a QJ71E71-100, 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
• External power supply 12VDC error (only 10BASE5)
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.
376
APPENDICES
Appendix 6.2 Hardware test (H/W Test)

A
The RAM and ROM of an E71 are checked.
(1) Operating procedure

1. Set the switch on the CPU module to "STOP".

2. Select "H/W Test" under "Mode" and write the
parameter to the CPU module.
Project window [Parameter]

[Network Parameter]
[Ethernet/CC IE/MELSECNET]
"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
the test is running normally, the RUN LED turns on.
If the test fails, the RUN and ERR. LEDs turn on.
Appendix 6.2 Hardware test (H/W Test)

Appendix 6 Self-Diagnostic Tests
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.
377
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 Comparison with a Built-in Ethernet port QCPU
For comparison of the specifications and functions between an E71 and a Built-in Ethernet port QCPU, refer to the
following.
QnUCPU User's Manual (Communication via Built-in Ethernet Port)
Appendix 7.2 Comparison with 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 Model name Product name

AJ71E71 AJ71E71, A1SJ71E71-B2, A1SJ71E71-B5
AJ71E71-S3 AJ71E71-S3, A1SJ71E71-B2-S3, A1SJ71E71-B5-S3
A series
AJ71E71N3-T, AJ71E71N-B5, AJ71E71N-B2, AJ71E71N-T, AJ71E71N-B5T, A1SJ71E71N3-T,
AJ71E71N
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
378
APPENDICES
(1) Functional comparison A

The following table lists the functional comparison between an E71 and QnA/A series modules.
AJ71E71-S3, QE71(N)
Function AJ71E71 E71
AJ71E71N 9706 or earlier 9706B or later
Initial process with the program

Initial process
Initial process with parameter settings × × ×
Open process with the program

Open process*1
Open process with parameter settings × × × ×
Procedure Exist *2
Communications using a
fixed buffer *2
No Procedure ×
Communications using a random access buffer
MC protocol communications *3 *3
Communications using data link instructions × × × *4
Interrupt process (upon BUFRCVS instruction × × × ×

data receiving) RECVS instruction × × × ×
Send/receive with the program × × × ×

E-mail function
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 × ×

Appendix 7 Differences from Ethernet Modules of Other Series
Selection of the communication data code (ASCII/binary)
CC-Link IE Controller Network, CC-Link IE Field Network, *4

× × ×
MELSECNET/H, MELSECNET/10 relay communications
Router relay function ×
Connected device alive Ping ×

check KeepAlive × × × ×
Pairing open ×
Unit of each timer setting 500ms ×*5 (Fixed) (Fixed) (Fixed)
value for data
communications 2s (Fixed) × × ×
Connection to TCP/IP × × × ×
MELSOFT products UDP/IP ×
Installation of EEPROM × × ×*6

TCP Maximum Segment Size Option transmission × *7 × *7 *8
Hub connection status monitor function × × × × *9
IP address in use detection function × × × × *9
Communications using SLMP × × × × *9
Data communications using the predefined protocol × × × × *9
Module error collection function × × × × *9
379
*1 For the E71, the number of connections for the open process from the CPU module has increased to 16 connections.
*2 Compatible with the I/O signal and QE71(N) buffer memory
*3 Data of up to 960 words can be read from/written to an E71, and up to 480 words in a QE71(N).
*4 Availability depends on the CPU module and programming tool version.
*5 This applies to a module with the software version of Q or earlier.
*6 No EEPROM is installed. Items registered in the EEPROM of a QE71(N) are set using the parameter settings of the
programming tool.
*7 This applies to a module with the software version of E or later.
*8 This function can be used in an E71 with a serial number (first five digits) of “05051” 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 38, Section 3.5.2) After changing the setting, execute the reinitialization process.
*9 Only the QJ71E71-100 can be used.
Availability depends on the QJ71E71-100 and a programming tool version ( Page 353, Appendix 3).
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.
: Communications allowed by using the program for an AJ71E71(-S3) and AJ71E71N on the connected device side,
-: Not allowed to use
Connected E71 
AJ71E71(-S3), E71  AJ71E71(-S3),
Function device  connected
AJ71E71N  E71 AJ71E71N
E71 device
Communications using a fixed buffer
("Procedure Exist")
Communications using a random
- - -
access buffer
Data read/write in the CPU module*1 - - -
*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.
380
APPENDICES
(b) QE71(N)
Program of connected devices
A
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) or
MELSECNET/B.)
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 QCPU. 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 a QCPU.
• 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

Appendix 7 Differences from Ethernet Modules of Other Series
• 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 canceled before open completion.
After the open completion, execute the close process.
381
Appendix 8 Operation Image and Data Structure of
Predefined Protocol
Appendix 8.1 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
Connected
E71 Data Header device
The operation image of "Send Only" is as follows.
(a) When the instruction ends normally
ECPRTCL instruction
Completion device
Waiting time to send
E71
Send packet
Connected device
Send packet
382
APPENDICES
(b) When the instruction ends abnormally at TCP (timeout error)

A
An error has
occurred.
ECPRTCL instruction
Completion device
The device
turns on upon
abnormal end.
Waiting time
E71
Send packet
The packet cannot be sent or

no response is received from
Connected device the connected device.
For an error occurred when the communication ends abnormally, refer to the error code stored in the buffer memory.
Appendix 8.1 Operation image of each communication type of protocol

Appendix 8 Operation Image and Data Structure of Predefined Protocol
383
(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
Not matched Header Data

Receive packet
(expected packet) Connected
Discarded
Data Receive data 2 device
Matched Header Data

Sixteen receive packets
can be specified.
Received
The operation image of "Receive Only" is as follows.
ECPRTCL instruction
Completion device
E71
Receive data
The receive data matched

the receive packet
(expected packet).
Connected device
Receive data
384
APPENDICES
(b) When the instruction ends abnormally (timeout error)

A
An error has
ECPRTCL instruction occurred.
Completion device
The device
turns on upon
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
Receive data Receive data
*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.
● 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.
385
(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
Connected
Not matched Header Data
Receive packet device
(expected packet)
Discarded
Data Receive data 2
Matched Header Data

Sixteen receive packets
can be specified.
Received
The operation image of "Send&Receive" is as follows.
ECPRTCL instruction
Completion device
Waiting time Waiting time

to send to receive
E71
Send packet Receive data
The receive data matched

the receive packet
(expected packet).
Connected device
Send packet Receive data
386
APPENDICES
(b) When the instruction ends abnormally (timeout error at sending)

A
An error has occurred.
ECPRTCL instruction
Completion device
The device turns on
upon abnormal end.
Waiting time
E71
Send packet
The packet cannot be

sent or no response is Discarded
received from the
Connected device connected device.
Receive data
(c) When the instruction ends abnormally (timeout error of waiting time to receive)
An error has
ECPRTCL instruction occurred.
Completion device
The device
turns on upon

Waiting time t: waiting time to receive or the time
to send specified by the destination alive check timer*1
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.
387
Appendix 8.2 Verification operation of receive packet
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
Receive data Received
(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.3 No.16
Sixteen receive
Not matched Matched packets can be
registered.
Receive data Received
(3) When received data are not matched to all receive packets (expected packets)
The received data are discarded.
Receive packets When sixteen

(expected packets) No.1 No.2 No.16 receive packets
were registered
Not matched Not matched
Receive data Discarded
388
APPENDICES
Appendix 8.3 Data examples of packet elements

A
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 "3210" "0123"
32H 33H 32H 31H 30H
Length calculation result 33H
123H Reverse direction
Conversion to 33H
ASCII
32H "0123" "3210"
hexadecimal
31H 30H 31H 32H 33H
"0" (30H)
30H
"1" (31H)
"2" (32H)
Byte swap
"3" (33H)
32H

33H "1032" "2301"
30H 31H 30H 33H 32H
31H
[When receiving] Data flow
Forward direction Length calculation result
30H Conversion from ASCII hexadecimal to binary
31H
"0123" 123H
32H
33H
Connected device Sending
Reverse direction
33H
"0123"
32H
33H 32H 31H 30H "3210" 3210H
31H
30H
Byte swap
32H
33H
"2301" 2301H
30H
31H
389
(b) Data flow
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 Packet Packet Packet Packet Packet

element 1 element 2 element 3 element 30 element 31 element 32
Packet format Non-conversion

Static data Length Static data Static data Static data
variable
Calculating
range for
the length
Example 1
Calculating range for the length

Example 2
Calculating range for the length

Example 3
Example 1) Calculating range when its start is 3 and end is 3

390
APPENDICES
(2) Non-conversion Variable A

(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
Connected
No byte swap Send data device
Data length storage area +0 0005H 06H 05H 04H 03H 02H 01H
Data storage area +1 0201H ↑
Sending Data are not sent.
+2 0403H ↓
+3 0605H 05H 06H 03H 04H 01H 02H
Byte swap
Ex. When receiving data whose length is an odd number
(Word) Specified device No byte swap

Data length storage area + 0 0005H
Data storage area +1 0201H
Connected

+2 0403H
Send data device
+3 0005H
Receiving 01H 02H 03H 04H 05H
(Word) Specified device Byte swap

Data length storage area + 0 0005H
Data storage area +1 0102H
+2 0304H
+3 0500H
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.
391
(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
Variable number of
1 byte 2 bytes 2 bytes 5 bytes 5 bytes characters 1 byte
Identification Country Manufacturer Product
STX code code code code EXT
Reading data
When the information is unnecessary

for users and the data
(including the number of characters)
Non-verified reception is are variable
set in the elements.
Example of a packet setting
2 bytes 2 bytes Variable number of characters 1 byte

Non-conversion
Static data Non-verified reception (variable number of characters) Static data
variable
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.
392
APPENDICES
Appendix 9 Usage example of MX Component A

MX Component is an ActiveX control library that supports all the communication routes between a personal computer
and programmable controller. Communications can be performed with a simple process without considering different
predefined protocols of each communication. This appendix describes how to create a program and sample programs
using MX Component.
Appendix 9.1 How to create a program
Visual Basic®.NET 2003 is used for the following procedure.
1. Follow the wizard to configure communication

settings from the personal computer to the
programmable controller. (For some controllers,
settings are configured only using the program,
without using any wizard.) In the wizard, configure
necessary settings such as a logical station
number, connection module type, and connection
destination programmable controller.
Appendix 9.1 How to create a program

Appendix 9 Usage example of MX Component
2. Paste the ACT control icon onto the form. Then set
the logical station number set in Step 1 to the
control as its property.
393
3. Use a function to write the program that reads the
device data.
4. Click the "Read Device" button.
Appendix 9.2 Sample Program
The following sample program is used to read D0 to D4 (five points) of a target programmable controller using a logical
station number.
(1) Window example (Form1)
Text1: A logical station No. is entered.
Button1 or Command1:
Connects the communication line.
Reads the device data.
Cuts off the communication line.
ACT control (ActEasyIF): ACT control for the utility setting type
(2) Program example

Program examples for development software below are described on the following pages.
• Visual Basic®.NET 2003
• Visual C++®.NET 2003
394
APPENDICES
(a) Visual Basic®.NET 2003

A
Private Sub Command1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles
Command1.Click
' ****************************************
' Connection
' *****************************************
Dim rtn As Integer
'Get LogicalstationNumber
AxActEasyIF1.ActLogicalStationNumber = Val(Text1.Text)
'Connection
rtn = AxActEasyIF1.Open()
If rtn = 0 Then
MsgBox("The Connection was successful")
Else
MsgBox("Connection Error:" & Hex(rtn))
End If
End Sub

Command2.Click
' ****************************************
' Read
' *****************************************
Dim rtn As Integer

Dim idata(5) As Short
'D0-D4 (5 points) are read
rtn = AxActEasyIF1.ReadDeviceBlock2("D0", 5, idata(0))
If rtn = 0 Then
MsgBox("D0-D4 = " & idata(0) & "," & idata(1) & "," & idata(2) & "," & idata(3) &
"," & idata(4))
Else
MsgBox(Read Error:" & Hex(rtn))
End If
End Sub
(To the next page)
395
Command3.Click
' ****************************************
' Disconnection
' *****************************************
Dim rtn As Integer
'Disconnection
rtn = AxActEasyIF1.Close()
If rtn = 0 Then
MsgBox("The disconnection was successful")
Else
MsgBox("Disconnection Error:"& Hex(rtn))
End If
End Sub
396
APPENDICES
(b) Visual C++®.NET 2003

A
//***************************************
//Connection
//****************************************
private: System::Void button1_Click(System::Object * sender, System::EventArgs * e)
{
int iRet
//Get LogicalStationNumber
axActEasyIF1->ActLogicalStationNumber=Convert::ToInt32(textBox1->Text);
//Connection
iRet = axActEasyIF1->Open();
if( iRet == 0 ){
MessageBox::Show("The connection was successful" );
} else {
MessageBox::Show( String::Format( "Connection Error:0x{0:x8} [HEX]", __box
(iRet) ) );
}
}
//****************************************
//Read
//****************************************
{

int iRet;
short sData[5];
String* szMessage= "";
String* lpszarrData[];
int iNumber;
String* szReadData
//D0-D4 are read

iRet = axActEasyIF1->ReadDeviceBlock2( "D0", 5, sData );
if( iRet == 0 ){
lpszarrData = new String * [ 5 ];
lpszarrData[0] = "D0-D4 = ";
(To the next page)
397
// Result display data is stored.
for( iNumber = 0 ; iNumber < 5 ; iNumber++ )
{
lpszarrData[ iNumber ] = sData[ iNumber ].ToString();
}
szReadData = String::Join(",",lpszarrData);
MessageBox::Show(String::Format("D0-D4 = {0}",szReadData));
} else {
MessageBox::Show( String::Format( "Read Error:0x{0:x8} [HEX]", __box(iRet) ) );
}
}
//****************************************
//Disconnection
//****************************************
{
int iRet;
//Disconnection
iRet = axActEasyIF1->Close();
if( iRet == 0 ){
MessageBox::Show( "The disconnection was successful" );
} else {
MessageBox::Show( String::Format( "Disconnection Error:0x{0:x8} [HEX]", __box
(iRet) ) );
}
}
398
APPENDICES
Appendix 10 Sample Program on the Connected Device A

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
The TCP connection is closed.

Is the TCP connection open?
Receive the remaining

response messages.
Appendix 10 Sample Program on the Connected Device Side

Were the data Timeout of the monitoring timer value
received within the monitoring
timer value?
The received data size

is insufficient.
Check the received data size.
If the response message to

the next request has been
Response message process 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.
399
(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".
400
APPENDICES
Appendix 10.1 When Visual C++®.NET is used (single CPU

A
system)
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 QCPU in the E71-mounted station Q25HCPU
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
Refer to (3)(a) in this section.
Programming tool setting setting
Open setting Refer to (3)(b) in this section.
(b) Connected device side
Item Description
Microsoft® Windows® XP Professional Operating System

Operation environment
Ver.2002 Service Pack2
Ethernet interface board model name WINSOCK compatible board
Appendix 10.1 When Visual C++®.NET is used (single CPU system)

Library to link WSOCK32.LIB
Visual C++®.NET 2003 manufactured by Microsoft®

Software development environment
Corporation
This setting is not required because the ARP function can be
MAC address
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)
401
(3) Programming tool setting
Set the parameters using the programming tool as shown below.
(b) Open setting
402
APPENDICES
(4) Sample program on the connected device side A

The program example of the connected device accessing the Q25HCPU in the E71-mounted 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 created) socket()

(Bind) bind()
Passive open Active open UDP
(Open) listen() connect()
accept()
(Communications) send()/recv() sendto()/recvfrom()
(Sending/reception disabled) shutdown()
(Close) closesocket
Completed
403
/**************************************************************************/
/** 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 0 // Completion flag OFF

#define FLAG_ON 1 // Completion flag ON
#define SOCK_OK 0 // Normal completion
#define SOCK_NG -1 // Abnormal completion
#define BUF_SIZE 4096 // Receive buffer size
#define ERROR_INITIAL 0 // Initial error

#define ERROR_SOCKET 1 // Socket creation error
#define ERROR_BIND 2 // Bind error
#define ERROR_CONNECT 3 // Connection error
#define ERROR_SEND 4 // Send error
#define ERROR_RECEIVE 5 // Receive error
#define ERROR_SHUTDOWN 6 // Shutdown error
#define ERROR_CLOSE 7 // 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;
(To the next page)
404
APPENDICES
int nErrorStatus; // Error information storage variable

int Dmykeyin; // Dummy key input A
int Closeflag; // Connection completion flag
int socketno;
int main()
{
WORD wVersionRequested=MAKEWORD(1,1); // Winsock Ver 1.1 request
WSADATA wsaData;
int length; // Communication data length
unsigned char s_buf[BUF_SIZE]; // Send buffer
unsigned char r_buf[BUF_SIZE]; // Receive buffer
int rbuf_idx; // Receive data storage head index
int recv_size; // Number of receive data
struct sck_inf sc;
struct sockaddr_in hostdata; // External device side data
struct sockaddr_in aj71e71; // E71 side data
void Sockerror(int); // Error handling function
unsigned long ulCmdArg ; // Non-blocking mode setting flag
sc.my_addr.s_addr=htonl(INADDR_ANY); // External device side IP address

sc.my_port=htons(0); // External device side port number
sc.aj_addr.s_addr=inet_addr("192.0.1.253"); // E71 side IP address (C00001FDH)
sc.aj_port=htons(0x2000); // 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); // Error handling
return(SOCK_NG);
}
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); // Create socket for TCP/IP
if(socketno==INVALID_SOCKET){
Sockerror(ERROR_SOCKET); // Error handling
return(SOCK_NG);
}
(To the next page)
405
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; // Connection completion flag ON
// Set to non-blocking mode

ulCmdArg = 1;
ioctlsocket(socketno, FIONBIO, &ulCmdArg); // Set to non-blocking mode
// 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)
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);
(To the next page)
406
APPENDICES
// Perform receiving size check and receiving processing simultaneously

rbuf_idx = 0; // Receive data storage head index initialization A
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) {
return (SOCK_NG);
} else {
continue; // Repeat until messages are received
}
} else {
rbuf_idx += length; // Update the receive data storage
// position
recv_size += length; // Update the number of receive data

if(recv_size >= RECV_ANS_1) // Have all response messages been
// received?
break; // Stop repeating as messages have

// been received
}
}
r_buf[rbuf_idx] = '\0' ; // 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);
(To the next page)
407
// 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?
return (SOCK_NG);
}
return (SOCK_NG);
} else {
continue; // Repeat until messages are received
}
} else {
rbuf_idx += length; // Update the receive data storage
// position
recv_size += length; // Update the number of receive data
if(recv_size >= RECV_ANS_2) // Have all response messages been
// received?
break; // Stop repeating as messages have
// been received
}
}
r_buf[rbuf_idx] = '\0' ; // Set NULL at the end of receive data
printf("\receive data\n%s\n", r_buf);
if(shutdown(socketno,2)!=SOCK_OK){ // Processing to disable

// sending/receiving
Sockerror(ERROR_SHUTDOWN); // Error handling
return(SOCK_NG);
}
if(closesocket(socketno)!=SOCK_OK){ // Close processing
Sockerror(ERROR_CLOSE); // Error handling
return(SOCK_NG);
}

WSACleanup(); // Release Winsock.DLL
(To the next page)
408
APPENDICES
printf("\nAJ_test End.\n\n Normally completed. \n");

printf("Press any key to exit the program.\n"); A
Dmykeyin=getchar(); // Wait for key input
return(SOCK_OK);
}
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
}
printf("Press any key to exit the program.\n");

Dmykeyin=getchar(); // Wait for a key input
WSACleanup(); // Release Winsock.DLL
return;
}
409
Appendix 10.2 When Visual C++®.NET is used (redundant system)
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 the connected device.
(a) CPU module side
Item Description
A model name of the QCPU in the E71-mounted station Q25PRHCPU
System A C0.00.01.FCH (192.00.01.252)
E71 IP address
System B C0.00.01.FDH (192.00.01.253)
Ethernet operation
setting
Programming tool setting
Redundant setting Refer to (3)(c) in this section.
Item Description

Library WSOCK32.LIB
Visual C++®.NET 2003 manufactured by Microsoft®

Corporation
MAC address
used.
IP address Received upon an Active open
Port number Received upon an Active open

TCP/IP is used.

Because parameters are set on a programming tool, no program is required.

Write data to the data registers D0 to D4 (five points) of the redundant CPU (control system) in word units using
the library described above. If data write from the system A side fails due to a communication error or other
reasons at this time, data are written from the system B side to the data registers of the redundant CPU (control
system).
410
APPENDICES
(3) Programming tool setting A

Set the parameters using a programming tool as shown below.
(b) Open setting

411
(c) Redundant setting
(4) Sample program on the connected device

The program example of the connected device accessing the Q25PRHCPU in the E71-mounted station is
described. When this program is executed, the contents of the following communication messages are displayed
in order:
• Version of used Winsock
• Test starting message
• Batch write command message in word units
• Batch read response message in word units
• Test end message
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. QJSAMP) 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. QJSAMP.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 (QJSAMP) 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 (QJSAMP.EXE).
• Exit Visual C++®.NET.
• Execute QJSAMP.EXE.
412
APPENDICES
/**************************************************************************/
A
/** Sample program (program name: QJSAMP.CPP) **/
/** **/
/** This program is a sample program for testing the **/
/** connection of the E71 and external device. **/
/** This program accesses the data registers (D) of **/
/** the redundant CPU (control system) mounted with the E71. **/
/** **/
/** Copyright(C) 2005 Mitsubishi Electric Corporation **/
/** All Rights Reserved **/
/**************************************************************************/
#include <stdio.h>
#include <winsock.h>
#define FLAG_OFF 0 // End flag OFF

#define FLAG_ON 1 // End flag ON
#define SOCK_OK 0 // Normal terminationP
#define SOCK_NG -1 // Unsuccessful termination
#define BUF_SIZE 4096 // Receive buffer size
#define ERROR_NO_ERROR 0 // No error

#define ERROR_INITIAL 1 // Initial error
#define ERROR_SOCKET 2 // Socket creation error
#define ERROR_BIND 3 // Bind error
#define ERROR_CONNECT 4 // Connect error

#define ERROR_SEND 5 // Send error
#define ERROR_SHUTDOWN 6 // Shutdown error
#define ERROR_CLOSE 7 // Line close error
// Definition for checking receive size

#define RECV_ANS_1 22 // Response message receive size in reply to device write (3E frame)
typedef struct sck_inf{

struct in_addr my_addr;
unsigned short my_port;
struct in_addr qj_addr;
unsigned short qj_port;
} sck_inf;
int nErrorStatus; // Error information storage variable

int Dmykeyin; // Dummy key input
int ShutdownflagA; // Shutdown flag (for System A connection)
int ShutdownflagB; // Shutdown flag (for System B connection)
(To the next page)
413
int CloseflagA; // Connection end flag (for System A connection)
int CloseflagB; // Connection end flag (for System B connection)
int socketnoA;
int socketnoB;
int ConnectLastErrorA; // Connect processing error information (for System A connection)
int ConnectLastErrorB; // Connect processing error information (for System B connection)
int SendFlag; // Send completion flag
int main()
{
WORD wVersionRequested = MAKEWORD(1, 1); // Winsock Ver 1.1 request
WSADATA wsaData;
unsigned char s_buf[BUF_SIZE]; // Send buffer
unsigned char r_bufA[BUF_SIZE],r_bufB[BUF_SIZE]; // Receive buffer
struct sck_inf scA,scB;
struct sockaddr_in hostdataA,hostdataB; // External device side data
struct sockaddr_in qj71e71A,qj71e71B; // E71 side data
BOOL DataRecv(int, unsigned char *, int); // Receive processing function
void Sockerror(int, int); // Error handling function
unsigned long ulCmdArgA,ulCmdArgB; // Non-blocking mode setting flag

scA.my_addr.s_addr = scB.my_addr.s_addr = htonl(INADDR_ANY);
// External device side IP address
scA.my_port = scB.my_port = htons(0); // External device side port number
scA.qj_addr.s_addr = inet_addr("192.0.1.252");
// E71 side IP address (System A: C00001FCh)
scB.qj_addr.s_addr = inet_addr("192.0.1.253");
// E71 side IP address (System B: C00001FDh)
scA.qj_port = scB.qj_port = htons(0x2000); // E71 side port number
ShutdownflagA = ShutdownflagB = FLAG_OFF; // Shutdown flag OFF
CloseflagA = CloseflagB = FLAG_OFF; // Connection end flag OFF
nErrorStatus = WSAStartup(wVersionRequested, &wsaData); // Winsock initial processing
ConnectLastErrorA = ERROR_NO_ERROR;
// Connect processing error information initialization (for System A)
ConnectLastErrorB = ERROR_NO_ERROR;
// Connect processing error information initialization (for System B)
if(nErrorStatus != SOCK_OK) {
Sockerror(ERROR_INITIAL, ERROR_INITIAL); // Error handling
return (SOCK_NG);
}
printf("Winsock Version is %1d.%1d\n", HIBYTE(wsaData.wVersion),

LOBYTE(wsaData.wVersion));
printf("QJ_test Start\n");
(To the next page)
414
APPENDICES
// System A connect processing

socketnoA = socket(AF_INET, SOCK_STREAM, 0); A
// TCP/IP socket (for System A connection) creation
if(socketnoA != INVALID_SOCKET) {
hostdataA.sin_family = AF_INET;
hostdataA.sin_port = scA.my_port;
hostdataA.sin_addr.s_addr = scA.my_addr.s_addr;
if(bind(socketnoA, (LPSOCKADDR)&hostdataA, sizeof(hostdataA)) == SOCK_OK) {

// Bind (System A)
qj71e71A.sin_family = AF_INET;
qj71e71A.sin_port = scA.qj_port;
qj71e71A.sin_addr.s_addr = scA.qj_addr.s_addr;
if(connect(socketnoA, (LPSOCKADDR)&qj71e71A, sizeof(qj71e71A)) ==

SOCK_OK) {
// Connect (Active open: System A)
ShutdownflagA = FLAG_ON; // Shutdown flag ON
CloseflagA = FLAG_ON; // Connection end flag ON
ulCmdArgA = 1;
ioctlsocket(socketnoA, FIONBIO, &ulCmdArgA);
// Set to non-blocking mode (for System A connection)
} else {
ConnectLastErrorA = ERROR_CONNECT; // Connection establishment failure
}
} else {

ConnectLastErrorA = ERROR_BIND; // Bind failure
}
} else {
ConnectLastErrorA = ERROR_SOCKET; // Socket creation failure
}
// System B connect processing

socketnoB = socket(AF_INET, SOCK_STREAM, 0);
// TCP/IP socket (for System B connection) creation
if(socketnoB != INVALID_SOCKET) {
hostdataB.sin_family = AF_INET;
hostdataB.sin_port = scB.my_port;
hostdataB.sin_addr.s_addr = scB.my_addr.s_addr;
if(bind(socketnoB, (LPSOCKADDR)&hostdataB, sizeof(hostdataB)) == SOCK_OK) {

// Bind (System A)
qj71e71B.sin_family = AF_INET;
qj71e71B.sin_port = scB.qj_port;
qj71e71B.sin_addr.s_addr = scB.qj_addr.s_addr;
(To the next page)
415
if(connect(socketnoB,(LPSOCKADDR)&qj71e71B,sizeof(qj71e71B))== SOCK_OK) {
// Connect (Active open: System B)
ShutdownflagB = FLAG_ON; // Shutdown flag ON
CloseflagB = FLAG_ON; // Connection end flag ON
ulCmdArgB = 1;
ioctlsocket(socketnoB, FIONBIO, &ulCmdArgB);
// Set to non-blocking mode (for System B connection)
} else {
ConnectLastErrorB = ERROR_CONNECT; // Connection establishment failure
}
} else {
ConnectLastErrorB = ERROR_BIND; // Bind failure
}
} else {
ConnectLastErrorB = ERROR_SOCKET; // Socket creation failure
}
// Connect completion processing
if( (CloseflagA == FLAG_OFF) && (CloseflagB == FLAG_OFF) ){
// When both systems are abnormal
Sockerror(ConnectLastErrorA, ConnectLastErrorB); // Error handling
return (SOCK_NG);
}
strcpy((char*)(s_buf), "500000FF03D000002C000A14010000D
*0000000005112233445566778899AA");
// D0-D4 batch write request (3E frame, addressed to control system)
length = strlen((char*)(s_buf));
printf("Send starts. Press any key. \n");

Dmykeyin = getchar(); // Waiting for key input
SendFlag = FLAG_OFF; // Send completion flag OFF

// System A send processing
if( CloseflagA == FLAG_ON && (SendFlag == FLAG_OFF) ){
if(send(socketnoA, (char*)(s_buf), length, 0) != SOCKET_ERROR) {
// Data send (System A)
printf("\n Send data (System A) \n%s\n", s_buf); // Send data display (System A)
SendFlag = FLAG_ON; // Send completion flag ON
// Receive processing
if(DataRecv(socketnoA, r_bufA, RECV_ANS_1) == TRUE) { // Data receive
printf("\n Receive data (System A) \n%s\n", r_bufA); // Receive data display
} else {
printf("Receive failure (System A) \n");
}
} else {
printf("Send failure (System A) \n");
}
}
(To the next page)
416
APPENDICES
// System B send processing

if( (CloseflagB == FLAG_ON) && (SendFlag == FLAG_OFF) ){ A
if(send(socketnoB, (char*)(s_buf), length, 0) != SOCKET_ERROR) {
// Data send (System B)
printf("\n Send data (System B) \n%s\n", s_buf); // Send data display (System B)
SendFlag = FLAG_ON; // Send completion flag ON
// Receive processing
if(DataRecv(socketnoB, r_bufB, RECV_ANS_1) == TRUE) { // Data receive
printf("\n Receive data (System B) \n%s\n", r_bufB); // Receive data display
} else {
printf("Receive failure (System B) \n");
}
}else{
printf("Send failure (System B) \n");
}
}
// Send completion processing

if( SendFlag == FLAG_OFF ){
Sockerror(ERROR_SEND, ERROR_SEND); // Error handling
return (SOCK_NG);
}
if(CloseflagA == FLAG_ON) {
ShutdownflagA = FLAG_OFF; // Shutdown flag OFF
if(shutdown(socketnoA, 2) != SOCK_OK) { // Send/receive inhibit processing (System A)
Sockerror(ERROR_SHUTDOWN, ERROR_NO_ERROR); // Error handling
return (SOCK_NG);

}
}
if(CloseflagB == FLAG_ON) {
ShutdownflagB = FLAG_OFF; // Shutdown flag OFF
if(shutdown(socketnoB, 2) != SOCK_OK) { // Send/receive inhibit processing (System B)
Sockerror(ERROR_NO_ERROR, ERROR_SHUTDOWN); // Error handling
return (SOCK_NG);
}
}
CloseflagA = FLAG_OFF; // Connection end flag OFF
if(closesocket(socketnoA) != SOCK_OK) { // Close processing (System A)
Sockerror(ERROR_CLOSE, ERROR_NO_ERROR); // Error handling
return (SOCK_NG);
}
CloseflagB = FLAG_OFF; // Connection end flag OFF
if(closesocket(socketnoB) != SOCK_OK) { // Close processing (System B)
Sockerror(ERROR_NO_ERROR, ERROR_CLOSE); // Error handling
return (SOCK_NG);
}
(To the next page)
417
WSACleanup(); // Winsock.DLL release
printf("\nQJ_test End. \n\nNormally completed. \n");

printf("Program is closed. Press any key. \n");
return (SOCK_OK);
}
BOOL DataRecv(int socketno, unsigned char *pR_buf, int size_max) // Receive processing function
{
int rbuf_idx; // Receive data storage starting index
int recv_size; // Number of received data
// Performs receive processing while simultaneously making size check

rbuf_idx = 0; // Receive data storage starting index initialization
recv_size = 0; // Initializes the number of received data
while(1) {
length = recv(socketno, ((char*)(pR_buf + rbuf_idx)), (BUF_SIZE - rbuf_idx), 0);
// Response data receive
if(length == 0) { // Has connection been cut?
return (FALSE); // Error handling
}
return (FALSE); // Error handling
} else {
continue; // Repeated until data are received
}
} else {
rbuf_idx += length; // Updates receive data storage position
recv_size += length; // Updates the number of received data
if(recv_size >= size_max) // Have all response messages received?
break; // Stops repeating as data are received
}
}
*(pR_buf + rbuf_idx) = '\0' ; // At the end of received data
// set NULL
return (TRUE); // Normal termination
}
(To the next page)
418
APPENDICES
void Sockerror(int error_kind_A, int error_kind_B) // Error handling function

{ A
if (error_kind_A == ERROR_INITIAL){
printf("Initial processing is abnormal. \n");
}
else{
switch(error_kind_A){
case ERROR_SOCKET:
printf("Socket could not be created. (System A)\n");
break;
case ERROR_BIND:
printf("Bind could not be executed. (System A)\n");
break;
case ERROR_CONNECT:
printf("Connection could not be established. (System A)\n");
break;
case ERROR_SEND:
printf("Send could not be executed. \n");
break;
printf("Shutdown could not be executed. (System A)\n");
break;
case ERROR_CLOSE:
printf("Normal close could not be executed. (System A)\n");
break;
}

switch(error_kind_B){
case ERROR_SOCKET:
printf("Socket could not be created. (System B)\n");
break;
case ERROR_BIND:
printf("Bind could not be executed. (System B)\n");
break;
case ERROR_CONNECT:
printf("Connection could not be established. (System B)\n");
break;
printf("Shutdown could not be executed. (System B)\n");
break;
case ERROR_CLOSE:
printf("Normal close could not be executed. (System B)\n");
break;
}
}
printf("Error code is %d. \n", nErrorStatus);
(To the next page)
419
if (ShutdownflagA == FLAG_ON){
nErrorStatus = shutdown(socketnoA, 2); // Shutdown processing (System A)
ShutdownflagA = FLAG_OFF; // Shutdown flag OFF (System A)
}
if (ShutdownflagB == FLAG_ON){
nErrorStatus = shutdown(socketnoB, 2); // Shutdown processing (System B)
ShutdownflagB = FLAG_OFF; // Shutdown flag OFF (System B)
}
if (CloseflagA == FLAG_ON){
nErrorStatus = closesocket(socketnoA); // Close processing (System A)
CloseflagA = FLAG_OFF; // Connection end flag OFF (System A)
}
if (CloseflagB == FLAG_ON){
nErrorStatus = closesocket(socketnoB); // Close processing (System B)
CloseflagB = FLAG_OFF; // Connection end flag OFF (System B)
}
printf("Program is closed. Press any key. \n");

WSACleanup(); // Winsock.DLL release
return;
}
420
APPENDICES
Appendix 10.3 When Visual Basic®.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.
(a) CPU module side
Item Description
A model name of the QCPU in the E71-mounted station Q25HCPU
E71 IP address C0.00.01.FDH (192.00.01.253)
Ethernet operation
Programming tool Setting setting
Item Description

Visual Basic®.NET 2003 manufactured by Microsoft®

Corporation
MAC address
used.
IP address An arbitrary number is assigned.
Port number An arbitrary number is assigned.

TCP/IP is used.

Because parameters are set on the programming tool, no program is required.

Data (D0 to D4) in the CPU module are read out.
421
(3) Programming tool setting
Set the parameters using the programming tool as shown below.
(b) Open setting
422
APPENDICES
(4) Sample program on the connected device side A

The program example of the connected device accessing the Q25HCPU in the E71-mounted station is
described. In this program, data of D0 to D4 (five points) in the Q25HCPU in the E71-mounted station are read
with an A-compatible 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.
Button2: Sends the A-compatible 1E frame command

(reading in units of words).
Button3: Cut off the line.
Button5: Button4: Ends the program.

Checks the connection status.
423
[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
(To the next page)
424
APPENDICES
'Form overrides dispose to clean up the component list.

Protected Overloads Overrides Sub Dispose(ByVal Disposing As Boolean) A
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
Dim Ajsock As Sockets.Socket
Private State As Boolean = False
'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.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
'
(To the next page)
425
Me.Command4.Text = "Close"
'
'Command3
'
Me.Command3.Text = "disconnect"
'
'Command2
'
Me.Command2.Text = "Sending a E71 command"
'
'Command1
'
Me.Command1.Text = "connect"
(To the next page)
426
APPENDICES
'
'Form1 A
'
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.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
#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
(To the next page)
427
Private Sub Command1_Click(ByVal eventSender As System.Object, ByVal eventArgs
As System.EventArgs) Handles Command1.Click
'Connect to the Ethernet interfece 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

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
(To the next page)
428
APPENDICES

As System.EventArgs) Handles Command3.Click A
'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

'End the program.
End
End Sub

'Check the connection state.
If State Then
MsgBox("Connected")
Else
MsgBox("Closed")
End If
End Sub

End Class
429
Appendix 11 Checking the Serial Number and Function
Version
The serial number and function version of the E71 can be checked with the following.
• Rating plate
• Front of the module
• Programming tool system monitor
(1) Checking on the rating plate

The rating plate is located on the side of the module. It also shows the MAC address and certification marks of
applicable standards.
ETHERNET I/F UNIT

QJ71E71-100
MAC address MAC ADD. 080070442FCF
Function version
100915000000000-D
Serial No. Applicable standards
(first 5 digits)
(2) Checking on the front of the module

The serial number and function version on the rating plate are printed on the front (at the bottom) of the module.
100915000000000-D Function version
Serial No.
430
APPENDICES
(3) Checking on the system monitor (product information list window) A

The serial number and function version can be checked on the system monitor of the programming tool. The
"Serial No." column shows the serial numbers and the "Ver" column shows the function versions. Because an
E71 does not support the production number, "-" is displayed on the "Production Number" column.
[Diagnostics] [System Monitor] button
Appendix 11 Checking the Serial Number and Function Version

The serial number displayed on the "Product Information List" window of the programming tool may differ from that on the
rating plate or on the front of the module.
• The serial number on the rating plate or on the front of the module indicates the management information of the
product.
• The serial number displayed on the "Product Information List" window is the functional information of the product.
The functional information of the product is updated when a function is added.
431
Appendix 11.1 Compatible software versions
The following table lists the compatible software versions.
Software version
CPU module
GX Developer GX Works2
Basic model QCPU Q00(J)/Q01CPU Version 7 or later*1
High Performance model
Q02(H)/Q06H/Q12H/Q25HCPU Version 4 or later*2
QCPU
Q02PH/Q06PHCPU Version 8.68W or later
Process CPU
Q12PH/Q25PHCPU Version 7.10L or later
Redundant CPU Q12PRH/Q25PRHCPU Version 8.18U or later*3
Q00U(J)/Q01UCPU Version 8.76E or later
Q02U/Q03UD/Q04UDH/ Q06UDHCPU Version 8.48A or later Refer to the GX Works2
Q10UDH/Q20UDHCPU Version 8.76E or later Version 1 Operating
Manual (Common).
Universal model Q13UDH/Q26UDHCPU Version 8.62Q or later
QCPU Q03UDE/Q04UDEH/ Q06UDEH/
Version 8.68W or later
Q13UDEH/Q26UDEHCPU
Q10UDEH/Q20UDEHCPU Version 8.76E or later
Q50UDEH/Q100UDEHCPU Incompatible
Safety CPU QS001CPU Version 8.65T or later
CPU module other than the above Incompatible
MELSECNET/H remote I/O station Version 6 or later
*1 To use a module in a multiple CPU system, Version 8 or later is required.

*2 To use a module in a multiple CPU system, Version 6 or later is required.
*3 To mount a module on an extension base unit, Version 8.45X or later is required.
Remark
For the compatible versions of MX Component, refer to the following.
MX Component Version 3 Operating Manual
432
APPENDICES
Appendix 12 External Dimension Diagram A

This appendix provides the external dimension diagrams of an E71.
(1) QJ71E71-100
98 (3.86)
*2
R1
(*1)
4 (0.16)
23 (0.91)
90 (3.54) 27.4 (1.08)
(Unit: mm (in.))
Appendix 12 External Dimension Diagram

*1 When connecting a twisted pair cable, keep the bending radius near the connector (reference value: R1) above four
times the outside diameter of the cable.
*2 The orientation of the connector is different (rotated) depending on the serial number.
433
(2) QJ71E71-B5
98 (3.86)
R2
(*1)
DC power supply for
4 (0.16)
a transceiver
23 (0.91)
90 (3.54) 8.5 (0.33) 27.4 (1.08)
(Unit: mm (in.))
*1 When connecting an AUI cable, keep the bending radius near the connector (reference value: R2) above four times the
outside diameter of the cable.
(3) QJ71E71-B2
29.2 (1.15)
98 (3.86)
23.65
(0.93)
4 (0.16)
23 (0.91)
90 (3.54) 11.5 (0.45) 27.4 (1.08)
(Unit: mm (in.))
434
APPENDICES
Appendix 13 ASCII Code List A

The following is the ASCII code table.
Higher 4 bits
Hexadecimal 0 1 2 3 4 5 6 7 8–F
Binary 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
Lower 7 0111 BEL ETB ‘ 7 G W g w
4 bits 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
Appendix 13 ASCII Code List
435
INDEX
0 to 9 D
100BASE-TX connection . . . . . . . . . . . . . . . . . . . 74 Data receiving using an interrupt program . . . . . . 149
100Mbps hub . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Data receiving using the main program . . . . . . . . 146
10BASE2 connection . . . . . . . . . . . . . . . . . . . . . . 77 Data transmission speed . . . . . . . . . . . . . . . . . . . 29
10BASE5 coaxial cable . . . . . . . . . . . . . . . . . . . . 76 DC power supply (power supply for a transceiver)
10BASE5 connection . . . . . . . . . . . . . . . . . . . . . . 76 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
10BASE-T connection . . . . . . . . . . . . . . . . . . . . . 75 Dedicated instructions . . . . . . . . . . . . . . . . . . . . 238
10Mbps hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Default router IP address . . . . . . . . . . . . . . . . . . 193
12VDC external power supply capacity. . . . . . . . . . 29 Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4E frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Do not wait for OPEN (Communications impossible at
STOP time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
A
E
Abnormal codes . . . . . . . . . . . . . . . . . . . . . . . . . 315
A-compatible 1E frame . . . . . . . . . . . . . . . . . . . . 106 E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
ACPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 E71-mounted station . . . . . . . . . . . . . . . . . . . . . . 15
Active open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 ECPRTCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Always wait for OPEN (Communication possible at E-mail function . . . . . . . . . . . . . . . . . . . . . . . . . . 33
STOP time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Enable online change . . . . . . . . . . . . . . . . . . . . . . 87
AnACPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 End codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
AnNCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 ERRCLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
AnUCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 ERRRD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Ethernet cable . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
ASCII code . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 Ethernet diagnostics . . . . . . . . . . . . . . . . . . . . . 341
AUI cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Ethernet operation setting . . . . . . . . . . . . . . . . . . . 87
Auto-open UDP port . . . . . . . . . . . . . . . . . . . . . . 352 External dimension diagram . . . . . . . . . . . . . . . . 433
B F
Basic functions . . . . . . . . . . . . . . . . . . . . . . . . . . 31 File transfer (FTP server) function . . . . . . . . . . . . . 33
Basic model QCPU . . . . . . . . . . . . . . . . . . . . . . . 16 Fixed buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Basic setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Fixed buffer communication . . . . . . . . . . . . . . . . 151
Broadcast communications . . . . . . . . . . . . . . . . . 162 FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Full-duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
BUFRCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Fullpassive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
BUFRCVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
BUFSND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
G
Built-in Ethernet port QCPU . . . . . . . . . . . . . . . . . 15
General specifications . . . . . . . . . . . . . . . . . . . . . 28
C GP.ECPRTCL . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Group No. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Cascade connection . . . . . . . . . . . . . . . . . . . . . . . 29 GX Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
CC-Link IE Controller Network, CC-Link IE Field GX Works2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Network, MELSECNET/H, MELSECNET/10 relay
communications . . . . . . . . . . . . . . . . . . . . . . . . . . 33
H
Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 H/W test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Communication data code. . . . . . . . . . . . . . . . . . . 87 Half-duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Communications using a fixed buffer . . . . . . . . . . 141 Hardware test . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Communications using a random access buffer . . . 176 High Performance model QCPU . . . . . . . . . . . . . . 16
Communications using an auto-open UDP port . . . 196 How to turn off the COM.ERR. LED . . . . . . . . . . . 342
Communications using data link instructions . . . . . . 33 HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Compliance with the EMC and Low Voltage Directives Hub connection status monitor function . . . . . . . . 213
...................................... 6
Connecting MELSOFT products and a GOT . . . . . 102
Connection target. . . . . . . . . . . . . . . . . . . . . . . . 103 I
Cross cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
ICMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Initial process . . . . . . . . . . . . . . . . . . . . . . . . . . 356
436
Initial timing . . . . . . . . . . . . . . . . . . . . . . . . . . 87,88 Part names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Input format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Passive open . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Performance specifications . . . . . . . . . . . . . . . . . . 29
Intelligent function module . . . . . . . . . . . . . . . . . . . 16 Physical addresses . . . . . . . . . . . . . . . . . . . . . . . 189
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 PING command . . . . . . . . . . . . . . . . . . . . . . . . . 371
Internal current consumption (5VDC) . . . . . . . . . . . 29 PING test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Interrupt pointer setting . . . . . . . . . . . . . . . . . . . . 152 POP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 I
Interrupt settings . . . . . . . . . . . . . . . . . . . . . . . . . 153 Port numbers used for the E71 . . . . . . . . . . . . . . . 352
IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Predefined protocol support function . . . . . . . . . . . . 16
IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Procedure exist . . . . . . . . . . . . . . . . . . . . . . . . . 141
IP address in use detection function . . . . . . . . . . . 214 Procedures before operation . . . . . . . . . . . . . . . . . 63
IP address setting . . . . . . . . . . . . . . . . . . . . . . . . . 87 Process CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
IP filter function . . . . . . . . . . . . . . . . . . . . . . . . . . 197 Product information list window . . . . . . . . . . . . . . 431
Programming tool . . . . . . . . . . . . . . . . . . . . . . . . . 16
4
L
Q
LED indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
List of buffer memory addresses . . . . . . . . . . . . . . . 38 QCPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
List of dedicated instructions . . . . . . . . . . . . . . . . 238 QCPU-mounted station . . . . . . . . . . . . . . . . . . . . . 16
List of I/O signals . . . . . . . . . . . . . . . . . . . . . . . . . 35 QnA-compatible 3E frame . . . . . . . . . . . . . . . . . . 106
Logical addresses . . . . . . . . . . . . . . . . . . . . . . . . 189 QnACPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
R
M
Rating plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
MAC address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 7
MC protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 RECV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
MC protocol communications . . . . . . . . . . . . . . . . 105 RECVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
MELSECNET/10 . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Redundant CPU . . . . . . . . . . . . . . . . . . . . . . . . . . 16
MELSECNET/H . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Redundant system function . . . . . . . . . . . . . . . . . 216 8
MELSECNET/H remote I/O station . . . . . . . . . . . . . 15 Reinitialization process . . . . . . . . . . . . . . . . . . . . 360
MELSOFT application transmission port (TCP) . . . 352 Remote password . . . . . . . . . . . . . . . . . . . . . . . . 203
MELSOFT application transmission port (UDP) . . . 352 Remote password check . . . . . . . . . . . . . . . . . . . 205
MELSOFT connection . . . . . . . . . . . . . . . . . . . . . 103 REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Retainer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
MRECV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 RG58A/U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
MSEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 RG58C/U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
MX Component. . . . . . . . . . . . . . . . . . . . . . . 15,393 RJ45 connector . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Router information . . . . . . . . . . . . . . . . . . . . . . . 193
Router IP address . . . . . . . . . . . . . . . . . . . . . . . . 195
N
Router relay function . . . . . . . . . . . . . . . . . . . . . . 191
Network components . . . . . . . . . . . . . . . . . . . . . . . 74
Network No. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 S
Network parameter . . . . . . . . . . . . . . . . . . . . . . . . 85
Network type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Safety CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
No procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Self-diagnostic tests . . . . . . . . . . . . . . . . . . . . . . 376
N-type terminating resistor . . . . . . . . . . . . . . . . . . . 76 Self-loopback test . . . . . . . . . . . . . . . . . . . . . 86,376
Number of occupied I/O points . . . . . . . . . . . . . . . . 29 SEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Send frame setting . . . . . . . . . . . . . . . . . . . . . . . . 87
Shielded twisted pair cable (STP) . . . . . . . . . . . . . . 74
O
SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Offline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Special functions . . . . . . . . . . . . . . . . . . . . . . . . . 33
OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 SREAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Open setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Start I/O No. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Open system . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Station No. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
OPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Straight cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Subnet address . . . . . . . . . . . . . . . . . . . . . . . . . 193
Subnet mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
P Subnet mask pattern . . . . . . . . . . . . . . . . . . . . . . 192
SWRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Packing list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
System configuration. . . . . . . . . . . . . . . . . . . . . . . 65
Pairing open . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Parameter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
437
T
TCP existence confirmation setting . . . . . . . . . . . . 87
TCP/IP communications . . . . . . . . . . . . . . . . . . . . 91
Transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Transceiver cable. . . . . . . . . . . . . . . . . . . . . . . . . 76
Transmission specifications. . . . . . . . . . . . . . . . . . 29
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 285
U
UDP/IP communications . . . . . . . . . . . . . . . . . . . . 99
UINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Universal model QCPU . . . . . . . . . . . . . . . . . . . . . 16
Unlock process . . . . . . . . . . . . . . . . . . . . . . . . . 204
Unpassive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Unshielded twisted pair cable (UTP). . . . . . . . . . . . 75
W
Web function . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
When using data link instructions . . . . . . . . . . . . . 240
Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Wiring with the QJ71E71-100 . . . . . . . . . . . . . . . . 79
Wiring with the QJ71E71-B2 . . . . . . . . . . . . . . . . . 82
Wiring with the QJ71E71-B5 . . . . . . . . . . . . . . . . . 80
WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Z
Z.BUFRCVS . . ......................... 269
ZNRD . . . . . . . ......................... 239
ZNWR . . . . . . ......................... 239
ZP.BUFRCV . . ......................... 265
ZP.BUFSND . . ......................... 261
ZP.CLOSE . . . ......................... 247
ZP.ERRCLR . . ......................... 272
ZP.ERRRD . . . ......................... 275
ZP.OPEN . . . . ......................... 243
ZP.UINI. . . . . . ......................... 279
438
REVISIONS
*The manual number is given on the bottom left of the back cover.
Print Date *Manual Number Revision
Dec., 1999 SH(NA)-080009-A First Edition
Oct., 2000 SH(NA)-080009-B • Reflect the contents of the function version B.
• Put Windows® base software products together from Mitsubishi Programmable
Controller MELSEC series to Mitsubishi integrated FA software MELSOFT series.
• Standardize the name from software package (GPP function) to product name (GX
Developer).
Correction
Entire manual (change MELSECNET/10H to MELSECNET/H), SAFETY
PRECAUTIONS, Contents, About Manuals, The Manual's Usage and Structure
(Structure of this manual (2)), About the Generic Terms and Abbreviations, Section 1.1,
1.2, 1.3, 2.1, 2.2, 2.3, 2.5, 2.6, 3.1, 3.2, 3.5, 3.6, 3.7, 3.8(2), 4.1.1, 4.2, 4.3, 4.4.1, 4.5
(entire), 4.5.1 (Table), 4.6, 4.7, 4.8, 4.9 (entire), 5.2.1, 5.2.2, 5.3, 5.5, 5.6 (entire), 5.7.2,
5.8, Chapter 6 (entire), Section 7.1, 7.2, 7.3.1, 7.3.2, 7.4.2, 7.5.2, Chapter 8, Section
8.1, 8.2, 8.3.1, 8.3.2, 8.5.1, 8.6.2, 9.2.3, 10.2 to 10.8, Chapter 11, Section 11.1.1,
11.1.2(2), 11.2, 11.2.2, 11.2.4, 11.3 (5) (6), 11.3.1 to 11.3.3, 11.4, 11.4.4, Appendix 1
(entire), Appendix 2 (entire), Appendix 3, Appendix 8 (entire), Appendix 11
Addition
Entire manual (add the explanation on MELSECNET/H remote I/O station), The
Manual's Usage and Structure (2) (e), Section 5.4, 11.2, 11.2.1, 11.2.3, 11.3.1 (error
code 63H), 11.3.3 (error code 0063H, C086H, C087H, C0DAH, C0DBH, C119H, C200H to
C205H)
Jun., 2001 SH(NA)-080009-C • Added the description of the model QJ71E71-100 Ethernet interface module.
Model Addition
QJ71E71-100
Correction
Compliance with the EMC and Low Voltage Directives, The Manual's Usage and
Structure, About the Generic Terms and Abbreviations, Product Configuration, Section
1.2, 1.3, 1.4 (Figure), 2.1, 2.2, 2.3 (POINT), 2.4, 2.5, 2.7, Chapter 3 (entire), Section 4.2,
4.3, 4.4, 4.7, 4.8.1, 5.1 (Figure), 5.3 (1)(Figure), 5.4, 5.5, 5.6 (POINT), 5.6.1, 5.6.2, 5.8
(2) (3), 5.9.1 (1) (2), 5.9.3 (Figure), 5.9.5, 5.9.6 (3), 5.9.7, 6.2, 7.1, 7.2 (Figure), 7.3.1
(Figure), 7.3.2 (2) (Figure), 7.5.2, 8.2 (Figure), 8.3.1 (Figure), 8.3.2 (2) (Figure), 8.5.1,
8.6.2, 9.2.3 (2) (Figure), 10.1 (POINT), 10.6, 10.8, 11.1.1, 11.1.2, 11.2.3, 11.3 (7)
(Figure), 11.3.3 (error codes C113H, C114H, and C14EH), 11.4 (POINT), 11.4.6 (Figure),
Appendix 1.1, Appendix 2.1, 2.2 (2), Appendix 8.3, Appendix 11
Addition
Section 1.2 (5) (6), 2.2 (1), 2.6, 5.4.2, 11.3 (6), 11.3.2 (error code 1FH), 11.3.3 (error
codes C0F7H and C300H), Appendix 4, Appendix 7, Appendix 9, Appendix 11
Oct., 2001 SH(NA)-080009-D

Correction
Section 1.2 (4) (7), 1.3, 1.4 (1), 2.2 (POINT), 2.5 (1), 2.7 (1), 3.1, 3.5, 3.8, 4.1.1 (2), 4.3,
4.4.1 (POINT), 4.7 (5), 5.2.2 (REMARKS), 5.2.3, 5.4.2, 5.5 (Table), 5.6.1, 5.6.2, 5.6.3,
10.1, Section 11.2.2 (2), 11.2.4, 11.3.3, Appendix 1.1, Appendix 8.2, Appendix 9
Addition
Section 10.9
439
Mar., 2002 SH(NA)-080009-E
Correction
About the Generic Terms and Abbreviations, Section 1.2 (7), 2.1(1), 2.7 (1), 3.7 (Table),
5.1 (Figure), 5.2.2 (REMARKS), 5.2.3, 7.5.1, 10.9, 11.3.1 (Table), 11.3.3(REMARKS),
11.4.2 (Figure), Appendix 1.1 (2) (Table), Appendix 2.2 (2)(a), Appendix 8
Addition
Section 11.3.3 (error code C1BAH), 11.4 2, Appendix 4 (4)
Apr., 2003 SH(NA)-080009-F

Model Addition
QJ71E71-B5
Model Deletion
QJ71E71
Correction
SAFETY PRECAUTIONS, About the Generic Terms and Abbreviations, Section 1.2 (1)
(5) (6), 1.3, 1.4 (1), 2.1, 2.2, 2.5, 2.6, 2.7, 3.1, 3.4, 3.8, 4.1, 4.3, 4.4, 4.5, 4.6, 5.2.2
(REMARKS)(5), 5.2.3 (REMARKS), 5.3, 5.4.2 (1)(c), 5.4.3, 5.5 (6), 5.6 (2) (POINT),
5.9.1, 5.9.6 (3) (6), 6.2, 10.8, 10.9, 11.1.1, 11.2.2(2), 11.3, 11.4.5 (Figure), Appendix 1.1,
Appendix 2, Appendix 4, Appendix 7, Appendix 10, Appendix 11
Addition
Section 11.2.1 (POINT), 11.3.3 (error code C0B2H, C0E0H to C0EFH, C171H to C17FH),
Appendix 9
Jul., 2003 SH(NA)-080009-G
Correction
The Manual's Usage and Structure, Section 1.4 (1), 2.2 (1), 2.7, 3.8, 4.7, 5.2.2
(REMARKS), 5.5 (POINT), 5.6.1, 5.6.2, 7.5.2, 8.6.2, 11.4, Appendix 2, Appendix 8.1,
Appendix 11, Appendix 12
Sep., 2003 SH(NA)-080009-H
Correction
Section 1.4 (1), 3.8, 5.2.3, Appendix 2.1, Appendix 8
Jun., 2004 SH(NA)-080009-I • Addition of the description of function version D
Correction
About the Generic Terms and Abbreviations, Section 1.1 (7), 1.3, Chapter 2 (entire),
Section 3.6, 3.8, 4.5, 4.6, 5.3, 5.5, 5.6 (2) (POINT), 5.8 (POINT), 6.1.4, 10.9, Appendix
1, Appendix 4, Appendix 11, Appendix 12
Addition
Section 1.1 (9), 5.10, 5.11, 11.3.3, 11.4.7, Appendix 8.2
Aug., 2005 SH(NA)-080009-J
Correction
SAFETY PRECAUTIONS, Section 1.1 (5), 1.3, 2.2, 2.7, 5.2.3, 5.11.3, 10.9, 11.3.3
(error code C062H, C0B9H, C0C0H, C0C4H, C0D7H), Appendix 1.1, Appendix 4 (4),
Appendix 11
Addition
Appendix 8.1, Appendix 8.2, Appendix 9
Jun., 2006 SH(NA)-080009-K
Correction
Section 2.1, 3.8, 5.6.3, 5.7.2, 5.9.3, 7.1, 7.3.1, 7.5.2, 8.1, 8.3.1, 8.6.2, 10.2, 10.6, 10.7,
10.8
Addition
Section 2.7, 3.4, 5.6, 7.3.1, 10.1
440
Jun., 2007 SH(NA)-080009-L
Correction
About the Generic Terms and Abbreviations, Section 1.2 (9), 1.3, 2.1, 2.7, 3.6, 4.1.1,
4.5.2 (12), 4.6, 4.9.1, 5.6 (1), (2) Point, 5.11, 5.11.3, 6.1.4, 10.2 to 10.9, 11.3.3, 11.4.7,
Appendix 1.1, Appendix 4 (4), Appendix 9.1 (4)
Addition
Section 2.5.1, 2.5.2
Oct., 2008 SH(NA)-080009-M
Correction
SAFETY PRECAUTIONS, Compliance with the EMC and Low Voltage Directives, The
Manual's Usage and Structure, About the Generic Terms and Abbreviations, Section 1.2
to 1.4, Chapter 2, Section 3.1 to 3.6, 3.8, 4.1.1, 4.3 4.4.2, 4.4.3, 4.5.2, 4.6 to 4.8, 5.1 to
5.5, 5.6.1, 5.6.2, 5.8, 5.9.1, 5.9.3, 5.9.5, 5.9.7, 5.11.3, 5.11.5, 6.1.1, 6.1.3, 6.1.4,6.2,
7.3.2, 7.5.2, 8.6.2, Chapter 10, Section 11.2.1, 11.3, 11.4, Appendix 1.1, Appendix 2.1,
Appendix 2.2, Appendix 4, Appendix 7, Appendix 9.1, Appendix 12
Apr., 2009 SH(NA)-080009-N
Correction
Section 1.3, 2.2, 2.7, 4.3, 5.2.3, 5.11.5, 8.5.1, 10.9, Appendix 1.1
Aug., 2010 SH(NA)-080009-O
Correction
Addition of "CC-Link IE Field Network" to the whole manual SAFETY PRECAUTIONS,
About the Generic Terms and Abbreviations, Section 1.2, 2.1, 2.5.2, 4.1.1, 4.9.1, 5.9.3,
5.11, 5.12.3, 11.3.3, 11.4
May, 2012 SH(NA)-080009-P The entire manual has been revised due to the manual layout change.
Jun., 2013 SH(NA)-080009-Q
Correction
SAFETY PRECAUTIONS, RELEVANT MANUALS, TERM, Chapter 1, Section 3.1, 3.2,
3.3.1, 3.3.2, 3.4, 3.5.2, 5.1, 7.1.1, 7.1.4, 12.4, 12.8, 12.9.3, 14.3.4, 14.6.2, 14.6.3,
14.6.4, 14.7, 15.1, 15.2.1, 15.5, 15.6, 15.8, 15.9, 15.10, 15.11, 15.12, 15.13, 16.4, 16.6,
Appendix 1, Appendix 3, Appendix 4, Appendix 5, Appendix 7, Appendix 10, Appendix
11.1
Addition
Chapter 10, 11, Section 15.7, 16.3, 16.5.5, 16.5.6, 16.5.7, Appendix 8
Apr., 2015 SH(NA)-080009-R
Correction
RELEVANT MANUALS, Section 3.2, 3.5.2, 5.1.5, 5.2.1, 6.2.2, 7.1.4, Chapter 9, Section
10.5, 11.3, 12.4.2, 12.6.2, 12.9.3, 13.4.2, 14.1.2, 15.5, 15.7, 16.5.2, 16.8, Appendix 3, 5
Jul., 2016 SH(NA)-080009-S
Correction
Chapter 1, Section 3.2, 3.3.1, 3.3.2, 3.5.2, 5.1.2, 5.1.4, 5.1.5, 5.2.1, 11.3, 15.5, 16.5.1,
16.6.3, Appendix 3
Addition
Section 14.3, 16.5.11
Sep., 2018 SH(NA)-080009-T
Correction
Section 3.3.2, 3.5.2, 14.3.1, Appendix 4.1
Feb., 2019 SH(NA)-080009-U

Correction
Section 3.4
Jul., 2020 SH(NA)-080009-V

Correction
SAFETY PRECAUTIONS, CONDITIONS OF USE FOR THE PRODUCT
441
Jul., 2021 SH(NA)-080009-W
Addition
Section 3.2
Oct., 2021 SH(NA)-080009-X

Correction
COMPLIANCE WITH THE EMC AND LOW VOLTAGE DIRECTIVES, Appendix 8.3
Japanese Manual Version SH-080004-AE
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.
©1999 MITSUBISHI ELECTRIC CORPORATION
442
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.
443
Microsoft, Visual Basic, Visual C++, Windows, Windows NT, and Windows XP are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
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.
444 SH(NA)-080009-X
SH(NA)-080009-X(2110)MEE
MODEL: QJ71E71-U-KI-E
MODEL CODE: 13JL88
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.

Q Corresponding Ethernet Interface Module User's Manual (Basic)

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Q Corresponding Ethernet Interface Module User's Manual (Basic)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Q Corresponding Ethernet Interface Module User's Manual (Basic)

Uploaded by

Copyright:

Available Formats

Q Corresponding Ethernet Interface Module

User's Manual (Basic)

Indicates that incorrect handling may cause hazardous conditions,

Indicates that incorrect handling may cause hazardous conditions,

[Setup and Maintenance Precautions]

[Precautions When Disposing of This Product]

COMPLIANCE WITH THE EMC AND LOW VOLTAGE

(1) For programmable controller system

(2) For the product

(1) E71 relevant manual

(2) Operating manual

CHAPTER 2 PART NAMES 26

3.4 List of I/O Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

CHAPTER 4 PROCEDURES BEFORE OPERATION 63

CHAPTER 5 SYSTEM CONFIGURATION 65

5.2 Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

CHAPTER 6 INSTALLATION AND WIRING 78

7.2 TCP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

7.3 UDP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

CHAPTER 8 CONNECTING MELSOFT PRODUCTS AND A GOT 102

CHAPTER 9 MC PROTOCOL COMMUNICATIONS 105

CHAPTER 10 SLMP COMMUNICATIONS 109

CHAPTER 11 DATA COMMUNICATIONS USING THE PREDEFINED PROTOCOL 114

12.2 Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

12.5 Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

12.6 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

12.7 Pairing Open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

12.8 Broadcast Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

12.9 Example of Communications Using a Fixed Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

CHAPTER 13 COMMUNICATIONS USING A RANDOM ACCESS BUFFER 176

13.3 Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

13.5 Precautions when Creating Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

CHAPTER 14 OTHER FUNCTIONS 191

14.3 IP Filter Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

14.4 Remote Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

14.5 Hub Connection Status Monitor Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

14.8 Alive Check Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

CHAPTER 15 DEDICATED INSTRUCTIONS 238

15.3 Precautions for Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

CHAPTER 16 TROUBLESHOOTING 285

16.5 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

16.6 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

16.7 Ethernet Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Appendix 5 Line Status Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Appendix 6 Self-Diagnostic Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Appendix 7 Differences from Ethernet Modules of Other Series . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Appendix 9 Usage example of MX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

Appendix 10 Sample Program on the Connected Device Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Appendix 11 Checking the Serial Number and Function Version . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

Appendix 12 External Dimension Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433

"" is used for window

[ ] is used for items

Ex. shows setting or

shows shows notes that

*1 The mouse operation example is provided below.

Ex. [Online] [Write to PLC...]

A window selected in the view selection area is displayed.

Ex. Project window [Parameter]