Download  Print this page

Advertisement

FX
-ENET
3U
USER'S MANUAL

Advertisement

Table of Contents

   Also See for Mitsubishi Electric FX3U-ENET

   Summary of Contents for Mitsubishi Electric FX3U-ENET

  • Page 1 -ENET USER'S MANUAL...
  • Page 3: Safety Precautions

    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: "WARNING" and "CAUTION." Indicates that incorrect handling may cause hazardous conditions, WARNING resulting in death or severe injury.
  • Page 4 [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.
  • Page 5 [Wiring Instructions] WARNING 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.
  • Page 6 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.
  • Page 7: Table Of Contents

    CONTENTS SAFETY PRECAUTIONS ........................A- 1 CONTENTS ............................A- 5 About Manuals ............................A- 9 Associated Manuals..........................A- 9 Applicable Standard..........................A-10 The Manual's Usage and Structure.......................A-12 About the Generic Terms and Abbreviations ..................A-14 1 OVERVIEW 1- 1 to 1- 9 1.1 Overview of the Ethernet Module....................1- 1 1.2 Features of the Ethernet Module ....................
  • Page 8 5 COMMUNICATION PROCEDURE 5- 1 to 5-46 5.1 Overview of the Communication Procedure .................. 5- 1 5.2 Initial Processing..........................5- 3 5.2.1 Initial processing ........................5- 3 5.2.2 Initial settings ........................... 5- 4 5.2.3 Re-initialization......................... 5-10 5.3 Router Relay Parameter ........................ 5-13 5.4 Confirming the Completion of the Initial Processing ..............
  • Page 9 8 COMMUNICATION USING MC PROTOCOL 8- 1 to 8- 4 8.1 Data Communication Function....................... 8- 1 8.1.1 Accessing the PLC using MC protocol..................8- 1 8.1.2 How to Read the Control Procedures of the MC Protocol ............8- 2 8.1.3 Access Timing on the PLC Side ....................8- 3 8.1.4 PLC setting for performing data communication..............
  • Page 10 11 TROUBLESHOOTING 11- 1 to 11-45 11.1 How to Check Errors Using LED Displays ................. 11- 2 11.1.1 Checking error display ......................11- 2 11.1.2 How to turn off COM.ERR LED and to read/clear error information ........11- 4 11.2 How to Check an Error Through FX Configurator-EN..............11- 6 11.2.1 Buffer memory that can be monitored with the FX Configurator-EN diagnostic function..
  • Page 11: About Manuals

    About Manuals This manual explains the mounting of FX -ENET, the specifications, broadcast functions and communication methods. For the instructions and programs of the sequence as well as the parameter settings by FX Configurator-EN, also refer to the following manuals. Associated Manuals Manual name Manual No.
  • Page 12: Applicable Standard

    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.
  • Page 13 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).
  • Page 14: The Manual's Usage And Structure

    The Manual's Usage and Structure How to use this manual In this manual, explanations are given for each application of the Ethernet modules -ENET). Please use this manual using the following key items below as a reference. (1) Features and utility lists (a) Features and functions •...
  • Page 15 (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.
  • Page 16: About The Generic Terms And Abbreviations

    About the Generic Terms and Abbreviations This manual uses the following generic terms and abbreviations to describe the Model FX -ENET Ethernet interface block. Generic Term/Abbreviation Description A machine-specific address that is also referred to as the MAC (Media Access Control Ethernet Address Address).
  • Page 17: Overview

    OVERVIEW MELSEC-F 1 OVERVIEW This manual provides information on the specifications of the Ethernet interface block, -ENET (hereinafter called FX -ENET 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.
  • Page 18 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/reception by e-mail (When using the e-mail function) POINT The module operation is not guaranteed if any of the following connection is...
  • Page 19: Features Of The Ethernet Module

    OVERVIEW MELSEC-F 1.2 Features 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.
  • Page 20 OVERVIEW MELSEC-F (3) Communication by e-mails (Details are explained in Chapter 10) Data can be sent to and received from an external device at a remote location using e-mail via an Internet line. (a) Sending/receiving e-mail from the PLC The following data can be sent/received by e-mail. 1) Sending/receiving data as attached files Up to 2k words of data can be sent to or received from a personal computer or other Ethernet module with mail function as a file attached to...
  • Page 21 OVERVIEW MELSEC-F (4) Connecting FX Configurator-EN (Details are explained in the Operating Manuals for FX Configurator-EN) (a) Simplifying sequence programs using FX Configurator-EN FX Configurator-EN 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, access is enabled from the external device to the PLC.
  • Page 22 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.). 1) Connection via TCP/IP communication • If a MELSOFT product is to be connected with the FX Configurator-EN open settings, a maximum of four units can be connected with MELSOFT product.
  • Page 23: Software Configuration

    OVERVIEW MELSEC-F 1.3 Software Configuration The Ethernet modules support the TCP/IP and UDP/IP protocols. OSI reference model corres- Personal computer/work-station(example) ponding to the PLC configuration (Layers) Main Unit User program FROM/TO instruction Application layer Buffer memory System call Presentation layer Session layer Communication Communication...
  • Page 24 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.
  • Page 25 OVERVIEW MELSEC-F 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.
  • Page 26: System Configurations

    SYSTEM CONFIGURATIONS MELSEC-F 2 SYSTEM CONFIGURATIONS This section explains the system configurations that may be combined with the Ethernet modules. 2.1 Applicable Systems Ethernet modules can be used with the following systems: (1) Applicable PLC and number of modules that can be mounted The following table lists the PLC where the Ethernet module can be mounted and the number of modules that can be mounted.
  • Page 27: Devices Required For Network Configuration

    SYSTEM CONFIGURATIONS MELSEC-F 2.2 Devices Required for Network Configuration This section explains the devices that are required to configure a network. Network installation work requires sufficient safeguard; ask a network specialist for installation. When connecting Ethernet module to a network, either a 10BASE-T or 100BASE-TX can be used.
  • Page 28 SYSTEM CONFIGURATIONS MELSEC-F (2) Connection using the 10BASE-T * Up to 4 levels are allowed Twisted pair cable for cascade connection 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) * Use a straight cable for connection between a hub and the Ethernet module.
  • Page 29: Specifications

    SPECIFICATIONS MELSEC-F 3 SPECIFICATIONS This section explains the Ethernet module general specifications, performance specifications and transmission specifications. 3.1 General specifications For items not listed below, specifications are the same as those of the PLC main unit. For general specifications, refer to the manual (Hardware Edition) of the PLC main unit. Item Specification Ambient temperature...
  • Page 30 SPECIFICATIONS MELSEC-F 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) •...
  • Page 31: Data Codes For Communication

    SPECIFICATIONS MELSEC-F NOTE The following explains each of the transmission specification items. [Connecting using the 10BASE-T] [Connecting using the 100BASE-TX] Maximum Maximum Maximum 100m 100m Up to Maximum 5m 100m Up to (2) levels are 4 levels allowed for cascade connection.
  • Page 32 SPECIFICATIONS MELSEC-F 2) Ethernet module Data is sent and received in binary code. Ethernet module Binary code Commu- nication Binary code External data device storage ASCII code BIN/ASCII area conversion (2) When communicating using ASCII code, 1-byte binary code data is automatically converted into 2-byte ASCII code data and then transmitted.
  • Page 33: Relationship Between The External Devices And Additional Functions For Each Communication Function

    SPECIFICATIONS MELSEC-F 3.4 Relationship between the External Devices and Additional Functions for Each Communication Function This section explains which external devices data communication can be performed with and which additional functions can be used for each function. (1) Communicability with external devices using various functions The following table lists the communicability with external devices using various functions.
  • Page 34: Ethernet Module Function List

    SPECIFICATIONS MELSEC-F 3.5 Ethernet Module Function List This section shows a list of Ethernet module functions. (1) Basic functions of the Ethernet module The Ethernet module can perform the communications shown in the table below via TCP/IP or UDP/IP communication. Function Description Reference section...
  • Page 35: List Of Setting Items For Ethernet Modules

    SPECIFICATIONS MELSEC-F 3.6 List of Setting Items for Ethernet Modules The following table lists the parameter setting items that are set using Ethernet Module. Function and parameter setting Reference Parameter setting item Description of setting requirement (* section Fixed Mail MELSOFT Settings for using the Ethernet module as a network Ethernet module settings...
  • Page 36: List Of Applications And Assignments Of The Buffer Memory

    SPECIFICATIONS MELSEC-F 3.7 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).
  • Page 37 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) BFM number Initial value Reference Attribute Flash ROM Application...
  • Page 38 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash Reference Attribute Application Name Decimal Decimal ROM save section (Hexadecimal) (Hexadecimal) Flash ROM writing control 0000 : Normal status 9872 : Write command for configuration data to a flash ROM. Flash ROM Automatically returns to 0000 after...
  • Page 39 SPECIFICATIONS MELSEC-F (b) Communication parameter setting area (BFM #32 to 102) BFM number Initial value Flash Reference Attribute Application Name Decimal Decimal section (Hexadecimal) save (Hexadecimal) Connection No. 1 • Usage of fixed buffer (b0) 0: For sending or fixed buffer communication is not executed 1: For receiving •...
  • Page 40 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash Reference Attribute Application Name Decimal Decimal section (Hexadecimal) save (Hexadecimal) Local station Port No. Section 5.5 41 to 42 Destination IP address Section 5.5 (29 to 2A Connection No.
  • Page 41 SPECIFICATIONS MELSEC-F (c) Communication status storage area (BFM #103 to 226) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) 103 to 104 — System area — — — (67 to 68 Initial error code Section 11.4 106 to 107 Local station IP address...
  • Page 42 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) Stores Ethernet module status (The same specification as BFM#28 "Module status — area") Hub connection status area •...
  • Page 43 SPECIFICATIONS MELSEC-F (d) Error log partition area (BFM #227 to 511) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) Number of error occurrences Section 11.4 Error log write pointer Error code/end code Subheader Command code Connection No.
  • Page 44 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) 376 to 377 Received IP packet count (178 to 179 378 to 379 Received IP packet count discarded Section 11.3 (17A to 17B due to sum check error...
  • Page 45 SPECIFICATIONS MELSEC-F (e) Router relay parameter setting area (BFM #512 to 1599) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) 512 to 513 Sub-net mask (200 to 201 Section 5.3 Router relay 514 to 515 parameter Default router IP address...
  • Page 46 SPECIFICATIONS MELSEC-F (f) Open/close control (BFM #1600 to 1663) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) • Write value Re-initialization request 0001 : Re-initialization ([COM.ERR.] LED OFF) 0002 : Re-initialization after reading data in Flash ROM ([COM.ERR.] LED OFF) 0005 : Re-initialization ([COM.ERR.] LED retains status.)
  • Page 47 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) When sending request or reception complete confirmation signal of connection No.1 • For sending 1) Write value 0001 : Sending request 2) Read value...
  • Page 48 SPECIFICATIONS MELSEC-F (g) Fixed buffer area (BFM #1664 to 9855) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) 1664 Data length (680 Fixed buffer Chapter 6, No. 1 Chapter 7 1665 to 2687 Fixed buffer data (681 to A7F 2688...
  • Page 49 SPECIFICATIONS MELSEC-F (h) Mail send parameter settings (BFM #9856 to 14499) BFM number Initial value Reference Flash ROM Attribute Application Name Decimal section Decimal save (Hexadecimal) (Hexadecimal) 9856 to 9887 Local station mail address (Maximum of 64 characters) "\0" Chapter 10 (2680 to 269F 9888 to 9903 —...
  • Page 50 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Reference Flash ROM Attribute Application Name Decimal section Decimal save (Hexadecimal) (Hexadecimal) • Write value Mail sending instruction (0001 10333 Mail sending Chapter 10 • Read value (285D command (0000 Returns to "0000 "...
  • Page 51 SPECIFICATIONS MELSEC-F Mail receive parameter settings (BFM #14500 to 20479) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) • Write value Receive mail instruction (0001 • Read value 14500 Mail receiving Chapter 10 Initial status (0000 (38A4 command...
  • Page 52 SPECIFICATIONS MELSEC-F Connection status storage area (BFM #20480 to 22639) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) Open complete signal 0: Open incomplete 1: Open completed • Connection No. 1 (b0) 20480 •...
  • Page 53 SPECIFICATIONS MELSEC-F (k) E-mail status storage area (BFM #22640 to 31999) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) 22640 Number of mails remaining on the server Section 11.4 (5870 22641 to 22642 —...
  • Page 54 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) 23353 to 23354 — System area — — — (5B39 to 5B3A 23355 Number of mails normally completed (5B3B 23356 Attached files sent count...
  • Page 55 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal) (Hexadecimal) 24320 SMTP server port number Section 10.6 (5F00 (Fixed to "25" in devices earlier than V. 1.01) SMTP authentication setting 0: No authentication 24321...
  • Page 56 SPECIFICATIONS MELSEC-F (Continued from the previous page) BFM number Initial value Flash ROM Reference Attribute Application Name Decimal Decimal save section (Hexadecimal)) (Hexadecimal) Designates the error information to be cleared 0000 : Clears initial error code (BFM#105) 0001 to 0008 : Clears the open error code of connection 1 to 8 (BFM#124, 134, 144, 154, 164, 174, 184, 194).
  • Page 57: Settings And Procedures Prior To Operation

    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.
  • Page 58: Installation Environment

    SETTINGS AND PROCEDURES PRIOR TO OPERATION MELSEC-F Be careful not to let any foreign matter such as wire chips get inside the module. CAUTION They may cause fire, as well as breakdowns and malfunctions of the module. Never disassemble or modify the module. This may cause breakdowns, malfunctions, injuries or fire.
  • Page 59: Settings And Procedures Prior To Starting The Operation

    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.
  • Page 60 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.
  • Page 61: Components Of The Ethernet Module

    SETTINGS AND PROCEDURES PRIOR TO OPERATION MELSEC-F 4.3 Components of the Ethernet Module This section shows the components of the Ethernet module. View with the cover removed Name Description LED display Refer to the contents of the LED displays (1). Connector for connecting the Ethernet module to the 10BASE-T/100BASE-TX.
  • Page 62 SETTINGS AND PROCEDURES PRIOR TO OPERATION MELSEC-F (*1) (1) LED display contents LED name Display description When the LED is on When the LED is off Normal Abnormal Normal operation display (when FROM/TO instruction can (when WDT is in operation) be executed from PLC side) Not processed INIT.
  • Page 63: Connecting To The Network

    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.
  • Page 64: Connecting To The 10base-t/100base-tx Network

    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...
  • Page 65: Ethernet Module Setting

    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.
  • Page 66: Operational Settings

    SETTINGS AND PROCEDURES PRIOR TO OPERATION MELSEC-F 4.6 Operational Settings This section explains how to set the operations parameters. BFM number [Decimal] Setting name Setting description Setting range/selection (bit number) OFF : Binary code Communication data code 24 (b1) Select the communication data code. ON : ASCII code ON : Use KeepAlive TCP Existence confirmation setting...
  • Page 67 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. Name of setting Description of setting Use the KeepAlive Checks connection status with KeepAlive.
  • Page 68 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". Name of setting Description of setting Do not wait for OPEN...
  • Page 69 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).
  • Page 70: Self-diagnostic Tests

    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.
  • Page 71: Hardware Test (h/w Test)

    SETTINGS AND PROCEDURES PRIOR TO OPERATION MELSEC-F 4.7.2 Hardware test (H/W Test) This section explains the RAM and ROM tests for the Ethernet module. The procedure for the hardware test is as shown in the table below. The test results are judged from the LED displays on the front of the Ethernet module. Status of LED Step Description of operation...
  • Page 72: Maintenance And Inspection

    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.
  • Page 73: Installing And Uninstalling The Module

    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.
  • Page 74: Communication Procedure

    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.
  • Page 75 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 Ethernet module (Subheader code) Fixed buffer communication Receive completion signal...
  • Page 76: Initial Processing

    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;...
  • Page 77: Initial Settings

    COMMUNICATION PROCEDURE MELSEC-F 5.2.2 Initial settings This section explains the initial settings. BFM number Setting item name Description of setting Setting range/options [Decimal] TCP ULP timer Set the time of packet existence at TCP data transmission. 2 to 32767 TCP zero window timer Set the interval for checking the reception enabled status.
  • Page 78 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)
  • Page 79 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)
  • Page 80 COMMUNICATION PROCEDURE MELSEC-F POINT To adjust settings with FX Configurator-EN, 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.
  • Page 81 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) TCP ULP timer value Number •...
  • Page 82 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 (*1) waiting to see whether or not a response is received.
  • Page 83: Re-initialization

    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.
  • Page 84 COMMUNICATION PROCEDURE MELSEC-F (2) Programming and timing for re-initialization The programming and timing for re-initialization is shown below: • For FX Series PLCs Program example for the unit No. 1 <<Re-initialization>> Instruction Re-initialization request self-holding Upon completion of Ethernet H0001 MOVP H0001 module initial processing,...
  • Page 85 COMMUNICATION PROCEDURE MELSEC-F (3) Operation for re-initialization Operation for re-initialization differs as follows, depending on the value written to BFM#1600. Operation Written value COM. ERR LED Re-reading flash ROM 0001 Not re-read Turns off 0002 Re-read 0005 Not re-read No change 0006 Re-read *1: When re-reading the flash ROM, the re-initialization is performed in the same status as...
  • Page 86: Router Relay Parameter

    COMMUNICATION PROCEDURE MELSEC-F 5.3 Router Relay Parameter This section explains the router relay parameter. Setting item name BFM number [Decimal] Description of setting Setting range/options 00 : Use Router relay function Select whether the router relay function is not used or is used. (b5, b4) 01 : Not used Sub-net mask pattern...
  • Page 87 COMMUNICATION PROCEDURE MELSEC-F (2) Subnet mask pattern (BFM#512, 513) (a) Set the subnet mask. (Setting range: C0000000 to FFFFFFFC 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.
  • Page 88: Confirming The Completion Of The Initial Processing

    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.) •...
  • Page 89: Ping Command (personal Computer Ethernet Module)

    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>...
  • Page 90: Loop Back Test (communication Using Mc Protocol)

    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.
  • Page 91: Open Settings

    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 8 external device stations Once a connection is established with an external device, it is possible to communicate using MC protocol, fixed buffer communication.
  • Page 92 COMMUNICATION PROCEDURE MELSEC-F (2) Open system (connection numbers 1 to 8; BFM#32 to 39 b15, b14) (a) Select the connection open system for each connection for which "TCP" is selected in "(1) Protocol". If "UDP" is selected, the specification of this item is not required.
  • Page 93 COMMUNICATION PROCEDURE MELSEC-F (3) Fixed buffer (connection numbers 1 to 8; BFM#32 to 39 b0) (a) Here it is selected whether the fixed buffer corresponding to each applicable connection number will be used for sending or receiving when communicating using the fixed buffers. Name of setting Description of setting Send...
  • Page 94 COMMUNICATION PROCEDURE MELSEC-F (5) Pairing open (connection numbers 1 to 8; BFM#32 to 39 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], [Procedure exist (MC)] or [No procedure] can be specified).
  • Page 95 COMMUNICATION PROCEDURE MELSEC-F (7) Local station Port No. (connection numbers 1 to 8; BFM#40, 47, 54, 61, 68, 75, 82, 89) (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.
  • Page 96 COMMUNICATION PROCEDURE MELSEC-F (9) Destination Port No. (connection numbers 1 to 8; BFM#43, 50, 57, 64, 71, 78, 85, 92) (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.
  • Page 97 COMMUNICATION PROCEDURE MELSEC-F POINT Set parameters according to the open method to be used for open connection. Communication system open system Active Passive ARP function of external device ARP function of external device Un-passive Full-passive Parameter Local station Port No. Communication Destination IP address address...
  • Page 98: Open Processing/close Processing Of The Connection

    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.
  • Page 99 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.
  • Page 100: Active Open Processing/close Processing

    COMMUNICATION PROCEDURE MELSEC-F 5.6.1 Active open processing/close processing This section explains the procedure for opening and closing a connection with an external device from the Ethernet module. • For FX Series PLCs Program example for the unit No. 1 <<Open processing for connection No.1>> M8000 [MOV K4M110...
  • Page 101 COMMUNICATION PROCEDURE MELSEC-F 1) Parameter update Power-on completed Open status Hub connected Open allowed status Closed status Initial normal completion BFM#27=0001 Hub connected signal BFM #28b7 OPEN status CLOSE OPEN CLOSE CLOSE OPEN CLOSE OPEN/ CLOSE instruction 0005 instruction instruction status processing processing...
  • Page 102 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.
  • Page 103 COMMUNICATION PROCEDURE MELSEC-F 1) The open request signal turns off by writing "8000 " 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.
  • Page 104 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 is 1.
  • Page 105 COMMUNICATION PROCEDURE MELSEC-F • For FX Series PLCs Program example for the unit No. 1 M8000 [MOV K4M110 ] Status Read of status Initial Initial completion completion signal status X000 M117 M103 (M100 Open request Open Initial Link Cancel (Self-holding) request completion status...
  • Page 106: Passive Open Processing/close Processing

    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.
  • Page 107 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 "0001 ") 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.
  • Page 108 COMMUNICATION PROCEDURE MELSEC-F • For FX Series PLCs Program example for the unit No. 1 X0:ON Open X0:OFF Close M8000 [MOV K4M110 ] Status Read of status Initial Initial completion completion signal status X000 M103 (M100 Open Open Initial Cancel of request request completion...
  • Page 109 COMMUNICATION PROCEDURE MELSEC-F Parameter communication Power-on completed Open status Open allowed status (closed) (*1) (Active open acknowledge enabled) Closed status Initial normal completion BFM#27="0001 " 0001 8000 0001 OPEN/ CLOSE operation TO BFM#1602 OPEN/ CLOSE status 0000 0003 0005 0009 0000 0003 FROM BFM#1602...
  • Page 110 COMMUNICATION PROCEDURE MELSEC-F POINT This example uses connection number 1 for explanation. Use the appropriate BFM signals and bits for other connection numbers. NOTE (1) If the settings of the connection need modifying, the modifications should be done before writing the open instruction to the buffer memory. (2) Once open processing is executed, an open request cannot be canceled before the open processing is completed.
  • Page 111 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 is 1.
  • Page 112 COMMUNICATION PROCEDURE MELSEC-F • For FX Series PLCs Program example for the unit No. 1 M8000 [MOV K4M110 ] Status Read status Initial Initial completion completion signal status X000 M103 (M100 Open Open Initial Cancel of request request completion self- (Self- status holding...
  • Page 113: Udp/ip Open Processing/close Processing

    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.
  • Page 114 COMMUNICATION PROCEDURE MELSEC-F • For FX Series PLCs Program example for the unit No. 1 <<Open processing for connection No.1>> M8000 [MOV K4M110 ] Status Status read value Initial Initial completion completion signal status X000 [MOVP G1602 OPEN Open Initial instruction/ request completion...
  • Page 115 COMMUNICATION PROCEDURE MELSEC-F Parameter Power-on update completed Open status Closed status Initial normal completion BFM#27=001 OPEN/CLOSE instruction and status BFM#1602 W0001 R0005 0000 0009 8000 0000 Open completion signal BFM#20480 Internal Internal processing processing 1) After communicating the parameter settings, confirm the normal completion of the Ethernet module initial processing.
  • Page 116: Pairing Open

    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.
  • Page 117: Example Of Pairing Open Settings

    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.
  • Page 118 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 •...
  • Page 119: Hub Connection Status Monitor Function

    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 Ethernet module...
  • Page 120: Fixed Buffer Communication (with The Procedure Exist Control Method)

    FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F 6 FIXED 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.
  • Page 121 FIXED 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) •...
  • Page 122: Sending Control Method

    FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F 6.2 Sending Control Method This section explains the control method when data is sent from the Ethernet module to an external device using the fixed buffer No. 1 and the area corresponding to connection No.
  • Page 123 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F Initial Open Send data Data sending Response processing processing writing receiving Initial processing normally completed BFM#=0001 HUB connection is signal BFM #28 b7 OPEN/CLOSE instruction status BFM#1602=0005 Write the send data word count and the send data in BFM Fixed buffer send instruction...
  • Page 124 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F POINT The destination setting (see Section 5.5) for a connection whose parameters are set in FX Configurator-EN becomes valid when the open completion signal (BFM#20480 corresponding bit) of the Ethernet module switches from off to on. The setting also becomes valid when the each value in BFM#1602 to 1609 is "0005 "...
  • Page 125: Receiving Control Method

    FIXED 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.
  • Page 126 FIXED 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. •...
  • Page 127: Data Format

    FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F 6.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 follows: Header Application data Maximum of 2040 bytes...
  • Page 128: Application Data

    FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F 6.4.2 Application data As shown below, the data code in the application data can be expressed in either binary code or ASCII code. Switching between binary code and ASCII code is performed via the communication data code setting (BFM #24 b1 OFF: binary code, ON: ASCII code).
  • Page 129 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F (2) Subheader The format of the subheader is as shown below. The user does not need to set the subheader when using the Ethernet module since the Ethernet module adds and deletes it. b7 b6 b5 b4 b3 b2 b1 b0 Command/response type...
  • Page 130 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F (3) Data length setting This value indicates the data size of the text (command) section. POINT The data length can be designated in the following range: • Communication using binary code : Maximum of 1017 words (*1) •...
  • Page 131 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F (b) Communication using ASCII code Command format Maximum of 1016 words (H) to (L) (H) to (L) (H) to (L) (H) to (L) Subheader ASCII-BIN conversion Data designation/ storage device for sending/ Data length receiving instructions...
  • Page 132: Programming

    FIXED 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.1 Precautions when creating programs (1) In order to communicate using the fixed buffer, the initial processing and the connection open processing must be completed.
  • Page 133: Fixed Buffer Communication Program Example (with The Procedure Exist Control Method)

    FIXED 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. -1st station -2nd station (1) Execution environment for the program example...
  • Page 134: Fixed Buffer Communication

    FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F (b) Receive program (FX -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 is 0.
  • Page 135 FIXED 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 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.
  • Page 136 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F (Send program) (See Subsection 5.6.1) Open processing program • For FX Series PLCs Program example for the unit No. 0 * <<Reading the status of Ethernet module>> M8000 [MOV K4M300 Initial completed * <<Sending 32 words from D1000 to the external device>>...
  • Page 137 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) MELSEC-F (Receive program) • For FX Series PLCs Program example for the unit No. 0 * <<Storing the data received from the external device to the fixed buffer No.1 in D1000 and later>> * <Receiving status >...
  • Page 138 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F 7 FIXED 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"...
  • Page 139 FIXED 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) As shown in the diagram below, when using each fixed buffer (No.
  • Page 140 FIXED 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 "0001 " in BFM#1610 to #1617) allows the fixed buffer data stored in the fixed buffer data area (BFM#1664 to #9855) to be sent to the specified external (*1) device (BFM#40 to #95).
  • Page 141: Sending Control Method

    FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F 7.2 Sending Control Method This section explains the control method when data is sent from the Ethernet module to an external device using fixed buffer No. 1 and the area corresponding to connection No.
  • Page 142 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F Initial Open Write Response processing Processing sent data receiving Data sending Initial processing normal completion BFM#27=0001 HUB connection is signal BFM#28 b7 OPEN/CLOSE instruction status BFM#1602=0005 Write sent byte count TO instruction and sent data to BFM Fixed buffer send instruction...
  • Page 143: Receiving Control Method

    FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F 7.3 Receiving Control Method This section explains the control method when the Ethernet module receives data from an external device. 7.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.
  • Page 144 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F Data receiving Read the word count FROM for the received data instruction and receive data Notice the receive status 0004 (Success) and receive completion BFM#1611=0001 0002 /0008 (Error issued) of the fixed buffer BFM#1611 1) Upon receiving data from the designated external device (set in the open processing), the Ethernet module processes the following.
  • Page 145: Data Format

    FIXED 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.
  • Page 146: Programming

    FIXED 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.1 Precautions when creating programs (1) In order to communicate using the fixed buffers, the initial processing and the connection open processing must be completed.
  • Page 147: Fixed Buffer Communication Program Example (with The No Procedure Control Method)

    FIXED 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. -1st station -2nd station (1) Execution environment for the program example...
  • Page 148 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F (b) Receive program (FX -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 is 0. 3) Make Operation settings in the following manner.
  • Page 149 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F (2) Outline of the program example (a) Send program (FX -1st station) 1) After setting each parameter with FX Configurator-EN 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.
  • Page 150 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F (Send program) • For FX Series PLCs Program example for the unit No. 0 * <<Reading the status of Ethernet module>> M8000 [MOV K4M300 ] Initial completed * <<Sending 32 words from D1000 to the external device>> Transmission X002 M300...
  • Page 151 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) MELSEC-F (Receive program) • For FX Series PLCs Program example for the unit No. 0 * <<Storing the data received from the external device to the fixed buffer No.2 in D1000 and after>> M8000 [MOV G1611...
  • Page 152: Communication Using Mc Protocol

    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.
  • Page 153: How To Read The Control Procedures Of The Mc Protocol

    COMMUNICATION USING MC PROTOCOL MELSEC-F (2) Remote control of the PLC This function executes remote RUN/STOP operations. Remote operations of the PLC can be performed from the external device side. Send frame Communication data code Function Device memory read/ Batch read/write in bit/ write word units Communication...
  • Page 154: Access Timing On The Plc Side

    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. External device Read/write command Reply to the (*1) (command) command (response)
  • Page 155: Plc Setting For Performing Data Communication

    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 and writing the parameters to the Ethernet module. Operational settings (see Section 4.6.) Initial settings (see Section 5.2) Open settings (see Section 5.5) 8.1.5 Precautions on Data Communication...
  • Page 156: When Communicating Data Using The Mc Protocol

    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.
  • Page 157 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) When an external device writes data to the PLC (Command message) External Area C device side PLC side (Response message) 1) Area C indicates transmission from the external device to the PLC. 2) The program of the external device is generated so that the data is transmitted sequentially from left to right.
  • Page 158: Message Format And Control Procedure

    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"...
  • Page 159 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.
  • Page 160 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) Text (Command) (Data name) The contents and arrangement of the data items in the text differs according to the function to use.
  • Page 161 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) Text (Command) (Data name) The contents and arrangement of the data items in the text differs according to the function to use.
  • Page 162: Contents Of Data Designation Items

    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;...
  • Page 163 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.
  • Page 164 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F NOTE The following example shows the designation of the subheader to the monitoring timer when communicating using MC protocol under the following conditions. (Designated value) • Target station : FX series to which Ethernet module is connected : FF •...
  • Page 165 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Format when communicating in ASCII code (a) The order when sending a command (external device Ethernet module) Application data Subheader PC number Monitoring timer Header "0" "0" "F" "F" "0" "0" "0"...
  • Page 166: Character Area Transmission Data

    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.
  • Page 167 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 Data Data...
  • Page 168 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).
  • Page 169 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).
  • Page 170: List Of Commands And Functions For The Mc Protocol

    WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F 9.2 List of Commands and Functions for The MC protocol The following table lists the commands and functions when an external device accesses the PLC. Number of points Command/response type Processing processed per Function communication Bit units...
  • Page 171: Device Memory Read/write

    WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F 9.3 Device Memory Read/Write This section explains the designations in the control procedure when reading from and writing to the device memory by providing an example. 9.3.1 Commands and device range (1) Commands used for reading from and writing to the device memory Number of points processed per Item Command/response type...
  • Page 172 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Designation method and accessible range of devices. (a) In device read/write, each device is set by a device code and number as shown in the diagram below. B0 B31 Device number (Set in hexadecimal) Device code [Example] In case of D100 D100 = 4420 00000064...
  • Page 173 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F POINT (1) Bit devices and word devices are classified according to the following. Bit devices X, Y, M, S, T (contact), C (contact) Word devices T (current value), C (current value), D, R (2) When word units are designated, always make the head device number of a bit device a multiple of 16 (0, 16...
  • Page 174: Batch Read In Bit Units (command: 00)

    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.
  • Page 175 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Communication in ASCII code (Data name) Head device External device side H L H L H L (Example) Data for the number (Data name) of designed device points Characters for the PLC side number of device points...
  • Page 176: Batch Write In Bit Units (command: 02)

    WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F 9.3.3 Batch write in bit units (command: 02) The examples shown in this section explain the command/response format when batch writing to 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.
  • Page 177 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Communication in ASCII code (Data name) Data for the number Monitoring of designed device points Head device timer Characters for the External device number of device points side H L H (Example) (Data name) PLC side...
  • Page 178: Test In Bit Units (random Write) (command: 04)

    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.
  • Page 179 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Communication in ASCII code (Data name) Designated device Designated device External device side (Example) ON Y45 OFF M60 45 (Octadecimal) = 25 (Hexadecimal) Designated device (Data name) ON S38 PLC side (Example) 9 - 24 9 - 24...
  • Page 180: Batch Read In Word Units (command: 01)

    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 "...
  • Page 181 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Communication in ASCII code (Data name) Head device External device side (Example) Y100 Data for the number (Data name) of designed device 32/16 = 2 points points Characters for the PLC side number of device Y100 (Octadecimal) = 40 (Hexadecimal) points...
  • Page 182 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.
  • Page 183 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) When communicating in ASCII code (Data name) Monitoring timer External Head device device side (4 bytes x 2) x 32=256bytes (Example) Head data Last data (Data name) Low 16bit High 16bit Low 16bit High 16bit PLC side...
  • Page 184: Batch Write In Word Units (command: 03)

    WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F 9.3.6 Batch write in word units (command: 03) The examples shown in this section explain the command/response format when batch writing to a word device memory and bit device memory (16 point units). For more details on the order and contents of data items of the areas marked by "...
  • Page 185 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Communication in ASCII code (Data name) Data for the number of Head device designed device points (Characters for the number of device points) External device side H L H L H L (Example) D100 (Data name)
  • Page 186 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.
  • Page 187 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) When communicating in ASCII code (4 bytes x 2) x 32 = 256 bytes (Data name) Head data Last data Monitoring External timer Head device Low16bit High16bit Low16bit High16bit device side (Example) (Data name) 12345678=00BC614E...
  • Page 188: Test In Word Units (random Write) (command: 05)

    WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F 9.3.7 Test in word units (random write) (command: 05) The examples shown in this section explain the command/response format when writing data by designating word device memories and bit device memories (16 point units) arbitrarily.
  • Page 189 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Communication in ASCII code (Data name) Designated device Device data Designated device Device data Monitoring (ON/OFF timer designation) External device side H L H (Example) 0 A 0 7 B 2 1234 Y20 (Octadecimal) = 10 (Hexadecimal) Designated device...
  • Page 190: Remote Run/stop, Plc Model Name Code Read

    WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F 9.4 Remote RUN/STOP, PLC model name code read This function is used to remotely RUN/STOP a PLC and read the model name of a PLC from an external device. 9.4.1 Commands and control contents This section describes the commands and control contents of the control procedure when controlling the status of the PLC.
  • Page 191: Remote Run (command: 13) / Remote Stop(command: 14)

    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.
  • Page 192 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F POINT • When executing the remote RUN/STOP using other external devices or computer link, the remote RUN/STOP is executed in the order of execution. • When the power of PLC is turned on, then off, and then on again with the remote RUN/STOP executed, the remote RUN/STOP status is canceled and the setting of the PLC's RUN/STOP switch becomes valid.
  • Page 193: Plc Model Name Read (command: 15)

    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.
  • Page 194: Loopback Test

    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...
  • Page 195 WHEN COMMUNICATING DATA USING THE MC PROTOCOL MELSEC-F (2) Performing a loopback test while communicating in ASCII code (Designated byte length 2) +10bytes (Data name) External device side (Example) (Data name) PLC side (Example) (Designated byte length 2) +6bytes POINT The number of the loopback data transmitted by an external device is returned to the external device it is.
  • Page 196: Using The E-mail Function

    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 a personal computer or PLC at a remote location using the network (via the mail server). Executed by operating the buffer memory in a sequence program.
  • Page 197 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. When sending e-mails When receiving e-mails Mail Mail server server (Does not decode) Subject Encode Subject (Base64/7bit)
  • Page 198: Configuration And Environment Of The Applicable System

    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) Internet service provider Internet service provider Router Access range of Ethernet module Router Access range of Ethernet module...
  • Page 199: Precautions For Using The E-mail Function

    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/receiving e-mails to/from a running system and controlling the PLC.
  • Page 200 USING THE E-MAIL FUNCTION MELSEC-F (f) When e-mail communication errors occur, check the error codes stored in the mail send/reception error log area of the buffer memory. (g) If e-mails cannot be received, try one of the following. 1) Execute the mail receive instruction (BFM#14500:0001 ) once.
  • Page 201: E-mail Specifications

    USING THE E-MAIL FUNCTION MELSEC-F 10.4 E-mail Specifications The following table lists the specifications of the e-mail function. Item Specification Attached file 2048 words Data size Main text 256 words When sending: Sends either a file as attachment or main text (select one). Data transfer method When receiving: Receives file as attachment.
  • Page 202: Processing Procedure Of The E-mail Function

    USING THE E-MAIL FUNCTION MELSEC-F 10.5 Processing Procedure of the E-mail Function The following flowchart illustrates the procedure that is required before sending and receiving e-mails: Start When DNS is not used When DNS is used Register the DNS server See Section 10.6 (1) Register the mail address of the local station's Ethernet module Register the mail address of...
  • Page 203: E-mail Settings

    USING THE E-MAIL FUNCTION MELSEC-F 10.6 E-mail Settings This section explains the settings required to send and receive 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)). BFM number Setting name Description of setting...
  • Page 204 USING THE E-MAIL FUNCTION MELSEC-F (2) E-mail settings Set in order to use the e-mail function. [Setting item] BFM number Setting item Description of setting item Setting range/option [Decimal] Set the password to the POP3 server Password 9913 to 9920 —...
  • Page 205 USING THE E-MAIL FUNCTION MELSEC-F (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. 2) Mail address: Designate the mail address of the local station's Ethernet module.
  • Page 206 USING THE E-MAIL FUNCTION MELSEC-F (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).
  • Page 207: Sending/receiving E-mail (attached Files) By The Plc

    USING THE E-MAIL FUNCTION MELSEC-F 10.7 Sending/Receiving E-mail (Attached Files) by the PLC This section explains how to send and receive attached files by e-mail. 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.
  • Page 208 USING THE E-MAIL FUNCTION MELSEC-F The table below shows the buffer memory to be used for sending mail. BFM number Items Contents Decimal (Hexadecimal) 10333 Start mail sending (0001 Mail sending command (285D Ignore (0000 Initial status (0000 10334 Mail sending normally completed (0001 Mail sending status Mail sending abnormally completed (0002 (285E...
  • Page 209 USING THE E-MAIL FUNCTION MELSEC-F • For FX Series PLCs Program example for the unit No. 1 Mail abnormally X000 M102 M103 completed (M100 Mail Mail Mail sending sending normally request instru- completed (Self-holding) ction M100 [MOV G10334 D100 Mail sending Mail Mail request...
  • Page 210 USING THE E-MAIL FUNCTION MELSEC-F [FEND M8000 [ZRST R1000 R1002 Creates Head of text data attached data M8000 [MOV R1234 R1000 Head of attached data [MOV H5678 R1001 [MOV R9ABC R1002 [SRET [END NOTE When an error occurs while sending e-mail from the sending mail server to an external device, an error code is stored in the receiving error log area.
  • Page 211 USING THE E-MAIL FUNCTION MELSEC-F (2) Execution timing of the instruction Initial Mail Mail sending processing sending start completed Initial processing normal completion Writing the mail Writing the necessary data data to BFM for sending a mail to BFM Mail sending request 0000 0000 0001...
  • Page 212 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.
  • Page 213: When Receiving Data In An Attached File

    USING THE E-MAIL FUNCTION MELSEC-F 10.7.2When receiving data in an attached file This section explains the buffer memory addresses and a program to receive e-mail from external devices. The following instruction shows how to read the received attached file. Read the value in BFM#22640 to check if there is incoming mail in the mail server.
  • Page 214 USING THE E-MAIL FUNCTION MELSEC-F POINT (1) The Ethernet module checks whether there is incoming mail in the mail server at the time interval set in the Mail parameter (BFM#9904). If there is incoming mail, the reception information is stored in the following areas of the buffer memory.
  • Page 215 USING THE E-MAIL FUNCTION MELSEC-F (1) Reception using the sequence program The following explains the designation method in a sequence program. • For FX Series PLCs Program example for the unit No. 1 [> G22640 [<> G14501 H8000 (M200 Number of Mail Mail receiving...
  • Page 216 USING THE E-MAIL FUNCTION MELSEC-F (2) Execution timing of the instruction Received Received Received Mail Mail Received Received Received mail count mail count mail count Initial mail count mail count receiving receiving mail count check check check processing check check start completed check...
  • Page 217 USING THE E-MAIL FUNCTION MELSEC-F (3) Sending from a personal computer This section explains how to send e-mails from a PC/UNIX to the Ethernet module. Once an environment that is capable of using the Internet through an application program that handles e-mail is set up, e-mail can be created and sent on the New Message screen.
  • Page 218: Contents Of The Attached Files

    USING THE E-MAIL FUNCTION MELSEC-F 10.7.3Contents 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.
  • Page 219 USING THE E-MAIL FUNCTION MELSEC-F (3) 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.
  • Page 220: Sending E-mail (main Text) By The Plc

    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.
  • Page 221 USING THE E-MAIL FUNCTION MELSEC-F The table below shows the buffer memory to be used for sending mail. BFM number Decimal Item Description (Hexadecimal) 10333 Start mail sending (0001 Mail sending command (285D Ignored (0000 Initial status (0000 10334 Mail sending normal completed (0001 Mail sending status (285E Mail sending abnormal completed (0002...
  • Page 222 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.
  • Page 223: Troubleshooting

    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.
  • Page 224: How To Check Errors Using Led Displays

    TROUBLESHOOTING MELSEC-F 11.1 How to Check Errors Using LED Displays This section describes the errors that can be checked with the LED displays on the front of the Ethernet module. 11.1.1 Checking error display The following can be checked with the LED displays on the front of the Ethernet module.
  • Page 225 TROUBLESHOOTING MELSEC-F (Continued from the previous page) LED name Status to check Cause/corrective action 1) [ERR.] or [COM.ERR] LED turns on. The [SD] LED does not flash • Remove the factors that turn on the [ERR.] or [COM.ERR] LED. 2) Program reviewing is required at data sending.
  • Page 226: How To Turn Off Com.err Led And To Read/clear Error Information

    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.
  • Page 227 TROUBLESHOOTING MELSEC-F (4) How to clear error information by writing to buffer memory Writing to BFM#31800 to 31802 allows clearing the error information and turning off COM.ERR. • For FX Series PLCs HFFFF Set error information to clear G31800 H0000 Error log and LED off instruction G31801 H0001...
  • Page 228: How To Check An Error Through Fx Configurator-en

    TROUBLESHOOTING MELSEC-F 11.2 How to Check an Error Through FX Configurator-EN The status of the various settings for the Ethernet module can be checked using the FX Configurator-EN 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.
  • Page 229: Buffer Memory That Can Be Monitored With The Fx Configurator-en Diagnostic Function

    TROUBLESHOOTING MELSEC-F 11.2.1 Buffer memory that can be monitored with the FX Configurator-EN diagnostic function The following is a list of the buffer memory addresses that can be displayed on the "Ethernet diagnostics" screen of FX Configurator-EN. BFM address Ethernet diagnostics Decimal Applicable buffer memory Display contents...
  • Page 230 TROUBLESHOOTING MELSEC-F BFM address Ethernet diagnostics Decimal Applicable buffer memory Display contents display screen (hexadecimal) 440 to 441 Received TCP packet count Total number of receives (1B8 to 1B9 442 to 443 Received TCP packet count Total number of Sum check error TCP packet discarded due to Sum check error annulments...
  • Page 231: Ethernet Diagnostics

    TROUBLESHOOTING MELSEC-F 11.2.2 Ethernet diagnostics [Purpose] The block status of an Ethernet module, parameter settings, communication status, error log and others can be checked using the Ethernet diagnostic function of FX Configurator-EN. [Operating procedure] FX Configurator-EN Diagnostics Diagnostics [Ethernet diagnostics screen] [Explanation of items] Item Description...
  • Page 232: Checking The Error Information By The Buffer Memory Batch Monitoring Function

    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"...
  • Page 233: Error Code List

    TROUBLESHOOTING MELSEC-F 11.4 Error Code List This section explains the error codes (abnormal codes) for the errors that may occur in each processing when communicating data between the Ethernet module and an external device as well as those generated by processing requests from the local station's FX series PLC.
  • Page 234 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"0001 ", BFM#28...b0: ON) is turns on, but can also be cleared by the following operations.
  • Page 235 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.
  • Page 236 TROUBLESHOOTING MELSEC-F (f) Error log block - Connection No. (starting from BFM#232) 1) The faulty connection No. 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. (g) Error log block - Local station Port No.
  • Page 237 TROUBLESHOOTING MELSEC-F (6) E-mail status storage area (BFM#22640 to 24575) * When the storage count exceeds FFFF times, the count starts from 0 again. (a) E-mail status storage area for reception (BFM#22640 to 23352) 1) Number of mails remaining on the server (BFM#22640) •...
  • Page 238 TROUBLESHOOTING MELSEC-F 7) Receiving error log write pointer (BFM#22648) • This address stores the error log block number where the latest error logging is registered. : No error. (No registration of error log) 1 or more : 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.
  • Page 239 TROUBLESHOOTING MELSEC-F (b) 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. : No mail was sent.
  • Page 240 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. : No error. (No registration of sending error log) 1 or more : Error log block 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.
  • Page 241: End Codes (complete Codes) Returned To An External Device During Data Communication

    TROUBLESHOOTING MELSEC-F 11.4.2 End codes (Complete codes) returned to an external device during data communication This section explains the end codes (complete codes) that are added to responses when communicating using the fixed buffer or the MC protocol. For more details on the error codes that are added to responses during communication using A compatible 1E frames through the MC protocol, see Subsection 11.4.3.
  • Page 242: Abnormal Codes Returned During Communication Using Mc Protocol

    TROUBLESHOOTING MELSEC-F 11.4.3 Abnormal codes returned during communication using MC protocol This section explains the abnormal codes (error codes) that are added to responses when communicating using MC protocol (An abnormal code is added only when an end code is "5B".) For more details on the end codes (error codes) that are added to responses, see Subsection 11.4.2.
  • Page 243: Error Codes Stored In The Buffer Memory

    TROUBLESHOOTING MELSEC-F 11.4.4 Error codes stored in the buffer memory When an error occurs at each data communication processing between the Ethernet module and an external device, the error code (abnormal code) is stored in the buffer memory of the Ethernet module. This section explains the contents of this type of errors and error handling procedures.
  • Page 244 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 • At initial processing, the IP address setting value of the Ethernet module is incorrect. • Correct the IP address. C001 •...
  • Page 245 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 • Correct the data length. C020 Data length exceeds the allowable range. • If the data transmitted is larger than the allowable size, divide and then send it.
  • Page 246 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 When TCP is used, the checksum of the receive C041 • Review the checksum on the external device data is incorrect. side and send the correct value.
  • Page 247 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 The request could not be executed on the target • Correct the network number and PC number. C05F • Correct the content of the read/write request. PLC.
  • Page 248 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 • Execute the initial processing again. C0C7 An Ethernet module system error occurred. • Execute the processing by referring Section 11.5 POINT (3).
  • Page 249 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 • Check whether or not there is a contact failure on the extension connector. • Check whether or not there are any factors Handshake error on TO instruction with a base possibly causing noise.
  • Page 250 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 • Designate an attached file on the sending side. • Check the program on the sending side. An e-mail was received that did not have an •...
  • Page 251 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 • Check whether or not the SMTP server is faulty. C124 A response from the SMTP server timed out. • Check whether or not there is too much load on the network.
  • Page 252 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 Cannot communicate with the POP3 server. C143 • Check if the POP3 server is busy. (Reset response) • Check whether or not the POP3 server is faulty.
  • Page 253 TROUBLESHOOTING MELSEC-F Storage destination Error code (abnormal Description of error Error handling code) BFM# BFM# BFM# BFM# BFM# BFM# 22649 • Correct the designated value of the network C1A7 Incorrect network number was designated. number. • Correct the designated value of the resent C1AC Incorrect resent count was designated.
  • Page 254 TROUBLESHOOTING MELSEC-F 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.
  • Page 255 TROUBLESHOOTING MELSEC-F 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.
  • Page 256: Troubleshooting Flowchart

    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 described in Subsection 11.2.2.
  • Page 257 TROUBLESHOOTING MELSEC-F Perform initial processing. (See Subsection 5.2.1.) Is initial If the initial processing parameters set processing normally completed with FX Configuration-EN and the (BFM#27= (BFM#27= sequence program for initial processing "0001 ") "0001 ") overlap, delete the sequence program for initial processing.
  • Page 258 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.
  • Page 259: Sending Errors During Fixed Buffer Communication (common To Procedure Exist And No Procedure)

    TROUBLESHOOTING MELSEC-F 11.5.1 Sending 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. Are the Execute the open processing of the corresponding connection applicable connection. (For details, LEDs (C1-C8) lit? see Section 5.6.) If so, modify the program.
  • Page 260 TROUBLESHOOTING MELSEC-F Does the Match the protocol with the communication protocol communication protocol (TCP/UDP) of (TCP/UDP) match that of the external device. (For details, see the external device? Section 5.5.) Correct the write condition of Was the "0001 " written to BFM#1610 to 1617.
  • Page 261: Receiving Errors During Fixed Buffer Communication (common To Procedure Exist And No Procedure)

    TROUBLESHOOTING MELSEC-F 11.5.2 Receiving errors during fixed buffer communication (common to procedure exist and no procedure) POINT Perform error code reading while the connection is open. Receiving error If the amount of actually received data is smaller than the length of data expected to be received, the subsequent processing must allow reception of the remaining data.
  • Page 262 TROUBLESHOOTING MELSEC-F Is the parameter for IP address of the Correct the IP address of the external external device correct? Is each Port No. device. of the local and the external station correct? Match the protocol with the Does the communication communication protocol (TCP/UDP) protocol (TCP/UDP) match with that of the external device.
  • Page 263 TROUBLESHOOTING MELSEC-F 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-C8, which are in correspondence with connections 1-8, turn on. For UDP communication When external device communication is possible, LEDs C1-C8, which are in correspondence with connections 1-8 turn on.
  • Page 264: Errors In Communication Using Mc Protocol

    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- Execute the open processing of the ponding connection LEDs applicable connection. (For details, (C1-C8) lit? see Section 5.6.) Send the command to the Ethernet Was a command sent...
  • Page 265 TROUBLESHOOTING MELSEC-F Is the IP address of the Correct the IP address and send the command again. command correct? Are the command formats, such as command type, device Correct the command format. designation, and address designation, designated correctly? Are there any open Check and fix the faulty part.
  • Page 266: Sending Errors During E-mail Communication

    TROUBLESHOOTING MELSEC-F 11.5.4 Sending errors during e-mail communication Sending error Is "0001 " written to BFM#10333? Correct the condition for writing to BFM#10333. Is the value of BFM#10334 set to "0001 "? Are the mail server port numbers set correctly in BFM#24320 and 24388? Set the server port numbers correctly.
  • Page 267: Receiving Errors During E-mail Communication

    TROUBLESHOOTING MELSEC-F 11.5.5 Receiving errors during e-mail communication Receiving error Was the e-mail successfully stored? Is the Fix the content according to the e-mail e-mail receiving error receiving error log (see Section 11.4). log normal? Is "0001 " written to BFM#14500? No inquiry? write "0001 "...
  • Page 268: Appendix

    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 number of connections used concurrently, and how the system is configured.
  • Page 269 APPENDIX MELSEC-F (2) Minimum processing time of communication using MC protocol (batch read and batch write) Tfs = Ke + (Kdt Df) + Scr number of scans required for processing + ACK processing time of external device : Time from when Ethernet module receives request data from personal computer until it completes processing (unit: Ke, Kdt : Constant (refer to the table below)
  • Page 270 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.
  • Page 271: Appendix 2 Ascii Code List

    APPENDIX MELSEC-F Appendix 2 ASCII Code List 0000 (SP) 0001 0010 “ 0011 0100 0101 0110 & 0111 ’ 1000 1001 1010 1011 1100 < 1101 — 1110 > 1111 Appendix 3 References For details on TCP/IP, refer to the DDN Protocol Handbook (3 volumes). Publisher DDN Network Information Center SRI International...
  • Page 272: Appendix 4 Program Examples

    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.
  • Page 273: Appendix 4.1 Program Example For Communication Using Mc Protocol -1

    APPENDIX MELSEC-F Appendix 4.1 Program example for communication using MC protocol -1 The following explains a program, its execution environment and the contents of data communication . (1) Execution environment of the program example (a) PLC side 1) Base module of the Ethernet installed station : FX 2) Ethernet module No.
  • Page 274 APPENDIX MELSEC-F (3) FX Configurator-EN settings Set the PLC parameters as follows. (a) Operation settings Communication data code : ASC II Initial timing : Always wait for OPEN (Communication possible at STOP time) IP address : 172.16.56.99 (AC.10.38.63 (b) Open settings Protocol : TCP Open system...
  • Page 275 APPENDIX MELSEC-F (4) Program on the external device side The program example of the external device shown below accesses the FX 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...
  • Page 276 Base Module installed together with the / ** ** / Ethernet block. / ** ** / / ** ** / / ** Copyright(C) 2005 Mitsubishi Electric ** / / ** Corporation ** / / ** All Rights Reserved ** / / **...
  • Page 277 // Connection completion flag off nErrorStatus=WSAStartup(wVersionRequested,&wsaData); // Winsock Initial processing if (nErrorStatus!=SOCK_OK) { Sockerror(ERROR_INITIAL); // Error handling return (SOCK_NG); printf ("Winsock Version is %ld.%ld\n",HIBYTE(wsaData.wVersion),LOBYTE(wsaData.wVersion)); printf ("FX3U-ENET Test Start\n"); socketno=socket(AF_INET,SOCK_STREAM,0); // Create socket for TCP/IP if (socketno==INVALID_SOCKET){ Sockerror (ERROR_SOCKET); // Error handling return(SOCK_NG);...
  • Page 278 APPENDIX MELSEC-F Closeflag=FLAG_ON; // Connection completion flag ON // Go to non-blocking mode ulCmdArg = 1; ioctlsocket(socketno, FIONBIO, &ulCmdArg); // Set to non-blocking mode strcpy(s_buf, "03FF000A4420000000000500112233445566778899AA"); // D0 to D4 batch write request (1E frame) length=(int)strlen(s_buf); if(send(socketno,s_buf,length,0)==SOCKET_ERROR){ // Data sending Sockerror(ERROR_SEND);...
  • Page 279 APPENDIX MELSEC-F while(1) { length = recv(socketno, &r_buf[rbuf_idx], (BUF_SIZE - rbuf_idx), 0); // Response data receiving if(length == 0) { // Is connection cut off? Sockerror(ERROR_RECIEVE); // Error handling return (SOCK_NG); if(length == SOCKET_ERROR) { nErrorStatus = WSAGetLastError(); if(nErrorStatus != WSAEWOULDBLOCK) { Sockerror(ERROR_RECIEVE);...
  • Page 280 APPENDIX MELSEC-F case ERROR_BIND: printf("Failed to bind."); break; case ERROR_CONNECT: printf("Failed to establish connection."); break; case ERROR_SEND: printf("Sending failed."); break; case ERROR_RECIEVE: printf("Receiving failed."); break; case ERROR_SHUTDOWN: printf("Failed to shutdown."); break; case ERROR_CLOSE: printf("Failed to close normally."); break; printf("Error code is %d.\n", nErrorStatus); if(Closeflag==FLAG_ON){ nErrorStatus=shutdown(socketno,2);...
  • Page 281: Appendix 4.2 Program Example For Communication Using Mc Protocol -2

    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.
  • Page 282 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.
  • Page 283 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...
  • Page 284 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 Client.Connect(IpAddress, PortNum) Catch ex As Exception...
  • Page 285 APPENDIX MELSEC-F End If lstOutput.SelectedIndex = lstOutput.Items.Count - 1 End If ' Line disconnection processing Client.GetStream().Close() Client.Close() End Sub End Class App - 18 App - 18...
  • Page 286: Appendix 5 Differences Between The Ethernet And The Ieee802.3

    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 data link layer header Ethernet module Ethernet frame (V 2.0) specification IEEE802.3 (ISO/IEC8802.3) frame specification (1) Ethernet Destination address Source address...
  • Page 287: Appendix 7 Setting Value Recording Sheets

    APPENDIX MELSEC-F Appendix 7 Setting Value Recording Sheets This section provides setting value recording sheets for parameters set with FX Configurator-EN Make copies as needed. Setting value recording sheet No. FX Configurator-EN setting screen Recording sheet 1 Ethernet operations Recording sheet 2 Ethernet initial settings Recording sheet 3 Ethernet open settings...
  • Page 288 APPENDIX MELSEC-F Recording sheet 2 [Block number Setting data FX Configurator-EN Data item setting screen Setting value Remark TCP ULP Timer initial: 60 (unit: 500 ms) TCP zero initial: 20 (unit: 500 ms) window Timer TCP resend timer initial: 20 (unit: 500 ms) TCP end timer initial: 40 (unit: 500 ms) IP assembly timer...
  • Page 289 APPENDIX MELSEC-F Recording Sheet 3 [Block number Setting data FX Configurator-EN Data item setting screen Setting value Remark Protocol Active Setting not required if Open system Unpassive UDP is selected. Fullpassive Send Fixed buffer Receive Procedure exist Fixed buffer communication No procedure No pairs Paring open...
  • Page 290 APPENDIX MELSEC-F Recording sheet 4 [Block number Setting data FX Configurator-EN Data item setting screen Setting value Remark Sub-net mask pattern Adjust to input format Setting the Ethernet Default router IP address Adjust to input format relay parameter Decimal Router information Input Input format format Hexadecimal...
  • Page 291 APPENDIX MELSEC-F Recording sheet 5 [Block number FX Configurator-EN Setting data Data item setting screen Setting value Remark Password Mail address General Check of received mail Check received mails Check: Check mark settings Set interval value to check received mail. Interval of inquiry Select unit for interval to check received mail.
  • Page 292: Appendix 8 Versioin Information

    APPENDIX MELSEC-F Appendix 8 Versioin Information Ethernet Module version is shown as "VERSION" on the label attached to the right side of the module as seen from the front. Right side Version App - 25 App - 25...
  • Page 293 Warranty Please confirm the following product warranty details before using this product. 1. Gratis Warranty Term and Gratis Warranty Range 2. Onerous repair term after discontinuation of production If any faults or defects (hereinafter "Failure") found to be the responsibility of Mitsubishi occurs during use of the Mitsubishi shall accept onerous product repairs for product within the gratis warranty term, the product shall be seven (7) years after production of the product is...
  • Page 294 Revised History Date Revision Description 10/2005 First Edition 9/2007 - The FX Series was added - Clerical error correction 9/2008 Clerical error correction 11/2009 - Change for the Ethernet module V1.10 are applied. - The FX Series was added - Clerical error correction 7/2010 - Power supply specifications description modified.
  • Page 296 -ENET USER’S MANUAL HEAD OFFICE: TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN FX3U-ENET-U-E MODEL 09R716 MODEL CODE JY997D18101G Effective July 2017 (MEE) Specifications are subject to change without notice.

This manual is also suitable for:

Fx3u-enet-l

Comments to this Manuals

Symbols: 0
Latest comments: