Mitsubishi Melsec-L, Melsec-LJ71E71-100 User Manual

SAFETY PRECAUTIONS

(Read these precautions before using this product.)

Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle the product correctly.

In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

WARNING

CAUTION

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.

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

Indicates that incorrect handling may cause hazardous conditions, resulting in minor or moderate injury or property damage.

[Design Precautions]

WARNING

● For the operating status of each station after a communication failure, refer to relevant manuals for each network. Incorrect output or malfunction due to a communication failure may result in an accident.

● To prevent the malfunction of the programmable controller system due to harmful e-mails, take preventive measures (such as antivirus measures) so that the mail server for this module does not receive harmful e-mails.

● To maintain the safety of the programmable controller system against unauthorized access from external devices via the Internet, take appropriate measures.

● When connecting a peripheral with the CPU module or connecting an external device, such as a personal computer, with an intelligent function module to modify data of a running programmable controller, configure an interlock circuit in the program to ensure that the entire system will always operate safely. For other forms of control (such as program modification or operating status change) of a running programmable controller, read the relevant manuals carefully and ensure that the operation is safe before proceeding. Especially, when a remote programmable controller is controlled by an external device, immediate action cannot be taken if a problem occurs in the programmable controller due to a communication failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions to be taken between the external device and CPU module in case of a communication failure.

● Do not write any data to the "system area" of the buffer memory in the intelligent function module. Also, do not use any "use prohibited" signal as an output signal from the CPU module to the intelligent function module. Doing so may cause malfunction of the programmable controller system.

[Design Precautions]

CAUTION

● Do not install the control lines or communication cables together with the main circuit lines or power cables. Keep a distance of 100mm or more between them. Failure to do so may result in malfunction due to noise.

● When changing the operating status of the CPU module (such as remote RUN/STOP) from the external device, select "Always wait for OPEN (Communication possible at STOP time)" for the "Initial timing" setting in the network parameter. The communication line will be closed when "Do not wait for OPEN (Communications impossible at STOP time)" is selected and the remote STOP is executed from the external device. Consequently, the CPU module cannot reopen the communication line, and the external device cannot execute the remote RUN.

[Installation Precautions]

CAUTION

● Use the programmable controller in an environment that meets the general specifications in the Safety Guidelines included with the MELSEC-L series CPU module. Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the product.

● To interconnect modules, engage the respective connectors and securely lock the module joint levers until they click. Incorrect interconnection may cause malfunction, failure, or drop of the module.

● Shut off the external power supply (all phases) used in the system before mounting or removing a module. Failure to do so may result in damage to the product.

● Do not directly touch any conductive parts and electronic components of the module. Doing so can cause malfunction or failure of the module.

[Wiring Instructions]

CAUTION

● When connecting a cable with connector to the module, connect the connector part to the module securely.

● Place the cables in a duct or clamp them. If not, dangling cable may swing or inadvertently be pulled, resulting in damage to the module or cables or malfunction due to poor contact.

● When disconnecting the communication and power cables from the module, do not pull the cables by hand. For the cable with connector, hold the connector part of the cable. Pulling the cable connected to the module may result in malfunction or damage to the module or cable.

● Prevent foreign matter such as dust or wire chips from entering the module. Such foreign matter can cause a fire, failure, or malfunction.

● A protective film is attached to the top of the module to prevent foreign matter, such as wire chips, from entering the module during wiring. Do not remove the film during wiring. Remove it for heat dissipation before system operation.

[Setup and Maintenance Precautions]

WARNING

● Shut off the external power supply (all phases) used in the system before cleaning the module. Failure to do so may result in electric shock.

[Setup and Maintenance Precautions]

CAUTION

● Do not disassemble or modify the module. Doing so may cause failure, malfunction, injury, or a fire.

● Shut off the external power supply (all phases) used in the system before connecting or disconnecting

a module. Failure to do so may cause the module to fail or malfunction.

● After the first use of the product (module and display unit), the number of connections/disconnections is limited to 50 times (in accordance with IEC 61131-2). Exceeding the limit may cause malfunction.

● Before handling the module, touch a conducting object such as a grounded metal to discharge the static electricity from the human body. Failure to do so may cause the module to fail or malfunction.

[Operating Precautions]

CAUTION

● When changing data and operating status, and modifying program of the running programmable controller from a personal computer connected to an intelligent function module, read relevant manuals carefully and ensure the safety before operation. Incorrect change or modification may cause system malfunction, damage to the machines, or accidents.

[Disposal Precautions]

CAUTION

● When disposing of this product, treat it as industrial waste.

CONDITIONS OF USE FOR THE PRODUCT

(1) Mitsubishi programmable controller ("the PRODUCT") shall be used in conditions;

i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident; and ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the case of any problem, fault or failure occurring in the PRODUCT.

(2) The PRODUCT has been designed and manufactured for the purpose of being used in general

industries. MITSUBISHI SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN MITSUBISHI'S USER, INSTRUCTION AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT. ("Prohibited Application") Prohibited Applications include, but not limited to, the use of the PRODUCT in;

• Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the public could be affected if any problem or fault occurs in the PRODUCT.

• Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality assurance system is required by the Purchaser or End User.

• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator, Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other applications where there is a significant risk of injury to the public or property.

Notwithstanding the above, restrictions Mitsubishi may in its sole discretion, authorize use of the PRODUCT in one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific applications agreed to by Mitsubishi and provided further that no special quality assurance or fail-safe, redundant or other safety features which exceed the general specifications of the PRODUCTs are required. For details, please contact the Mitsubishi representative in your region.

INTRODUCTION

Remark

Thank you for purchasing the Mitsubishi MELSEC-L series programmable controllers. This manual describes the operating procedure, system configuration, parameter settings, functions, programming, and troubleshooting of the LJ71E71-100 Ethernet interface module (hereafter referred to as E71).

Before using this product, please read this manual and the relevant manuals carefully and develop familiarity with the functions and performance of the MELSEC-L series programmable controller to handle the product correctly. When applying the program examples introduced in this manual to 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.

Unless otherwise specified, this manual describes the program examples in which the I/O numbers of X/Y00 to X/Y1F are assigned for an E71. For I/O number assignment, refer to the following.

MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)

COMPLIANCE WITH EMC AND LOW VOLTAGE

DIRECTIVES

(1) Method of ensuring compliance

To ensure that Mitsubishi programmable controllers maintain EMC and Low Voltage Directives when incorporated into other machinery or equipment, certain measures may be necessary. Please refer to one of the following manuals.

• MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)

• Safety Guidelines (This manual is included with the CPU module.)

The CE mark on the side of the programmable controller indicates compliance with EMC and Low Voltage Directives.

(2) Additional measures

To ensure that this product maintains EMC and Low Voltage Directives, please refer to one of the manuals listed under (1).

RELEVANT MANUALS

The manuals related to this product are listed below. Please place an order as needed.

(1) E71 (relevant) manuals

Manual name

MELSEC-Q/L Ethernet Interface Module User's Manual (Application)

<SH-080010, 13JL89>

MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)

<SH-080180, 13JR40>

MELSEC-Q/L MELSEC Communication Protocol Reference Manual

<SH-080008, 13JF89>

(2) CPU module user's manuals

Manual name

MELSEC-L CPU Module User's Manual (Hardware Design, Maintenance and Inspection)

<SH-080890ENG, 13JZ36>

MELSEC-L CPU Module User's Manual (Function Explanation, Program Fundamentals)

