Mitsubishi_Electronics_Garage_Door_Opener

SAFETY PRECAUTIONS

(Read these precautions before use.)

Before installation, operation, maintenance or inspection of this product, thoroughly read through and understand this manual and all of the associated manuals. Also, take care to handle the module properly and safely.

This manual classifies the safety precautions into two categories: "DANGER" and "CAUTION."

DANGER

CAUTION

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

Indicates that incorrect handling may cause hazardous conditions, resulting in medium or slight personal injury or physical damage.

Depending on the circumstances, procedures indicated by CAUTION may also cause severe injury. It is important to follow all precautions for personal safety.

Store this manual in a safe place so that it can be taken out and read whenever necessary. Always forward it to the end user.

[Design Precautions]

DANGER

To prevent malfunctions of the PLC system that may be caused by illegal e-mail, take proper countermeasures (such as virus detection) so that illegal e-mail is not received by the mail server of this module.

If it is necessary to ensure the security of the PLC system against unauthorized access from external devices via the Internet, appropriate measures must be incorporated by the user.

When controlling the PLC (modifying data) while it is in operation by connecting computer peripheral devices to the main unit or connecting personal computers to the extension device, make sure to have an interlock circuit outside of the PLC to ensure safe system operation.

Do not write any data in the "system area" of the buffer memory of the extension device. When writing a value to the buffer memory including "System Area," pay close attention not to change the system bit. If data is written to the "system area" or the "use prohibited" signal is output, there is a risk that the PLC system may malfunction.

When the program examples introduced in this manual are applied to the actual system, examine the safety of the control in the target system.

[Design Precautions]

CAUTION

When the status control (remote RUN/STOP) of the PLC is performed from the external device, select the "Always wait for OPEN" parameter set by an user in advance. (Select with the initial timing setting (BFM#24 b8) in the operational setting.) When "Do not wait for OPEN" is selected, the communication line at remote STOP is closed. The communication line cannot be reopened on the PLC side after that, and the remote RUN from the external device cannot start.

[Installation Precautions]

CAUTION

Use the product within the generic environment specifications described in chapter 3 of this manual.

Never use the product in areas with excessive dust, oily smoke, conductive dusts, corrosive gas (salt air, Cl2, H2S, SO2 or NO2), flammable gas, vibration or impacts, or exposed to high temperature, condensation, or rain and wind.

If the product is used in such conditions, electric shock, fire, malfunctions, deterioration or damage may occur.

When drilling screw holes or wiring, make sure cutting or wire debris does not enter the ventilation slits.

Failure to do so may cause fire, equipment failures or malfunctions.

Be sure to remove the dust proof sheet from the PLC's ventilation port when installation work is completed. Failure to do so may cause fire, equipment failures or malfunctions.

Connect the extension cables securely to their designated connectors. Unsecured connection may cause malfunctions.

[Wiring Instructions]

DANGER

Before mounting or wiring the module, make sure to shut off all of the external power supply. Failure to do so may cause electric shocks or damage the module.

When turning on the power and operating after mounting or wiring the module, make sure to install the accessory terminal covers to the product.

Otherwise, it may cause electric shocks.

CAUTION

Make sure to place the communication cables and the power cables in a duct or fasten them using a clamp.

If the cables are not placed in a duct or fastened with a clamp, their positions can be unstable, moved and pulled inadvertently. This may damage the module and the cables, or cause the module malfunction due to unsecured cable connections.

When disconnecting the communication cables and the power cables, do not pull the cables. When disconnecting a cable with a connector, hold the connector to the module by hand and pull it out to remove the cable.

When disconnecting a cable connected to a terminal block, loosen the screws on the terminal block before removing the cable.

If a cable is pulled while being connected, it may cause the module malfunction or damage the module and the cable.

Do not bundle the control line and the communication cables together with or lay it close to the main circuit or power line. As a guideline, lay the control line and the communication cables at least 100mm (3.94") or more away from the main circuit or power line.

Noise may cause malfunctions.

Before connecting twisted pair cables, the ground pin brush grounded via a resistor enables discharging static electricity on the cables effectively. This can prevent the electrostatic discharge to the product.

[Setup and Maintenance Precautions]

DANGER

Do not touch any terminal while the PLC's power is on. Doing so may cause electric shock or malfunctions.

Before cleaning or retightening terminal screws and module mounting screws, externally cut off all phases of the power supply.

Failure to do so may cause electric shock, fire, malfunctions and product damage.

Before modifying or disrupting the program, forcible output, RUN and STOP while they are in operation, carefully read through this manual and the associated manuals and ensure the safety of the operation.

An operation error may damage the machinery or cause accidents.

CAUTION

Do not disassemble or modify the PLC.

Doing so may cause fire, equipment failures, or malfunctions. For repair, contact your local Mitsubishi Electric distributor.

Cut off all phases of the power supply externally before installation or wiring work in order to avoid damage to the product or electric shock.

[Precautions When Disposing of This Product]

CAUTION

Dispose of this product as an industrial waste.

[Transportation Precautions]

CAUTION

The PLC is a precision instrument. During transportation, avoid impacts larger than those specified in the general specifications of the PLC main unit manual.

Failure to do so may cause failures in the PLC. After transportation, verify the operations of the PLC.

Other company and product names herein are either trademarks or registered trademarks of their respective owners.

Microsoft , Windows 2000, Outlook , Visual C++ and Visual Basic are either registered trademarks or trade- marks of Microsoft Corporation in the United States and/or other countries.

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.

Applicable Standard

Certification of UL, cUL standards

The following product has UL and cUL certification.

UL, cUL File Number: E95239

Models: MELSEC FX3U series manufactured

FX3U-ENET-L

Regarding the standards that comply with the main unit, please refer to either the FX series product catalog or consult with your nearest Mitsubishi product provider.

Compliance with EC directive (CE Marking)

This note does not guarantee that an entire mechanical module produced in accordance with the contents of this note will comply with the following standards. Compliance to EMC directive and LVD directive of the entire mechanical module should be checked by the user / manufacturer. For more details please contact the local Mitsubishi Electric sales site.

Regarding the standards that comply with the main unit, please refer to either the FX series product catalog or consult with your nearest Mitsubishi product provider.

Requirement for Compliance with EMC directive

The following products have shown compliance through direct testing (of the identified standards below) and design analysis (through the creation of a technical construction file) to the European Directive for Electromagnetic Compatibility (2004/108/EC) when used as directed by the appropriate documentation.

Attention

???This product is designed for use in industrial applications.

???Manufactured by:

Mitsubishi Electric Corporation

2-7-3 Marunouchi, Chiyoda-ku, Tokyo, 100-8310 Japan

??? Manufactured at:

Mitsubishi Electric Corporation Himeji Works

840 Chiyoda-machi, Himeji, Hyogo, 670-8677 Japan

???Authorized Representative in the European Community: Mitsubishi Electric Europe B.V.

Gothaer Str. 8, 40880 Ratingen, Germany

Type: Programmable Controller (Open Type Equipment)

Models: MELSEC FX3U series manufactured

Caution to conform with EC Directives

???Installation in Enclosure

Programmable logic controllers are open-type devices that must be installed and used within conductive control cabinets. Please use the programmable logic controller while installed within a conductive shielded control cabinet. Please secure the cabinet door to the control cabinet (for conduction).

Installation within a control cabinet greatly affects the safety of the system and aids in shielding noise from the programmable logic controller.

???Control cabinet

-The control cabinet must be conductive.

-Ground the control cabinet with the thickest possible grounding cable.

-To ensure that there is electric contact between the control cabinet and its door, connect the cabinet and its doors with thick wires.

-In order to suppress the leakage of radio waves, the control cabinet structure must have minimal openings. Also, wrap the cable holes with a shielding cover or other shielding devices.

-The gap between the control cabinet and its door must be as small as possible by attaching EMI gaskets between them.

*1. These wires are used to improve the conductivity between the door and control cabinet.

The Manual's Usage and Structure

How to use this manual

In this manual, explanations are given for each application of the Ethernet modules (FX3U-ENET-L).

Please use this manual using the following key items below as a reference.

(1)Features and utility lists

(a)Features and functions

???Chapter 1 describes the features of the Ethernet modules.

???Chapter 3 describes the common functions and specifications of the Ethernet modules.

(b)Items included in this package and network configured items

???Section 2.2 describes the system configuration of the Ethernet module. Parts and components other than those packaged with the module must be purchased separately by the user.

(2)Processing required prior to starting the operation of the Ethernet module

(a)Startup procedure

???Section 4.2 describes an outline of the procedures to do before starting the operation of the Ethernet module.

(b)Connection to the Ethernet network.

???Section 2.2 describes the devices required to connect to the Ethernet network.

???Section 4.4 describes the connection methods for each type of interface.

(c)Parameter settings required before starting Ethernet module operation

???Section 3.6 describes the parameter settings required in order to use each function.

Confirm the required parameters, set them according to the relevant section, and save the setting values in the PLC to which the Ethernet module is installed.

???Section 4.5 describes the types of Ethernet parameter setting in order to use the Ethernet module.

(d)Checking for Ethernet module failures

???Section 4.7 describes the self-diagnostic test for the Ethernet module.

(e)Checking for connection errors with the external devices

???Subsection 5.4.1 describes how to check for connection errors using the "PING" command.

???Subsection 5.4.2 describes how to check for connection errors by performing the loopback test through MC protocol-based communication.

(3)Connection between the Ethernet module and external devices

(a)Communication procedures

???Section 5.1 describes an outline of the communication procedures

(b)Connections with the external devices

???Section 5.6 describes the connections (open and close processing) for each communication method (TCP/IP) and the open method (Active, Passive), including programming procedures.

(4)Details on the data communication functions

(a)Communication functions

???Section 1.2 describes an overview of the Ethernet module communication functions and related section numbers that can be referenced for more detailed explanations.

(5)Data communication functions and programming

(a)Reading from and writing to the PLC

???Data is read from and written to the PLC with communication functions using MC protocol.

???Chapter 8 is an overview of the communication functions using MC protocol.

???Chapter 9 is a detail on the communication functions using MC protocol.

(b)Sending and receiving data between the PLC and the external devices

???Data communication between the PLC and external devices is performed with the fixed buffer communication functions.

???Chapters 6 and 7 explains the communication functions and programming using the fixed buffers.

(6)Checking for error occurrences and taking corrective actions

(a)Error codes

???Chapter 11 describes troubleshooting, how to check for errors, and the contents and reference for error codes.

(b)Error code storase area in the buffer memory of the Ethernet module

???Section 11.3 describes the error code storage areas in the buffer memory.

FX Configurator-EN-L (FX3U-ENET-L Configuration tool)

Using FX Configurator-EN-L to set parameters, the sequence programs for communicating with external devices can be simplified.

For details on the parameter settings from FX Configurator-EN-L, refer to the FX Configurator-EN-L operation manual.

1 OVERVIEW

MELSEC-F

1 OVERVIEW

This manual provides information on the specifications of the Ethernet interface block, FX3U-ENET-L (hereinafter called FX3U-ENET-L or the Ethernet module), as well as the procedures before starting operation, the control procedures and data communication method for communicating with external devices, maintenance, inspection, and troubleshooting.

When the program examples introduced in this manual are applied to an actual system, examine the safety of the control in the target system before use.

1.1 Overview of the Ethernet Module

The Ethernet module is an interface module on the PLC side for connecting the FX3U/ FX3UC series PLC with the host system, such as a personal computer work station, and other PLCs using the TCP/IP or UDP/IP communication protocol via Ethernet (100BASE-TX, 10BASE-T).

Internet (Public dial-up line)

Internet service

Internet serviceProvider

Provider

GX Developer

1 OVERVIEW

MELSEC-F

1)Collection and modification of PLC data

(Communication using the MELSEC Communication Protocol (referred to below as the MC Protocol))

2)Transmission and reception of arbitrary data to/from external devices (Communication using fixed buffers)

3)Data transmission by e-mail (When using the e-mail function)

POINT

The module operation is not guaranteed if any of the following connection is used. Check the module operation on the user side.

???Connections using the Internet (general public line) (Connections using Internet connection service provided by Internet service providers and telecommunications carriers)

???Connections using devices in which a firewall is installed

???Connections using broadband routers

???Connections using wireless LAN

1 OVERVIEW

MELSEC-F

1.2Features of the Ethernet Module

(1)Data communication using MC protocol (Details are explained in

Chapter 8 and Chapter 9)

Using MC protocol, the device data of the PLC can be read from/written to the host system.

This protocol is a passive protocol that communicates data solely according to the requests from the host system. It does not require a sequence program for data communication after a connection is established.

Local station

External device

(2) Communication using fixed buffers (Details are explained in Chapters 6 and 7)

With communication using fixed buffers, a maximum of 1023 words of arbitrary data can be sent or received between PLCs or between the PLC and an arbitrary device.

An Ethernet module is provided with 2 fixed buffer data areas each with 1023 word storage space, and each is assigned as either a sending or receiving buffer for an arbitrary device.

Since communication using MC protocol is passive, communication using fixed buffers is an active protocol. Data can be sent from the PLC side to another PLC and an arbitrary device when equipment errors occur or when some specified conditions are satisfied.

External device

1 OVERVIEW

MELSEC-F

(4)Connecting FX Configurator-EN-L (Details are explained in the Operating Manuals for FX Configurator-EN-L)

(a)Simplifying sequence programs using FX Configurator-EN-L

FX Configurator-EN-L supports the parameter setting function to perform the Ethernet module initialization and the open processing with external devices. By setting up the following parameters with FX Configurator-EN-L, access is enabled from the external device to the PLC. It can also simplify sequence

programs used to perform communication by Ethernet modules.

For more information on setting up the Ethernet module, see Section 3.5, "List of Setting Items for Ethernet Modules" and other applicable reference sections.

External device

FX Configurator-EN-L

*1 Access is enabled only when MELSOFT connection is set in the open method of the Ethernet module.

*2 The open settings is not set for the initial state of the Ethernet module. Set it through serial communication.

1 OVERVIEW

MELSEC-F

(b)Connecting multiple MELSOFT products (GX Developer, MX Component) This product can be connected with one or more MELSOFT product, via TCP/IP communication (through the in-house LAN, etc.) or UDP/IP communication (through the in-house LAN, etc.).

1)Connection via TCP/IP communication

???If a MELSOFT product is to be connected with the FX Configurator- EN-L open settings, a maximum of two units can be connected with MELSOFT product.

???If a MELSOFT product is to be connected, the settings of buffer memory for the MELSOFT connection or the following settings using FX Configurator-EN-L are required.

For FX Configurator-EN-L, on the "Open settings" screen, set "TCP" in the protocol field of the connection number to be used, and "MELSOFT connection" in the open method field. (See Section 5.5.)

Connection via TCP/IP communication only

Multiple units (Maximum two units)

For use when the user specifies a MELSOFT connection.

"Ethernet open setting" parameter is needed.

1 OVERVIEW

MELSEC-F

(2) UDP (User Datagram Protocol)

This protocol may not guarantee data credibility or reliability in communication between a personal computer/work station and PLC that are connected via network. Thus, even if the data does not reach the target node, it will not be retransmitted.

???Because it is connectionless, communication efficiency is much improved than TCP/IP.

???A check sum is used to increase the reliability of the communication data. When greater reliability must be maintained, a user application or TCP should be used for retrying operation.

(3)IP (Internet Protocol)

???Communication data is sent and received in datagram format.

???Communication data can be divided and reassembled.

???Routing option is not supported.

(4)ARP (Address Resolution Protocol)

???This protocol is used to get the Ethernet physical addresses from the IP addresses.

(5)ICMP (Internet Control Message Protocol)

???This protocol is used to exchange errors which occur on an IP network and various information related to the network.

???Provides a function to transmit IP error messages.

???See Appendix for information regarding the types of ICMP supported.

(6)DNS (Domain Name System)

???This system translates IP addresses to names that are easy to remember by the user.

(7)SMTP (Simple Mail Transfer Protocol)

???This protocol transfers mail.

(8)POP3 (Post Office Protocol Ver. 3)

???This protocol transfers mail received by a mail server to a local computer.

(9)Flag bit of TCP/IP (SYN, ACK, PSH, FIN, RST, and URG)

In communication using TCP, these flag bits indicate segments where connection/disconnection or response confirmation is executed or emergency data is included.

1)SYN (Synchronized Flag)

When this bit is ON (1), it indicates that the initial sequence number value is set in the sequence number field.

This bit is used when the connection is newly opened.

2)ACK (Acknowledgment Flag)

When this bit is ON (1), it indicates that ACK (confirmation response number) field is valid.

It also indicates that this segment includes the information on response confirmation.

When this bit is OFF (0), it indicates that ACK (confirmation response number) field is invalid.

1 OVERVIEW

MELSEC-F

3)PSH (Push Flag)

When this bit is ON (1), the host that has received this segment sends the data to the upper application with high priority.

This bit is to be turned ON when the data should be sent to an external device as soon as possible.

When this bit is OFF (0), the timing when the received data is sent to the upper application depends on the TCP layer of the receiving side.

4)FIN (Fin Flag)

When this bit is ON (1), it indicates that there is no more data to be sent from the segment source and that the send source wants to disconnect. However, data can be received from the external device.

The connection is on until the segment whose FIN bit is ON is received from the external device.

5)RST (Reset Flag)

When this bit is ON (1), the host from which the segment has sent disconnects unilaterally (forcibly).

Disconnection by this method is used when an unrecoverable error with the normal method has occurred or when the host has been restored after being down.

6)URG (Urgent Flag)

When this bit is ON (1), it indicates that this data segment includes the emergency data flag.

2 SYSTEM CONFIGURATIONS

MELSEC-F

2 SYSTEM CONFIGURATIONS

This section explains the system configurations that may be combined with the

Ethernet modules.

(2) Applicable software packages

When using the Ethernet module, the FX Configurator-EN-L for software packages applicable to the Ethernet module can be used.

Refer to the manual of FX Configurator-EN-L for the details.

1)The Ethernet module is set with FX Configurator-EN-L [Configurable by BFM].

2)To use FX Configurator-EN-L, either of the following software should be installed.

???GX Developer (V 8.88S or later)

3)For starting FX Configurator-EN-L, the following shows two kinds of methods.

???Independently starting FX Configurator-EN-L

???Starting from [Tools] menu of GX Developer

4)The installation form of FX Configurator-EN-L differs depend-

ing on sales territory or country of this product.

Consult with the dealer of this product for details.

2 SYSTEM CONFIGURATIONS

MELSEC-F

(2) Connection using the 10BASE-T

External device

Ethernet module

Use devices that satisfy the standards of IEEE802.3 and 10BASE-T.

???Shielded twisted pair cable (STP cable), category 3 (4, 5)

*Straight cables can be used.

(Correct operation is not guaranteed if a crossed cable is used to connect to an external device via the 10BASE-T of the Ethernet module. However, it is possible to use crossed cables to connect two Ethernet modules for data communication or to connect an Ethernet module.)

???RJ45 plug

???10Mbps hub

POINT

???During the high-speed communication (100 M bps) via 100BASE-TX connection, a communication error may occur due to the effect of high frequency noise from devices other than PLC in a given installation environment.The following describes countermeasures on the FX3U-ENET-L side to prevent the effect of high frequency noise for construction of a network

system.

(1)Wiring connection

???Do not bundle the twisted pair cables with the main circuit and power wires, and do not install them close to each other.

???They should be installed at least 100 mm (3.94 in) away from each other.

???Make sure to place the twisted pair cables in a duct.

(2)Communication method

???Data communication with an external device is performed using TCP/IP communication.

???Increase the number of communication retries as necessary.

[When the error cannot be solved]

???Communication is performed at a data transmission rate of 10 M bps by changing the connection hub for the FX3U-ENET-L to a hub capable of handling 10 M bps.

3 SPECIFICATIONS

MELSEC-F

3 SPECIFICATIONS

This section explains the Ethernet module performance specifications and transmission specifications.

For the general specifications, refer to the packaged manual and the User???s Manual of the PLC main unit.

3.1 Performance Specifications

The following explains the performance specifications of the Ethernet module.

*1 Length between the Hub and node.

POINT

The module operation is not guaranteed if any of the following connection is used. Check the module operation on the user side.

???Connections using the Internet (general public line) (Connections using Internet connection service provided by Internet service providers and telecommunications carriers)

???Connections using devices in which a firewall is installed

???Connections using broadband routers

???Connections using wireless LAN

3 SPECIFICATIONS