<SH-080889ENG, 13JZ35>

Description

The e-mail function, CPU module monitoring function, communications over CCLink IE Controller Network, CC-Link IE Field Network, MELSECNET/H, or MELSECNET/10, communications using data link instructions, and file transfer function (FTP server) of the E71

The Web function of the E71

Communication methods and control procedures through the MC protocol used for data communications between a connected device and a CPU module using the C24/E71

Description

Specifications of the CPU modules, power supply modules, display unit, branch module, extension module, SD memory cards, and batteries, information on how to establish a system, maintenance and inspection, and troubleshooting

Functions, programming methods, and devices of the CPU module

(3) Operating manual

Manual name

GX Works2 Version 1 Operating Manual (Common)

<SH-080779ENG, 13JU63>

Description

System configuration, parameter settings, and online operations (common to Simple project and Structured project) of GX Works2

CONTENTS

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

COMPLIANCE WITH EMC AND LOW VOLTAGE DIRECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

MANUAL PAGE ORGANIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

TERM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

PACKING LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

CHAPTER 1 FEATURES 19

CHAPTER 2 PART NAMES 24

CHAPTER 3 SPECIFICATIONS 26

3.1 General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.2 Performance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.3 Function List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.3.1 Function list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.3.2 Use with other functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

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

3.5 Buffer Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.5.1 Configuration of the buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.5.2 List of buffer memory addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

CHAPTER 4 PROCEDURES BEFORE OPERATION 54

CHAPTER 5 SYSTEM CONFIGURATION 56

5.1 Overall System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.2 Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

5.3 Applicable Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

CHAPTER 6 INSTALLATION AND WIRING 59

6.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

6.2 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

CHAPTER 7 COMMUNICATION PROCEDURE 62

7.1 Setting Parameters Required for Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.1.1 Parameter list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

7.1.2 Basic setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

7.1.3 Ethernet Operation Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

7.1.4 Open Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

7.2 TCP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.2.1 Establishing a connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

7.2.2 Communication process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

7.2.3 Active open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

7.2.4 Passive open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

7.3 UDP/IP Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.3.1 Communication process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.3.2 Open procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

CHAPTER 8 CONNECTING MELSOFT PRODUCTS AND A GOT 81

8.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

8.2 Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

CHAPTER 9 MC PROTOCOL COMMUNICATIONS 84

9.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

9.2 Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

9.3 Data Communication Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

9.4 Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

CHAPTER 10 COMMUNICATIONS USING A FIXED BUFFER 87

10.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

10.1.1 Differences between the "Procedure Exist" and "No Procedure" control methods . . . . . . . . 87

10.2 Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

10.3 Data Sending Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

10.4 Data Receiving Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

10.4.1 Data receiving using the main program (BUFRCV instruction) . . . . . . . . . . . . . . . . . . . . . . . 92

10.4.2 Data receiving using an interrupt program (BUFRCVS instruction) . . . . . . . . . . . . . . . . . . . . 95

10.5 Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

10.5.1 Parameter setting when using an interrupt program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

10.6 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

10.6.1 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

10.6.2 Application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

10.7 Pairing Open. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

10.7.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

10.7.2 Parameter setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

10.8 Broadcast Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107

10.8.1 Sending/receiving procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

10.8.2 Parameter setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

10.8.3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

10.9 Example of Communications Using a Fixed Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112

10.9.1 System configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

10.9.2 Parameter setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

10.9.3 Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

CHAPTER 11 COMMUNICATIONS USING A RANDOM ACCESS BUFFER 120

11.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .120

11.2 Communication Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

11.2.1 How data is read from a connected device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

11.2.2 How a connected device writes data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

11.3 Parameter Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123

11.4 Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

11.4.1 Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

11.4.2 Application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

11.4.3 Examples of command and response formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

11.5 Precautions when Creating Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

11.6 Physical and Logical Addresses of a Random Access Buffer . . . . . . . . . . . . . . . . . . . . . . . .133

11.7 Example of Communications Using a Random Access Buffer . . . . . . . . . . . . . . . . . . . . . . . .134

CHAPTER 12 OTHER FUNCTIONS 135

12.1 Router Relay Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

12.1.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

12.1.2 Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

12.2 Communications Using an Auto-open UDP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139

12.2.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

12.3 Remote Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140

12.3.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

12.3.2 Remote password setting processes (unlock and lock processes) . . . . . . . . . . . . . . . . . . . 141

12.3.3 Remote password check procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

12.3.4 Differences in functions according to the remote password check status (enabled/disabled)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

12.3.5 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

12.3.6 Parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

12.4 Hub Connection Status Monitor Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150

12.5 IP Address in Use Detection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

12.6 Alive Check Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

CHAPTER 13 DEDICATED INSTRUCTIONS 155

13.1 List of Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .155

13.2 Parameter Settings for Using Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

13.2.1 When using data link instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

13.3 Precautions for Dedicated Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

13.4 Organization of the Dedicated Instruction Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157

13.5 ZP.OPEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158

13.6 ZP.CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

13.7 ZP.BUFSND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165

13.8 ZP.BUFRCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169

13.9 Z.BUFRCVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173

13.10 ZP.ERRCLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .175

13.11 ZP.ERRRD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

13.12 ZP.UINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182

CHAPTER 14 TROUBLESHOOTING 189

14.1 Before Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

14.2 Troubleshooting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189

14.3 Checking with the Module Error Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .190

14.4 Checking the LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191

14.4.1 If the RUN LED turns off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

14.4.2 If the ERR. LED or COM.ERR. LED turns on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

14.4.3 If the SD/RD LED does not flash when data is sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

14.5 Checking with a Display Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

14.6 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

14.6.1 Communications cannot be performed with the connected device. . . . . . . . . . . . . . . . . . . . 194

14.6.2 The E71 frequently fails to receive a message sent from the connected device. . . . . . . . . 195

14.6.3 A dedicated instruction is not completed.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

14.6.4 MC protocol communications cannot be performed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

14.6.5 Data cannot be sent with communications using a fixed buffer.. . . . . . . . . . . . . . . . . . . . . . 197

14.6.6 Data cannot be received with communications using a fixed buffer. . . . . . . . . . . . . . . . . . . 198

14.6.7 Communications using a random access buffer cannot be performed. . . . . . . . . . . . . . . . . 199

14.6.8 An e-mail cannot be sent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

14.6.9 An e-mail cannot be received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

14.6.10 Communications using data link instructions cannot be performed. . . . . . . . . . . . . . . . . . . 202

14.7 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

14.7.1 End codes returned to a connected device during data communications . . . . . . . . . . . . . . 210

14.7.2 Abnormal codes returned during communications using an A-compatible 1E frame. . . . . . 213

14.7.3 Error codes stored in the buffer memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

14.8 Ethernet Diagnostics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

14.9 Checking the Status of the E71 with the System Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . .238

14.10 How to Turn Off the COM.ERR. LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .240

APPENDICES 241

Appendix 1 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241

Appendix 2 Port Numbers Used for the E71 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

Appendix 3 Initial Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .246

Appendix 3.1 Setting the initial process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Appendix 3.2 Reinitialization process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Appendix 4 Line Status Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256

Appendix 4.1 PING test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Appendix 4.2 Loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Appendix 5 Self-Diagnostic Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265

Appendix 5.1 Self-loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Appendix 5.2 Hardware test (H/W Test). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Appendix 6 Differences from Ethernet Modules of Other Series . . . . . . . . . . . . . . . . . . . . . . . . . . .267