MELSEC-F

3.6 List of Applications and Assignments of the Buffer Memory

Data transmission/reception between Ethernet Module and PLC is performed via the Ethernet Module buffer memory (hereinafter called BFM).

Reading/writing data in the buffer memory from the PLC must be performed by the FROM/TO instructions (instructions that can access BFM).

In addition, the initial value of the buffer memory or the internally stored value is written when the power is turned on.

(1) Configuration of the buffer memory

Buffer memory consists of a user area and a system area, as listed below.

(a)User areas

1)The areas where the user writes/reads data.

2)A user area consists of a parameter area for initial processing and data communication, an area for data communication, and an area for storing communication status and communication error data.

3)Reading/writing data to the user area should be performed according to the instructions in the corresponding detailed explanation section. Data communication may take longer if continually executed; therefore, execute only when needed.

(b)System areas

The areas used by the Ethernet module

Important

Do not write data in the "system areas" of the buffer memory.

If data is written to any of the system areas, the PLC system may not operate properly.

When writing a value to the buffer memory including "System Area," pay close attention not to change the system bit.

3 SPECIFICATIONS

MELSEC-F

(2) Assignments of the buffer memory

A buffer memory consists of 16 bits per address. <Bit configuration diagram>

The following shows the buffer memory addresses.

(a) Initial processing parameter (BFM #0 to 31)

Communication condition setting (Operational Set- tings) area

???Communication data code setting (b1)

0:Communication in binary code

1:Communication in ASCII code

???TCP Existence confirmation setting (b4)

???Initial timing setting (b8)

0:Do not wait for OPEN (communication impossible at STOP time)

1:Always wait for OPEN (communication

possible at STOP time)

Bits other than above are reserved for system use.

(Continues on the next page)

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

This chapter explains the settings and procedures required prior to operating the

Ethernet module in a system.

4.1 Loading and Installation

This section explains precautions for Ethernet module handling from unpacking to installation, as well as the installation environment common to all modules.

For more details on module mounting and installation, refer to the Installation Manual supplied with the Ethernet module.

4.1.1 Handling precautions

(1)Since it is made of resin, the Ethernet module case should not be dropped or subjected to any shock.

(2)Tighten the module terminal and fixing screws within the following specified clamping torque range:

Make sure to turn off all phases of the external power supply before cleaning or re-tightening the screws. Failure to do so may cause damages or malfunctions of the module.

If the screws are loose, it may cause the module to short circuit, malfunction or fall off.

Tightening the screws excessively may damage the screws and/or the module and cause the module to short circuit, malfunction or fall off.

Do not write any data in the "System area" of the buffer memory on the module.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.1.2 Installation environment

This section explains the installation environment for the PLC. When installing the PLC, the following environments must be avoided:

??? Locations where the ambient temperature exceeds the range of 0 to 55 .

???Locations where the ambient humidity exceeds the range of 5 to 95 % RH.

???Locations where condensation occurs due to a sudden temperature change.

???Locations where there are corrosive or flammable gases.

???Locations exposed to considerable amounts of conductive powdery substances such as dust and iron filing, oil mist, salt, or organic solvents.

???Locations exposed to direct sunlight.

???Locations exposed to strong electric or magnetic fields.

???Locations where vibrations or impacts are directly applied to the main unit.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.2 Settings and Procedures Prior to Starting the Operation

The following shows a flow of the procedure that is required prior to operating:

Procedures prior to operation

Connect the Ethernet module to the base module and wire the 24VDC power supply.

Connect the Ethernet module to the Ethernet network.

Setting the Ethernet module network parameters .

Send the "Ping" command from an external device and confirm the completion of the Ethernet module initial processing

Create a program for each communication

Operation

See Section 4.4, "Connecting

to the Network."

See Section 4.5, "Settings from Ethernet Parameters."

See Section 5.4, "Confirming the Completion

of the Initial Processing."

See applicable communication function

POINT

(1)When the parameter settings are added or modified using the

FX Configurator-EN-L, the settings differs depending on the connection condition to the Ethernet module as shown below.

When directly connected to the PLC

After the parameter settings are added or modified, re-initialization processing can be automatically performed.

When connected via Ethernet

The added or modified parameter settings are not reflected.

To operate the Ethernet module after the parameter settings are added or modified with FX Configurator-EN-L, first save the parameter values, second reboot the Ethernet's module power.

(2)Timing for powering ON

Power ON the PLC and the Ethernet module with the timing as shown below.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

Important

(1)Do not write any data in the "System area" of Ethernet module buffer memory.

(2)When status control (such as remote RUN/STOP) from a external device is used for the PLC, the user should select "Always wait for OPEN" beforehand using the setting parameters. (Select using initial timing in the operation settings.)

If "Do not wait for OPEN" is selected, the communication line will be closed during remote STOP. After that, communication cannot be reopened from the PLC side and remote run from the external device will not work.

(3)When the Ethernet module is replaced, reset the parameters.

(4)When the Ethernet module is replaced, reboot the external device as well. (If the external device retains the Ethernet address, it may be impossible to continue communication because when a module is replaced the Ethernet address changes.)

In the same way, when the external device (personal computer, etc.)is replaced, reboot the Ethernet module.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.4 Connecting to the Network

The following explains how to connect the Ethernet module to the 100BASE-TX/ 10BASE-T networks.

Some precautions that should be observed while connecting the Ethernet module are also shown below. Pay close attention to safety and use the Ethernet module properly.

(1)Sufficient network knowledge and safety precautions are required when installing 100BASE-TX or 10BASE-T networks. Consult a specialist when connecting cable terminals or installing trunk line cables, etc.

(2)Use a connection cable conforming to the standards shown in Section 2.2.

Make sure to place the communication and power cables to be connected to the module in a duct or fasten them using a clamp.

If the cables are not placed in a duct or fastened with a clamp, their positions may be unstable or moved, and they may be pulled inadvertently. This may damage the module and the cables or cause the module to malfunction because of faulty cable connections.

When disconnecting the communication and power cables from the module, do not pull the cables by hand.

When disconnecting a cable with a connector, hold the connector to the module by hand and pull it out to remove the cable.

When disconnecting a cable without a connector, loosen the screws on the terminal block first before removing the cable.

If a cable is pulled while connected to the module, it may cause the module to malfunction or damage the module and the cable.

POINT

Cautions regarding powering the hub, PLC and Ethernet module simultaneously. On some hubs, for a fixed period of time immediately after powering up, even if packets are sent from the Ethernet device, there are cases when packets are not sent to the external device. For this case, create a sequence program that waits a sufficient amount of time after powering up before sending packets.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.4.1 Connecting to the 10BASE-T/100BASE-TX network

This section explains how to connect the Ethernet module to the 10BASE-T, 100BASE-TX network.

The following shows the connection diagram for the twisted paid cable.

RJ45 type modular

shielded twisted-pair cable (Category 3, 5, 5e)

RJ45 type modular jack

(Step 1) Connect the twisted-pair cable to the hub.

(Step 2) Connect the twisted-pair cable to the Ethernet module.

POINT

(1)The Ethernet module detects whether it is 10BASE-T or 100BASE-TX, and in full-duplex or half-duplex transmission mode automatically according to the hub.

For connection to the hub without the auto detection function, set the half- duplex mode on the hub side.

(2)For 10BASE-T or 100BASE-TX connection required devices and a sample system configuration, refer to Section 2.2 (1) and (2).

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.5 Ethernet Module Setting

Setting the Ethernet module as a network module.

The settings found must always be set in order to use the Ethernet module.

(1) "Operational settings" (Details are explained in Section 4.6)

This is for setting common items for when other modules use the Ethernet module.

This settings must always be set, since they are required for the Ethernet initial processing.

(2) "Initial settings" (Details are explained in Section 5.2)

This is for setting common timer values for TCP/IP communication to be used in the Ethernet module as well as for setting the DNS server in order to use the e- mail function.

It is not necessary to set the timer values when communicating using the initial timer values.

(3) "Open settings" (Details are explained in Section 5.5)

This is for setting connection open processing, buffer memory for fixed buffer communication and MC protocol to communicate data with an external device.

(4) "Router relay parameter (Routing information)" (Details are explained in Section 5.3.)

The following setting for data communication with external devices are set:

???Communicating with external devices connected to other Ethernet networks via a router

(5)"E-mail settings" (Details are explained in Section 10.6)

These settings are for using the e-mail transmission.

Ethernet parameter settings are written to buffer memory with a ladder program, and the contents are stored in the Ethernet module's flash ROM.

Also, the contents can be set with FX Configurator-EN-L.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

(2) TCP Existence confirmation setting (BFM #24 b4)

Select the existence check method for TCP communication.

For the existence check function, refer to Subsection 5.2.2.

POINT

(1)"Operational settings" parameters must always be set.

If the settings are changed, the power to the PLC and the Ethernet module must be turned off once and then turned on again.

(2)If re-initialization of the Ethernet module is required due to the occurrence of an error, perform re-initialization using a sequence program.

NOTE

When adjusting settings with FX Configurator-EN-L, select "Operating Settings" at the initial screen and adjust the settings at the "Ethernet Operating Settings" screen.

(3)Send frame setting (BFM #24 b5)

(a)Select the frame of the Ethernet header for the data link layer to be sent by the Ethernet module.

(b)When receiving data from the external device, reception should occur regardless of whether the Ethernet frame or IEEE802.3 frame is used

NOTE

(1)Transmission using Ethernet frames is generally recommended.

(2)When communication with the external device fails, check whether or not communication is possible using a PING command.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

(4)Initial Timing (BFM#24 b8)

(a)Select the timing to open connections for which TCP-Passive open or UDP

open are selected with the "Open settings" parameter (*1).

*1 For more details on the open settings, see Section 5.5 "Open Settings".

*2 If the sequence program of the local station's PLC executes the close processing, the station is not placed in the OPEN request wait status after the connection is shut off.

(b)In the following cases, open/close processing is required with instructions written to the buffer memory (BFM #1602 to 1605).

???When "Do not wait for OPEN" is selected in the initial timing settings.

???If the "Open settings" are not performed for a connection.

???If "TCP-Active" is selected in the "Open settings" for a connection.

For detail on the open/close processing, see Section 5.6 "Open Processing/

Close Processing of the Connection".

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

(5)IP Address settings - IP address (BFM #0 to 1)

(a)Set the IP address of the local station according to the specified input format (decimal or hexadecimal).

It should be set so that the local station Ethernet module and the communicating external device have the same class and sub-net address (two words).

Values bits 7 to 0

Values bits 31 to 24

(Example) Program for "192.168.1.254 (C0 A8 01 FEH)"

DMOV H0C0A801FE U\G0

IP adress "192.168.1.254 (C0 A8 01 FEH)" is stored in BFM #0, #1

Write command for configuration data to a flash ROM.

corresponds to the module number.

(b)It is necessary to use the router relay function in order to communicate with an external device on another Ethernet network (different sub-net address). For more details, see Section 5.3, "Router Relay Parameter".

(c)Set the IP address after consulting a network administrator (the person who plans the network and manages IP addresses).

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.7 Self-Diagnostic Tests

This section explains the self-diagnostic tests for checking the hardware and transmission and reception function of the Ethernet module.

4.7.1 Self loopback test

The following explains the self loopback test that is used to check the hardware including the Ethernet module's transmission and reception circuit.

The self loopback test transmits a test message within the Ethernet module to check if the same message can be received or not. (Connection to the hub is not necessary.) The following explains the procedure for performing the self loopback test. The test takes approximately five seconds to complete.

The test result can be judged from the LED displays on the front of the Ethernet module.

: Lit : Off

The following are probable causes of errors.

???Ethernet module hardware error

???Ethernet line error

An error code is stored in the error log area (BFM#229) in the buffer memory of the Ethernet module; the error content can then be checked from GX Developer. (See Sections 11.2 and 11.3.)

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.8 Maintenance and Inspection

This section explains the maintenance and inspection as well as the installing and uninstalling of the Ethernet module.

4.8.1 Maintenance and inspection

The Ethernet module does not need to be inspected for anything particular other than checking whether or not the connections of cables and the terminal screws are loose. Maintain and inspect the system according to the same inspection items as described in the user's manual for the PLC in order to use it in optimal operating conditions.

Make sure to turn off all phases of the external power supply before cleaning or re-tightening the screws. Failure to do so may cause damages or malfunctions of the module.

If the screws are loose, it may cause the module to short-circuit, malfunction or fall off.

Tightening the screws excessively may damage the screws and/or the module and cause the module to short circuit, malfunction or fall off.

4 SETTINGS AND PROCEDURES PRIOR TO OPERATION

MELSEC-F

4.8.2 Installing and uninstalling the module

Before installing or uninstalling the Ethernet module, make sure to read Section 4.1, "Handling Precautions" thoroughly, ensure the safety of the installation, and handle the module properly according to the instructions.

The following explains the procedures when installing/uninstalling the Ethernet module.

<Operation procedure when replacing the Ethernet module> (*1)

(Step 1) Read and save the parameters from the Ethernet module using FX Configurator-EN-L (*2)

(Step 2) Turn off the power supply to the base module, the extension device, and the Ethernet module.

(Step 3) Remove the network cable and Ethernet module.

(Step 4) Set up and start up the new Ethernet module according to Section 4.2, "Settings and Procedures Prior to Starting the Operation." (*3)

(Step 5) Reset the external device. (*4)

*1 It is recommended to record and save parameters not only when the Ethernet module is replaced but also when parameters for the Ethernet module are created or modified.

*2 When FX Configurator-EN-L is not installed :

1)Monitor the buffer memory in the Ethernet module using GX Developer, and record set values of the parameters for the Ethernet module.

For details on the parameters, refer to Section 4.6 "Operational Settings", Section 5.2 "Initial Processing", Section 5.3 "Router Relay Parameter" and Section 5.5 "Open Settings".

2)After replacing Ethernet module, write the setting value into BFM by GX Developer.

3)Write the setting value into the Flash ROM by BFM#25.

*3 When the Ethernet module is replaced, use the FX Configurator-EN-L to reset the parameters.

*4 When the Ethernet module is replaced, reset the external device as well. (If the external device retains the Ethernet address, it may be impossible to continue communication because when a module is replaced the Ethernet address changes.)

In the same way, when the external device (personal computer, etc.)is replaced, restart the Ethernet module.

(Step 1) Turn off the power supply to the FX base module and the Ethernet module.

(Step 2) Replace the FX base module. (See the Manual of FX base module.) (Step 3) Turn on the power.

5 COMMUNICATION PROCEDURE

MELSEC-F

5 COMMUNICATION PROCEDURE

This chapter gives an overview of the communication procedure using the Ethernet module, as well as the required initial processing of the Ethernet prior to data communication and the open processing for communication with an external device. The sequence program can be effectively simplified by setting the parameters of the Ethernet module supported by FX Configurator-EN-L.

5.1 Overview of the Communication Procedure

This section gives an overview of the procedure for performing data communication with external devices via the Ethernet module.

???Start data communication by establishing connections with external devices via the initial or open processing.

???End data communication by closing the connection, and, as a result, terminating all communication processing.

The following diagram illustrates the communication procedure:

(There is no connection since UDP/IP does not have a notion of connection.)

5 COMMUNICATION PROCEDURE

MELSEC-F

NOTE

The following communication can be performed with an open device on other end.

???Communication using MC protocol

???Sending/receiving in fixed buffer communication (procedure exists)

When receiving communication request data from an external device

PLC

Receive completion signal

Receive data acquisition processing

Receive data normal completion BFM operation

Store data received

*For receiving when the communication is open

Ethernet module

(Subheader code)

Fixed buffer communication (Procedure exists)

(communication)

60H

Request from an external device (receive)

Device memory, etc.

Data

Head

Response to the request (send)

Head

5 COMMUNICATION PROCEDURE

MELSEC-F

5.2 Initial Processing

This section explains the initial processing of the Ethernet module.

5.2.1 Initial processing

The initial processing enables data communication with an external device by setting the parameters required for data communication via the Ethernet module.

Set the following parameters in the sequence program, write them to the Ethernet module; the initial processing of the Ethernet module is then performed by one of the following methods.

???Re- initialization request (Write the re-initialization request (0001H, 0002H, 0005H or 0006H) to BFM #1600.)

???Power ON the Ethernet module again.

(1)Parameters required for initial processing

(2) Confirmation of initial processing result

If the initial processing does not complete normally, correct the above parameter setting value and write to the Ethernet module. Then re-initialize the Ethernet module.

5 COMMUNICATION PROCEDURE

MELSEC-F

(1)Timer setting - TCP ULP timer (BFM#4)

(a)This item sets the time of packet existence during TCP data sending.

This timer is passed through the parameter when TCP opens or data is sent.

(b)Set the value in the range from 2 to 32767.

(c)Timer setting = setting value 500 ms

(2)Timer setting - TCP zero window timer (BFM#5)

(a)The window indicates the reception buffer on the receiving side.

(b)When there is no more space in the receiving buffer (window size = 0) on the receiving side, data communication has to wait until enough space is made. When this occurs, the sending side sends a sending window confirmation packet to the receiving side after the TCP zero window timer value has been reached, and confirms the reception enabled status.

(c)Set the value in the range from 2 to 32767.

(d)Timer setting = setting value 500 ms

(3)Timer setting - TCP resend timer (BFM#6)

(a)Set the resend time if ACK is not returned during TCP opening or data transmission. This timer is also used for the existence time of the ARP function.

(ARP is resent in "TCP resend timer" value/2 if a response is not returned after the sent ARP request.)

(b)Set the value in the range from 2 to 32767.

(c)Timer setting = setting value 500 ms

(4)Timer setting - TCP end timer (BFM#7)

(a)When the TCP connection is closed from the local station, this timer sets the monitoring time for how long the local station waits for a FIN request from an external device after it sends a FIN request and the external device returns an ACK.

(b)If the FIN request cannot be received from the external device before the time designated by the TCP end timer setting, a RST should be sent to the external device to forcibly close the connection.

(c)Set the value in the range from 2 to 32767.

(d)Timer setting = setting value 500 ms

5 COMMUNICATION PROCEDURE

MELSEC-F

(5)Timer setting - IP assembly timer (BFM#8)

(a)Communication data may be divided on the IP level due to the buffer restriction at the sending or receiving station.

(b)Set the value in the range from 1 to 32766.

(c)Timer setting = setting value 500 ms

(6)Timer setting - Response monitoring timer (BFM#9)

(a)This timer setting sets the following times.

1)The time to wait for a response after sending a command.

2)The time to wait for the last message after receiving the first message when the message is divided.

(b)Set the value in the range from 2 to 32767.

(c)Timer setting = setting value 500 ms

(7)Timer setting - Destination existence confirmation starting interval (BFM#10)

(a)This timer sets the time interval before attempting to confirm the existence of an external side when an open connection for which existence confirmation is required does not respond.

(b)Set the value in the range from 1 to 32767.

(c)Timer setting = setting value 500 ms

(8)Timer setting - Destination existence confirmation interval timer (BFM#11)

(a)This timer sets the time interval before reconfirming the existence of an external device on an open connection for which existence confirmation is required that does not respond.

(b)Set the value in the range from 1 to 32767.

(c)Timer setting = setting value 500 ms

(9)Timer setting - Destination existence confirmation resend timer (BFM#12)

(a)This timer sets the number of times to reconfirm existence when there is no response from an external device on an open connection for which existence confirmation is required.

(b)Set the value in the range from 1 to 32767.

(10)DNS setting - IP address of DNS server n (*1)

*1 The DNS setting is set when the e-mail sending function is used. Refer to Chapter 10, "E-mail Function".

5 COMMUNICATION PROCEDURE

MELSEC-F

POINT

To adjust settings with FX Configurator-EN-L, select "Initial Settings" from the initial screen, and make the settings at the "Ethernet Initial Settings" screen.

NOTE

(1)Set the value of each timer on the Ethernet module side such that the following relations are met.

Furthermore, when connecting a line using Mitsubishi products, you should make sure that both nodes have the same settings.

(2)Set the value of each timer on the external device side such way that the following relations are met.

Communication errors such as transmission timeouts may occur more frequently if the timer values are not set so that they satisfy the following relationships.

TCP resend timer value on the external device side

*1 n is the number of TCP segment transmissions and can be obtained via the following calculation:

Example1: Number of TCP segment transmissions when communicating via the same line

The maximum segment size is 1460 bytes via the same line (without going through a router) and the number of TCP segment transmissions is as follows:

???n = 1, if the size of the message transmitted by the Ethernet module is 1460 bytes or less.

???n = 2, if the size of the message transmitted by the Ethernet module is greater than 1460 bytes.

Example2: Number of TCP segment transmissions when communicating via separate lines

The maximum segment size is at least 536 bytes on a separate line (via router, etc.) and the number of TCP segment transmissions is as follows:

???n = 1, if the size of the message transmitted by the Ethernet module is 536 bytes or less.

???n = 2, if the size of the message transmitted by the Ethernet module is greater than 536 bytes and no more than 1072 bytes.

???n = 3, if the size of the message transmitted by the Ethernet module is greater than 1072 bytes and no more than 1608 bytes.

5 COMMUNICATION PROCEDURE

MELSEC-F

(3)When communication errors occur, the setting value should be changed to increase the number of retries.

The number of retries is obtained by using the following equation: (In case of the initial values, 2 = (60/20) - 1)

Example: Assuming the values are set in such a way that the number of retries is two, a data transmission error will occur at the timing shown in the figure below if data transmission fails (when communicating using fixed buffer).

A(Each: TCPtimerresendvaluetimershouldvaluebe identical.)

(The time after which the data should be retransmitted when an "ACK" is not returned after sending data.)

(4)Perform the following setting in order to eliminate the retries explained in (3) (i.e., to set the number of retries to 0).

(Each timer value should be identical.)

(5)The target existence check is a function whereby the Ethernet module checks whether or not a remote device is functioning normally by sending an existence check message and then waiting to see whether a response message is received. It is used if a connection to a remote device is open but communication with the remote device has not been performed for a certain period of time.

(a)The existence check function has two methods of checking: PING and KeepAlive.

The Ethernet module performs each of the existence checks based on the setting values explained in (7) to (9) of this section and the existence check setting of the open settings (refer to Section 5.5 (6)).

The existence check function (Ping or KeepAlive) can be selected at the time of operation setting or re-initialization.

For the operation setting, refer to Section 4.6.

Refer to Subsection 5.2.3 for the explanation on re-initialization.

5 COMMUNICATION PROCEDURE

MELSEC-F

1)Checking by KeepAlive

This method is used for a connection opened via the TCP/IP protocol. The Ethernet module performs an existence check by sending an existence check ACK message to a remote device with which communication has not been performed for a certain period of time and waiting to see whether or not a response is received. (*1)

*1 The connection is cut off if the remote device does not support the TCP KeepAlive function (response to KeepAlive ACK messages).

2)Checking by PING

This method is used for a connection opened via the TCP/IP or UDP/IP protocol.

The Ethernet module performs an existence check by sending a PING command (using the ICMP echo request/response function) to a remote device with which communication has not been performed for a certain

period of time and waiting to see whether or not a response is received.

(*2)

*2 Note that the Ethernet module automatically returns 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 communication with the remote device is closed.)

(b)The following actions are taken if a response message cannot be received (an error is detected) from the remote device.

???The corresponding connection will be forcibly closed (the line is disconnected). (*3)

*3 It is possible to reopen it with a user program.

???The open completion signal (the corresponding bit of BFM#20480) is turned off and, the error code (C035H) is stored in places such as the open error code storage area.

Also, the open/close status (BFM #1602 to 1605) value becomes "0000H".

Example: Assuming the values are set under the condition that the number of retries is three, the Ethernet module performs target existence check at the timing shown in the figure below.

(An example of existence check by PING)

Open completion signal

BFM#20480

5 COMMUNICATION PROCEDURE

MELSEC-F

5.2.3 Re-initialization

Re-initialization is performed in order to place the Ethernet module into its startup status without actually restarting the PLC.

Re-initialization of the Ethernet module can be performed in a sequence program. The purposes of and how to program the re-initialization of the Ethernet module are explained below.

NOTE

When FX Configurator-EN-L is being used, re-initialization can be performed after downloading the parameters.

However, if it is connected to the Ethernet module via Ethernet, re-initialization cannot be performed.

Re-initialize from the sequence program.

(1)Purposes of performing re-initialization

(a)To update address information of an external device maintained by the Ethernet module

The Ethernet module maintains the IP address of the external device with which it has been communicating and the corresponding Ethernet address (MAC address). This is done in order to prevent other devices from accessing the PLC illegally using the IP address of an external device with which communication was performed normally. (*1)

For this reason it is necessary to re-initialize in order to clear the address information of the external device maintained by the Ethernet module in case a module or board on the external device side has been replaced due to failure.

*1 Ethernet address is unique to a device. No devices share the same Ethernet address.

(b)To change the IP address of the Ethernet module of the local station

If the system is changed, it is possible to restart communication with external devices by changing the IP address (for the Ethernet module of the local station) in the operation settings (see Section 4.6).

(c)To change the communication condition setting values

It is possible to restart communication with external devices by changing the communication conditions in the operation settings (see Section 4.6).

5 COMMUNICATION PROCEDURE

MELSEC-F

(2) Programming and timing for re-initialization

The programming and timing for re-initialization is shown below:

??? Program example for the unit No. 1

<<Re-initialization>>

Re-initialization request self-holding

Upon completion of Ethernet module initial processing, re-initialization is performed

Self-holding cancel

Processing upon normal completion

Abnormal end

BFM #27 is set to "0000H" at abnormal end.

FROM BFM#1600

Module initialization

1)It is confirmed whether the initial processing has been completed normally.

2)All data communication currently being performed with external devices is terminated, and close processing will be performed on all connections.

3)"0001H ", "0002H ", "0005H " or "0006H " is written to BFM#1600. (Initial normal completion signal: BFM#27 "0001H ")

(Open completion signal: BFM#20480 "All OFF(0H)")

4)When re-initialization is completed, the value in BFM#1600 will be 8000H (normal completion) or C000H (abnormal completion).

*If the re-initialization is completed abnormally, the error code is stored in the following area.

Initial error code storage area (BFM#105)

5 COMMUNICATION PROCEDURE

MELSEC-F

(3) Operation for re-initialization

Operation for re-initialization differs as follows, depending on the value written to

BFM#1600.

*1: When re-reading the flash ROM, the re-initialization is performed in the same status as when the power supply is turned on.

POINT

Please keep the following points in mind when re-initializing the Ethernet module. (Failure to do so may cause errors in the data communication with the external devices.)

(1)Be sure to end all current data communication with external devices and close all connections before re-initializing.

(2)Be sure to reset external devices if the IP address of the Ethernet module has been changed. (If an external device maintains the Ethernet address of a device with which it communicates, the communication may not work after the IP address of the Ethernet module has been changed.)

NOTE

It is possible to change the operational settings when re-initializing by a sequence program.

: Valid, : Invalid

5 COMMUNICATION PROCEDURE

MELSEC-F

5.3 Router Relay Parameter

This section explains the router relay parameter.

NOTE

When making settings with the FX Configurator-EN-L, select [Router Relay

Parameters] from the initial screen and adjust the settings at the [Ethernet Router

Relay Parameter Settings] screen.

(1)Router relay function (BFM#2 b4,b5)

(a)Set whether the router relay function will be used or not.

The router relay function is not needed when communicating with the target device on the same Ethernet network (the subnet address of the IP address is the same).

(b)The router relay function allows communication with devices on other Ethernet networks via routers and gateways.

(The router relay function does not mean a function to act as a router.)

(c)One router can be set for the router relay function.

5 COMMUNICATION PROCEDURE

MELSEC-F

(2)Subnet mask pattern (BFM#512, 513)

(a)Set the subnet mask. *1 (Setting range: C0000000 to FFFFFFFCH) Consult the network administrator for the setting.

(b)When not using the subnet mask, set any of the following table values according to the class.

*1 Ethernet networks include small-scaled network systems where multiple devices are connected to one Ethernet hub along with medium and large- scaled network systems where multiple small-scaled networks are connected by routers, etc.

The subnet mask logically divides one network, where many devices are connected, into multiple sub-networks to facilitate administration.

(Example) Class B

Network address

POINT

(1)All devices on the same sub-network must have a common subnet mask.

(2)When not administrated by the sub-network, the connected devices need not have a subnet mask. (Set the network address of the corresponding class.)

(3)Router IP address (BFM#514, 515)

Set the IP address of the router to be used when FX3U-ENET-L communicates with the target device on another Ethernet network (refer to (4) below).

Set the value that satisfies the following conditions.

???Condition 1: The IP address class is either A, B or C.

???Condition 2: The sub-net address of the default router is the same as that of

the local station Ethernet module.

??? Condition 3: The host address bits are not all "0" or all "1".

5 COMMUNICATION PROCEDURE

MELSEC-F

5.4 Confirming the Completion of the Initial Processing

The initial processing for the Ethernet module completes by selecting re-initialization, then turning the power ON again, or re-initializing via buffer memory operations after parameters are written to the Ethernet module.

(When the processing is completed normally, the [INIT.] LED on the front of the Ethernet module turns on.)

???"Operational settings" parameter

???"Initial settings" parameter

This section explains how to check the completion of the initial processing.

POINT

The status of the Ethernet module becomes communication enabled when the initial processing is completed normally. See reference sections for each communication function to perform communication.

When the initial processing has not been completed normally, do the following to check the error contents, take corrective actions, then execute the initial processing again.

???Check the error code using the "Parameter status" of the Ethernet diagnostics. (See Section 11.2.)

???Check the contents of the error corresponding to the error code, then take corrective actions. (See Section 11.3 and Section 11.4.)

5 COMMUNICATION PROCEDURE

MELSEC-F

5.4.1 PING command (Personal computer Ethernet module)

The following example illustrates how to confirm the completion of the initial processing by issuing the PING command to the local station's Ethernet module from an external device connected on the same Ethernet network. (In the example, the confirmation is made between devices whose IP address class and sub-net address are identical.)

<Designation method> ping IP address

IP address of the Ethernet module: 192.0.1.254

Example of screen at normal completion

C:\>ping 192.0.1.254Execute the ping command

Pinging 192.0.1.254 with 32 bytes of data:

Reply from 192.0.1.254: bytes=32 time=1ms TTL=128

Reply from 192.0.1.254: bytes=32 time<10ms TTL=128

Ping statistics for 192.0.1.254:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 1ms, Average = 0ms

C:\>_

Example of screen at abnormal completion

C:\>ping 192.0.1.254Execute the ping command

Pinging 192.0.1.254 with 32 bytes of data:

Request timed out:

Ping statistics for 192.0.1.254:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>_

Check the following items and send the PING command again.

???Check the Ethernet module's attachment.

???Check the connection to the Ethernet network.

???Check the contents of each parameter written to the Ethernet module.

???Check the operation condition of the Ethernet module (are there any irregularities?).

???Check the IP address of the Ethernet module dictated by the PING command.

5 COMMUNICATION PROCEDURE

MELSEC-F

5.4.2 Loop back test (Communication using MC protocol)

The loop back test can be performed with communication using MC protocol in order to check the completion status of the initial processing for the target Ethernet module. The following is an overview of the loop back test for communication using MC protocol. See Chapter 9 for details.

(1)Loop back test for communication using MC protocol

The loop back test is a function designed to check the following:

???Whether a line has been properly connected to the test target Ethernet module.

???Whether the parameters for the Ethernet module have been correctly set.

???Whether the initial processing for the Ethernet module has been completed normally.

???Whether the program for the external device is running correctly.

(2)It is necessary to connect lines when performing communication using MC protocol with the user port on the Ethernet module side.

Perform the open processing for the connection to be used on the Ethernet module side.

(3)This function can only be used for the Ethernet module of the local station. The function cannot be used for the Ethernet module of another station via a network system.

(Loop back test target station)

5 COMMUNICATION PROCEDURE

MELSEC-F

5.5 Open Settings

This section explains the open setting.

A sequence program can perform open processing (establishing connection) with up to a maximum of 4 external device stations

Once a connection is established with an external device, it is possible to communicate using MC protocol, fixed buffer communication.

Thus, the open processing is required even when communicating using MC protocol.

NOTE

When adjusting settings in FX Configurator-EN-L, select the [Open Settings] from the initial screen and adjust the settings at the [Ethernet Open Settings] screen.

5.5.1 Fixed buffer connection (connection No. 1 and connection No. 2)

*1 "1 (Pairs)" cannot be selected in connection No. 2.

(1)Protocol

(connection numbers 1, 2; BFM#32, 33 b8)

(a) Select the protocol for each connection.

(b) For protocols (TCP/UDP), see 1.3, "Software Configuration".

5 COMMUNICATION PROCEDURE

MELSEC-F

(4)Fixed buffer communication

(connection numbers 1, 2; BFM#32, 33 b9 to b10)

(a)For this item, select the communication method when communicating using the fixed buffers.

(5)Pairing open

(connection numbers 1 only; BFM#32 b7)

(a)Select whether or not the Ethernet module's receiving and sending connections are made into one pair and connected to one port of an external device when using fixed buffer communication (Either one among [Procedure exist] or [No procedure] can be specified).

For more detail, see [Section 5.7 Pairing Open].

(b)"Pairs" can be selected only in connection No. 1.

If "Pairs" is selected in connection No. 2, an error will occur when the connections are opened.

???Error information is stored in the error log area (BFM#227 to 511) in the buffer memory.

???The open error code is stored in BFM#134.

5 COMMUNICATION PROCEDURE

MELSEC-F

(6)Existence confirmation

(connection numbers 1, 2; BFM#32, 33 b1)

(a)This setting selects whether or not the Ethernet module should confirm that an external device still operates normally when there is no communication for a fixed period of time. The open processing for the connection with the external device must have been completed.

(b)When an error occurs in the existence confirmation, the Ethernet module performs the following processing.

???Forcibly closes the line and stores the error information in the error log area (BFM#227 to 511) of the buffer memory.

???Turns off the open completion signal (BFM#20480) and stores the open error code in BFM#124, 134.

(c)If the external device will be changed while a UDP/IP connection is open, "No confirm" should be selected.

If "Confirm" is selected, the Ethernet module will confirm the existence of the first destination after the UDP/IP connection is opened. Existence confirmation is not performed for the changed destination, i.e. the newly selected external device.

(7)Local station Port No.

(connection numbers 1, 2; BFM#40, 47)

(a)In this item the port number of each connection for the Ethernet module is set.

(b)The setting values are designated in the range from 1025 to 5548 and from 5552 to 65534. Set port numbers that are not already used by other ports.

(c)Set the port numbers for the Ethernet module upon consulting a network administrator.

(8)Destination IP address

(connection numbers 1, 2; BFM#41 to 42, 48 to 49)

(a)Set the IP addresses (two words) for external devices in the chosen input format.

(b)The IP addresses of external devices must be given values other than 0H,

FFFFFFFFH.

(c)Set the IP addresses of external devices upon consulting a network administrator.

5 COMMUNICATION PROCEDURE

MELSEC-F

5.5.2 MELSOFT/MC protocol connections (connection No. 3 and connection No. 4)

*1 Used to connect MELSOFT products through TCP/IP communication.

It performs passive open processing of TCP connection for all MELSOFT products connected to the network. (It waits for an Active open request given to its own station.)

*2 Regardless of the initial timing setting in the operation settings (refer to Section 4.6), this connection will always wait for the open status.

*3 The set connection is used only for data communication with MELSOFT products.

*4 Set connections for all connected MELSOFT products when connecting two or more MELSOFT products at the same time.

Up to 2 connections can be set.

Number of MELSOFT connections + Number of MC protocol connections 2

(1) Local station Port No. (connection numbers 3, 4; BFM#54, 61)

Select this item when using connections for MC protocol.

(a)In this item the port number of each connection for the Ethernet module is set in Decimal.

(b)The setting values are designated in the range from 1025 to 5548 and from 5552 to 65534. Set port numbers that are not already used by other ports.

(c)Set the port numbers for the Ethernet module upon consulting a network administrator.

(2)Destination IP address (connection numbers 3, 4; BFM#55 to 56,

62 to 63)

Select this item when using connections for MC protocol.

(a)Set the IP addresses (two words) for external devices in the chosen input format (decimal/hexadecimal).

(b)The IP addresses of external devices must be given values other than 0H,FFFFFFFFH.

(c)Set the IP addresses of external devices upon consulting a network administrator.

(3) Destination Port No. (connection numbers 3, 4; BFM#57, 64)

Select this item when using connections for MC protocol.

(a)Set the port numbers of the external devices for each connection.

(b)The port numbers of the external devices are set in the range from 1025 to 65534.

(c)Set the port numbers for the external device upon consulting a network administrator.

(d)Refer to Paragraph 5.5.1 (9) for cautions on setting the port number.

5 COMMUNICATION PROCEDURE

MELSEC-F

5.6 Open Processing/Close Processing of the Connection

This section explains the open processing/close processing using sequence programs.

(1)Open processing

(a)The purpose of the open processing is to establish a connection with an external device in order to perform the following forms of data communication.

They can be performed with an external device opened by the user.

???Sending/receiving using the fixed buffers (Procedure exists/No procedure)

:Connections No. 1 and 2 only

???Communication using MC protocol ("Unpassive open (MC)" or "Full passive open (MC)" in the open system setting) must be set.

:Connections No. 3 and 4 only

(b)When the following is set by the parameter settings, the open processing should be performed in a sequence program.

1) In the Operational settings (Section 4.6)

When "Do not wait for OPEN" is set in the "Initial timing setting".

2) In the open settings (Section 5.5)

When "Active" is set in the "OPEN system" setting.

(c)In order to perform open processing, the initial processing must be complete (BFM #28b0: ON) and the hub communication status (BFM #28b7: ON) must be on.

(d)A connection with an external device must be established (open processing) when communicating using either the MC protocol, fixed buffers. (*1)

Two types of data communication mentioned above can also be performed with an external device opened by the user.

*1 Since the Ethernet module recognizes the external device by the IP address, the open processing is required for UDP communication.

(e)Up to a maximum of 4 connections can be opened to external devices. However, two buffers are required when communicating with the same external device using fixed buffer communication, so in this case the number of external devices that can be communicated with will be lower.

POINT

During communication using MC protocol, if data communication is to continue even after the Ethernet module installed PLC, has been placed in the STOP status, enable "Always wait for OPEN (communication possible at STOP time)" under "Initial timing setting" (see 4.6, "Operation Settings").

5 COMMUNICATION PROCEDURE

MELSEC-F

(2)Close processing

(a)The purpose of the close processing is to disconnect (cancel) the connection with the external device established by open processing mentioned previously.

(b)The close processing is used when terminating a connection with an external device, changing an external device of a connection, changing communication conditions, etc.

(c)Perform the close processing for connections established by open processing using sequence programs.

(d)Determine the timing of close processing with the external device.

The examples in the following sections describe the procedures for establishing a connection from the Ethernet module to an external device and subsequently closing it again by open and close processing for connection number 1.

POINT

Except when the close processing is requested, the open completion signal (applicable bit of BFM#20480) automatically turns off and the communication line is closed in the following cases:

(1)When the existence confirmation function times out (see Section 5.5).

(2)When a close or RST command is received from an external device.

(3)When the Active open request is received again from the external device in the open completion status of TCP.

After returning ACK to the external device, the Ethernet module closes the connection when the RST command is received from the external device. However, when receiving the Active open request again from the external device with a different IP address or port No., the Ethernet module only sends the RST command. (It does not close the connection.)

5 COMMUNICATION PROCEDURE

MELSEC-F

Power-on

Open status

Open allowed status

Closed status

Initial normal completion

BFM#27=0001H

Hub connected signal

BFM #28b7

OPEN/ CLOSE instruction status BFM#1602

Open completion signal

BFM#20480

Open request signal

BFM#20482

1)Parameter update completed

2) Hub connected

OPEN status 0005H (OPEN failure 0010H)

SYN

4) 5)

SYN+ACK

1)After communicating the parameter settings, confirm the normal completion of the Ethernet module initial processing.

(Initial completion signal BFM#27 "0001H")

2)Confirm that the Ethernet module and hub are connected. (BFM#28 b7:ON)

3)Start the open processing writing with pulse execution instruction 0001H to BFM#1602.

4)The Ethernet module executes the open processing.

??? Sends the open request (SYN).

5)When the open processing completes normally

Data communication is enabled.

When the open processing completes abnormally (*1)

???The open error code is stored in the buffer memory.(*2)

???Open error detection (BFM#1602 "0010H" or "0015H")

???Area for module status (BFM#28 b6:ON)

6)Start the close processing writing 8000H to BFM#1602.

7)The Ethernet module executes the close processing.

???Sends the close request (FIN).

8)When the close processing completes normally (*3)

??? Open completion signal (BFM#2048 b0) : OFF

??? Open/Close instruction status (BFM#1602 "0000 H ")

5 COMMUNICATION PROCEDURE

MELSEC-F

POINT

This example uses connection number 1 for explanation. Use the corresponding

BFM No. and bits for other connection numbers.

*1 Processing when the open processing is abnormally completed (TCP)

When opening from the Ethernet module under a normal situation, if the Ethernet module sends a SYN, the external device returns an ACK and a SYN.

However, if the Ethernet module sends a SYN and then the external device returns a RST, the open abnormal completion (BFM#28 b6) is immediately turned on and open processing ends.

*2 The open status and error code at abnormal end can be confirmed with the following buffer memory.

???Each connection open abnormal code area of the communication status storage area

(Connection numbers 1 to 4; BFM#120 to 159)

???Error log area (BFM#227 to 372)

???Error codes stored in the open error code area are cleared when writing "0001H" to the BFM #1602 to 1605 to perform the open operation.

*3 Processing when the close processing is abnormally completed (TCP) When closing normally from the Ethernet module, the Ethernet module sends a FIN request and the external device returns an ACK and a FIN. However, if an ACK and a FIN are not returned because the external device is faulty, the Ethernet module forcibly disconnects the connection (sends a RST message).

5 COMMUNICATION PROCEDURE

MELSEC-F

1)The open request signal turns off by writing "8000H" to the BFM#1602.

2)The Ethernet module executes the close processing.

3)The Ethernet module sends a FIN request to the external device.

4)The external device sends back FIN and ACK messages in reply to the FIN request sent by the Ethernet module.

(When the reply is not returned, the Ethernet module sends the FIN request again.)

5)The Ethernet module waits for the external device to send an ACK and a FIN.

(The module waits for the amount of time set in the TCP end timer value. For details on how to set it, see Section 5.2, "Initial Settings".)

If the ACK and FIN messages are received at this point, it returns an ACK as in the normal processing.

6)If an ACK and a FIN are not received within the time designated by the TCP end timer, an RST message is sent to the external device.

7)The Ethernet module determines that the close procedure is completed and turns off the open completion signal regardless of the status of the external device.

NOTE

(1)When the procedure above is performed, the Ethernet module determines that the closing of the external device is executed normally, thus the close processing result is not stored in the error log area.

(2)The procedure described above is a special function of the Ethernet module; it is not available for general TCP/IP protocols.

5 COMMUNICATION PROCEDURE

MELSEC-F

Program example

This example explains a program for open processing/close processing when

Active open is selected in the Open system setting.

(1)Execution environment for the program example

(a)The Ethernet module is connected to the second special module. (The unit number is setting 1)

(b)The unit number specified at the sequence program and FX Configurator- EN-L is 1.

(c)Make Operation settings in the following manner.

(f)The area enclosed with in the program example should be used when the [Open settings] Ethernet module parameters are not set for

FX Configurator-EN-L.

This part of the program is not required when the [Open settings] parameters are used for FX Configurator-EN-L.

(2)Outline of the program example

(a)After each parameter is set in FX Configurator-EN-L or the sequence program and written to the Ethernet module, re-initialize or power ON the module again and confirm the completion of the initial processing via buffer memory operations.

(b)The Ethernet module performs the open processing for connection No. 1 to the external device set in the [Open settings] or control data.

(c)The close processing for connection No. 1 is performed according to the close instruction to the Ethernet module or the close request from the external device.

5 COMMUNICATION PROCEDURE

MELSEC-F

5.6.2 Passive open processing/close processing

This section explains the procedure for opening and closing a connection with the Ethernet module via an external device.

The operations of Passive open processing/close processing differ depending on whether "Always wait for OPEN" or "Do not wait for OPEN" is selected, as shown in this section.

(1) When "Always wait for OPEN" is selected in the operational setting

This is an explanation of (BFM #24 b8: ON) open processing/close processing when initial timing settings for Operational Settings are set to be always wait OPEN (Communication Possible at STOP).

In this case, sequence programs for open processing and close processing are not required because the Ethernet module keeps the connection in the always wait for the OPEN status according to the [Open settings] parameter setting.

For detail on the [Open settings] parameter, see Section 5.5, "Open Settings".

*1 An open request (SYN) received after the normal completion of an initial processing and before the Ethernet module is placed in the open acknowledge enabled status generates an error, and the Ethernet module sends a connection forced close (RST).

5 COMMUNICATION PROCEDURE

MELSEC-F

1)After the parameters are sent, the normal completion of the Ethernet module initial processing is confirmed (Initial normal completion signal BFM#27 "0001H")

After the initial processing is normally completed, the connection is placed in the open allowed status and the Ethernet module waits for an open request from the external device.

2)The Ethernet module starts the open processing upon receiving the open request (SYN) from the external device.

When the open processing is normally completed (Open/close status (BFM#1602 "0005H")), the open completion signal (BFM#20480 b0) turns on and data communication is enabled.

3)The Ethernet module starts the close processing upon receiving the close request (FIN) from the external device.

When the close processing is completed (BFM#1602 "0000H"), the open completion signal (BFM#20480 b0) turns off and data communication is disabled.

4)After the Ethernet module's internal processing is Rissn/completed, the connection returns to the open acknowledge enabled status.

NOTE

For Passive open connections for which [Always wait for OPEN (Communication possible at STOP time)] is selected in [Operational settings], the connection open/ close processing of the Ethernet module side is performed according to the open/ close request from the external device.

When the close processing is performed from the Ethernet module (this station), the applicable connection will not return to the open acknowledge enabled status after the close processing, even if [Always wait for OPEN (communication possible at STOP time)] is selected in [Operational settings].

(It requires the same open processing and close processing as the connection for Passive open for which [Do not wait for OPEN (communication impossible at STOP)] is selected.)

(2) When "Do not wait for OPEN" is selected in the operational setting

When initial timing settings of operational settings are at [Do not wait for OPEN (communication impossible at STOP time)], the (BFM #24 b8: OFF) open processing/close processing is performed as explained below.

Since open processing/close processing is executed by a sequence program, an external device can be changed while the connection is established.

5 COMMUNICATION PROCEDURE

MELSEC-F

Open completion signal

BFM#20480

*1 If an open request (SYN) received after the normal completion of an initial processing and before the Ethernet module is placed in the open acknowledge enabled status, an error is generated, and the Ethernet module sends a connection forced close (RST).

1)After communicating the parameter settings, confirm the normal completion of the Ethernet module initial processing.

(Initial normal completion signal (BFM#27 "0001H":)

2)Start the open processing by writing "0001H" to the BFM#1602. (Open request signal (BFM#20482 b0) : ON

3)OPEN possible (Listen status) from external device. (Open/close status BFM #1602 "0003H")

4)The Ethernet module starts the open processing upon receiving the open request (SYN) from the external device.

??? OPEN/CLOSE instruction status (BFM#1602 "0010H" or "0015H")

5)The Ethernet module starts the close processing upon receiving the close request (FIN) from the external device.

When the close processing is completed, the open completion signal turns off and data communication is disabled.

5 COMMUNICATION PROCEDURE

MELSEC-F

Program example

This example explains a program for open processing/close processing when

Unpassive open is selected in the open system setting.

(1)Execution environment for the program example

(a)The Ethernet module is connected to the second special module. (The unit number is setting 1)

(b)The unit number specified at the sequence program and in FX Configurator- EN-L is 1.

(c)Adjust Operation settings in the following manner.

(e)The following contact signals are used in the program. X000 Open instruction

M100 Open request self-hold

M101 Open complete

M102 Closed indicator self-hold

M103 Cancel self-hold when closed

(2)Outline of the program example

(a)The open processing for connection No. 1 of the Ethernet module is performed.

After the completion of the open processing, connection No. 1 waits for the open request from the external device.

(b)The close processing for connection No. 1 is performed according to the close instruction (X000=OFF) to the Ethernet module.

5 COMMUNICATION PROCEDURE

MELSEC-F

5.6.3 UDP/IP open processing/close processing

The following explains the UDP/IP open processing.

The operations of the open processing/close processing in UDP/IP differ depending on whether "Always wait for OPEN" or "Do not wait for OPEN" is selected in the initial timing settings (BFM #24 b8) from operational settings.

(1) When "Always wait for OPEN" is selected in the operational settings (Communications possible at STOP time)

According to the Open settings (BFM#32), a selected connection for the UDP/IP communication is established automatically after the Ethernet module installed station has been restarted, and data transmission/reception is enabled. Sequence programs for open processing and close processing are not required. For details on the [Open settings] parameter, see Section 5.5, "Open Settings".

NOTE

When performing the open and close processing by writing to the buffer memory from the Ethernet module side, even if [Always wait for OPEN (Communications impossible at STOP time)] is selected at [Operational settings], it is required to use the sequence program to process all that follows the processing for the applicable connection.

If "Do not wait for OPEN (Communication impossible at STOP time)" is selected, open processing and close processing need to be done in the same manner as a connection.

(2) When "Do not wait for OPEN" is selected in the operational settings (Communications impossible at STOP time)

In this case, the open processing and close processing in the sequence program shown in the next page are required. Data transmission and reception are enabled after the open processing is normally completed.

Perform the open processing and close processing by writing "0001H" in BFM#1602 to 1605.

5 COMMUNICATION PROCEDURE

MELSEC-F

5.7 Pairing Open

The following explains communication using the paring open method via the Ethernet module.

5.7.1 Pairing open

Pairing open is an opening method for establishing a connection in which the local station and the external device use a single port for each, by pairing the receiving and sending connections through fixed buffer communication (both the procedure exists and no procedure are allowed) of the Ethernet module.

By designating the pairing open method, data communication can be performed with two connections by performing open processing for only one port.

The procedure for performing the open/close processing for pairing open is explained below.

[Example]

Ethernet module

(TCP/IP or UDP/IP communication) Send data

Receive data

Connection No. 2 fixed buffer (for sending)

POINT

(1)When setting the pairing open method, the fixed buffer of the applicable connection number (for receiving only) and the fixed buffer of the next consecutive connection number (for sending only) are paired in the order of receiving, then sending.

For the applicable connection (for receiving only), choose connection No. 1.

(2)The range of external devices that can be communicated by the pairing open method are limited to devices on the Ethernet to which the Ethernet module is connected and devices connected with the router relay function (see Section 5.3, "Router Relay Parameter").

(3)By the open/close processing of the applicable connection (for receiving only) for which the pairing open method has been set, the open/close processing of the next connection (for sending only) will automatically be performed.

5 COMMUNICATION PROCEDURE

MELSEC-F

5.7.2 Example of pairing open settings

This section explains the settings in order to communicate in the pairing open method by giving an example.

???Connection No. 1 and 2 are used.

(When connection No. 1 is specified at pairing open settings, connection No. 2 is automatically used as pairing.

Therefore, connection No. 2 cannot be specified as pairing.)

[BFM#32 Connection usage setting area]

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

(1) Fixed buffer

(2) Existence confirmation

(3) Pairing open

(4) Protocol

(5) Fixed buffer communication

(6) Open system

(1) Fixed buffer (BFM#32 b0)

In the open pairing, the applicable connection No. and the subsequent connection No. are paired. Set the applicable connection No. to "Receive" and the next connection number to "Send".

(2) Existence confirmation (BFM#32 b1)

If existence confirmation is going to be executed, set the receiving connection to "Confirm".

If existence confirmation is not going to be executed, select "No confirm".

(3) Pairing open (BFM#32 b7)

Set connection No. 1 as the receiving connection by selecting "Pairs", and set connection No. 2 as the sending connection by selecting "No pairs".

(4) Protocol (BFM#32 b8)

Both "TCP/IP" and "UDP/IP" are allowed.

(5) Fixed buffer communication (BFM#32 b9, b10)

Both "Procedure exist" and "No procedure" can be selected.

(6) Open system (BFM#32 b14, b15)

All the open systems - "Active", "Unpassive", and "Fullpassive" - can be set.

5 COMMUNICATION PROCEDURE

MELSEC-F

(7) Local station Port No. (BFM#40, 47)

Set this for the receiving connection for receiving only. (Setting is not required for the sending connection.)

Set the port number upon consulting a network administrator.

(8)Destination IP address (BFM#41 to 42, 48 to 49)

(a)If the setting is not required

???Open system: At [Unpassive] setting

(b)If the setting is required

Set for the receiving connection only upon consulting a network administrator.

???Open system: At [Active] and [Fullpassive] setting

???Protocol: At [UDP/IP] setting

(9)Destination Port No. (BFM#43, 50)

(a)If the setting is not required

???Open system: At [Unpassive] setting

(b)If the setting is required

Set for the receiving connection only upon consulting a network administrator.

???Open system: At [Active] and [Fullpassive] setting

???Protocol: At [UDP/IP] setting

NOTE

When making settings in the FX Configurator-EN-L, select [Open Settings] from the initial screen and at the [Ethernet Open Settings] screen, set "Pairing Open" to "Yes".

5 COMMUNICATION PROCEDURE

MELSEC-F

5.8 Hub Connection Status Monitor Function

The current connection status of the Ethernet module and hub, the transmission speed, and the number of times the Ethernet module detected disconnection can be checked at the following buffer memory addresses.

10BASE-T/100BASE-TX, Full duplex/half duplex

(1) Hub connection status area (BFM#201)

Stores the current connection status of the FX3U-ENET-L and hub and the transmission speed.

(Bits other than above are reserved for system use.) *1 When a switching hub is used, it may not be displayed correctly.

(2)Disconnection detection count storage area (BFM#20995)

(a)Stores the number of disconnection detection times after initial processing is completed.

Disconnection is detected in any of the following cases.

???Disconnection between Ethernet module and hub

???Cable removal from hub side connector

???Hub power-off

???Cable removal from Ethernet module side connector

(b)If an error has occurred 65536 times or more, a count stops at FFFFH (65535).

Write "0" to this area using a sequence program to clear the stored value.

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

This chapter explains how the PLC and external device communicate in a 1:1 mode using the fixed buffers (with the procedure exist control method) of the Ethernet module.

6.1 Control Method

The following explains how communication is performed using the fixed buffers and the procedure exist control method.

In communication using the fixed buffers, data transmission from the PLC and the external device is executed through handshaking.

(1) The data flow during communication is as follows.

FX3U main unit

(For sending)

TO instruction (Transmission request)

FROM instruction (Transmission complete)

(For receiving)

FROM instruction (Reading the data received)

Fixed buffer

No.1

As shown in the diagram below, when using each fixed buffer (No. 1, No. 2), the destination devices and usage conditions (for sending/receiving, procedure exist/ no procedure, etc.) should be set when the connection via the Ethernet module is opened to fix the external device for each buffer.

(a)At TCP/IP communication

It is allowed to change external devices only when the open completion signal of the applicable connection is off.

(b)At UDP/IP communication

External devices can be changed regardless of the status of the applicable connection.

("Destination IP address" and "Destination Port No." in the communication address setting area can be changed. However, the "Local station Port No." cannot be changed.)

When changing external devices, do not use the "Pairing open" and "Existence confirmation" functions.

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

POINT

In communication where the procedure exist control method is selected, the data can be communicated by the following methods after the open processing is completed.

???Fixed buffer communication with the procedure exist control method (sending or receiving)

(3)At data sending/receiving, the Ethernet module processes the following.

(a)When sending data

In response to the fixed buffer communication transmission request (write "0001H" to BFM #1610, #1611), the Ethernet module sends the data of the fixed buffer stored in the fixed buffer area (BFM #1664 to 3711) to the the specified external device (BFM #40 to 53). (*1)

(b)When receiving data

The Ethernet module processes the received data if the data is received from an external device set in the communication setting area that corresponds to fixed buffer No. n. (*1)

If data is received from an external device not set in the connection information area of the buffer memory, the Ethernet module ignores the received data to the PLC side.

6*1 In case of TCP/IP Unpassive open, data is communicated with an external device stored in the connection information area corresponding to fixed buffer No. n.

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

6)7)

1)Confirm the normal completion of the initial processing.

2)Confirm that the link status is normal between the Ethernet module and the connected HUB.

3)Confirm the normal completion of the open processing of connection No. 1

4)Write the send data word count and the send data in the fixed buffer data area (communication address setting area: BFM#1664 to 2687) by TO instruction.

5)Write "0001H" in the fixed buffer communication transmission request (BFM#1610).

6)The size of send data in the fixed buffer (No. 1) area designated by the send data length is sent to the designated external device (set in the open processing).

The value in BFM#1610 becomes "0002H".

7)Upon receiving the data from the Ethernet module, the external device returns a "Response" to the Ethernet module.

8)Upon receiving the "Response" from the external device, the Ethernet module ends the data transmission.

If the "Response" is not returned within the response monitoring time values (see Section 5.2), a data send error occurs.

At normal completion

At abnormal completion

Fixed buffer transmission result (BFM#1610) : 0008H

If the data transmission is abnormally completed, execute the send process again writing "0001H" in BFM#1610.

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

6.3 Receiving Control Method

This section explains the control method when the Ethernet module receives data from an external device.

6.3.1 Receive processing with the main program

This section explains the receiving process to be performed with the main program, using an example in which the fixed buffer No. 2 and the area corresponding to connection No. 2.

???Program example for the unit No. 0

*<<Storing the data received from the external device to the fixed buffer No.2 in D1000 and later>>

User applications are described at the area enclosed with .

Data receiving

ACK

(only TCP)

Response

ACK

(only TCP)

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

1)Confirm the normal completion of the open processing of connection No. 2.

2)Upon receiving data from the designated external device (set in the open processing), the Ethernet module processes the following.

??? Stores the received data to the fixed buffer (No. 2) area.

3)Execute the FROM instruction to read the received word length and received data to the PLC.

4)Execute the TO instruction to write "0002H" in the fixed buffer communication receive result (BFM#1611).

5)Return "Response" to communication destination.

6)The receive processing is performed.

POINT

(1)The destination setting (see Section 5.5) for a connection whose parameters are set with FX Configurator-EN-L becomes valid when the open completion signal (BFM#20480 corresponding bit) of the Ethernet module switches from off to on.

(2)Execute data receiving process when the corresponding connection's bit in the fixed buffer receive status signal storage area (BFM#20485) of the buffer memory switches from off to on or when the value "0001H" is stored in the fixed buffer communication receive results (BFM#1610, 1611).

(3)At abnormal data receiving, each buffer memory status is shown in the following.

(For connection No. 2)

???The fixed buffer receive completion signal (BFM#20485 b1) remains off.

???The fixed buffer communication receive result (BFM#1611) remains "0008H".

???Data is not stored in the fixed buffer (No.2) area.

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

6.5 Programming

This section explains the programming method when the Ethernet module communicates with an external device using fixed buffers and the procedure exist control method.

6.5.1Precautions when creating programs

(1)In order to communicate using the fixed buffer, the initial processing and the connection open processing must be completed.

(2)The contents of the parameter settings have been loaded into the Ethernet module when the Ethernet module open completion signal (BFM#20480 corresponding bit) switches from off to on.

(3)The data length (word count) is established using the instruction for procedure exist communication control method.

If the send data length exceeds this range at data sending, a communication error occurs and the data is not sent.

(4)Reading or writing to the buffer memory using fixed buffer communication.

???Data sending

Write the send data in the buffer memory (BFM#1664 to #3711). Write "0001H" in BFM#1610, #1611 to send the data.

???Data receiving

Check the data received (BFM#1610, #1611: "0001Hs") and read the received data to the PLC (BFM#1664 to #3711).

After reading out, write "0002H" in BFM#1610, #1611 to send the response.

(5)The following should be observed when using a connection opened by UDP. External devices can be switched by modifying the setting values in the communication address setting area of the communication parameter setting area before sending/receiving data. Thus, data can be sent to multiple external devices sequentially. When sending/receiving, make sure to switch between external devices properly so that no communication problems occur.

(6)For data (command) transmission, the next data (command) should be after the data commnication is complete (such as after receiving a response) for the transmission of the previous data (command).

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

6.5.2 Fixed buffer communication program example (with the procedure exist control method)

This section explains the programming method in order to communicate data (procedure exist control method) with an external device using the fixed buffers.

(1)Execution environment for the program example

(a)Send program (FX3U-1st station)

1)Connection No. 1 is used for fixed buffer sending.

2)The unit number specified in the sequence program and FX Configurator-EN-L is 0.

3)The communication parameter settings are assumed to have been set as described in Subsection 5.6.1, "Active open processing/close processing".

(see the table below)

4)Fixed buffer No. 1 send data

:Stored in D1000 to D1031

5)Fixed buffer No. 1 send instruction complete device

:M201

6)Fixed buffer No. 1 send instruction abnormal complete device

:M202

7)Fixed buffer No. 1 send instruction complete status

:D101

[Operational settings]

[Open settings]

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

(b)Receive program (FX3U-2nd station)

1)Connection No. 1 is used to process the fixed buffer receiving in the main program.

2)The unit number specified at the sequence program and FX Configurator-EN-L is 0.

3)Make Operational Settings in the following manner.

Connection No.1 Local station Port No.

: 8192 (BFM#40) (For use in main program)

5)Fixed buffer No. 1 receive data : Stored in D1000 to D1031

6)Fixed buffer No. 1 receive status : D100

[Operational settings]

[Open settings]

POINT

Make sure to have sufficient device memory according to the maximum data length sent in order to prevent device areas used for other purposes from being overwritten by the received data.

6FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST

CONTROL METHOD)

MELSEC-F

(2)Outline of the program example

(a)Send program (Ethernet module-1st station)

1)After setting each parameter with FX Configurator-EN-L or a sequence program and writing to the Ethernet module, select re-initial, power ON the module again, or confirm that the initial processing is completed via buffer memory operations.

2)Perform open processing (Active open) of connection No. 1. (*1)

3)Communicate with the PLC using fixed buffer communication (procedure exist sending).

4)After sending is complete, perform close processing of connection No. 1. (*1)

*1 Use the program example described in Subsection 5.6.1, "Active open processing/close processing" for the sequence program that executes the open processing/close processing.

(b)Receive program (Ethernet module -2nd station)

completed via buffer memory operations.

If the initial processing is normally completed, connection No. 1 wait for an Active open request from the external device.

2)Transfer data from the external device using fixed buffer communication (procedure exist sending).

3)The data received by the corresponding fixed buffer data area in the Ethernet module is read to the PLC.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

This chapter explains how the PLC and external device communicate using the fixed buffers (with the no procedure control method) via the Ethernet module.

POINT

The following points describe the difference from the "Procedure exist" using fixed buffer communication:

1)It is possible to send and receive data which match the message format of the external device.

At data sending, subheader, data length, etc. are not included in the application data field of a message; only the data in the fixed buffer is sent. Upon data reception, all the data in the message excluding the header is stored in the fixed buffer.

2)A response to data receiving is not sent.

3)Communication is performed using binary code regardless of the communication data code settings (see Section 4.6, "Operational Settings").

4)The maximum application data area is 2046 bytes per communication.

5)The applicable connection is dedicated to the no procedure fixed buffer communication.

As with the procedure fixed buffer communication, and communication using MC protocol cannot be performed at the same time as the no procedure fixed buffer communication.

7.1 Control Method

The following explains how communication is performed using the fixed buffers and the no procedure control method.

In communication using the fixed buffers, data transmission from the PLC and the external device is executed using the no procedure control method.

(1) The data flow during communication is as follows.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

(2)Data can be communicated with the following external devices.

???Device on the Ethernet to which the Ethernet module is connected.

???Devices connected with the router relay function (see Section 5.3)

(a)At TCP/IP communication

It is allowed to change external devices only when the open completion signal of the applicable connection is off.

(b)At UDP/IP communication

External devices can be changed regardless of the status of the applicable connection.

("Destination IP address" and "Destination Port No." in the communication address setting area can be changed. However, "Local station Port No." cannot be changed.)

When changing external devices, do not use the "Pairing open" and "Existence confirmation" functions.

POINT

The connections for which no procedure is selected are dedicated to the fixed buffer sending or receiving after the completion of open processing.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

(3)At data sending/receiving, the Ethernet module processes the following.

1)When sending data

The fixed buffer communication transmission request (writing "0001H " in BFM#1610, #1611) allows the fixed buffer data stored in the fixed buffer data area (BFM#1664 to #3711) to be sent to the specified external device (BFM#40 to #53). (*1)

2)When receiving data