Appendix 6.1 Differences from a built-in Ethernet port LCPU. . . . . . . . . . . . . . . . . . . . . . . . 267

Appendix 6.2 Differences from Q series modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Appendix 6.3 Differences from QnA/A series modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Appendix 7 Sample Program on the Connected Device Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . .271

Appendix 7.1 When Visual C++®.NET is used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Appendix 7.2 When Visual Basic®.NET is used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Appendix 8 Checking the Serial Number, Function Version, and MAC address . . . . . . . . . . . . . . .291

Appendix 9 External Dimension Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .292

Appendix 10ASCII Code List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

INDEX 294

REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

MANUAL PAGE ORGANIZATION

The section of the current page is shown.

The chapter of the current page is shown.

"" is used for window names and items.

[ ] is used for items in the menu bar and the project window.

shows operating procedures.

shows reference manuals.

shows notes that requires attention.

shows mouse operations.

shows reference pages.

shows setting or operating examples.

Ex.

shows useful information.

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.

*1 The mouse operation example is provided below.

Menu bar

Ex.

A window selected in the view selection area is displayed.

Ex.

View selection area

[Online] [Write to PLC...]

Select [Online] on the menu bar, and then select [Write to PLC...].

Project window

[PLC Parameter]

Select [Project] from the view selection area to open the Project window.

In the Project window, expand [Parameter] and select [PLC Parameter].

[Parameter]

Pages describing instructions are organized as shown below.

Descriptions of setting data and data type

Instruction name

Structure of the instruction in the ladder mode

A device with is applicable to the instruction.

Execution condition of the instruction

Setting side User: A device value is set by the user. System: A device value is set by the CPU module.

Word device.Bit No.

The following illustration is for explanation purpose only, and should not be referred to as an actual documentation.

• Instructions can be executed under the following conditions.

Any time During on On the rising edge During off On the falling edge

No symbol

• The following devices can be used.

Internal device

Bit

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, 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 . However, bit specification cannot be used for timer (T), retentive

timer (ST), and counter (C).

Word K, H $

File register

D0.A

Constant

For details on each device, refer to the following.

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

The following data types can be used.

Data type Description

Bit Bit data or the start number of bit data

BIN 16-bit 16-bit binary data or the start number of word device

BIN 32-bit 32-bit binary data or the start number of double-word device

BCD 4-digit Four-digit binary-coded decimal data

BCD 8-digit Eight-digit binary-coded decimal data

Real number Floating-point data

Character string Character string data

Device name Device name data

TERM

Unless otherwise specified, this manual uses the following terms.

Term Description

ARP

BUFRCV The abbreviation for ZP.BUFRCV

BUFRCVS The abbreviation for Z.BUFRCVS

BUFSND The abbreviation for ZP.BUFSND

CLOSE The abbreviation for ZP.CLOSE

C24 Another term for the L series serial communication module

DNS

ERRCLR The abbreviation for ZP.ERRCLR

ERRRD The abbreviation for ZP.ERRRD

E71 Another term for the LJ71E71-100

E71-connected station The abbreviation for the station where the E71 is connected

FTP

GX Developer

GX Works2

HTTP

ICMP

IP The abbreviation for Internet Protocol

MAC address

MC protocol

MELSECNET/H The abbreviation for a MELSECNET/H network system

MELSECNET/H remote I/O station A generic term for the QJ72LP25-25, QJ72LP25G, and QJ72BR15

MELSECNET/10 The abbreviation for a MELSECNET/10 network system

MRECV The abbreviation for ZP.MRECV

MSEND The abbreviation for ZP.MSEND

MX Component The abbreviation for MX Component (SW0D5C-ACT-E or later)

OPEN The abbreviation for ZP.OPEN

POP3

READ The abbreviation for JP.READ and GP.READ

RECV The abbreviation for JP.RECV and GP.RECV

RECVS The abbreviation for Z.RECVS

REQ The abbreviation for J.REQ, JP.REQ, G.REQ, and GP.REQ

SEND The abbreviation for JP.SEND and GP.SEND

SMTP

SREAD The abbreviation for JP.SREAD and GP.SREAD

SWRITE The abbreviation for JP.SWRITE and GP.SWRITE

The abbreviation for Address Resolution Protocol. This protocol is used to obtain the MAC address of Ethernet from an IP address.

The abbreviation for Domain Name System. This system is mainly used to convert host names on the Internet or domain names used for e-mails to IP addresses.

The abbreviation for File Transfer Protocol. This protocol is used to transfer data files over a network.

The product name of the software package for the MELSEC programmable controllers

The abbreviation for Hyper Text Transfer Protocol. This protocol is used to send and receive content, such as HTML files, between a Web browser and a Web server.

The abbreviation for Internet Control Message Protocol. This protocol is used to exchange messages of errors in an IP network or other information related to an Ethernet network.

A unique identifier assigned to each external device on a network. This address is also known as an Ethernet hardware address.

The abbreviation for MELSEC Communication Protocol. This protocol is used to access MC protocol supporting modules, such as the C24 and E71, or programmable controllers connected to MC protocol supporting modules from external devices.

The abbreviation for Post Office Protocol Ver.3. This protocol is used to transfer e-mails from a mail server to a local computer.

The abbreviation for Simple Mail Transfer Protocol. This protocol is used to transfer e-mails over the Internet.

Term Description

UINI The abbreviation for ZP.UINI

WRITE The abbreviation for JP.WRITE and GP.WRITE

ZNRD The abbreviation for J.ZNRD and JP.ZNRD

ZNWR The abbreviation for J.ZNWR and JP.ZNWR

Intelligent function module

Subnet mask

Device A device (X, Y, M, D, or others) in a CPU module

Buffer memory

Buffer memory address

Programming tool Another term for GX Works2

Dedicated Instruction An instruction that simplifies programming for using functions of intelligent function modules

A module that has functions other than an input or output, such as an A/D converter module and 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:

• 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 memory in an intelligent function module, where data (such as setting values and monitoring values) exchanged with a CPU module are stored

An address that indicates the storage location of data assigned to the buffer memory in an intelligent function module

PACKING LIST

The following items are included in the package of this product. Before use, check that all the items are included.

LJ71E71-100

LJ71E71-100 Before Using the Product

CHAPTER 1 FEATURES

Another stationOwn station Connected device Connected device Web server

Programming tool

Internet

Connected device Connected device

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.

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)

• Exchange of data with connected devices (communications using a fixed buffer and random access buffer)

• Prevention of unauthorized access through a remote password

• E-mail sending/receiving (e-mail function)

• Data sending/receiving using the Web function

(1) Connection with MELSOFT products and a GOT

In Ethernet, a programming tool can create programming of a programmable controller and monitor a programmable controller (MELSOFT connection), and the GOT can monitor and test a programmable controller. Remote operations making full use of the Ethernet capability, long-distance connectivity and high-speed communications, are achieved.

Programming tool

E71

GOT

(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 84, CHAPTER 9)

Response

Command

E71

Connected device

CHAPTER 1 FEATURES

(3) Exchange of data with connected devices (communications using a fixed

buffer and random access buffer)

(a) Communications using a fixed buffer

Up to 1K-word data can be exchanged among programmable controllers or between a programmable controller and the host system. While MC protocol communications are passive, communications using a fixed buffer are an active protocol. If an error occurs in equipment or certain conditions are met, the programmable controller can send data to the host system. Using an interrupt program allows the CPU module to quickly read