The Ethernet module processes the received data if it is received from an external device set in the communication setting area that corresponds to fixed buffer No. n. (*1)

Also, when the Ethernet module stores the received data in the corresponding fixed buffer in the receive processing, it updates the destination IP address and destination port No. in the corresponding fixed buffer connection information area (BFM#120 to #139)

If data is received from an external device not set in the connection information area of the buffer memory, the Ethernet module ignores the received data.

*1 In case of TCP/IP Unpassive open, data is communicated with an external device stored in the connection information area of the buffer memory.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

BFM#1610

Data receiving

ACK

(only TCP)

1)Confirm normal completion of the initial processing.

2)Confirm that the Ethernet module is connected to the hub. (BFM#28 b7:ON)

3)Confirm the normal completion of the open processing for connection No. 1.

4)Write the byte count for send data and the send data to the fixed buffer data area (BFM#1664 to #2687) by TO instruction.

5)Write "0001H" in the fixed buffer transmission request (BFM#1610).

6)Only the size of the send data in the fixed buffer (No. 1) designated by the send data length is sent to the designated external device.

The value of BFM#1610 becomes "0002H ".

7)The Ethernet module terminates the data transmission.

If the data transmission is abnormally completed, rewrite "0001H" in BFM#1610 and execute the send processing again.

POINT

The following precaution should be observed when communicating using UDP/IP:

???When the Ethernet module's internal processing is normally completed, data send processing ends even if the communication line between the PLC and an external device is disconnected because of cable disconnection, etc. It is recommended to send/receive data using a user defined communication procedure.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

1)Upon receiving data from the designated external device (set in the open processing), the Ethernet module processes the following.

???Stores the received data to the fixed buffer (No. 2) area.

(Area beginning from the head address of the target fixed buffer + 1)

???Stores the data length to the head address area of the target fixed

2)Execute the FROM instruction to read out the receive byte length and receive data to the PLC.

3)Execute the TO instruction to write "0002H" in the fixed buffer communication receive results (BFM#1611).

4)Result of the receiving processing is indicated.

POINT

(1)The destination setting (see Section 5.5) for a connection whose parameters are set in FX Configurator-EN-L becomes valid when the open completion signal (BFM#20480 corresponding bit) of the Ethernet module switches from off to on.

(2)When data is received and the data in the buffer memory's fixed buffer is set, BFM #1610, #1611 is set to "0001H".

(3)At abnormal data receiving, each buffer memory status becomes as follows.

???Fixed buffer receive completion signal (BFM#20485 b1) remains off.

???Fixed buffer communication receive results (BFM#1611): 0008H

???Data is not stored in the fixed buffer (No.2) area.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

7.4 Data Format

When communicating between the Ethernet module and an external device, the data format explained below is used.

The communication data consists of a "header" and "application data" as shown below.

(1) Header

The header for TCP/IP or UDP/IP is used. In case of the Ethernet module, the Ethernet module adds and deletes the header. Thus, the user does not need to set it.

(Details of the size of the header section)

1) In case of TCP/IP

2) In case of UDP/IP

(2) Application Data

The data code in the application data is expressed in binary code. Communication is performed using binary code, regardless of the set communication data (see Section 4.6).

Text (command)

Maximum of 2046 bytes

NOTE

The subheader and data length that are added for communications using the fixed buffers in the procedure exist control method are not present for communications in the no procedure control method. All data is treated as valid text.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

7.5 Programming

This section explains the programming method when the Ethernet module communicates with an external device using fixed buffers and the no-procedure control method.

7.5.1Precautions when creating programs

(1)In order to communicate using the fixed buffers, the initial processing and the connection open processing must be completed.

(2)The contents of the parameter settings have been loaded into the Ethernet module when the Ethernet module open completion signal (BFM#20480 corresponding bit) switches from off to on.

(3)The data length (byte count) is established using the instruction for no procedure communication.

If the send data length exceeds this range at data sending, a communication error occurs and the data is not be sent.

(4)Reading or writing to the buffer memory using fixed buffer communication.

???When sending data

Write the send data to the buffer memory (BFM#1664 to #3711). Write "0001H" in BFM#1610, #1611 before sending the data.

???When receiving data

Check that data has been received (BFM#1610, #1611: "0001H") and read out the received data (BFM#1664 to #3711) to the PLC.

(5)The following should be observed when using a connection opened by UDP.

???External devices can be switched by modifying the setting values in the communication address setting area of the communication parameter setting area before sending/receiving data. Thus, data can be sent to multiple external devices sequentially. When sending/receiving, make sure to switch between external devices properly so that no communication problems occur.

(6)Message data length is not included in a packet when communicating with the no procedure.

The Ethernet module stores the size of the received message (packet) in the receive data length storage area and turns on the fixed buffer receiving status signal (BFM#20485 corresponding bit).

It is recommended to employ a check system, such as including the data length and data type code in the application data of a message, so that the byte count and data type in the application data can be identified by the receiving side.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

7.5.2 Fixed buffer communication program example (with the no procedure control method)

This section explains the programming method in order to communication data (through the no procedure control method) with an external device using the fixed buffers.

(1)Execution environment for the program example

(a)Send program (FX3U-1st station)

1)Connection No. 1 is used for fixed buffer sending.

2)The communication parameters settings are assumed to have been set as described in Subsection 5.6.1, "Active open processing/close processing" except the "Fixed buffer communication" parameter.

(see the table below)

3)Fixed buffer No. 1 send data

:Stored in D1000 to D1031

4)Fixed buffer No. 1 send Send instruction complete device

:M201

5)Fixed buffer No. 1 send Send instruction abnormal complete device

:M202

6)Fixed buffer No. 1 send Send instruction complete status

:D101

[Operational settings]

[Open settings]

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

(b)Receive program (FX3U -2nd station)

1)Connection No. 2 is used to process the fixed buffer receiving.

2)The unit number specified at the sequence program and FX Configurator-EN-L is 0.

3)Make Operation settings in the following manner.

Communication data code : Binary code

5)Fixed buffer No.1 receive data.

:Stored in D1000 to D1031

6)Fixed buffer No.1 receive instruction complete status.

:D100

[Operational settings]

[Open setting]

POINT

Make sure to have sufficient device memory according to the maximum data length sent in order to prevent device areas used for other purposes from being overwritten by the received data.

7FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE

CONTROL METHOD)

MELSEC-F

(2)Outline of the program example

(a)Send program (FX3U-1st station)

1)After setting each parameter with FX Configurator-EN-L or a sequence program and writing to the Ethernet module, power ON the module again, or confirm that the initial processing is completed via buffer memory operations.

2)Perform open processing (Active open) for connection No. 1. (*1)

3)Communicate data from the PLC using fixed buffer communication (no procedure sending).

4)After data sending is complete, perform close processing for connection No. 1. (*1)

*1 Use the program example described in Subsection 5.6.1, "Active open processing/close processing" for the sequence program that executes the open processing/close processing.

Make sure to change the "Fixed buffer communication" setting from "Procedure exist" to "No procedure".

(b)Receive program (FX3U-2nd station)

1)After setting each parameter with FX Configurator-EN-L or a sequence program and writing to the Ethernet module select re-initial and power ON the module again, or confirm that the initial processing is completed via buffer memory operations.

If the initial processing is normally completed, connection No. 2 waits for an Active open request from the external device.

2)Transfer data from the external device using fixed buffer communication (no procedure sending).

3)The data received by the corresponding fixed buffer data area in the Ethernet module is read to the PLC.

8 COMMUNICATION USING MC PROTOCOL

MELSEC-F

8 COMMUNICATION USING MC PROTOCOL

This chapter gives an overview of the MC protocol.

NOTE

The frame type of MC protocol (data communication messages) used by the external device to access the PLC via this product is equivalent to A compatible 1E frame.

(Example)

Header

Subheader

00H

Text (Command)

(Command message for the A compatible 1E frame)

8.1 Data Communication Function

The MC protocol is the abbreviated name of the MELSEC protocol that is a communication system for the PLCs. Using this protocol, the external devices can read or write device data from/to the PLC via the Ethernet module.

Any external devices on which application programs can be installed and which can send and receive data in accordance with the MELSEC PLC protocol can access the PLC using MC Protocol.

8.1.1 Accessing the PLC using MC protocol

This section explains the main functions for accessing the PLC using MC protocol. On the PLC side, the Ethernet module sends and receives data based on the instructions (protocol) from the external devices, so the PLC side does not require sequence programs for data communication.

(1) Data read/write

This function reads/writes data from/to the PLC device memory to which the Ethernet module is connected.

By reading and writing data, the PLC operation monitoring, dzata analysis and production management can be performed on the external device side.

8 COMMUNICATION USING MC PROTOCOL

*1 Time required for communication in binary code is shorter because the amount of communication data is approximately a half of what is required for communication in ASCII code data.

8.1.2 How to Read the Control Procedures of the MC Protocol

This section explains the control procedures when an external device accesses the

PLC using MC protocol.

(1) Transmission of command messages

Data communication through the MC protocol is performed using half-duplex communication.

When accessing the PLC, send the next command message after receiving a response message from the PLC side for the previous command message transmission.

(2)When a normal completion response message to a command message cannot be received

81) If an abnormal completion response message is received

Handle the case according to the error code in the response message.

2)If the response message cannot be received or nothing can be received Send the command message again after the monitoring time of the response monitor timer.

*Modify the value of the monitoring time as needed.

8 COMMUNICATION USING MC PROTOCOL

MELSEC-F

8.1.3 Access Timing on the PLC Side

The following diagram illustrates the access timing on the PLC side when an external device accesses the PLC via the Ethernet module.

Ethernet module

2)3)

1)A command message is transmitted from the external device to the PLC side.

2)Upon receiving a command message from the external device, the Ethernet module on the PLC side sends a data read/write request to the PLC according to the content of the command.

3)The PLC reads/writes data according to the request from the external device at the time of executing the sequence program's END instruction, and passes the processing result to the Ethernet module.

4)Upon receiving the processing result from the PLC, the Ethernet module sends a response message including the processing result to the external device that originated the request.

*1 The ACK response shown in the diagram is sent/received between the Ethernet module and the external device respectively when the access via the Ethernet module is performed by TCP/IP communication.

It is different from the response to the processing requested by the external device in the command message (the processing result). When access via the Ethernet module is performed by UDP/IP, the ACK response indicated by *1 is not sent.

NOTE

Regarding the scan time of the PLC

1)While the PLC is performed by required command, access command to the Ethernet module and the PLC is processed during every END processing. (The scan time becomes longer according to the amount of time it takes to process the command.)

2)When multiple external devices issue access requests to the Ethernet module at the same time, the processing requested from the external devices may have to wait for multiple END processing executions depending on the timing of the requests.

8 COMMUNICATION USING MC PROTOCOL

MELSEC-F

8.1.4 PLC setting for performing data communication

Data communication via MC protocol is enabled by adjusting the following settings using FX Configurator-EN-L and writing the parameters to the Ethernet module.

1)Operational settings (see Section 4.6.)

2)Initial settings (see Section 5.2)

3)Open settings (see Subsection 5.5.2)

8.1.5Precautions on Data Communication

This section explains some precautions that should be observed when performing data communication between an external device and the Ethernet module.

(1)Precautions that should be observed when performing data communication via the Ethernet module

(a)Perform read/write only when the buffer memory status of Ethernet module is the following.

If the initial normal completion signal (BFM# 27 [0001H]) and the open completion signal (BFM#20480 corresponding bit) of the used connection is ON (open completion status), it is possible to communicate from an external device using MC protocol without regard to the existence of a sequence program. (Only connections No. 3 and 4 are available in communication using MC protocol.)

(b)Use the UDP connection set to "Always wit for OPEN (BFM #24 b8: ON)" in the initial timing setting in the operation settings. Or use the passive open connection in the case of TCP.

(c)Communication using MC protocol is enabled only when the communication parameter for an open connection is set to "MC protocol usable" in "Connection usage" as described in the table in Subsection 5.5.2.

To set this using FX Configurator-EN-L, select the open settings from the initial screen, and when a protocol is TCP, select [Unpassive(MC)] or [Fullpassive(MC)] in [Open system].

(d)Replacing the Ethernet module

The Ethernet address (MAC address) differs depending on the device. When the Ethernet module is replaced due to breakdown, reboot any external devices also.

Similarly, reboot the Ethernet module even when an external device is replaced (such as a personal computer).

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

This chapter explains the message format, how to designate data items in a message and restrictions for data communication with an Ethernet module using MC protocol with A compatible 1E frames.

9.1 Message Formats and Control Procedures

This section explains the message format and control procedure for each command when data communication is performed using A compatible 1E frames.

The MC protocol for the Ethernet module is a subset of A compatible 1E frames. Both TCP/IP and UDP can be used as lower layer protocol and support both ASCII code and binary code.

9.1.1 How to read the command reference section

The following explains how to read the message explanation diagrams shown in each of the command description Sections 9.3 through 9.5.

(1) When an external device reads data from the PLC

External device side

PLC side

(Command message)

Complete code

Subheader

Header

Area B

(Response message)

1)Area A indicates transmission from the external device to the PLC.

2)Area B indicates transmission from the PLC to the external device.

3)The program of the external device is generated so that the data is transmitted sequentially from left to right. (For example: in case of area A, data should be sequentially sent from Header to the right.)

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.1.2 Message format and control procedure

This section explains the message format and control procedure.

(1) Message format

This section explains the message format for transmission between the Ethernet module and an external device.

The communication data consists of "header" and "application data" as shown below.

(a)Header

The header for TCP/IP or UDP/IP is used. The user does not need to specify it; the Ethernet module attaches it.

(b)Application data

The application data is largely divided into "subheader" and "text" as shown below.

The subheader represents command/response and the setting value is predetermined.

The text contains the request data (command) and response data (response) for each function and this data is determined by the prescribed format (for a more detailed description, see sections 9.3 and later).

(c)Format in the application data field

??? Communication in ASCII code

Application data

NOTE

When communicating in the MC protocol, the user does not need to specify a response for a command from an external device; the Ethernet module generates it and then responds.

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

(2) Control procedure

The following diagrams illustrate the control procedure for communicating with the MC protocol and the order of data items in the application data field.

The header section shown in the message explanation diagram of this section corresponds to the portion of the message explanation diagrams indicated in Subsection 9.3.2 and later.

See Subsection 9.1.3 regarding the content of data items in the message format and data specification method.

(a)Communication in ASCII code

1)When reading data from the local station PLC at the external device side

External device side PLC side (Command message)

The contents and arrangement of the data items in the text differs according to the function to use. See the sections explaining functions found in Subsection 9.3.2 and after for details

PLC side External device side (Response message)

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

2) When writing data to the local station PLC from the external device side

External device side PLC side (Command message)

The contents and arrangement of the data items in the text differs according to the function to use. See the sections explaining functions found in Subsection 9.3.2 and after for details

PLC side External device side (Response message)

(Normal completion)

(Abnormal completion)

38H 32H 35H 42H 31H 32H 30H 30H

Exists only when the complete code is "5B."

(b)Communication in binary code

1)When reading data from the local station PLC at the external device side

Text (Command)

Character area A

The contents and arrangement of the data items in the text differs according to the function to use. See the sections explaining functions found in Subsection 9.3.2 and after for details

PLC side External device side (Response message)

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.1.3 Contents of data designation items

This section explains the data items of commands and responses when communicating using MC protocol.

In the response that is returned by the Ethernet module to an external device, the data is automatically specified by the Ethernet module; the user does not need to specify it.

(1) Header

The header for TCP/IP or UDP/IP is used. The user does not need to specify it at the PLC side; the Ethernet module attaches it.

(2) Subheader

The format of the subheader is configured as follows.

Command/response type

(This differs for each function. For details, see Section 9.2 and later.)

Command/response flag For command: 0

For response: 1

(3) PC number

The PC number is fixed at a value of "FFH".

(a)When communicating in binary code, the PC number is expressed in binary value.

(b)When communicating in ASCII code, the PC number is expressed in hexadecimal ASCII code.

(4)Monitoring timer

This is a timer for setting the period of time that the Ethernet module should wait after outputting a read/write request to the PLC until the result is returned.

(a) Specify the value as shown below.

*1 It keeps waiting until a response is returned from the PLC.

(b)For normal data communications, using a value within the setting range of 1 to 40 (0.25 to 10s) is recommended.

(5)Character field (command)

This data contains the Ethernet module commands that indicate functions for when an external device reads/writes data from/to the target PLC station. The contents and order of data in the Character field (command) field differ depending on the function used.