received data. ( Page 87, CHAPTER 10)

Send/receive

Another station

Own station

(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 120, CHAPTER 11)

Send/receive

Connected device

Read/write

E71

Connected device

Read/write

Connected device

(4) 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 140, Section 12.3)

(5) E-mail sending/receiving (e-mail function)

E71

Connected device

Mail server Mail server

Internet

Sending/receiving e-mail

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

CHAPTER 1 FEATURES

(6) Data sending/receiving using the Web function

The system administrator can monitor a CPU module in a remote location via the Internet using a Web browser. For details, refer to the following.

MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)

HTTP

MC protocol

header

(command message)

HTTP

E71

MC protocol (response message)

HTTP header

Web server

HTML

ASP

Communication

library

Connected device

Web browser

Display of requests/ results

CHAPTER 2 PART NAMES

1) 1)

This chapter describes the E71 parts.

No. Name Application

1) Module joint lever A lever to fix modules

RUN Indicates operating status.

ON In normal operation

OFF

INIT. Indicates initial process status.

ON Normal completion

OFF Not processed

OPEN

ERR. Indicates hardware failure status.

COM.ERR.

ON An open process normally completed (connection open)

OFF An open process normally completed (no connection)

ON A hardware failure has occurred.

OFF Normal

OFF Normal communications in progress

An error has occurred. ( Page 191, Section 14.4.1)

Indicates open process status.

Indicates whether a communication failure has occurred.

A communication failure has occurred. ( Page 191, Section 14.4.2)

No. Name Application

SPEED Indicates a transmission speed.

ON 100Mbps

OFF 10Mbps or a cable not connected

SD/RD Indicates data communication status.

10BASE-T/100BASE-TX communication connector (RJ45)

4) Serial number display A display indicating the serial number printed on the rating plate

5) DIN rail hook A hook to install the module on a DIN rail

*1 The OPEN LED turns on and off depending on the open status of user connections 1 to 16. (The open status of the

*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

ON Data communications in progress

OFF

system connections (e.g. automatic open UDP port) is not included.)

"How to Turn Off the COM.ERR. LED". ( Page 240, Section 14.10)

Data not sent or not received ( Page 192, Section 14.4.3)

A connector to connect an E71 to the 10BASE-T or 100BASE-TX network (An E71 judges whether to connect to the 10BASE-T or 100BASE-TX network based on the hub.)

CHAPTER 2 PART NAMES

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

3.2 Performance Specifications

The following table lists the performance specifications of an E71.

Specifications

Item

100BASE-TX 10BASE-T

Data transmission speed 100Mbps 10Mbps

Interface RJ45 (AUTO MDI/MDI-X)

Transmission specifications

Sending/receiving data storage memory

Number of occupied I/O points 32 points (I/O assignment: Intelligent 32 points)

Internal current consumption (5VDC) 0.60A

External dimensions 95 (H) × 28.5 (W) × 90 (D) [mm]

Weight 0.18kg

Communication mode Full-duplex/Half-duplex Half-duplex

Transmission method Base band

Maximum segment length

Maximum number of cascade connections

Number of simultaneous open connections

Fixed buffer 1k word × 16

Random access buffer 6k words × 1

E-mail

Attachment 6k words × 1

Main text 960k words × 1

Cascade connection (maximum of 2

100m (length between a hub and a node)

levels*

)

16 connections (Connections usable on a program)

LJ71E71-100

Cascade connection (maximum of 4

levels*2)

Transmission specifications sending/receiving data

*1 For the maximum segment length (a length between hubs), consult with the manufacturer of the switching hub used. *2 This applies when a repeater hub is used. For the number of levels that can be constructed when a switching hub is

*3 If divided files are received, only the first file is received and the remaining files are discarded. *4 If an e-mail is sent from a connected device to the programmable controller side, specify the encoding method

CHAPTER 3 SPECIFICATIONS

Specifications

Item

LJ71E71-100

100BASE-TX 10BASE-T

Data size

Data transfer method

Subject Us-ASCII format or ISO-2022-JP (Base64)

Attachment format MIME format

MIME Version 1.0

Data of attachment format

Division of attachment

When sending (encode)

When receiving (decode)

Encryption None

Compression None

Communications with a mail server

Operation check mailer

used, consult with the manufacturer of the switching hub used.

(Base64/7 bits/8 bits/Quoted Printable) of the attachment.

Attachment 6k words × 1

Main text 960k words × 1

When sending: Send either a file as attachment or main text (select one).

When receiving: Receive a file as attachment.

Can be selected from binary, ASCII, and CSV.

File name: XXXX.bin (binary), XXXX.asc (ASCII), XXXX.csv (CSV)

(CSV: Comma Separated Value)

Cannot be divided (Only one file can be sent/received.)

Subject: Base64/7 bits

Main text: 7 bits

Attachment: Base64

Subject: (Does not decode)

Main text: (Cannot be received)

Attached file: Base64/7 bits/8 bits/Quoted Printable

SMTP (sending server) Port number = 25,

POP3 (receiving server) Port number = 110

Microsoft

Corporation Microsoft Office Outlook 2003

3.2 Performance Specifications

3.3 Function List

This section lists the E71 functions.

3.3.1 Function list

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 products and a GOT

MC protocol communications

Procedure exists

No procedure

Communications using a fixed buffer

Communications using a random access buffer

Router relay function

Communications using an auto-open UDP port

Remote password Unauthorized remote access to a CPU module is prevented. Page 140, Section 12.3

Hub connection status monitor function

IP address in use detection function

Alive check function

Module error collection function

Pairing open

Broadcast communications

An E71 can be connected with MELSOFT products, such as a programming tool and MX Component, and a GOT.

CPU module data can be read/written from/to connected devices. Access to files can be also performed.

Any data is sent/received between a CPU module and connected devices using the fixed buffer of an E71.

Paring receiving/sending connections enables data communications with two connections by performing the open process for one port.

Broadcast communications are enabled with all E71connected stations in the same Ethernet network that is connected to the E71 when “No Procedure” communications using a fixed buffer are performed using UDP/IP.

Data is read/written from multiple connected devices to the random access buffer of an E71.

Data communications are performed through a router and a gateway. This function is not the function where an E71 operates as a router.

Communications are enabled without the open/close processes after an E71-connected station is started up.

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.

If different stations in the same network use the same IP address, the address in use can be detected.

Whether a connected device is normally operating after a connection is established (open process) can be checked.

An error that has occurred in an E71 can be stored in the CPU module as error history. The history data can be stored on a memory with the backup power feature; therefore, error details are held even if the CPU module is reset or the system is powered off.

Page 81, CHAPTER 8

Page 84, CHAPTER 9

Page 87, CHAPTER 10

Page 105, Section 10.7

Page 107, Section 10.8

Page 120, CHAPTER 11

Page 135, Section 12.1

Page 139, Section 12.2

Page 150, Section 12.4

Page 151, Section 12.5

Page 153, Section 12.6

Page 190, Section 14.3

(2) Special functions

The following special functions are also available. For the functions, refer to the following.

MELSEC-Q/L Ethernet Interface Module User's Manual (Application)

Function Description

E-mail function

CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10 relay communications

Communications using data link instructions

File transfer (FTP server) function

CHAPTER 3 SPECIFICATIONS

Data are sent/received using an e-mail.

• Data sent/received by a CPU module