The order of data items for each function is explained in each function's reference section in Subsection 9.3.2. and later.

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

(6) Character field (response)

This data contains data read/processing result when an external device reads/ writes data from/to the target PLC station.

The contents and order of data in the Character field (response) differ depending on the function used.

The order or data items at normal completion for each function is explained in each function's reference section in Subsection 9.3.2. and later.

(7) Complete code

The result of processing when an external device reads/writes data from/to the target PLC station is indicated by the following values.

(a)When communicating in binary code, the complete code is expressed in binary values.

(b)When communicating in ASCII code, the complete code is expressed in hexadecimal ASCII code.

(c)When the complete code indicates abnormal completion, check the content and take an action according to the troubleshooting section of Chapter 11. When the complete code is 5BH/"5B," the abnormal code data (10 to 18H) and 00H/"00" are included immediately after.

(8)Abnormal code

This value indicates the nature of the error when the processing result of reading/ writing data from/to the target PLC station by an external device is faulty and the complete code is 5BH/"5B." (Abnormal code: 10 to 18H)

(a)When communicating in binary code, the abnormal code is expressed in binary values.

(b)When communicating in ASCII code, the abnormal code is expressed in hexadecimal ASCII code.

(c)Check the content and take an action according to the troubleshooting section of Chapter 11.

POINT

The data code (ASCII/binary) when sending/receiving commands and responses between the Ethernet module and an external device is determined in the operation settings in FX Configurator-EN-L.

The external device communicating with Ethernet module should send the values specified in each data item in the commands and responses in the above setting using the code shown below. Also, it should receive the corresponding values in the code shown below.

In the explanation hereafter in this section, the values specified in each item in a command and response are shown in binary values.

(1)Communication in binary code

Unless specifically stated, the value shown in each explanation is sent/ received in the designated order (L to H) since it is in binary.

(2)Communication in ASCII code

Unless specifically stated, the value shown in each explanation is converted to hexadecimal ASCII code and sent/received in the designated order (H to L).

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.1.4 Character area transmission data

This section explains how to transmit the bit device data and word device data handled in the character areas, as well as the order of transmission when communicating data between an external device and the PLC by each command. The transmission data shown in the examples is contained in character area B when reading, and in character area C when writing, testing.

(1)Data communication using ASCII code

(a)When reading to or writing from a bit device memory

The bit device memory can be read and written in bit units (one device point) or word units (16 device points).

How data is transmitted in each case is explained below.

1)Bit units (one point)

In case of bit units, the bit device memory is handled from the designated head device for the number of designated device points sequentially from the left. They are expressed as "1" (31H) if the device is on or "0" (30H) if the device is off.

(Example)

Indicating the ON/OFF status of five points from M10

34H 44H 32H 30H 30H 30H 30H 30H 30H 30H 30H 41H 30H 35H 31H 30H 31H 30H 31H

Indicates that M14 is ON

Indicates that M13 is OFF

Indicates that M12 is ON

Indicates that M11 is OFF

Indicates that M10 is ON

2)Word units (16 points)

When the bit device memory is handled as word units, each word is expressed in hexadecimal values in 4-bit units sequentially from the higher bit.

(Example)

Indicating the ON/OFF status of 32 points from M16

The device point is "02" in 16-point units.

34H 44H 32H 30H 30H 30H 30H 30H 30H 30H 31H 30H 30H 32H 41H 42H 31H 32H 33H 34H 43H 44H

M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

(b)When reading from or writing to a word device memory

Each word of the word device memory is expressed in hexadecimal values in 4-bit units sequentially from the higher bit.

(Example)

Indicating the storage contents of data registers D350 and D351

34H 34H 32H 30H 30H 30H 30H 30H 30H 31H 35H 35H 30H 32H 35H 36H 41H 42H 31H 37H 30H 46H

B15B14B13B12 B11B10B9 B8 B7 B6 B5 B4 B3 B2 B1 B0 B15B14B13B12 B11B10B9 B8 B7 B6 B5 B4 B3 B2 B1 B0

1: Indicates ON

0 1 0 1 0 1 1 0 1 0 1 0 1 0 1 1 0 0 0 1 0 1 1 1 0 0 0 0 1 1 1 1

POINT

0: Indicates OFF

(1)When designating alphabet letters in the character area, use upper case code.

(2)When data other than an integer value (real number, character string, etc.) was stored in a word device memory to be read, the stored value is read as an integer value.

(Example 1)

When the real number (0.75) is stored in D0 and D1, it is read as the following integer values:

D0 = 0000H, D1 = 3F40H (Example 2)

When the character string ("12AB") is stored in D2 and D3, it is read as the following integer values:

D2 = 3231H, D3 = 4241H

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

(2)Data communication using binary code

(a)When reading to or writing from the bit device memory

The bit device memory can be read and written in bit units (one device point) or word units (16 device points).

How data is transmitted in each case is explained below.

1)Bit units (one point)

In case of bit units, four bits designate one point and the bit device memory is handled from the designated head device for the number of designated device points sequentially from the left. They are expressed as "1" if the device is ON or "0" if the device is OFF.

(Example)

Indicating the ON/OFF status of five points from M10

0AH 00H 00H 00H 20H 40H 05H 10H 10H 10H

Expressed by dummy when the point is an odd number

Indicates that M14 is ON

Indicates that M13 is OFF

Indicates that M12 is ON

Indicates that M11 is OFF

Indicates that M10 is ON

2)Word units (16 points)

In case of word units, one bit designates one point and the bit device memory is handled from the designated head device for the number of designated device points sequentially from the left. They are expressed in 16-point units in the order, low byte (L: bits 0 to 7) to high byte (H: bits 8 to 15).

(Example)

Indicating the ON/OFF status of 32 points from M16

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

(b)Reading from or writing to a word device memory

Each word of a word device memory is designated by 16 bits and the designated number of points from the designated head device are sequentially expressed in one-point units in the order, low byte (L: bits 0 to 7) to high byte (H: bits 8 to 15).

(Example)

Indicating the storage contents of data registers D350 and D351

(L)

(H)

(L)

POINT

(1)When data other than an integer value (real number, character string, etc.) was stored in a word device memory to be read, the module reads the stored value as an integer value.

(Example 1)

When the real number (0.75) is stored in D0 and D1, it is read as the following integer values:

D0 = 0000H, D1 = 3F40H (Example 2)

When the character string ("12AB") is stored in D2 and D3, it is read as the following integer values:

D2 = 3231H, D3 = 4241H

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.3.2 Batch read in bit units (command: 00)

The examples shown in this section explain the command/response format when batch-reading the bit device memory.

For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, see Subsection 9.1.2.

[Control procedure]

Reading the on/off status of M100 to M111 of the PLC on which the FX3U-ENET-L is loaded.

(1) Communication in binary code

00H FFH 0AH 00H 64H 00H 00H 00H 20H 4DH 0CH 00H

(Data name)

PLC side

(Example)

Subheader

80H

NOTE

Use the designation "00H" when the number of device points is 256 points.

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.3.4 Test in bit units (random write) (command: 04)

The examples shown in this section explain the command/response format when writing data by designating bit device memories arbitrarily.

For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, see Subsection 9.1.2.

[Control procedure]

Specifying Y45 to ON, M60 to OFF, and S38 to ON at the PLC on which the Ethernet module is loaded.

(Data name)

External device side

(Example)

(Data name)

PLC side

(Example)

(1) Communication in binary code

45 (Octadecimal) = 25 (Hexadecimal)

Designates to turn Y45 ON.

Designates to turn M60 OFF.

Designates to turn S38 ON.

84H 00H

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.3.5 Batch read in word units (command: 01)

The examples shown in this section explain the command/response format when batch reading the word device memory and the bit device memory (16 point units). For more details on the order and contents of data items of the areas marked by " " shown in the control procedure diagram, see Subsection 9.1.2.

[Control procedure]

Reading the on/off status of Y100 to Y137 (32 points) of the PLC on which the

Ethernet module is loaded.

(Data name)

External device side

(Example)

(Data name)

PLC side

(Example)

(1) Communication in binary code

1 0 0 1 1 1 0 1 1 0 0 0 0 0 1 0 0 0 1 1 1 1 1 0 0 1 0 1 0 1 0 1

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

NOTE

C200 to C255 (Current Values) Batch Read

Since C200 to C255 are 32 bit devices, the device points should be specified as twice as much as the points actually read.

Also, make sure that the device points are specified by an even number.

If they are specified by an odd number, the batch read cannot be performed. (Error code 57H will be stored)

Example) When 32 devices are read at one access from C220 to C251 in the PLC on which the Ethernet module is mounted.

(1) When communicating in binary code

(Data name)

External device side *

(Example)

(Data name)

PLC side

(Example)

32 points x 2 = 64 word *

4 bytes x 32=128 bytes

12345678=00BC614EH 45678912=02B90140H

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

NOTE

C200 to C255 (Current Values) Batch Write

Since C200 toC255 are 32 bit devices, the device points should be specified twice as much as the points actually read.

Also, make sure that the device points are specified by even number.

If they are specified by odd number, the batch read cannot be performed. (Error code 57H will be stored)

Example) When 32 points are written at one access from C220 to C251 in the PLC on which the Ethernet module is mounted.

(Data name)

External device side *

(Example)

(Data name)

PLC side

(Example)

(1) When communicating in binary code

83H 00H

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.4.2 Remote RUN (command: 13) / Remote STOP(Command: 14)

The examples shown in this section explain the control procedure of remote RUN. The order and content of data items of the areas marked by "" shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.

See the detailed information described in Subsection 9.1.2.

[Control procedure]

(1) Executing remote RUN while communicating in binary code

For remote RUN 13H

For remote STOP 14H

For remote RUN 93H

For remote STOP 94H

(2) Executing remote RUN while communicating in ASCII code

(Data name)

External device side

(Example)

(Data name)

PLC side

(Example)

For remote RUN 3133H (13H)

For remote STOP 3134H (14H)

For remote RUN 3933H (93H) For remote STOP 3934H (94H)

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.4.3 PLC model name read (command: 15)

The examples shown in this section explains the control procedure for reading the model name of the PLC.

The order and content of data items of the areas marked by " " shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.

See the detailed information described in Subsection 9.1.2.

[Control procedure]

(Data name)

External device side

(Example)

(Data name)

PLC side

(Example)

(1) Data communication in binary code

Model name of

FX3U/FX3UC

(2) Data communication in ASCII code

Model name of

FX3U/FX3UC

POINT

Distinguish the PLC model name by the model name code.

"F3H", which is the model code of FX3U/FX3UC, is read as the PLC model name.

9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL

MELSEC-F

9.5 Loopback Test

A loopback test checks whether or not the communication function between an external device and the Ethernet module operates normally. The examples show the control procedure using this function.

POINT

(1)A loopback test checks whether or not the connection between the external device and the Ethernet module is correct and that the data communication function operates properly when the FX3U-ENET-L is started up or when a problem occurs.

(2)Use the following data for loopback tests. Send the head part first.

???When communicating in binary code

Maximum of 254 bytes of numerical values (00 to FFH).

???When communicating in ASCII code

Maximum of 254 single-byte characters ("0" to "9", "A" to "F").

9.5.1Loopback test (command: 16)

The examples shown in this section explain the control procedure for an external device performing a loopback test with the Ethernet unit.

The order and content of data items of the areas marked by "" shown in the control procedure diagram differ depending on the module used as well as the frame and format used for communication.

See the detailed information described in Subsection 9.1.2.

[Control procedure]

(1) Performing a loopback test while communicating in binary code

Designated byte length+5bytes

(Data name)

PLC side

(Example)

96 H 00 H

Designated byte length+3bytes

10 USING THE E-MAIL FUNCTION

MELSEC-F

10 USING THE E-MAIL FUNCTION

This chapter explains e-mail functions of the Ethernet module.

10.1 E-mail Function

The e-mail function sends e-mails to PCs or PLCs at a remote location using the network (via the mail server).

The PLC sends e-mails using sequence programs and buffer memory.

10.1.1E-mail send by the PLC

(1)Sending e-mail by the PLC

When sending an e-mail, the PLC sends the PLC information of a station connected to an Ethernet module as a file attached to the e-mail or in the text of the e-mail to an external device such as a PC.

External device

Portable terminal

Sending e-mail by the PLC(device thatRemark

cannot handle attached files)

*1 It is not possible to send an attached file and main text at the same time.

(a)Sending e-mail from the PLC

Data is transmitted via the main text or attached file of an e-mail.

1)For an attached file, device data and other information is sent by converting into binary/ASCII/CSV data format.

2)For the main text, ASCII code data (character string data) created by a sequence program is sent.

10 USING THE E-MAIL FUNCTION

MELSEC-F

(2)Data conversion method used by the Ethernet module

The following shows the data conversion method used by the Ethernet module.

PLC

Operation for(FROM/TO esending mails-instruction)

(3)Flow of the e-mail

The following diagram illustrates the flow of e-mail sent by the PLC to the external device:

[When sending by the Ethernet module]

1)Send an e-mail to the mail server of the local station's Ethernet module.

2)The mail server of the local station's Ethernet module sends the e-mail to the receive mail server of the send destination device.

[When receiving by a PC]

3) Mails can be received using applications such as e-mail software.

10 USING THE E-MAIL FUNCTION

MELSEC-F

10.2 Configuration and Environment of the Applicable System

This section explains the environment and system configuration for using the e-mail function from the Ethernet module.

Internet (Public line)

Ethernet module

(1)E-mails can be sent in an environment where the Internet service is available as shown above. (Ethernet modules do not send e-mails directly via the internet connection. The mail server sends e-mails.)

(2)Set each Internet mail setting value for the Ethernet module and PC following the directions from the system administrator.

(3)Each of the Ethernet module parameters for using the e-mail function is set with FX Configurator-EN-L or a sequence program.

POINT

The module operation is not guaranteed if any of the following connection is used. Check the module operation on the user side.

???Connections using the Internet (general public line) (Connections using Internet connection service provided by Internet service providers and telecommunications carriers)

???Connections using devices in which a firewall is installed

???Connections using broadband routers

???Connections using wireless LAN

10 USING THE E-MAIL FUNCTION

MELSEC-F

10.3 Precautions for Using the E-mail Function

The following explains precautions when using the e-mail function of the Ethernet module.

(1)Precautions regarding the system

(a)Design the system so that the entire system operates normally at all times when sending e-mails to/from a running system and controlling the PLC.

(2)Precautions regarding the external device

(a)E-mails can be sent to PLC stations in which Q series Ethernet modules are installed.

(b)To send files to the Ethernet module as attachments to e-mail, specify the encoding method (Base 64/7 bits/Quoted Printable) of the attached files.

(3)Common precautions

(a)The maximum sizes of data that can be sent by the Ethernet module are as follows:

???Data size of attached files: Up to 2048 words

???Data size of main text: Up to 256 words (Sending only)

(b)Mail that is sent do not support encrypted data, compressed data, and data conversion.

(c)If the external device cannot be found when sending an e-mail from the Ethernet module, the user can check the error code in the buffer memory. * If an external device cannot be found when sending e-mail using the

operation of buffer memory, failure of e-mail transmission may not be recognized, depending on the operation of the mail server. Be sure to verify the receiver's e-mail address in advance.

* Error codes are stored within BFM#10335. (For details on error codes, refer to section 11.4.)

(d)The e-mail function is supported for SMTP.

(e)When e-mail communication errors occur, check the error codes stored in the mail send error log area of the buffer memory.

(f)When the receive data of an e-mail sent is abnormal (garbled characters, etc.), review the transmission data format (binary/ASCII/CSV) designated with BFM#10338.

* The Subject should be in ASCII code data format. (It is not converted to ASCII format.)

(g)Confirm with a system administrator regarding the minimum time intervals for accessing the mail server when sending e-mail, reading received e-mail, and inquiring whether or not there is any received e-mail.

Depending on the mail server's security setting, frequent access may be prohibited.

10 USING THE E-MAIL FUNCTION

MELSEC-F

10.6 E-mail Settings

This section explains the settings required to send e-mails.

(1)DNS settings

Specify the IP address of the DNS server when setting the mail server name using the domain name from the e-mail settings (see (2)).

(a)DNS settings

Set the IP addresses of the domain name system (DNS) servers designated by a system administrator.

1)Designate the IP addresses of the DNS servers 1 to 4.

POINT

(1)The DNS servers manage networks.

DNS settings are required to allow search for the SMTP server or POP3 server from a domain name.

(2)Adjust the DNS settings when the mail server name shown in item (2) is specified with a domain name.

Setting is not required when it is specified with an IP address.

(3)When obtaining the IP addresses from a domain name, the DNS servers are searched sequentially starting from the first DNS server.

NOTE

To adjust settings using FX Configurator-EN-L, select [Initial Settings] from the initial screen and adjust the settings at the initial settings screen.

10 USING THE E-MAIL FUNCTION

MELSEC-F

(2)E-mail settings

Set in order to use the e-mail function.

[Setting item]

*1 The setting is required only when "POP before SMTP" is selected in the SMTP authentication method.

(a)General settings

Designate the mail setting values that have been registered with the mail registration information designated by the system administrator.

1)Password:

Designate the mail password of the local station's Ethernet module.*1

2)Mail address:

Designate the mail address of the local station's Ethernet module.

(b)Mail server name

Set the IP addresses or domain name of the mail servers designated by the system administrator.

1)Select the input format (decimal/hexadecimal) of the IP addresses.

2)Set the IP address or sending mail server (SMTP) domain name.

3)Set the IP address or receiving mail server (POP3) domain name.*1

4)Set port numbers of the outgoing mail server (SMTP).

5)Set port numbers of the incoming mail server (POP3).*1

*1 The setting is required only when "POP before SMTP" is selected in the SMTP authentication methed.

10 USING THE E-MAIL FUNCTION

MELSEC-F

POINT

???The mail server must be designated in order to use the e-mail function. (See POINT of (1).)

(c)SMTP authentication setting

1)Set the authentication method for the outgoing mail server (SMTP).

The steps 2) and 3) below are required when "SMTP-AUTH" is selected in the SMTP authentication method.

2)Set the login ID of the outgoing mail server (SMTP).

3)Set the password of the outgoing mail server (SMTP).

NOTE

To adjust the settings in FX Configurator-EN-L, select [Email Settings] from the initial screen and adjust the settings from the email settings screen.

(3) Send mail address setting

[Setting item]

(a)Send mail address

1)Designate the mail addresses of a maximum of 10 external devices to which mail is being sent from the local station's Ethernet module. (Only one e-mail address can be specified for each area.)

2)When sending e-mail by the Ethernet module, specify the send e-mail address by the bit 0 to 9 of BFM#10337.

NOTE

To adjust the settings in FX Configurator-EN-L, select [Email Settings] from the initial screen and adjust the settings from the email settings screen.

10 USING THE E-MAIL FUNCTION

MELSEC-F

10.7 Sending E-mail (Attached Files) by the PLC

This section explains how to send attached files when sending e-mails.

10.7.1When sending data as an attached file

The following explains the buffer memory addresses and program for sending e-mail. The following instruction shows how to store data in an attached file and send it to an external device.

1)Check whether mail can be sent or not. (BFM#10334 b15: OFF)

2)Designate the destination of the mail.

Turn the bit corresponding to the e-mail destination address to ON in BFM#10337. To send to all of the mail addresses registered, write to "3FFH".

3)Write the mail data to the following buffer memory addresses.

(Contents of main text or attached file: BFM#10404 to 12451)

4)Write "0001H" in BFM#10333 to send the mail.

5)Read BFM#10334 to check if mail was correctly sent.

10 USING THE E-MAIL FUNCTION

MELSEC-F

(2) Execution timing of the instruction

1)Check whether the initial processing has been completed normally.

2)Write mail data to the buffer memory.

(Mail sending destination: BFM#10337 b0 to b9)

(Subject: BFM#10339 to 10402)

(Attached file format: BFM#10338)

(Word count of attached file: BFM#10403)

(Contents of main texts or attached files: BFM#10404 to 12451)

3)Write "0001H" in BFM#10333.*1 The e-mail is sent to the mail server.

4)When sending to the mail server is complete, the result is stored in BFM#10334.*2

*1 Specify the attached file format by writing a parameter in BFM#10338 before sending e-mail.

0000H: Sends the attached file in binary format

0001H: Sends the attached file in ASCII format

0002H: Sends the attached file in CSV format

0004H: Sends the attached file as a text mail

*2 For details on causes of errors, see "Troubleshooting" in Chapter 11.

(a)Designate binary format when communicating between Ethernet modules. The name of the attached file is mmddhhss.bin (system date.bin).

mm: Month dd: Date hh: Hour ss: minute

(b)Designate either binary format, ASCII format or CSV format when a PC/UNIX receives e-mail sent from an Ethernet module.

1)When binary format is designated

The name of the attached file is mmddhhss.bin (system date.bin).

mm: month dd: day hh: hour ss: minute

2) When ASCII format is designated

The name of the attached file is mmddhhss.asc (system date.asc). mm: month dd: day hh: hour ss: minute

3)When CSV format is designated

The name of the attached file is mmddhhss.csv (system date.csv).

mm: month dd: day hh: hour ss: minute

*For details on how to receive e-mails, see (3).

*The system date for the file name is the data managed by the PLC in

which the Ethernet module is installed.

10 USING THE E-MAIL FUNCTION

MELSEC-F

(3)Receiving with a personal computer

The following explains how a PC/UNIX receives e-mails sent from the Ethernet module.

After setting an environment with application software that processes e-mails,

e-mails can be received on a receive message screen as shown below. (Example) The following shows an example of the received e-mail.

(The screen display shows Microsoft Corporation's Outlook Express 6.)

(c)

<Data contents for attached files> 123456789abc

(a)From

Displays the mail address of the Ethernet module.

NOTE

By entering the mail addresses of the send destination devices in the address book, the registered names (display names) can be displayed and makes management easier.

(b)Subject

This indicates the transmission destination No. (*1) and the Subject

written by a sequence program.

*1 The Ethernet module automatically adds this number, sequentially starting from 00001.

(After the maximum number (99999) is reached, the number starts from 00000.)

(c)Attached file

This indicates the name of the attached file sent by the Ethernet module.

POINT

Data in the attached file in CSV format can be read in cell units in Excel, etc., for each word of data.

10 USING THE E-MAIL FUNCTION

MELSEC-F

10.7.2Contents of the attached files

The following explains the contents of the attached file data.

The data format of the attached file is ASCII code (ASCII format, CSV format) or binary code (binary format).

The following example shows the transmission contents for each data format (binary/ ASCII/CSV) when the Ethernet module sends the data register value as an attached file.

(1) When sending from the Ethernet module

BFM# 1234H 10404

10405 5678H

Ethernet module

BINASCII conversion

In case of CSV

10413 9ABCH

(2)Data configuration in CSV format

Data in CSV format can be used as control data for the cell units in Excel, etc. Data in CSV format handled by the Ethernet module is the data expressed as follows.

???1 word (16 bits) binary data is converted to four digit ASCII code when expressed as a hexadecimal. (4 bytes of ASCII code)

???When handling multiple word data, insert comma data between each word (4 bytes of ASCII code).

Data is sent in the following arrangement.

Arrangement of data

1)In addition to the data conversion and insertion described above, CR (code: 0DH) and LF (code: 0AH) are inserted for each 8 words of data.

2)The arrangement of data sent in CSV format is shown below.

8 device (8-word unit)

10 USING THE E-MAIL FUNCTION

MELSEC-F

10.8 Sending E-mail (Main Text) by the PLC

This section explains how to send the main text of e-mail.

10.8.1When sending data as main text of e-mail

The following explains the buffer memory address and sequence program for sending e-mail.

This section explains how to store the data in main text and send it to the external device.

1)Check whether mail can be sent or not. (BFM#10334 b15: OFF)

2)Destination of the mail.

Turn the bit corresponding to the e-mail destination address to ON in BFM#10337.

To send to all of the mail addresses registered (maximum 10 addresses), write 3FFH.

3)Write the mail data to the following buffer memory addresses. (Subject: BFM#10339 to 10403)

(Attached file format: Set "0004H" : BFM#10338)

(Mail text/word count of attached file : BFM#10403)

(Contents of main text: BFM#10404 to BFM#12451)

4)Write "0001H" to BFM#10333 to send the mail.

5)Read the value in BFM#10334 to check if mail was correctly sent.

10 USING THE E-MAIL FUNCTION

MELSEC-F

(1)Send using the sequence program

Method for sending e-mails by the sequence program is similar to the one by an attached file.

See Subsection 10.7.1 for sample programs for sending e-mail from PLC.

(2)Receiving by a personal computer

The following explains how a PC/UNIX/portable terminal receives e-mail sent from the Ethernet module.

After setting an environment for using the Internet with application software that

processes e-mails, e-mails can be received on a receive message screen as shown below.

(Example) The following shows an example of a received e-mail.

(The screen display shows Microsoft Corporation's Outlook Express 6.)

(a)From

Displays the e-mail address of the Ethernet module.

NOTE

By entering the mail addresses of the send destination devices in the address book, the registered names (display names) can be displayed and makes management easier.

(b)Subject

This indicates the transmission destination No. (*1) and the Subject written by a sequence program.

*1 The Ethernet module automatically adds this number, sequentially, starting from 00001.

(After the maximum number (99999) is reached, the number starts again from 00000.)

(c)Main text of e-mail

This indicates the main text of the e-mail sent by the Ethernet module.

11 TROUBLESHOOTING

MELSEC-F

11 TROUBLESHOOTING

This section explains the contents of the errors that may occur during communication between the Ethernet module and an external device as well as the troubleshooting procedures.

The following are methods for checking if there is an error on the Ethernet module side and the contents of the error.

Use one of the following methods to check if there is an error and its content, then take corrective actions.

(1) Check using the display LED on the front of the Ethernet module (See Section 11.1.)

The display LED on/off status can be used to check if an error is occurring in the

Ethernet module.

(2) Check through FX Configurator-EN-L

FX Configurator-EN-L can be used to check various conditions of the Ethernet module as well as the error code corresponding to the contents of the error occurring and to perform tests.

(a)Ethernet diagnostics (See Subsection 11.2.2.)

1)PING test (See Subsection 5.4.1.)

2)COM. ERR off (See Subsections 11.1.2 and 11.2.1.)

(3)Check through GX Developer

(a)Buffer memory batch monitor

The error code can be checked by monitoring the buffer memory of the Ethernet module.

(4)Check the contents of the error using the error code (See Section 11.4.)

The contents of the error can be checked using the error code confirmed on the dedicated screen above or by monitoring the buffer memory by referring to Section 11.4.

NOTE

If line errors and other errors occur when connecting devices of multiple manufacturers, the users needs to isolate the malfunctioning parts using line analyzers, etc.

11 TROUBLESHOOTING

MELSEC-F

11.1.2 How to turn off COM.ERR LED and to read/clear error information

This section explains how to turn off [COM.ERR] LED and to read/clear error information using a sequence program.

(1) How to turn off [COM.ERR] LED using buffer memory

The [COM.ERR] LED on the front of the Ethernet module is turned on when a communication error occurs in an external device. (BFM#28...b4: ON)

(a)The [COM.ERR] LED is turned off by writing "0001H" to the off request signal (BFM#1601).

[COM.ERR] LED off request signal BFM#1601=0001H

[COM.ERR] LED on BFM#28, b4

Error occurrence

(b) The off processing is performed by writing "0001H" to BFM#1601.

(c)The error information in the error log area of the buffer memory is not cleared (deleted) even if "0001H" is written to BFM#1601.

(2)How to turn off [COM.ERR] LED on the "Ethernet diagnostics" screen of FX Configurator-EN-L (See Subsection 11.2.2.)

(a) Clicking on the COM.ERR off button turns the [COM.ERR] LED off.

(b)The error information in the error log area of the buffer memory is not cleared (deleted).

(3)Reading buffer memory to read error information

Read the error information stored in the buffer memory of Ethernet module.

The "Initial alarm code" and each connection's "Open alarm code" are stored in the following buffer memory.

11 TROUBLESHOOTING

MELSEC-F

11.2 How to Check an Error Through FX Configurator-EN-L

The status of the various settings for the Ethernet module can be checked using the FX Configurator-EN-L functions.

(1) Ethernet diagnostics (See Section 11.2.2.)

The block status of an Ethernet module, parameter settings, communication status, error log and others can be checked using the diagnostic function. The following are the functions of the diagnostics.

Diagnostics

Parameter status

Checks the stored parameters after the initial processing for the Ethernet module. (See Section 5.2.)

Error log

Checks the error stored in the error log area. (See Section 11.4.)

Status of each connection

Checks the status of each connection after the connection to the external device is established with the open processing. (See Section 5.6.)

Status of each protocol

Checks the communication status of each protocol supported by the Ethernet module.

LED status

Checks the on/off status of the LED on the

front of the Ethernet module. (See Section 11.1.)

Send e-mail information

Checks the information for sent e-mail. (See Section 11.4.)

Checks the completion of the initial processing with the issuance of the PING command.

Turns off the [COM.ERR.] LED on the front of the Ethernet module.

(2) Buffer memory batch monitor (See Section 11.3.)

The buffer memory of an Ethernet module is monitored.

POINT

See Subsection 11.2.1 for the buffer memory that can be checked on the "Ethernet diagnostics" screen.

11 TROUBLESHOOTING

MELSEC-F

11.3 Checking the error information by the buffer memory batch monitoring function

It is explained here how the Ethernet module errors can be checked from GX Developer.

Error codes stored in the buffer memory of the Ethernet module can be monitored using the "Buffer memory batch monitoring" function of GX Developer.

[Operating procedure]

(Step 1) Select [Online] - [Monitor] - [Buffer memory batch] from the GX Developer menu bar, and start the "Buffer memory batch monitoring" screen.

(Step 2) Enter [Module start address:].

Assign a special module number to each base module following the order that 0 is assigned to the rightmost module, 1 to the second rightmost module, and goes same up to 7.

However, for FX3UC-32MT-LT(-2) which incorporates the CC-Link/LT function, the first special module will be assigned with No.1.

(Step 3) Enter [Buffer memory start address:].

Enter the buffer memory address to be monitored, using the selected input format (decimal/hexadecimal).

For a list of the buffer memory addresses where error codes are stored, see Section 11.4, "Error Code List".

(Example)

When monitoring the initial abnormal code (BFM #105): Enter "105" + "decimal"

(Step 4) Click the Start Monitor button.

The contents of the buffer memory after the specified address are displayed. (In case of the above example, the contents of 105H and succeeding addresses are displayed.)

POINT

To see if the PLC base module recognizes the FX3U-ENET-L or not, monitor BFM #30.

If BFM #30's value is K7132, the FX3U-ENET-L is being recognized.

NOTE

The display format can by modified as follows:

For details, refer to the "Operating Manual" for GX Developer.

11 TROUBLESHOOTING

MELSEC-F

(1)Initial error code (BFM#105)

(a)This address stores the error codes generated when the initial processing is executed.

(b)Error codes are stored as binary values when the initial abnormal completion signal (BFM#28...b5) is on.

(c)An error code is cleared when the initial normal completion signal (BFM#27"0001H", BFM#28...b0: ON) is turns on, but can also be cleared by the following operations.

1)Writing the value in BFM#1600 to perform re-initialization or turning off the PLC and Ethernet module

2)Re-downloading the parameter with FX Configurator-EN-L or sequence pragram

(2)Open error code

(connection numbers: 1 to 4; BFM#124 to 154)

(a)These addresses store the result of the open processing for the applicable connections.

(b)The results of the open processing are stored in binary values.

0: Normal completion

Other than 0 : Abnormal completion (BFM#28 b6: ON)

(c)An error code is cleared by the following operations.

1)Reopening the connection that caused an open error

2)Performing the re-initial processing by writing the value to BFM#1600

(3)Fixed buffer sending error code

(connection numbers: 1 to 2; BFM#125 to 135)

(a)These addresses store error codes generated when an error in data sending to an external device occurs during fixed buffer communication using the applicable connection.

(b)A sending error code is cleared when the next data sending is normally completed.

(4)Connection end code

(connection numbers: 1 to 2; BFM#126 to 136)

(a)These addresses store end codes returned from an external device as a response during the fixed buffer communication using the applicable connection.

(b)Determine how to handle the end codes in the responses by arranging with the particular external device.

11 TROUBLESHOOTING

MELSEC-F

(5) Error log area (BFM#227 to 372)

This area stores the following errors.

???Errors whose source cannot be confirmed

???Errors that occurred during communications using the random access buffer

???Errors that occurred during communications using MC protocol

(a)Number of error occurrences (BFM#227)

1)This address stores the number of errors registered in the error log block area.

2)When errors occur more than 65536 times, the count is stopped at FFFFH (65535).

(b)Error log write pointer (BFM#228)

1)This address stores the error log block number where the latest error

logging is registered.

*If the pointer value is "16", it means that the latest error logging is registered in the error log block 16 area.

2)When 17 or more errors occur, the registration of error logging starts from error log block 1 area again.

POINT

(1)An error log block area consists of sixteen error log blocks that have the same data order.

(2)The error information continues to be stored into the following areas even if the count of the error occurrences is stopped and no longer stored:

???Error log write pointer storage area

???Error log block

(c)Error log block - Error code/end code (starting from BFM#229)

1)In the error code/end code area, error codes are stored that indicate error content. (See Section 11.3.)

(d)Error block - Subheader (starting from BFM#230)

1)The subheader code of a faulty message is stored in bits 0 to 7 of the corresponding area. ("0" is stored in bits 8 to 15).

2)For errors below the TCP and UDP levels, "0" is stored.

(e)Error log block - Command code (starting from BFM#231)

1)This block stores the command code of a errors message.

Command code

2)"0" is stored in the following case.

???For messages not containing a command code

???For errors below the TCP and UDP levels (because their commands are unknown)

11 TROUBLESHOOTING

MELSEC-F

(f)Error log block - Connection No. (starting from BFM#232)

1)The faulty connection No. is stored in bits 0 to 3 of the corresponding area. ("0" is stored in bits 4 to 15).

2)For errors below the TCP and UDP levels, "0" is stored.

(g)Error log block - Local station Port No. (starting from BFM#233)

1)This block stores the local station's port No. when an error occurred.

2)"0" is stored for errors below the TCP and UDP levels.

(h)Error log block - Destination IP address (starting from BFM#234)

1)This block stores the IP address of an external device when an error occurred.

2)"0" is stored in the following cases.

???For errors below the IP level

???When an error response was relayed through the PLC.

(i)Error log block - Destination Port No. (starting from BFM#236)

1)This block stores the external device's port No. when an error occurred.

2)"0" is stored for errors below the TCP and UDP levels.

(j)Status for each protocol (BFM#376 to 511)

1)This address stores the count of the occurrence for the applicable contents of each protocol's condition.

(The value counted by the Ethernet module.)

2)When the count value exceeds two words, the count stops at FFFFFFFFH (4294967295).

POINT

Values stored in the buffer memory are cleared when the Ethernet module's local station is powered on. (They are not cleared during the initial processing.) Normally, it is not necessary to read this area; so, read it as needed during maintenance.

11 TROUBLESHOOTING

MELSEC-F

(6)E-mail status storage area (BFM#22640 to 24575)

*When the storage count exceeds FFFFH times, the count starts from 0H again.

(a) E-mail status storage area for sending (BFM#23355 to 23712)

1)Number of mails normally completed (BFM#23355)

???This address stores a cumulative count of how many times the Ethernet module transferred send mails to the Send mail server.

2)Attached file sending count (BFM#23356)

???This address stores a cumulative count of how many times the Ethernet module sent mails with files attached.

3)Sending to the server count (BFM#23357)

???This address stores a cumulative count of sending to the send mail server.

4)Number of mails abnormally completed (BFM#23358)

???This address stores a cumulative count of communication error occurrences that are returned when requesting sending to the transmitting mail server.

0: No communication error between servers, or no transmission has been made

1 or more : Cumulative count of communication error occurrences

5)Error log write count (BFM#23359)

???This address stores a cumulative count of registrations made to the sending error log block area.

11 TROUBLESHOOTING

MELSEC-F

6)Sending error log write pointer (BFM#23360)

???This address stores the error log block area number where the latest sending error logging is registered.

*If the pointer value is "8", it means that the latest error logging is registered in the sending error log block 8 area.

???When 9 or more sending errors occur, the registration of sending error logging starts from sending error log block 1 area again.

POINT

The sending error log block area consists of eight error log blocks that have the same order of data items.

7)Error log block - Error code (BFM#23361 onwards)

???This block stores the error codes that indicate the contents of errors. (See Section 11.4.)

8)Error log block - Command code (BFM#23362 onwards)

???This block stores the system command codes for the error causing messages.

9)Error log block - To (BFM#23363 onwards)

???This block stores eight words from the beginning of the sending source mail address of an error causing e-mail during communication with the mail server, in ASCII code characters.

(Example)

If the sending source mail address was "use@from.add.sample.co.jp",

"use@from.add.sam" is stored as ASCII code characters. 10)Error log block - Date (BFM#23371 onwards)

???This block stores the time and date on which the e-mail is sent in BCD code.

???The order of date and time to be stored is the same as for the date and time of e-mail reception shown in (a) 11).

11)Error log block - Subject (BFM#23375 onwards)

???This block stores 30 words from the beginning of the Subject of the e-mail.

???A Subject is not stored successfully if it contains characters other than alphanumeric and ASCII code.

11 TROUBLESHOOTING

MELSEC-F

*1 Take corrective action using the following procedure.

1)Check whether the expansion connectors are connected correctly.

2)Check whether the operating environment of the Ethernet module is within the general specifications range of the module.

3)Check whether the power supply capacity is sufficient or not.

4)Check whether the hardware of the Ethernet module, power supply block and PLC are normal according to the manuals of the corresponding modules.

If any module is faulty, please request your local Mitsubishi service center or representative to have it serviced.

5)If the problem cannot be solved through the above steps, please consult your local Mitsubishi service center or representative, explaining the operation/communication conditions at the time of error occurrence and the information stored in the error log area within the buffer memory of the Ethernet module.

NOTE

Depending on the restrictions of the buffers of the local station and external device, data may be divided for communication.

Data received separately is restored (reassembled) by the Ethernet module to be communicated using the fixed buffer, etc. The received data is restored (reassembled) based on the data length in the communication data.

The Ethernet module performs the following processing if data among the communication data is incorrect.

11 TROUBLESHOOTING

MELSEC-F

(1)When communication is performed using fixed buffer (with procedure)

(a)If the data length specified immediately after the subheader is smaller than the amount of text data received

1)The data immediately following the part of the text data equivalent to the data length specified immediately after the subheader will be regarded as the next message.

2)Since the header of each message will be a subheader, the Ethernet module performs processing according to the code in the subheader.

3)If the subheader contains a code that is not recognized by the Ethernet module, the Ethernet module will send a response to the external device notifying it of abnormal completion.

This section is processed as a subheader.

At this point, the Ethernet module returns a response containing a code obtained by changing the most significant bit of the code processed as subheader to 1.

For example, if the subheader field of a command is 65H, the subheader of the response will become E5H.

(b)If the data length specified immediately after the subheader is larger than the amount of text data received

1)The Ethernet module waits for the reception of the remaining missing data.

2)If the remaining data could be received within the time allotted by the response monitoring timer, the Ethernet module performs processing according to the code in the subheader.

3)If the remaining data could not be received within the time allotted by the response monitoring timer, the Ethernet module performs the following processing.

???Sends the ABORT (RST) instruction to the external device and closes the line.