• Data sent using the programmable controller CPU monitoring function (automatic notification function)

Data are communicated over multiple network systems where Ethernet and other networks exist together or network systems that relay multiple Ethernet networks.

Data of a CPU module in other stations can be read/written over Ethernet using data link instructions.

Data can be read/written in files from connected devices using an exclusive FTP command.

(3) Web function

This function allows data to be read/written from/to a remote CPU module over the Internet using a Web browser. For the function, refer to the following.

MELSEC-Q/L Ethernet Interface Module User's Manual (Web function)

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

open

Communications

using an

auto-open UDP

port

Remote

password

Broadcast

communications

*1 *

3 *4

Network, CC-Link IE

Communication

function

MC protocol communications

Communications using a fixed buffer

Communications using a random access buffer

E-mail function × × × × × × × ×

Communications using data link instructions

File transfer (FTP server) function

Web function × × × × ×

Field Network,

MELSECNET/H,

MELSECNET/10 relay

communications

*1 *2

××

××××

×××× ××

Router

relay

function

Alive

check

function

Pairing

×× × ×

Communication

method

TCP/IP UDP/IP

3.3 Function List

3.3.2 Use with other functions

*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.

3.4 List of I/O Signals

The following table lists the I/O signals for an E71. The I/O signal assignment of when the start I/O number of an E71 is 0000 is listed below.

Device

number

X10

X11

Signal name

For fixed buffer communication of connection No.1 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.1 (ON: Detection of sending error or reception error, OFF: -)

For fixed buffer communication of connection No.2 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.2 (ON: Detection of sending error or reception error, OFF: -)

For fixed buffer communication of connection No.3 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.3 (ON: Detection of sending error or reception error, OFF: -)

For fixed buffer communication of connection No.4 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.4 (ON: Detection of sending error or reception error, OFF: -)

For fixed buffer communication of connection No.5 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.5 (ON: Detection of sending error or reception error, OFF: -)

For fixed buffer communication of connection No.6 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.6 (ON: Detection of sending error or reception error, OFF: -)

For fixed buffer communication of connection No.7 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.7 (ON: Detection of sending error or reception error, OFF: -)

For fixed buffer communication of connection No.8 (ON: Sending normal completion or reception completion, OFF: -)

For fixed buffer communication of connection No.8 (ON: Detection of sending error or reception error, OFF: -)

Open completed for connection No.1 (ON: Open completion signal, OFF: -)

Open completed for connection No.2 (ON: Open completion signal, OFF: -)

Device

number

Y10 Use prohibited

Y11 Use prohibited

Connection No.1 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.2 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.3 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.4 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.5 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.6 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.7 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.8 (ON: At sending request or reception complete confirmation signal, OFF: -)

Connection No.1 (ON: Open request, OFF: -)

Connection No.2 (ON: Open request, OFF: -)

Connection No.3 (ON: Open request, OFF: -)

Connection No.4 (ON: Open request, OFF: -)

Connection No.5 (ON: Open request, OFF: -)

Connection No.6 (ON

: Open request, OFF: -)

Connection No.7 (ON: Open request, OFF: -)

Connection No.8 (ON: Open request, OFF: -)

Signal name

CHAPTER 3 SPECIFICATIONS

Remark

Device

number

X12

X13

X14

X15

X16

X17

X18

X19

X1A

X1B Use prohibited Y1B Use prohibited

X1C

X1D Use prohibited Y1D Use prohibited

X1E Use prohibited Y1E Use prohibited

X1F

Open completed for connection No.3 (ON: Open completion signal, OFF: -)

Open completed for connection No.4 (ON: Open completion signal, OFF: -)

Open completed for connection No.5 (ON: Open completion signal, OFF: -)

Open completed for connection No.6 (ON: Open completion signal, OFF: -)

Open completed for connection No.7 (ON: Open completion signal, OFF: -)

Open completed for connection No.8 (ON: Open completion signal, OFF: -)

Open abnormal detection signal (ON: At off request, OFF: -)

Open abnormal detection signal (ON: Normal completion, OFF: -)

Open abnormal detection signal (ON: Abnormal end, OFF: -)

COM.ERR. LED lit confirmation (ON: lit, OFF: off)

Watchdog timer error detection (ON: Watchdog timer error, OFF: -)

Signal name

Device

number

Y12 Use prohibited

Y13 Use prohibited

Y14 Use prohibited

Y15 Use prohibited

Y16 Use prohibited

Y17

Y18 Use prohibited

Y19

Y1A Use prohibited

Y1C Use prohibited

Y1F Use prohibited

COM.ERR. LED Off request (ON: At off request, OFF: -)

Initial request signal (ON: At request, OFF: -)

Signal name

3.4 List of I/O Signals

Do not use any use prohibited signal as an I/O signal to the CPU module. Doing so may cause malfunction of the programmable controller system.

The I/O signals listed in this section are mainly applied when QnA series module programs are used. For the L series, the I/O signals for intelligent function modules are turned on and off with dedicated instructions. When QnA series module programs are used, it is recommended to replace the signals with the dedicated instructions described in the section that describes the corresponding functions.

3.5 Buffer Memory

This section describes the E71 buffer memory.

3.5.1 Configuration of the buffer memory

This section describes a buffer memory configuration.

(1) Buffer memory address configuration

A buffer memory area consists of 16 bits per address.

b9b15 b14 b13 b12 b11 b10 b8 b7 b6 b5 b4 b3 b2 b1 b0

(2) Buffer memory area configuration

Buffer memory consists of user areas and system areas.

(a) User areas

A user area is an area where a user writes or reads data. A user area consists of a parameter area for the initial process and data communications, an area for data communications, and an area to store communication status and communication error data. Data communications may take long if user areas are used continually; therefore, use them only when needed.

(b) System areas

A system area is an area used by a system.

Do not write any data to the "system area". Doing so may cause malfunction of the programmable controller system.

3.5.2 List of buffer memory addresses

The following table lists the buffer memory addresses of an E71.

CHAPTER 3 SPECIFICATIONS

Address

Decimal

(Hexadecimal)

0 and 1

and 1H)

2 and 3

and 3H)

)

5 to 10

to AH)

)

(10

)

(11

(12

)

(13

Application Name

Own station E71 IP address

System area - -

Special function settings Router relay function (b5, b4)

• 00: Do not use

•01: Use Conversion system setting for CC-Link IE Controller Network, CC-Link IE Field Network, MELSECNET/H, MELSECNET/10 relay function (b7, b6)

• 00: Automatic response system

• 01: IP address computation system

• 10: Table exchange system

• 11: Use-together system FTP function setting (b9, b8)

• 00: Do not use

•01: Use

Bits other than those described above are reserved for system use.

Initial process parameter setting area

System area - -

TCP ULP timer value (Setting time = setting value × 500 ms)

TCP zero window timer value (Setting time = setting value × 500 ms)

TCP resend timer value (Setting time = setting value × 500 ms)

TCP end timer value (Setting time = setting value × 500 ms)

IP assembly timer value

Monitoring timer

(Setting time = setting value × 500 ms)

Response monitoring timer value (Setting time = setting value × 500 ms)

Destination existence confirmation starting interval timer value (Setting time = setting value × 500 ms)

Destination existence confirmation interval timer value (Setting time = setting value × 500 ms)

Destination existence confirmation resending time

Initial

value

C00001FE

0100

(60)

(20)

(40)

(10)

(60)

4B0

(1200)

(20)

Programming

tool setting

applicability

(3)

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

Address

Decimal

(Hexadecimal)

)

(14

21 to 29

to 1DH)

(15

(1E

)

(1F

)

Application Name

Initial process parameter setting area

Initial process parameter setting area (For reinitialization)

Auto-open UDP port number

System area - -

TCP Maximum Segment Transmission setting area

: Enable TCP Maximum Segment Size Option

•0

transmission

: Disable TCP Maximum Segment Size Option

• 8000

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

• 1: Use the KeepAlive

Send frame setting (b5)

• 0: Ethernet

• 1: IEEE 802.3

Setting of write enable/disable at RUN time (b6)

• 0: Disable

• 1: Enable

Initial timing setting (b8)

• 0: Do not wait for OPEN (Communications impossible at

STOP time)

• 1: Always wait for OPEN (Communication possible at

STOP time)

Reinitialization specification (b15)

• 0: Reinitialization process complete (reset by the system)

• 1: Reinitialization process request (set by the user)

Initial

value

1388

8000

Programming

tool setting

applicability

Bits other than those described above are reserved for system use.

CHAPTER 3 SPECIFICATIONS

Address

Decimal

(Hexadecimal)

)

(20

)

(21

)

(22

)

(23

)

(24

)

(25

)

(26

)

(27

Application Name

Connection No.1 Usage of fixed buffer (b0)

• 0: For sending, or communications using a fixed buffer are not performed

• 1: For receiving

Destination existence confirmation (b1)

• 0: No confirm

• 1: Confirm

Pairing open (b7)

• 0: Disable

•1: Enable

Communication method (protocol) (b8)

• 0: TCP/IP

• 1: UDP/IP

Communications using a fixed buffer (b9)

• 0: Procedure exists

• 1: No procedure

Open system (b15, b14)

Communication parameter setting area

Connection usage setting area

• 00: Active open or UDP/IP

• 10: Unpassive open

• 11: Fullpassive open

Bits other than those described above are reserved for system use.

Connection No.2 (The bit configuration is the same as Connection No.1.)

Connection No.3 (The bit configuration is the same as Connection No.1.)

Connection No.4 (The bit configuration is the same as Connection No.1.)

Connection No.5 (The bit configuration is the same as Connection No.1.)

Connection No.6 (The bit configuration is the same as Connection No.1.)

Connection No.7 (The bit configuration is the same as Connection No.1.)

Connection No.8 (The bit configuration is the same as Connection No.1.)

Initial

value

Programming

tool setting

applicability

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

Address

Decimal

(Hexadecimal)

)

(28

41 and 42

and 2AH)

(29

)

(2B

44 to 46

to 2EH)

(2C

47 to 53

to 35H)

(2F

54 to 60

to 3CH)

(36

61 to 67

to 43H)

(3D

68 to 74

to 4AH)

(44

75 to 81

to 51H)

(4B

82 to 88

to 58H)

(52

89 to 95

to 5FH)

(59

96 to 102

to 66H)

(60

103 and 104

and 68H)

(67

105

)

(69

106 and 107

and 6BH)

(6A

108 to 110

to 6EH)

(6C

111 t o 11 5

to 73H)

(6F

116

)

(74

117

)

(75

118

(76

)

119

(77

)

Application Name

Connection No.1

Connection No.2 (The bit configuration is the same as Connection No.1.)

Communication

Communication parameter setting area

Communication status storage area

address setting area

System area - -

Area for the initial process

Connection No.3 (The bit configuration is the same as Connection No.1.)

Connection No.4 (The bit configuration is the same as Connection No.1.)

Connection No.5 (The bit configuration is the same as Connection No.1.)

Connection No.6 (The bit configuration is the same as Connection No.1.)

Connection No.7 (The bit configuration is the same as Connection No.1.)

Connection No.8 (The bit configuration is the same as Connection No.1.)

Initial error code

Own station IP address

Own station MAC address

System area - -

Auto-open UDP port number

System area - -

Station number (b0 to b7) Network number of the own station (b8 to b15)

Own station group number

Own station port No.

Destination IP address

Destination Port No.

Destination MAC address

Initial

value

FFFFFFFFF

FFF

Programming

tool setting

applicability

CHAPTER 3 SPECIFICATIONS

Address

Decimal

(Hexadecimal)

120

)

(78

121 and 122

and 7AH)

(79

123

)

(7B

124

)

(7C

125

)

(7D

126

)

(7E

127

)

(7F

128

)

(80

129

)

(81

130 to 139

to 8BH)

(82

140 to 149

to 95H)

(8C

150 to 159

to 9FH)

(96

160 to 169

to A9H)

(A0

170 to 179

to B3H)

(AA

180 to 189

to BDH)

(B4

190 to 199

to C7H)

(BE

Application Name

Connection No.1

Communication status storage area

Connection information area

Connection No.2 (The bit configuration is the same as Connection No.1.)

Connection No.3 (The bit configuration is the same as Connection No.1.)

Connection No.4 (The bit configuration is the same as Connection No.1.)

Connection No.5 (The bit configuration is the same as Connection No.1.)

Connection No.6 (The bit configuration is the same as Connection No.1.)

Connection No.7 (The bit configuration is the same as Connection No.1.)

Connection No.8 (The bit configuration is the same as Connection No.1.)

Own station port No.

Destination IP address

Destination Port No.

Open error code

Fixed buffer sending error code

Connection end code

Fixed buffer communication time (Maximum value)

Fixed buffer communication time (Minimum value)

Fixed buffer communication time (Current value)

Initial

value

Programming

tool setting

applicability

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

Address

Decimal

(Hexadecimal)

200

)

(C8

Application Name

LED on/off status (Stores the on/off status of the LEDs on the front of the Ethernet module) INIT. LED (b0)

•0: OFF

• 1: ON (initial process completed)

OPEN LED (b1)

•0: OFF

• 1: ON (connection open processing completed)

ERR. LED (b3)

•0: OFF

• 1: ON (hardware failure)

COM.ERR. LED (b4)

•0: OFF

• 1: ON (communication error)

Initial

value

Programming

tool setting

applicability

201

(C9

202

(CA

Communication status storage area

)

Area for module status

Bits other than those described above are reserved for system use.

Hub connection status area Communication mode (b9)

• 0: Half duplex

• 1: Full duplex

Hub connection status (b10)

• 0: Hub not connected/disconnected

• 1: Hub connected

Data transmission speed (b15, b14)

• 00: Operating at 10BASE-T

• 01: Operating at 100BASE-TX

Bits other than those described above are reserved for system use.

Switch status (operational mode setting) Communication data code setting

•0: Online

• 1: Offline

• 2: Self-loopback test

• 3: Hardware test

CHAPTER 3 SPECIFICATIONS

Address

Decimal

(Hexadecimal)

203

)

(CB

Application Name

Status of settings with a programming tool Communication data code setting (b1)

• 0: Communications in a binary code

• 1: Communications in an ASCII code

Initial/open method setting (b2)

• 0: No parameter setting (start up according to the program)

• 1: Parameter setting (start up according to the parameters)

TCP Existence confirmation setting (b4)

• 0: Use the Ping

• 1: Use the KeepAlive

Send frame setting (b5) Module status area

Communication status storage area

• 0: Ethernet

• 1: IEEE 802.3 Setting of write enable/disable at RUN time (b6)

• 0: Disable

•1: Enable Initial timing setting (b8)

• 0: Do not wait for OPEN

(Communications impossible at STOP time)

• 1: Always wait for OPEN

(Communication possible at STOP time)

Initial

value

Programming

tool setting

applicability

204

(CC

205

(CD

206

(CE

207

(CF

208

(D0

209

(D1

210 to 223

to DFH)

(D2

224 to 226

(E0

to E2H)

227

(E3

228

(E4

Bits other than those described above are reserved for system use.

)

Area for sending/

)

receiving instructions

)

System area - -

RECV instruction execution request

System area - -

Data link instruction execution result

ZNRD instruction

System area - -

ZNWR instruction

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

System area - -

)

Error log area

Number of errors

Error log write pointer

Address

Decimal

(Hexadecimal)

229

)

(E5

230

)

(E6

231

)

(E7

232

)

(E8

233

)

(E9

234 and 235

and EBH)

(EA

236

)

(EC

237

)

(ED

238 to 246

to F6H)

(EE

247 to 255

to FFH)

(F7

256 to 264

to 108H)

(100

265 to 273

to 111H)

(109

274 to 282

to 11AH)

(112

283 to 291

to 123H)

(11B

292 to 300

to 12CH)

(124

301 to 309

to 135H)

(12D

310 to 318

to 13EH)

(136

319 to 327

to 147H)

(13F

328 to 336

to 150H)

(148

337 to 345

to 159H)

(151

346 to 354

to 162H)

(15A

355 to 363

to 16BH)

(163

364 to 372

to 174H)

(16C

Application Name

Error log block 1

Error log block 2 (The bit configuration is the same as Error log block 1.)

Error log block 3 (The bit configuration is the same as Error log block 1.)

Error log block 4 (The bit configuration is the same as Error log block 1.)

Error log area

Error log block area

Error log block 5 (The bit configuration is the same as Error log block 1.)

Error log block 6 (The bit configuration is the same as Error log block 1.)

Error log block 7 (The bit configuration is the same as Error log block 1.)

Error log block 8 (The bit configuration is the same as Error log block 1.)

Error log block 9 (The bit configuration is the same as Error log block 1.)

Error log block 10 (The bit configuration is the same as Error log block 1.)

Error log block 11 (The bit configuration is the same as Error log block 1.)

Error log block 12 (The bit configuration is the same as Error log block 1.)

Error log block 13 (The bit configuration is the same as Error log block 1.)

Error log block 14 (The bit configuration is the same as Error log block 1.)

Error log block 15 (The bit configuration is the same as Error log block 1.)

Error log block 16 (The bit configuration is the same as Error log block 1.)

Initial

value

Error code/end code

Subheader

Command code

Connection No.

Own station port No.

Destination IP address

Destination Port No.

Programming

tool setting

applicability

System area - -

CHAPTER 3 SPECIFICATIONS

Address

Decimal

(Hexadecimal)

373 to 375

to 177H)

(175

376 and 377

and 179H)

(178

378 and 379

(17A

and 17BH)

380 and 381

(17C

and 17DH)

382 to 407

to 197H)

(17E

408 and 409

and 199H)

(198

410 and 411

(19A

and 19BH)

412 and 413

(19C

and 19DH)

414 and 415

(19E

and 19FH)

416 and 417

(1A0

and 1A1H)

418 and 419

and 1A3H)

(1A2

420 and 421

and 1A5H)

(1A4

422 to 439

to 1B7H)

(1A6

440 and 441

and 1B9H)

(1B8

442 and 443

(1BA

and 1BBH)

444 and 445

(1BC

and 1BDH)

446 to 471

to 1D7H)

(1BE

472 and 473

and 1D9H)

(1D8

474 and 475

(1DA

and 1DBH)

476 and 477

(1DC

and 1DDH)

478 to 481

to 1E1H)

(1DE

Programming

tool setting

applicability

Application Name

Initial

value

System area --

Received IP packet count

Received IP packet count discarded due to sumcheck

error

Sent IP packet total count

System area - -

Received ICMP packet count

Received ICMP packet count discarded due to sum

check error

Sent ICMP packet total count

Echo request total count of

Error log area

Status for each protocol

ICMP

received ICMP packets

Echo reply total count of sent ICMP packets

Echo request total count of sent ICMP packets

Echo reply total count of received ICMP packets

System area - -

Received TCP packet count

TCP

discarded due to sum check error

Sent TCP packet total count

System area - -

Received UDP packet count

UDP

discarded due to sum check error

Sent UDP packet total count

System area - -

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

Address

Decimal

(Hexadecimal)

482 to 511

to 1FFH)

(1E2

512 and 513

and 201H)

(200

514 and 515

and 203H)

(202

516

)

(204

517 and 518

and 206H)

(205

519 and 520

and 208H)

(207

521 to 524

to 20CH)

(209

525 to 528

to 210H)

(20D

529 to 532

to 214H)

(211

533 to 536

to 218H)

(215

537 to 540

to 21CH)

(219

541 to 544

to 220H)

(21D

545 to 548

to 224H)

(221

549

)

(225

Application Name

Error log area

Router relay parameter setting area

Status for each protocol

System area - -

Sub-net mask

Default router IP address

Number of registered routers

Sub-net address

Router 1

Router IP address

Router 2 (The bit configuration is the same as Router 1.)

Router 3 (The bit configuration is the same as Router 1.)

Router 4 (The bit configuration is the same as Router 1.)

Router 5 (The bit configuration is the same as Router 1.)

Router 6 (The bit configuration is the same as Router 1.)

Router 7 (The bit configuration is the same as Router 1.)

Router 8 (The bit configuration is the same as Router 1.)

System area - -

Initial

value

Programming

tool setting

applicability

CHAPTER 3 SPECIFICATIONS

Address

Decimal

Application Name

(Hexadecimal)

550 and 551

and 227H)

(226

552

)

(228

553 and 554

and 22AH)

(229

555 and 556

and 22CH)

(22B

557 and 558

and 22EH)

(22D

559 to 564

to 234H)

(22F

Station No. <-> IP information setting area

to to

931 to 936

to 3A8H)

(3A3

937 and 938

and 3AAH)

(3A9

939 to 943

to 3AFH)

(3AB

944 to 949

to 3B5H)

(3B0

950 to 953

to 3B9H)

(3B6

954

(3BA

)

FTP setting area

955

)

(3BB

956 to 1663

to 67FH)

(3BC

System area - -

Number of conversion table data

Communication request destination/source stations network

Conversion information No.1

number and station number

External station Ethernet module IP address

System area - -

Conversion information No.2 (The bit configuration is the same as Conversion information No.1.)

Conversion information No.64 (The bit configuration is the same as Conversion information No.1.)

Subnet mask pattern for CC-Link IE Controller Network, CCLink IE Field Network, MELSECNET/H, and MELSECNET/10 routing

System area - -

FTP login name "LJ71E71"

Password "LJ71E71"

Command input monitoring timer

Programmable controller CPU monitoring timer

System area - -

Initial

value

708

Programming

tool setting

applicability

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

Address

Decimal

(Hexadecimal)

1664

)

(680

1665 to 2687

to A7FH)

(681

2688 to 3711

to E7FH)

(A80

3712 to 4735

to 127FH)

(E80

4736 to 5759

to 167FH)

(1280

5760 to 6783

to 1A7FH)

(1680

6784 to 7807

to 1E7FH)

(1A80

7808 to 8831

to 227FH)

(1E80

8832 to 9855

to 267FH)

(2280

9856 to 16383

to 3FFFH)

(2680

16384 to 20479

to 4FFFH)

(4000

Application Name

Data length

Fixed buffer data

Fixed buffer data area

Shared area for random access buffers and e-mail buffers

Fixed buffer No.1

Fixed buffer No.2 (The bit configuration is the same as Fixed buffer No.1.)

Fixed buffer No.3 (The bit configuration is the same as Fixed buffer No.1.)

Fixed buffer No.4 (The bit configuration is the same as Fixed buffer No.1.)

Fixed buffer No.5 (The bit configuration is the same as Fixed buffer No.1.)

Fixed buffer No.6 (The bit configuration is the same as Fixed buffer No.1.)

Fixed buffer No.7 (The bit configuration is the same as Fixed buffer No.1.)

Fixed buffer No.8 (The bit configuration is the same as Fixed buffer No.1.)

Shared area for random access buffers and e-mail buffers

System area - -

Initial

value

Programming

tool setting

applicability

CHAPTER 3 SPECIFICATIONS

Address

Decimal

(Hexadecimal)

20480

)

(5000

20481

)

(5001

20482

)

(5002

20483 and 20484

and 5004H)

(5003

20485

)

(5005

20486

)

(5006

20487

(5007

)

Application Name

Open completion signal

• 0: Open incomplete

• 1: Open completed

Connection No.1 (b0) Connection No.2 (b1)

Connection No.16 (b15)

Connection status storage area

System port information area

Connection status information area

Fixed buffer information area

Remote password status storage area

System area - -

Open request signal

• 0: No open request

• 1: Open being requested

Connection No.1 (b0) Connection No.2 (b1) to Connection No.16 (b15)

System area - -

Fixed buffer reception status signal

• 0: Data not received

• 1: Data being received

Connection No.1 (b0) Connection No.2 (b1) to Connection No.16 (b15)

Remote password status

• 0: Unlock status/no remote password

setting

• 1: Lock status

Connection No.1 (b0) Connection No.2 (b1) to Connection No.16 (b15)

Remote password status

• 0: Unlock status/no remote password

setting

• 1: Lock status

• Auto-open UDP port (b0)

• MELSOFT application transmission port

(UDP) (b1)

• MELSOFT application transmission port

(TCP) (b2)

• FTP transmission port (b3)

Initial

value

Programming

tool setting

applicability

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

Address

Decimal

(Hexadecimal)

20488

)

(5008

20489 to 20591

to 506FH)

(5009

20592

(5070

)

20593

)

(5071

20594

(5072

)

20595

(5073

)

20596

)

(5074

20597

)

(5075

20598

)

(5076

20599 to 20603

to 507BH)

(5077

20604 to 20608

to 5080H)

(507C

20609 to 20613

to 5085H)

(5081

20614 to 20618

to 508AH)

(5086

20619 to 20623

to 508FH)

(508B

20624 to 20628

to 5094H)

(5090

Application Name

System port use prohibited designation

• 0: Use allowed

• 1: Use prohibited

• Auto-open UDP port (b0)

• MELSOFT application transmission port

(UDP) (b1)

• MELSOFT application transmission port

(TCP) (b2)

System area - -

Remote password mismatch notification accumulated count designation (For user open port)

• 0: No designation

• 1 or higher: Notification accumulated

count

Remote password mismatch notification accumulated count designation (For autoopen UDP port, MELSOFT application transmission port (TCP/ UDP) and FTP transmission port)

• 0: No designation

• 1 or higher: Notification accumulated

count

Connection No.1

Connection No.2 (The bit configuration is the same as Connection No.1.)

Connection No.3 (The bit configuration is the same as Connection No.1.)

Connection No.4 (The bit configuration is the same as Connection No.1.)

Connection No.5 (The bit configuration is the same as Connection No.1.)

Connection No.6 (The bit configuration is the same as Connection No.1.)

Connection No.7 (The bit configuration is the same as Connection No.1.)

System port information area

Monitoring area

System port use prohibited designation area

Remote password function monitoring area

Accumulated count of unlock process normal completion

Accumulated count of unlock process abnormal end

Accumulated count of lock process normal completion

Accumulated count of lock process abnormal end

Accumulated count of lock process based on close

Initial

value

Programming

tool setting

applicability

CHAPTER 3 SPECIFICATIONS

Address

Decimal

(Hexadecimal)

20629 to 20633

to 5099H)

(5095

20634 to 20638

to 509EH)

(509A

20639 to 20643

to 50A3H)

(509F

20644 to 20648

to 50A8H)

(50A4

20649 to 20653

to 50ADH)

(50A9

20654 to 20658

to 50B2H)

(50AE

20659 to 20663

to 50B7H)

(50B3

20664 to 20668

to 50BCH)

(50B8

20669 to 20673

to 50C1H)

(50BD

20674 to 20678

to 50C6H)

(50C2

20679 to 20683

to 50CBH)

(50C7

20684 to 20688

to 50D0H)

(50CC

20689 to 20693

to 50D5H)

(50D1

Application Name

Connection No.8 (The bit configuration is the same as Connection No.1.)

Connection No.9 (The bit configuration is the same as Connection No.1.)

Connection No.10 (The bit configuration is the same as Connection No.1.)

Connection No.11 (The bit configuration is the same as Connection No.1.)

Connection No.12 (The bit configuration is the same as Connection No.1.)

Connection No.13 (The bit configuration is the same as Connection No.1.)

Connection No.14 (The bit configuration is the same as Connection No.1.)

Connection No.15 (The bit configuration is the same as Connection No.1.)

Connection No.16 (The bit configuration is the same as Connection No.1.)

Auto-open UDP port (The bit configuration is the same as Connection No.1.)

MELSOFT application transmission port (UDP) (The bit configuration is the same as Connection No.1.)

MELSOFT application transmission port (TCP) (The bit configuration is the same as Connection No.1.)

FTP transmission port (The bit configuration is the same as Connection No.1.)

Monitoring area

Remote password function monitoring area

Initial

value

Programming

tool setting

applicability

3.5 Buffer Memory

3.5.2 List of buffer memory addresses

Address

Decimal

(Hexadecimal)

20694 to 20736

to 5100H)

(50D6

20737

)

(5101

20738

)

(5102

20739

)

(5103

20740

)

(5104

20741

)

(5105

20742

)

(5106

20743

)

(5107

20744

)

(5108

20745 and 20746

and 510AH)

(5109

20747 to 20750

to 510EH)

(510B

20751 to 20757

to 5115H)

(510F

20758 to 20764

to 511CH)

(5116

20765 to 20771

to 5123H)

(511D

20772 to 20778

to 512AH)

(5124

20779 to 20785

to 5131H)

(512B

20786 to 20792

to 5138H)

(5132

20793 to 20799

to 513FH)

(5139

20800 to 20806

to 5146H)

(5140

20807 to 20813

to 514DH)

(5147

20814 to 20820

to 5154H)

(514E

20821 to 20827

to 515BH)

(5155

20828 to 20834

to 5162H)

(515C

Application Name

System area - -

Error log pointer

Log counter (HTTP response code 100 to 199)

Log counter (HTTP response code 200 to 299)

Log counter (HTTP response code 300 to 399)

Log counter (HTTP response code 400 to 499)

Log counter (HTTP response code 500 to 599)

System area - -

HTTP response code

HTTP status storage area