???Notifies the PLC side about occurrence of an open error via the open error detection signal (BFM#28.b6=ON)

???Stores the error code in the open error code storage area. (The error code is not stored in the error log storage area.)

POINT

Designate the actual data size of the text field for "data length" specified in the application data field of a message sent from the external device to the Ethernet module.

The Ethernet module never sends text whose size is different from the specified data length to the external device.

11 TROUBLESHOOTING

MELSEC-F

11.5 Troubleshooting Flowchart

This section explains some simple troubleshooting procedures when the Ethernet module and an external device have communication problems in a flowchart format. (*1)

POINT

If trouble occurs when using the Ethernet module, check the block status, error status and others for the Ethernet module using the Ethernet diagnostic function of FX Configurator-EN-L described in Subsection 11.2.2.

Data cannot be communicated.

Check whether or not an error occurred in the PLC base unit to which the Ethernet module is installed.

Did an error

that makes the PLCYES stop processing

occur?

Check the status of the applicable Ethernet module.

Is the data code

(binary/ASCII) setting of the NO communication data

correct?

YES

Refer to the troubleshooting section in the applicable PLC ???s user???s manual and fix the problems.

Turn on the PLC and Ethernet module again.

If the [RUN] LED does not turn on even after resetting, the Ethernet module???s hardware may be faulty. Replace the Ethernet module and restart all the external devices that communicate with the local station.

Check whether or not a parameter error occurred. If an error is found,

first correct it and then re-download.

Check the error contents using the diagnostics function of

FX Configurator-EN-L.

Lock the cable securely.

Data cannot be sent/received because the data code is different in sending node and receiving node and the command can therefore not

be successfully decoded. Change the setting in [Communicational data code] of [Operational settings] using

FX Configurator-EN-L.

(See Section 4.6.) (*2)

11 TROUBLESHOOTING

MELSEC-F

Perform initial processing. (See Subsection 5.2.1.)

If the initial processing parameters set with FX Configurator-EN-L and the

sequence program for initial processing overlap, delete the sequence program for initial processing.

Check and fix the faulty part for each communication processing.

*1 See Section 11.1 when the value of BFM#27 is "0000H" or when the display LED COM.ERR (communication error detection display) lights up.

(Check an error code that is stored in the buffer memory in reaction to an error occurrence, then check the contents of the error and take corrective actions by referring to Section 11.4.)

*2 Error codes not found in the error code list may be returned to the external device side if the communication data settings on the Ethernet module side (see Section 4.6) and the data code settings on the external device side are different.

The Ethernet module cannot decode commands correctly if data with different data codes is received. The Ethernet module returns error responses according to the communication data code settings.

[example] When communication is performed using a fixed buffer.

*3 If the FG ( )terminals of the Ethernet module are not set, the communication line is closed (disconnected) due to

the effects of noise, and as a result communication with an external device may not be performed.

11 TROUBLESHOOTING

MELSEC-F

POINT

(1)When the Ethernet module is replaced due to an error, reboot the following external devices and restart data communication:

(If the external device retains the Ethernet address, it may be impossible to continue communication because when a module is replaced the Ethernet address changes.)

In the same way, when the external device (personal computer, etc.) is replaced, restart the Ethernet module.

???All external devices that communicated with the station whose Ethernet module was replaced.

???All external devices that communicated with other station's PLC via a station whose Ethernet module was replaced.

(2)When connecting a device to the Ethernet module, see the following sections for the required devices and connection method:

Section 2.2: Devices Required for Network Configuration

Section 4.4: Connecting to the Network

(3)If the Ethernet module could not receive messages sent from external devices frequently, check the values stored in the following buffer memory.

(a) Simultaneous transmission error detection count storage area (BFM#398 to 399) and Error/End code storage area for each error log block (BFM#229...)

When the error detection count number is high or when the error code C0C7H has been stored, high load may be applied to the Ethernet connection line to transfer data among connected devices.

To reduce the load to the Ethernet line, it is necessary to take corrective measures such as dividing the network or reducing the data transmission frequency.

Consult your network administrator and take appropriate measures.

11 TROUBLESHOOTING

MELSEC-F

11.5.1Sending errors during fixed buffer communication

(common to procedure exist and no procedure)

Sending error

Check the open status of the connection with an external device.

YES

If so, modify the program.

Read the open abnormal code (BFM #229...) of the error log area and check that no errors have occurred.

YES

Read the content of the communication abnormal code storage area (BFM #125, 135) corresponding to the

fixed buffer of the buffer memory and check whether or not a communication error has occurred.

YES

Check that "send" is set in the parameter open settings.

Execute the open processing of the applicable connection. (For details,

see Section 5.6.)

Fix the error according to the error code (see Section 11.4).

Change parameters to "send".

Correct the IP address of the external device.

11 TROUBLESHOOTING

Does the

communication protocol NO (TCP/UDP) match that of

the external device?

Is the word

count (procedure) or byte NO count (non-procedure) set at the

head of the fixed buffer?

YES

Check the communication status of the external device.

Are there any

open errors or initial errors NO in the error log area?

YES

MELSEC-F

Match the protocol with the communication protocol (TCP/UDP) of the external device. (For details, see Section 5.5.)

Correct the write condition of

BFM#1610, 1611.

Check the fixed buffer transfer error code of BFM#125, 135

Write the data length.

Fix the faulty part of the external device. (If the receiving side is also an Ethernet module, see Section 11.4.)

Check and fix the faulty part.

The Ethernet module hardware on the sending side may be faulty.

Consult your nearest branch office or dealer with the details of the errors.

POINT

If the external device communicates normally, the following conditions occur. For TCP communication

When the external device's open status is complete, LEDs C1, C2, which are in correspondence with connections 1, 2, turn on.

For UDP communication

When external device communication is possible, LEDs C1, C2, which are in correspondence with connections 1, 2, turn on.

11 TROUBLESHOOTING

MELSEC-F

11.5.2Receiving errors during fixed buffer communication

(common to procedure exist and no procedure)

POINT

Perform error code reading while the connection is open.

Check the open status of the connection with an external device.

YES

Read the open abnormal code (BFM #124, 134) of the communication status storage area and check that no errors have occurred.

Execute the open processing of the applicable connection.

(For details, see Section 5.6.)

Fix the error according to the parameter error code (see Section 11.4).

YES

Read the content of the communication abnormal code storage area (BFM #125, 135) corresponding to the fixed buffer

of the buffer memory and check whether or not a communication error has occurred.

Check that "receive" is set in the parameter open settings.

Fix the error according to the communication error code in the error log area (see Section 11.4).

Receive is set

YES

Change parameters to "receive".

11 TROUBLESHOOTING

MELSEC-F

11.5.3 Errors in communication using MC protocol

Communication error

Check the open status of the connection with the external device.

Are the corres- ponding connection LEDs

(C3, C4) lit?

YES

Was a command sent form the external device?

YES

Was a response returned to the device that sent

the command?

YES

Is the IP address designation of the command correct?

YES

Does the communication protocol (TCP/UDP) match with that of the external device?

YES

The command may not be sent to the Ethernet module from the external device on the command sending side. Check the sending side.

NO Correct the IP address and send the command again.

Is the end code of the response "0"?

YES

11 TROUBLESHOOTING

MELSEC-F

Is the IP address of the command correct?

YES

Are the command formats,

such as command type, device designation, and address designation, designated correctly?

YES

Are there any open errors or initial errors in the error

log area?

YES

Correct the command format.

Check and fix the faulty part.

The Ethernet module hardware may be faulty. Consult your nearest dealer with the details of the errors.

POINT

???If the external device communicates normally, the following conditions occur. For TCP communication

When the external device's open status is complete, LEDs C3, C4, which are in correspondence with connections 3, 4, turn on.

For UDP communication

When external device communication is possible, LEDs C3, C4, which are in correspondence with connections 3, 4, turn on.

???In connections used for communication using MC protocol, it is necessary to set the communication parameter to "MC protocol usable" in "Connection usage" as described in the table in Subsection 5.5.2, or select "Unpassive open (MC)" or "Fullpassivel open (MC)" in the open system settings in FX Configurator-EN-L .

11 TROUBLESHOOTING

MELSEC-F

11.5.4 Sending errors during e-mail communication

Sending error

Is "0001H" written to BFM#10333?

YES

Correct the condition for writing to BFM#10333.

Is the value of BFM#10334 set to "0001H"?

YES

Are the mail server port numbers set correctly in

BFM#24320 and 24388?

YES

Is the SMTP authentication setting used?

YES

Set the server port numbers correctly.

Can the error response be received from

the mail server using the mail receiving operation?

Check the following items.

E-mail parameter settings of the Ethernet module

Whether or not the mail server's system is down

Whether or not there is an error on the communication path

When "SMTP-AUTH" is selected, check whether the SMTP login ID and password are set correctly.

When "POP before SMTP" is selected, check whether the POP password and local mail address are set correctly.

APPENDIX

MELSEC-F

APPENDIX

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 App number of connections used concurrently, and how the system is configured. Use the

values obtained from the expressions below as a guideline for the processing time when communication is performed using only one connection.

(1)Minimum processing time of communication using the fixed buffer (communication between the Ethernet module)

(a)Communication using the fixed buffer (Procedure exist) Tfs = St + Ke + (Kdf Df) + Sr

(b)Communication using the fixed buffer (No procedure) Tfs = St + Ke + (Kdf Df)

[Calculation example]

Calculate the time from the start of sending to the completion of sending (unit: ms) when the FX3U-ENET-L communicate using TCP/IP and send 32 words of binary code data using fixed buffer communication (procedure exist).

???Assume that the scan time on the receiving side is 30 ms and the scan time on the transmission side is 25 ms:

67 (ms) 30 + 12 + (0.0065 32) + 25

APPENDIX

MELSEC-F

[Calculation example 1]

Calculate the required time (unit: ms) to complete the processing of a data request from a PC after receiving it, when the Ethernet module and the PC perform TCP/IP communication and read 32 points of ASCII code data from the data register (D) in the PLC using MC protocol communication.

???Assume that the scan time of the FX3U-ENET-L installed station is 40 ms:

59.17+ ACK processing time of the external device (ms)

18 + (0.015 (12 + 66)) + 40 1 + ACK processing time of the external device

Command data length = 12 words Response data length = 66 words

[Calculation example 2]

Calculate the required time (unit: ms) the FX3U-ENET-L takes to complete the processing of a data request from a PC after receiving it, when the Ethernet module and the PC performs TCP/IP communication and writes 32 points of ASCII code data to the data register (D) in the PLC using MC protocol communication.

???Assume that the scan time of the FX3U-ENET-L installed station is 40 ms:

58.11(ms) 16 + (0.027 (76 + 2)) + 40 1

Command data length = 76 words

Response data length = 2 words

APPENDIX

MELSEC-F

Appendix 4 Program Examples

The program examples presented in this section test the connection between the Ethernet module and an external device (personal computer) that is connected to the same Ethernet.

For each program, only the minimum programming that is required to perform the communication test is done. Modify the IP address, port number and other values according to your system configuration. In addition, abnormal handling may be added.

(1) Receive processing of target device

A receive processing example on the target device side is shown below.

Communication processing on the external device side

Request message/transmission processing

Response message/reception processing

The TCP connection is closed

Is the TCP connection open?

Receive remaining response messages

Insufficient size of data received

Check the size of the received data

If a response message to the

next request was received

Response message processing

Have all the received messages been processed?

Background

For Ethernet communications, the TCP socket functions are used inside the personal computer. However, these functions do not have any limits. Therefore, when the "send" function is executed once to transmit data, the receiving end (node) needs to execute the "recv" function once or more in order to read the data ("send" and "recv" is not proportional to 1:1 execution). For this reason, the receiving procedure explained above, is required.

APPENDIX

MELSEC-F

(4) Program on the external device side

The program example of the external device shown below accesses the FX3U of the station in which the Ethernet module is installed.

When this program is executed, the contents of the following communication messages are displayed in sequence:

1)Batch write command message in word units

2)Batch write response message in word units

3)Batch read command message in word units

4)Batch read response message in word units

REMARK

(1)The following explains an outline of the compiling procedure for a program created using Microsoft Corporation Visual C++ .NET

1)Start Visual C++ .

2)Prepare for program creation.

Select "New Project" from the project tab, select "Win32 console project", and create an empty project with the name "ENETSAMP".

3)Add ENETSAMP.C to the project and create a program. (See the program example on the next page.)

4)Compile the created file from the compile screen of the build menu.

5)From the project menu property setting screen, add WSOCK32.LIB to the linker addition dependency files.

6)Create an executable file (ENETSAMP.EXE) on the build screen of the build menu.

7)End Visual C++ .NET.

8)Execute ENETSAMP.EXE.

(2)Outline of the procedure for calling the socket routine

APPENDIX

MELSEC-F

Appendix 4.2 Program example for communication using MC protocol -2

This section explains an example of an external device program that reads/writs data from the PLC.

A sample program, its execution environment and contents of data communication are shown below.

(1)Execution environment of the program example

1)The settings of the PLC side are the same as those of the execution environment described in Section 4.1 (1) (a) and (3) of Appendix.

2)The settings of the external device side are the same as those of the execution environment described in Section 4.1 (1) (b) of Appendix, except for the following including the software development:

??? Software development environment:Microsoft Corporation Visual

Basic .NET

??? Arbitrary numbers are assigned for the IP address and port number.

3)The communication protocol is TCP/IP

(2)Outline of the program example

With the A-compatible 1E frame command (01: batch read in word units), this program reads data from D0 to D4 (five points) of the PLC of the station on which the Ethernet module is mounted.

(3)Outline of the sample program

(a)Create a new project and form.

(b)Create the (example) window shown in (4) below using " Button" and "List Box" in the toolbox.

(c)Create the program shown in (5).

APPENDIX

MELSEC-F

(4) Window example (Form 1)

(Object name) Start

Connect to the Ethernet module and perform communications

1st Output

Display data that was read from the Ethernet module

(5) Sample program (Form 1)

Parts in italic are created automatically by Visual Basic .NET, so no input is required. Only input where written in bold.

Option Explicit On

Option Strict On

Imports System.Net.Sockets

Public Class Form1

Inherits System.Windows.Forms.Form

#Region " Windows Code created by Form Designer "

Public Sub New()

MyBase.New()

'This call is necessary for Windows Form Designer. InitializeComponent()

'InitializeComponent() Initialization is added after the call. End Sub

'The Form overwrites dispose to execute after-processing in the component list. Protected Overloads Overrides Sub Dispose(ByVal disposing As Boolean)

If disposing Then

If Not (components Is Nothing) Then components.Dispose()

End If End If

MyBase.Dispose(disposing) End Sub

'Necessary for Windows Form Designer.

Private components As System.ComponentModel.IContainer

APPENDIX

MELSEC-F

Memo: The following procedure is necessary for Windows Form Designer. Change by using Windows Form Designer.

Do not use code editor to change.

Friend WithEvents Start As System.Windows.Forms.Button Friend WithEvents lstOutput As System.Windows.Forms.ListBox

<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent() Me.Start = New System.Windows.Forms.Button

Me.lstOutput = New System.Windows.Forms.ListBox Me.SuspendLayout()

'Start

Me.Start.Location = New System.Drawing.Point(16, 16) Me.Start.Name = "Start"

Me.Start.Size = New System.Drawing.Size(88, 32) Me.Start.TabIndex = 0

Me.Start.Text = "Start"

'lstOutput

Me.lstOutput.ItemHeight = 12

Me.lstOutput.Location = New System.Drawing.Point(16, 64) Me.lstOutput.Name = "lstOutput"

Me.lstOutput.Size = New System.Drawing.Size(264, 196) Me.lstOutput.TabIndex = 1

'Form1

Me.AutoScaleBaseSize = New System.Drawing.Size(5, 12) Me.ClientSize = New System.Drawing.Size(296, 273) Me.Controls.Add(Me.lstOutput)

Me.Controls.Add(Me.Start) Me.Name = "Form1" Me.Text = "Form1" Me.ResumeLayout(False)

End Sub

#End Region

Private Sub Start_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Start.Click

Dim IpAddress As String

Dim PortNum As Integer

Dim Client As TcpClient Dim Buffer() As Byte Dim InBuff(1532) As Byte

Dim TxCommand As String

APPENDIX

MELSEC-F

Dim RxResponse As String

Dim Temp As String

Dim j As Integer

Dim Dreg(5) As Double

Dim DregStr$

Dim SubHeader$

'IP Address specification IpAddress = "172.16.56.99"

'Port Number specification PortNum = 10000

Client = New TcpClient 'Line connection processing Try

Client.Connect(IpAddress, PortNum) Catch ex As Exception

MsgBox("Connection with the server failed, and the following code was returned: "& ex.Message, 0, "connection error")

Exit Sub End Try

'Read D0 to D4 (5 points) with the A-compatible 1E frame command. TxCommand = "01ff000a4420000000000500"

Buffer = System.Text.Encoding.Default.GetBytes(TxCommand.ToCharArray) 'Sending a read command

Client.GetStream().Write(Buffer, 0, Buffer.Length) 'Waiting for a response from an Ethernet block While Not Client.GetStream().DataAvailable()

Application.DoEvents() End While

If Client.GetStream().DataAvailable() Then Client.GetStream().Read(InBuff, 0, InBuff.Length)

RxResponse = System.Text.Encoding.Default.GetString(InBuff) SubHeader = Mid$(RxResponse, 3, 2)

If SubHeader = "00" Then 'Normal response

Temp = "" 'Initialization of an output character string For j = 0 To 4

DregStr$ = Mid(RxResponse, j * 4 + 5, 4) Dreg(j) = Val("&H" + DregStr$)

Temp = Temp + Format(Dreg(j), "#####0") + " " Next

lstOutput.Items.Insert(lstOutput.Items.Count, Temp)

ElseIf SubHeader = "5B" Then ' In an abnormal response, an abnormal code is added.

APPENDIX

MELSEC-F

Appendix 5 Differences between the Ethernet and the IEEE802.3

The following shows the Ethernet header in the data link layer supported by the

Ethernet module.

Ethernet frame (V 2.0) specification

IEEE802.3 (ISO/IEC8802.3) frame specification

(1) Ethernet

(2) IEEE802.3

Appendix 6 ICMP Protocol Supported by the Ethernet Module

The following table outlines the types of ICMP supported by the Ethernet module and the processing performed by the Ethernet module.

*1 The Ethernet module can simultaneously receive two ICMP ECHO requests (type 8, Ping message), which are used for existence confirmation, etc., and handles them accordingly.

When three or more ICMP ECHO requests are received at the same time, the third and succeeding requests will be ignored.

If a response is not returned to the external device when an ICMP ECHO request is sent to the Ethernet module, send an ICMP ECHO request to the Ethernet module again.

The Ethernet module is able to receive a maximum of 1460 bytes ICMP message at one time. Do not send an ICMP message request exceeding 1460 bytes to the Ethernet module.

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.

a)Failure occurring from inappropriate storage or handling, carelessness or negligence by the user. Failure caused by the user's hardware or software design.

b)Failure caused by unapproved modifications, etc., to the product by the user.

c)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.

d)Failure that could have been avoided if consumable parts (battery, backlight, fuse, etc.) designated in the instruction manual had been correctly serviced or replaced.

e)Relay failure or output contact failure caused by usage beyond the specified Life of contact (cycles).

f)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.

g)Failure caused by reasons unpredictable by scientific technology standards at time of shipment from Mitsubishi.

h)Anyother failure found not to be the responsibility of Mitsubishi or that admitted not to be so by the user.

2.Onerous repair term after discontinuation of production

1)Mitsubishi shall accept onerous product repairs for seven (7) years after production of the product is discontinued.

Discontinuation of production shall be notified with Mitsubishi Technical Bulletins, etc.

2)Product supply (including repair parts) is not available after production is discontinued.

3.Overseas service

Overseas, repairs shall be accepted by Mitsubishi's local overseas FA Center. Note that the repair conditions at each FA Center may differ.

4.Exclusion of loss in opportunity and secondary loss from warranty liability

Regardless of the gratis warranty term, Mitsubishi shall not be liable for compensation of damages caused by any cause found not to be the responsibility of Mitsubishi, loss in opportunity, lost profits incurred to the user or third person by Failures of Mitsubishi products, special damages and secondary damages whether foreseeable or not , compensation for accidents, and compensation for damages to products other than Mitsubishi products, replacement by the user, maintenance of on-site equipment, start-up test run and other tasks.

5.Changes in product specifications

The specifications given in the catalogs, manuals or technical documents are subject to change without prior notice.

6.Product application

1)In using the Mitsubishi MELSEC programmable logic controller, the usage conditions shall be that the application will not lead to a major accident even if any problem or fault should occur in the programmable logic controller device, and that backup and fail-safe functions are systematically provided outside of the device for any problem or fault.

2)The Mitsubishi programmable logic controller has been designed and manufactured for applications in general industries, etc. Thus, applications in which the public could be affected such as in nuclear power plants and other power plants operated by respective power companies, and applications in which a special quality assurance system is required, such as for Railway companies or Public service purposes shall be excluded from the programmable logic controller applications.

In addition, applications in which human life or property that could be greatly affected, such as in aircraft, medical applications, incineration and fuel devices, manned transportation, equipment for recreation and amusement, and safety devices, shall also be excluded from the programmable logic controller range of applications.

However, in certain cases, some applications may be possible, providing the user consults their local Mitsubishi representative outlining the special requirements of the project, and providing that all parties concerned agree to the special circumstances, solely at the users discretion.