Mitsubishi Electronics FX3U Manuale Utente

FX3U-ENET-LUSER'S MANUAL

A - 8 A - 811 TROUBLESHOOTING 11- 1 to 11-4211.1 How to Check Errors Using LED Displays ...

5 - 30MELSEC-FCOMMUNICATION PROCEDURE55 - 301) The open request signal turns off by writing "8000H" to the BFM#1602.2) The Ethernet module e

5 - 31MELSEC-FCOMMUNICATION PROCEDURE55 - 31Program exampleThis example explains a program for open processing/close processing when Active open is se

5 - 32MELSEC-FCOMMUNICATION PROCEDURE55 - 32• Program example for the unit No. 1X000M100M103X000M102[= D100 H5 ]]H10D100[=]H0D100[=[MOV D100(M100(M101

5 - 33MELSEC-FCOMMUNICATION PROCEDURE55 - 335.6.2 Passive open processing/close processingThis section explains the procedure for opening and closing

5 - 34MELSEC-FCOMMUNICATION PROCEDURE55 - 341) After the parameters are sent, the normal completion of the Ethernet module initial processing is confi

5 - 35MELSEC-FCOMMUNICATION PROCEDURE55 - 35• Program example for the unit No. 1X000M100M103X000M102[= D100 H15 ][= D100 H10 ][= D100 H5 ][= D100 H3 ]

5 - 36MELSEC-FCOMMUNICATION PROCEDURE55 - 36*1 If an open request (SYN) received after the normal completion of an initial processing and before the E

5 - 37MELSEC-FCOMMUNICATION PROCEDURE55 - 37NOTE(1) If the settings of the connection need modifying, the modifications should be done before writing

5 - 38MELSEC-FCOMMUNICATION PROCEDURE55 - 38Program exampleThis example explains a program for open processing/close processing when Unpassive open is

5 - 39MELSEC-FCOMMUNICATION PROCEDURE55 - 39• Program example for the unit No. 1X000M100M103X000M102[= D100 H15 ][= D100 H10 ][= D100 H5 ][= D100 H3 ]

A - 9 A - 9About ManualsThis manual explains the mounting of FX3U-ENET-L, the specifications, broadcast functions and communication methods.For the in

5 - 40MELSEC-FCOMMUNICATION PROCEDURE55 - 405.6.3 UDP/IP open processing/close processingThe following explains the UDP/IP open processing.The operati

5 - 41MELSEC-FCOMMUNICATION PROCEDURE55 - 41• Program example for the unit No. 1X000[= D100 H15 ][= D100 H10 ][= D100 H5 ][MOV D100 ][INCP D0 ][INCP D

5 - 42MELSEC-FCOMMUNICATION PROCEDURE55 - 421) After communicating the parameter settings, confirm the normal completion of the Ethernet module initia

5 - 43MELSEC-FCOMMUNICATION PROCEDURE55 - 435.7 Pairing OpenThe following explains communication using the paring open method via the Ethernet module.

5 - 44MELSEC-FCOMMUNICATION PROCEDURE55 - 445.7.2 Example of pairing open settingsThis section explains the settings in order to communicate in the pa

5 - 45MELSEC-FCOMMUNICATION PROCEDURE55 - 45(7) Local station Port No. (BFM#40, 47)Set this for the receiving connection for receiving only. (Setting

5 - 46MELSEC-FCOMMUNICATION PROCEDURE55 - 465.8 Hub Connection Status Monitor FunctionThe current connection status of the Ethernet module and hub, th

6 - 1FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 16MELSEC-F6 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL

6 - 2FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 26MELSEC-F(3) At data sending/receiving, the Ethernet module processes t

6 - 3MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 36.2 Sending Control MethodThis section explains the control met

A - 10 A - 10Applicable StandardCertification of UL, cUL standardsThe following product has UL and cUL certification.UL, cUL File Number: E95239Mode

6 - 4MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 41) Confirm the normal completion of the initial processing.2) C

6 - 5MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 5POINTThe destination setting (see Section 5.5) for a connection

6 - 6MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 66.3 Receiving Control MethodThis section explains the control m

6 - 7MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 71) Confirm the normal completion of the open processing of conn

6 - 8MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 86.4 Data FormatWhen communicating between the Ethernet module a

6 - 9MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 96.4.2 Application dataAs shown below, the data code in the appl

6 - 10MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 10(2) SubheaderThe format of the subheader is as shown below. T

6 - 11MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 11(3) Data length settingThis value indicates the data size of

6 - 12MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 12(b) Communication using ASCII code(Example)(5) End codesFor m

6 - 13MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 136.5 ProgrammingThis section explains the programming method w

A - 11 A - 11Caution to conform with EC Directives• Installation in EnclosureProgrammable logic controllers are open-type devices that must be install

6 - 14MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 146.5.2 Fixed buffer communication program example (with the pr

6 - 15MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 15(b) Receive program (FX3U-2nd station)1) Connection No. 1 is

6 - 16MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 16(2) Outline of the program example(a) Send program (Ethernet

6 - 17MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 17(Send program)(See Subsection 5.6.1)• Program example for the

6 - 18MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD)66 - 18(Receive program)• Program example for the unit No. 0M8000[MO

7 - 1FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 17MELSEC-F7 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHO

7 - 2FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 27MELSEC-F(2) Data can be communicated with the following external devices.

7 - 3MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 3(3) At data sending/receiving, the Ethernet module processes the f

7 - 4MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 47.2 Sending Control MethodThis section explains the control method

7 - 5MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 51) Confirm normal completion of the initial processing.2) Confirm

A - 12 A - 12The Manual's Usage and StructureHow to use this manualIn this manual, explanations are given for each application of the Ethernet mo

7 - 6MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 67.3 Receiving Control MethodThis section explains the control meth

7 - 7MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 71) Upon receiving data from the designated external device (set in

7 - 8MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 87.4 Data FormatWhen communicating between the Ethernet module and

7 - 9MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 97.5 ProgrammingThis section explains the programming method when t

7 - 10MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 107.5.2 Fixed buffer communication program example (with the no pr

7 - 11MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 11(b) Receive program (FX3U -2nd station)1) Connection No. 2 is us

7 - 12MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 12(2) Outline of the program example(a) Send program (FX3U-1st sta

7 - 13MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 13(Send program)• Program example for the unit No. 0M8000X002 M300

7 - 14MELSEC-FFIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD)77 - 14(Receive program)•Program example for the unit No. 0U0\G2688Rece

8 - 1COMMUNICATION USING MC PROTOCOL88 - 18MELSEC-F8 COMMUNICATION USING MC PROTOCOLThis chapter gives an overview of the MC protocol.NOTEThe frame ty

A - 13 A - 13(3) Connection between the Ethernet module and external devices(a) Communication procedures• Section 5.1 describes an outline of the comm

8 - 2COMMUNICATION USING MC PROTOCOL88 - 28MELSEC-F(2) Remote control of the PLCThis function executes remote RUN/STOP operations.Remote operations of

8 - 3MELSEC-FCOMMUNICATION USING MC PROTOCOL88 - 38.1.3 Access Timing on the PLC SideThe following diagram illustrates the access timing on the PLC si

8 - 4MELSEC-FCOMMUNICATION USING MC PROTOCOL88 - 48.1.4 PLC setting for performing data communicationData communication via MC protocol is enabled by

8 - 5MELSEC-FCOMMUNICATION USING MC PROTOCOL88 - 5MEMO

9 - 1WHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 19MELSEC-F9 WHEN COMMUNICATING DATA USING THE MC PROTOCOLThis chapter explains the message form

9 - 2WHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 29MELSEC-F(2) When an external device writes data to the PLC1) Area C indicates transmission fr

9 - 3MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 39.1.2 Message format and control procedureThis section explains the message format and

9 - 4MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 4(2) Control procedureThe following diagrams illustrate the control procedure for commu

9 - 5MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 52) When writing data to the local station PLC from the external device side(b) Communi

9 - 6MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 62) When writing data to the local station PLC from the external device sideExternal de

A - 14 A - 14About the Generic Terms and AbbreviationsThis manual uses the following generic terms and abbreviations to describe the Model FX3U-ENET-

9 - 7MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 79.1.3 Contents of data designation itemsThis section explains the data items of comman

9 - 8MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 8(6) Character field (response)This data contains data read/processing result when an e

9 - 9MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 9NOTEThe following example shows the designation of the subheader to the monitoring tim

9 - 10MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 10(2) Format when communicating in ASCII code(a) The order when sending a command (ext

9 - 11MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 119.1.4 Character area transmission dataThis section explains how to transmit the bit

9 - 12MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 12(b) When reading from or writing to a word device memoryEach word of the word device

9 - 13MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 13(2) Data communication using binary code(a) When reading to or writing from the bit

9 - 14MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 14(b) Reading from or writing to a word device memoryEach word of a word device memory

9 - 15MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 159.2 List of Commands and Functions for The MC protocolThe following table lists the

9 - 16MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 169.3 Device Memory Read/WriteThis section explains the designations in the control pr

1 - 1OVERVIEW11 - 11MELSEC-F1OVERVIEWThis manual provides information on the specifications of the Ethernet interface block, FX3U-ENET-L (hereinafter

9 - 17MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 17(2) Designation method and accessible range of devices.(a) In device read/write, eac

9 - 18MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 18POINT(1) Bit devices and word devices are classified according to the following. Bit

9 - 19MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 199.3.2 Batch read in bit units (command: 00)The examples shown in this section explai

9 - 20MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 20(2) Communication in ASCII codeNOTE(1) Use the designation "00H" when the

9 - 21MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 219.3.3 Batch write in bit units (command: 02)The examples shown in this section expla

9 - 22MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 22(2) Communication in ASCII codeNOTEIf the number of device points to be set is an od

9 - 23MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 239.3.4 Test in bit units (random write) (command: 04)The examples shown in this secti

9 - 24MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 24(2) Communication in ASCII code(Data name)External deviceside(Example)Designated dev

9 - 25MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 259.3.5 Batch read in word units (command: 01)The examples shown in this section expla

9 - 26MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 26(2) Communication in ASCII code30H38H30H031H41H35HY10032/16 = 2 points31H146HFHLF46H

1 - 2OVERVIEW11 - 21MELSEC-F1) Collection and modification of PLC data(Communication using the MELSEC Communication Protocol (referred to below as the

9 - 27MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 27NOTEC200 to C255 (Current Values) Batch ReadSince C200 to C255 are 32 bit devices, t

9 - 28MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 28(2) When communicating in ASCII code*030HHF46H*131HLF46HH030H-030H-030HLA41H838H131H

9 - 29MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 299.3.6 Batch write in word units (command: 03)The examples shown in this section expl

9 - 30MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 30(2) Communication in ASCII codeF30H038HD10033H346H46H30H030H030H041HA34H434H432H230H

9 - 31MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 31NOTEC200 to C255 (Current Values) Batch WriteSince C200 toC255 are 32 bit devices, t

9 - 32MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 32(2) When communicating in ASCII code*030HHF46H*333HLF46HH030H-030H-030HLA41H838H333H

9 - 33MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 339.3.7 Test in word units (random write) (command: 05)The examples shown in this sect

9 - 34MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 34(2) Communication in ASCII codeY2030H35H46H46H30H30H30H41H30H33H30H30H35H39H32H30H31

9 - 35MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 359.4 Remote RUN/STOP, PLC model name code readThis function is used to remotely RUN/S

9 - 36MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 369.4.2 Remote RUN (command: 13) / Remote STOP(Command: 14)The examples shown in this

1 - 3MELSEC-FOVERVIEW11 - 31.2 Features of the Ethernet Module(1) Data communication using MC protocol (Details are explained in Chapter 8 and Chapter

9 - 37MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 37POINT• When executing the remote RUN/STOP using other external devices or computer l

9 - 38MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 389.4.3 PLC model name read (command: 15)The examples shown in this section explains t

9 - 39MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 399.5 Loopback TestA loopback test checks whether or not the communication function be

9 - 40MELSEC-FWHEN COMMUNICATING DATA USING THE MC PROTOCOL99 - 40(2) Performing a loopback test while communicating in ASCII codePOINTThe number of t

10 - 1USING THE E-MAIL FUNCTION1010 - 110MELSEC-F10 USING THE E-MAIL FUNCTIONThis chapter explains e-mail functions of the Ethernet module.10.1 E-mail

10 - 2USING THE E-MAIL FUNCTION1010 - 210MELSEC-F(2) Data conversion method used by the Ethernet moduleThe following shows the data conversion method

10 - 3MELSEC-FUSING THE E-MAIL FUNCTION1010 - 310.2 Configuration and Environment of the Applicable SystemThis section explains the environment and sy

10 - 4MELSEC-FUSING THE E-MAIL FUNCTION1010 - 410.3 Precautions for Using the E-mail FunctionThe following explains precautions when using the e-mail

10 - 5MELSEC-FUSING THE E-MAIL FUNCTION1010 - 510.4 E-mail SpecificationsThe following table lists the specifications of the e-mail function.NOTEMail

10 - 6MELSEC-FUSING THE E-MAIL FUNCTION1010 - 610.5 Processing Procedure of the E-mail FunctionThe following flowchart illustrates the procedure that

1 - 4MELSEC-FOVERVIEW11 - 4(3) Sending by e-mail (Details are explained in Chapter 10)In "E-mail send", data can be sent to and from an exte

10 - 7MELSEC-FUSING THE E-MAIL FUNCTION1010 - 710.6 E-mail SettingsThis section explains the settings required to send e-mails.(1) DNS settingsSpecify

10 - 8MELSEC-FUSING THE E-MAIL FUNCTION1010 - 8(2) E-mail settingsSet in order to use the e-mail function.[Setting item]*1 The setting is required onl

10 - 9MELSEC-FUSING THE E-MAIL FUNCTION1010 - 9(c) SMTP authentication setting1) Set the authentication method for the outgoing mail server (SMTP).The

10 - 10MELSEC-FUSING THE E-MAIL FUNCTION1010 - 1010.7 Sending E-mail (Attached Files) by the PLCThis section explains how to send attached files when

10 - 11MELSEC-FUSING THE E-MAIL FUNCTION1010 - 11The table below shows the buffer memory to be used for sending mail.(1) Send using the sequence progr

10 - 12MELSEC-FUSING THE E-MAIL FUNCTION1010 - 12• Program example for the unit No. 1 X000M100M102 M103M101D100.1D100.0D100.FM8029M101[MOV D100 K100

10 - 13MELSEC-FUSING THE E-MAIL FUNCTION1010 - 13M8000[MOV R1234 R1000 ]][MOV H5678 R1001R1002][MOV R9ABC ][FEND[SRET ][END ]P0Head ofattacheddata[ZRS

10 - 14MELSEC-FUSING THE E-MAIL FUNCTION1010 - 14(2) Execution timing of the instruction1) Check whether the initial processing has been completed nor

10 - 15MELSEC-FUSING THE E-MAIL FUNCTION1010 - 15(3) Receiving with a personal computerThe following explains how a PC/UNIX receives e-mails sent from

10 - 16MELSEC-FUSING THE E-MAIL FUNCTION1010 - 1610.7.2Contents of the attached filesThe following explains the contents of the attached file data.The

1 - 5MELSEC-FOVERVIEW11 - 5(4) Connecting FX Configurator-EN-L (Details are explained in the Operating Manuals for FX Configurator-EN-L)(a) Simplifyin

10 - 17MELSEC-FUSING THE E-MAIL FUNCTION1010 - 1710.8 Sending E-mail (Main Text) by the PLCThis section explains how to send the main text of e-mail.1

10 - 18MELSEC-FUSING THE E-MAIL FUNCTION1010 - 18The table below shows the buffer memory to be used for sending mail.BFM numberItem DescriptionDecimal

10 - 19MELSEC-FUSING THE E-MAIL FUNCTION1010 - 19(1) Send using the sequence programMethod for sending e-mails by the sequence program is similar to t

11 - 1TROUBLESHOOTING1111 - 111MELSEC-F11 TROUBLESHOOTINGThis section explains the contents of the errors that may occur during communication between

11 - 2TROUBLESHOOTING1111 - 211MELSEC-F11.1 How to Check Errors Using LED DisplaysThis section describes the errors that can be checked with the LED d

11 - 3MELSEC-FTROUBLESHOOTING1111 - 3(Continued from the previous page)*1 Confirm the completion for the initial processing and check whether or not t

11 - 4MELSEC-FTROUBLESHOOTING1111 - 411.1.2 How to turn off COM.ERR LED and to read/clear error informationThis section explains how to turn off [COM.

11 - 5MELSEC-FTROUBLESHOOTING1111 - 5(4) How to clear error information by writing to buffer memoryWriting to BFM#31800 to 31802 allows clearing the e

11 - 6MELSEC-FTROUBLESHOOTING1111 - 611.2 How to Check an Error Through FX Configurator-EN-LThe status of the various settings for the Ethernet module

11 - 7MELSEC-FTROUBLESHOOTING1111 - 711.2.1 Buffer memory that can be monitored with the FX Configurator-EN-L diagnostic functionThe following is a li

1 - 6MELSEC-FOVERVIEW11 - 6(b) Connecting multiple MELSOFT products (GX Developer, MX Component)This product can be connected with one or more MELSOFT

11 - 8MELSEC-FTROUBLESHOOTING1111 - 8BFM address Decimal(hexadecimal)Applicable buffer memoryEthernet diagnostics display screenDisplay contents408 to

11 - 9MELSEC-FTROUBLESHOOTING1111 - 911.2.2 Ethernet diagnostics[Purpose]The block status of an Ethernet module, parameter settings, communication sta

11 - 10MELSEC-FTROUBLESHOOTING1111 - 1011.3 Checking the error information by the buffer memory batch monitoring functionIt is explained here how the

11 - 11MELSEC-FTROUBLESHOOTING1111 - 1111.4 Error Code ListThis section explains the error codes (abnormal codes) for the errors that may occur in eac

11 - 12MELSEC-FTROUBLESHOOTING1111 - 12(1) Initial error code (BFM#105)(a) This address stores the error codes generated when the initial processing i

11 - 13MELSEC-FTROUBLESHOOTING1111 - 13(5) Error log area (BFM#227 to 372)This area stores the following errors.• Errors whose source cannot be confir

11 - 14MELSEC-FTROUBLESHOOTING1111 - 14(f) Error log block - Connection No. (starting from BFM#232)1) The faulty connection No. is stored in bits 0 to

11 - 15MELSEC-FTROUBLESHOOTING1111 - 15(6) E-mail status storage area (BFM#22640 to 24575)* When the storage count exceeds FFFFH times, the count star

11 - 16MELSEC-FTROUBLESHOOTING1111 - 166) Sending error log write pointer (BFM#23360)• This address stores the error log block area number where the l

11 - 17MELSEC-FTROUBLESHOOTING1111 - 1711.4.2 End codes (Complete codes) returned to an external device during data communicationThis section explains

1 - 7MELSEC-FOVERVIEW11 - 71.3 Software ConfigurationThe Ethernet modules support the TCP/IP and UDP/IP protocols.(1) TCP (Transmission Control Protoc

11 - 18MELSEC-FTROUBLESHOOTING1111 - 1811.4.3 Abnormal codes returned during communication using MC protocolThis section explains the abnormal codes (

11 - 19MELSEC-FTROUBLESHOOTING1111 - 1911.4.4 Error codes stored in the buffer memoryWhen an error occurs at each data communication processing betwee

11 - 20MELSEC-FTROUBLESHOOTING1111 - 20Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

11 - 21MELSEC-FTROUBLESHOOTING1111 - 21Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

11 - 22MELSEC-FTROUBLESHOOTING1111 - 22*1 When this error occurs, the COM.ERR light turns on, but turns off again about one second later.Error code (a

11 - 23MELSEC-FTROUBLESHOOTING1111 - 23Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

11 - 24MELSEC-FTROUBLESHOOTING1111 - 24Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

11 - 25MELSEC-FTROUBLESHOOTING1111 - 25Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

11 - 26MELSEC-FTROUBLESHOOTING1111 - 26Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

11 - 27MELSEC-FTROUBLESHOOTING1111 - 27Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

1 - 8MELSEC-FOVERVIEW11 - 8(2) UDP (User Datagram Protocol)This protocol may not guarantee data credibility or reliability in communication between a

11 - 28MELSEC-FTROUBLESHOOTING1111 - 28Error code (abnormal code)Description of error Error handlingStorage destinationInitialOpenFixed sendingConnect

11 - 29MELSEC-FTROUBLESHOOTING1111 - 29* 1 Take corrective action using the following procedure.1) Check whether the expansion connectors are conne

11 - 30MELSEC-FTROUBLESHOOTING1111 - 30(1) When communication is performed using fixed buffer (with procedure)(a) If the data length specified immedia

11 - 31MELSEC-FTROUBLESHOOTING1111 - 31(2) When communication is performed using fixed buffer (non-procedure)Since no message data length is specified

11 - 32MELSEC-FTROUBLESHOOTING1111 - 3211.5 Troubleshooting FlowchartThis section explains some simple troubleshooting procedures when the Ethernet mo

11 - 33MELSEC-FTROUBLESHOOTING1111 - 33*1 See Section 11.1 when the value of BFM#27 is "0000H" or when the display LED COM.ERR (communicatio

11 - 34MELSEC-FTROUBLESHOOTING1111 - 34POINT(1) When the Ethernet module is replaced due to an error, reboot the following external devices and restar

11 - 35MELSEC-FTROUBLESHOOTING1111 - 3511.5.1 Sending errors during fixed buffer communication (common to procedure exist and no procedure)Sending er

11 - 36MELSEC-FTROUBLESHOOTING1111 - 36POINTIf the external device communicates normally, the following conditions occur. For TCP communicationWhen t

11 - 37MELSEC-FTROUBLESHOOTING1111 - 3711.5.2 Receiving errors during fixed buffer communication (common to procedure exist and no procedure)POINTPer

1 - 9MELSEC-FOVERVIEW11 - 93) PSH (Push Flag)When this bit is ON (1), the host that has received this segment sends the data to the upper application

11 - 38MELSEC-FTROUBLESHOOTING1111 - 38Does the external device operate normally?YESThe Ethernet module hardware onthe sending side may be faulty.Cons

11 - 39MELSEC-FTROUBLESHOOTING1111 - 39POINTIf the external device communicates normally, the following conditions occur. For TCP communicationWhen t

11 - 40MELSEC-FTROUBLESHOOTING1111 - 4011.5.3 Errors in communication using MC protocolCommunication errorCheck the open status of the connection with

11 - 41MELSEC-FTROUBLESHOOTING1111 - 41POINT• If the external device communicates normally, the following conditions occur.For TCP communicationWhen t

11 - 42MELSEC-FTROUBLESHOOTING1111 - 4211.5.4 Sending errors during e-mail communicationIs "0001H" written toBFM#10333?NOYESCorrect the cond

App - 1APPENDIXApp - 1 AppMELSEC-FAPPENDIXAppendix 1 Processing TimeCalculate the minimum processing time for each function using the expressions belo

App - 2APPENDIXApp - 2AppMELSEC-F(2) Minimum processing time of communication using MC protocol (batch read and batch write)Tfs = Ke + (Kdt Df) + Sc

App - 3MELSEC-FAPPENDIXApp - 3[Calculation example 1]Calculate the required time (unit: ms) to complete the processing of a data request from a PC aft

App - 4MELSEC-FAPPENDIXApp - 4Appendix 2 ASCII Code ListAppendix 3 ReferencesFor details on TCP/IP, refer to the DDN Protocol Handbook (3 volumes).Pub

App - 5MELSEC-FAPPENDIXApp - 5Appendix 4 Program ExamplesThe program examples presented in this section test the connection between the Ethernet modul

2 - 1SYSTEM CONFIGURATIONS22 - 12MELSEC-F2 SYSTEM CONFIGURATIONSThis section explains the system configurations that may be combined with the Ethernet

App - 6MELSEC-FAPPENDIXApp - 6Appendix 4.1 Program example for communication using MC protocol -1The following explains a program, its execution envir

App - 7MELSEC-FAPPENDIXApp - 7(3) FX Configurator-EN-L settingsSet the PLC parameters as follows.(a) Operation settings(b) Open settingsCommunication

App - 8MELSEC-FAPPENDIXApp - 8(4) Program on the external device sideThe program example of the external device shown below accesses the FX3U of the s

App - 9MELSEC-FAPPENDIXApp - 9#include <stdio.h>#include <winsock.h>#define FLAG_OFF 0 // Completion flag OFF#define FLAG_ON 1 // Completi

App - 10MELSEC-FAPPENDIXApp - 10int main(){WORD wVersionRequested=MAKEWORD(1,1); // Winsock Ver 1.1 request WSADATA wsaData;int length; // Communicati

App - 11MELSEC-FAPPENDIXApp - 11Closeflag=FLAG_ON; // Connection completion flag ON// Go to non-blocking modeulCmdArg = 1;ioctlsocket(socketno, FIONBI

App - 12MELSEC-FAPPENDIXApp - 12while(1) {length = recv(socketno, &r_buf[rbuf_idx], (BUF_SIZE - rbuf_idx), 0); // Response data receivingif(length

App - 13MELSEC-FAPPENDIXApp - 13case ERROR_BIND:printf("Failed to bind.");break;case ERROR_CONNECT:printf("Failed to establish connecti

App - 14MELSEC-FAPPENDIXApp - 14Appendix 4.2 Program example for communication using MC protocol -2This section explains an example of an external dev

App - 15MELSEC-FAPPENDIXApp - 15(4) Window example (Form 1)(5) Sample program (Form 1)Parts in italic are created automatically by Visual Basic .NET,

2 - 2SYSTEM CONFIGURATIONS22 - 22MELSEC-F2.2 Devices Required for Network ConfigurationThis section explains the devices that are required to configur

App - 16MELSEC-FAPPENDIXApp - 16Memo: The following procedure is necessary for Windows Form Designer.Change by using Windows Form Designer.Do not use

App - 17MELSEC-FAPPENDIXApp - 17Dim RxResponse As StringDim Temp As StringDim j As IntegerDim Dreg(5) As DoubleDim DregStr$Dim SubHeader$' IP Add

App - 18MELSEC-FAPPENDIXApp - 18End IflstOutput.SelectedIndex = lstOutput.Items.Count - 1End If' Line disconnection processingClient.GetStream().

App - 19MELSEC-FAPPENDIXApp - 19Appendix 5 Differences between the Ethernet and the IEEE802.3The following shows the Ethernet header in the data link

App - 20MELSEC-FAPPENDIXApp - 20Appendix 7 Setting Value Recording SheetsThis section provides setting value recording sheets for parameters set with

App - 21MELSEC-FAPPENDIXApp - 21Recording sheet 2[Block number ]FX Configurator-EN-Lsetting screenData itemSetting dataSetting value R

App - 22MELSEC-FAPPENDIXApp - 22Recording Sheet 3[Block number ]FX Configurator-EN-Lsetting screenData itemSetting dataSetting value R

App - 23MELSEC-FAPPENDIXApp - 23Recording sheet 4[Block number ]FX Configurator-EN-Lsetting screenData itemSetting dataSetting value R

App - 24MELSEC-FAPPENDIXApp - 24Recording sheet 5[Block number ]FX Configurator-EN-Lsetting screenData itemSetting dataSetting value R

App - 25MELSEC-FAPPENDIXApp - 25Appendix 8 Versioin InformationEthernet Module version is shown as "VERSION" on the label attached to the ri

2 - 3MELSEC-FSYSTEM CONFIGURATIONS22 - 3(2) Connection using the 10BASE-TUse devices that satisfy the standards of IEEE802.3 and 10BASE-T.• Shielded t

App - 26MELSEC-FAPPENDIXApp - 26MEMO

WarrantyPlease confirm the following product warranty details before using this product. 1. Gratis Warranty Term and Gratis Warranty Range If any faul

Revised HistoryDate Revision Description10/2009 A First Edition

HEAD OFFICE: TOKYO BULDING, 2-7-3 MARUNOUCHI, CHYODA-KU, TOKYO 100-8310, JAPAN HIMEJI WORKS: 840, CHIYODA CHO, HIMEJI, JAPANJY997D38001A(MEE)Effecti

3 - 1SPECIFICATIONS33 - 13MELSEC-F3 SPECIFICATIONSThis section explains the Ethernet module performance specifications and transmission specifications

A - 1 A - 1SAFETY PRECAUTIONS(Read these precautions before use.)Before installation, operation, maintenance or inspection of this product, thoroughly

3 - 2SPECIFICATIONS33 - 23MELSEC-F *1 The setting is required only when "POP before SMTP" is selected in the SMTP authentication method.NOTE

3 - 3MELSEC-FSPECIFICATIONS33 - 33.2 Data Codes for CommunicationThis section explains the data codes used in the communication between the Ethernet m

3 - 4MELSEC-FSPECIFICATIONS33 - 42) Ethernet module PLCData is sent and received in binary code.(2) When communicating using ASCII code, 1-byte binary

3 - 5MELSEC-FSPECIFICATIONS33 - 53.3 Relationship between the External Devices and Additional Functions for Each Communication FunctionThis section ex

3 - 6MELSEC-FSPECIFICATIONS33 - 63.4 Ethernet Module Function ListThis section shows a list of Ethernet module functions.(1) Basic functions of the Et

3 - 7MELSEC-FSPECIFICATIONS33 - 73.5 List of Setting Items for Ethernet ModulesThe following table lists the parameter setting items that are set usin

3 - 8MELSEC-FSPECIFICATIONS33 - 83.6 List of Applications and Assignments of the Buffer MemoryData transmission/reception between Ethernet Module and

3 - 9MELSEC-FSPECIFICATIONS33 - 9(2) Assignments of the buffer memoryA buffer memory consists of 16 bits per address.<Bit configuration diagram>

3 - 10MELSEC-FSPECIFICATIONS33 - 10(Continued from the previous page)BFM numberAttribute Application NameInitial valueDecimal(Hexadecimal)Flash ROM sa

3 - 11MELSEC-FSPECIFICATIONS33 - 11(b) Communication parameter setting area (BFM #32 to 102)(Continues on the next page)BFM numberAttribute Applicatio

A - 2 A - 2[Design Precautions][Installation Precautions] CAUTIONWhen the status control (remote RUN/STOP) of the PLC is performed from the external d

3 - 12MELSEC-FSPECIFICATIONS33 - 12(Continued from the previous page)BFM numberAttribute Application NameInitial valueDecimal(Hexadecimal)Flash ROM sa

3 - 13MELSEC-FSPECIFICATIONS33 - 13(c) Communication status storage area (BFM #103 to 226)(Continues on the next page)*1 Initial processing writes IP

3 - 14MELSEC-FSPECIFICATIONS33 - 14(Continued from the previous page)*1 It varies after initialization.*2 Values written to BFM #202 will become activ

3 - 15MELSEC-FSPECIFICATIONS33 - 15(d) Error log partition area (BFM #227 to 511)(Continues on the next page)BFM numberAttribute Application NameIniti

3 - 16MELSEC-FSPECIFICATIONS33 - 16(Continued from the previous page)BFM numberAttribute Application NameInitial valueDecimal(Hexadecimal)Flash ROM sa

3 - 17MELSEC-FSPECIFICATIONS33 - 17(e) Router relay parameter setting area (BFM #512 to 1599)BFM numberAttribute Application NameInitial valueDecimal(

3 - 18MELSEC-FSPECIFICATIONS33 - 18(f) Open/close control (BFM #1600 to 1663)(Continues on the next page)*1 Required only when MC protocol is set.BFM

3 - 19MELSEC-FSPECIFICATIONS33 - 19(Continued from the previous page)BFM numberAttribute Application NameInitial valueDecimal(Hexadecimal)Flash ROM sa

3 - 20MELSEC-FSPECIFICATIONS33 - 20(g) Fixed buffer area (BFM #1664 to 9855)BFM numberAttribute Application NameInitial valueDecimal(Hexadecimal)Flash

3 - 21MELSEC-FSPECIFICATIONS33 - 21(h) Mail send parameter settings (BFM #9856 to 20479) (Continues on the next page)BFM numberAttribute Application N

A - 3 A - 3[Wiring Instructions] DANGERBefore mounting or wiring the module, make sure to shut off all of the external power supply. Failure to do so

3 - 22MELSEC-FSPECIFICATIONS33 - 22(Continued from the previous page)BFM numberAttribute Application NameInitial valueDecimal(Hexadecimal)Flash ROM sa

3 - 23MELSEC-FSPECIFICATIONS33 - 23(i) Connection status storage area (BFM #20480 to 22639)BFM numberAttribute Application NameInitial valueDecimal(He

3 - 24MELSEC-FSPECIFICATIONS33 - 24(j) E-mail status storage area (BFM #22640 to 31999)(Continues on the next page)*1 The timestamp for an email that

3 - 25MELSEC-FSPECIFICATIONS33 - 25(Continued from the previous page)BFM numberAttribute Application NameInitial valueDecimal(Hexadecimal)Flash ROM sa

4 - 1SETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 14MELSEC-F4 SETTINGS AND PROCEDURES PRIOR TO OPERATIONThis chapter explains the settings and proce

4 - 2SETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 24MELSEC-F4.1.2 Installation environmentThis section explains the installation environment for the

4 - 3MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 34.2 Settings and Procedures Prior to Starting the OperationThe following shows a flow of

4 - 4MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 4Important(1) Do not write any data in the "System area" of Ethernet module buff

4 - 5MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 54.3 Components of the Ethernet ModuleThis section shows the components of the Ethernet mo

4 - 6MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 6(1) LED display contents (*1)*1 Refer to Subsection 11.1.1 for causes of error displays a

A - 4 A - 4[Setup and Maintenance Precautions][Precautions When Disposing of This Product][Transportation Precautions] DANGERDo not touch any terminal

4 - 7MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 74.4 Connecting to the NetworkThe following explains how to connect the Ethernet module to

4 - 8MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 84.4.1 Connecting to the 10BASE-T/100BASE-TX networkThis section explains how to connect t

4 - 9MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 94.5 Ethernet Module SettingSetting the Ethernet module as a network module.The settings f

4 - 10MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 104.6 Operational SettingsThis section explains how to set the operations parameters.(1)

4 - 11MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 11(2) TCP Existence confirmation setting (BFM #24 b4)Select the existence check method fo

4 - 12MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 12(4) Initial Timing (BFM#24 b8)(a) Select the timing to open connections for which TCP-P

4 - 13MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 13(5) IP Address settings - IP address (BFM #0 to 1)(a) Set the IP address of the local s

4 - 14MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 144.7 Self-Diagnostic TestsThis section explains the self-diagnostic tests for checking t

4 - 15MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 154.7.2 Hardware test (H/W Test)This section explains the RAM and ROM tests for the Ether

4 - 16MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 164.8 Maintenance and InspectionThis section explains the maintenance and inspection as w

A - 5 A - 5CONTENTSSAFETY PRECAUTIONS ...

4 - 17MELSEC-FSETTINGS AND PROCEDURES PRIOR TO OPERATION44 - 174.8.2 Installing and uninstalling the moduleBefore installing or uninstalling the Ether

5 - 1COMMUNICATION PROCEDURE55 - 15MELSEC-F5 COMMUNICATION PROCEDUREThis chapter gives an overview of the communication procedure using the Ethernet m

5 - 2COMMUNICATION PROCEDURE55 - 25MELSEC-FNOTEThe following communication can be performed with an open device on other end.• Communication using MC

5 - 3MELSEC-FCOMMUNICATION PROCEDURE55 - 35.2 Initial ProcessingThis section explains the initial processing of the Ethernet module.5.2.1 Initial proc

5 - 4MELSEC-FCOMMUNICATION PROCEDURE55 - 45.2.2 Initial settingsThis section explains the initial settings. *1 Details are explained in Section 10.6.

5 - 5MELSEC-FCOMMUNICATION PROCEDURE55 - 5(1) Timer setting - TCP ULP timer (BFM#4)(a) This item sets the time of packet existence during TCP data sen

5 - 6MELSEC-FCOMMUNICATION PROCEDURE55 - 6(5) Timer setting - IP assembly timer (BFM#8)(a) Communication data may be divided on the IP level due to th

5 - 7MELSEC-FCOMMUNICATION PROCEDURE55 - 7NOTE(1) Set the value of each timer on the Ethernet module side such that the following relations are met.••

5 - 8MELSEC-FCOMMUNICATION PROCEDURE55 - 8TCP ULPtimer valueTCP endtimer value=TCP resendtimer value=(Each timer value should be identical.)(3) When c

5 - 9MELSEC-FCOMMUNICATION PROCEDURE55 - 91) Checking by KeepAliveThis method is used for a connection opened via the TCP/IP protocol.The Ethernet mod

A - 6 A - 65 COMMUNICATION PROCEDURE 5- 1 to 5-465.1 Overview of the Communication Procedure ...

5 - 10MELSEC-FCOMMUNICATION PROCEDURE55 - 105.2.3 Re-initializationRe-initialization is performed in order to place the Ethernet module into its start

5 - 11MELSEC-FCOMMUNICATION PROCEDURE55 - 11(2) Programming and timing for re-initializationThe programming and timing for re-initialization is shown

5 - 12MELSEC-FCOMMUNICATION PROCEDURE55 - 12(3) Operation for re-initializationOperation for re-initialization differs as follows, depending on the va

5 - 13MELSEC-FCOMMUNICATION PROCEDURE55 - 135.3 Router Relay ParameterThis section explains the router relay parameter.NOTEWhen making settings with t

5 - 14MELSEC-FCOMMUNICATION PROCEDURE55 - 14(2) Subnet mask pattern (BFM#512, 513)(a) Set the subnet mask. *1 (Setting range: C0000000 to FFFFFFFCH)Co

5 - 15MELSEC-FCOMMUNICATION PROCEDURE55 - 155.4 Confirming the Completion of the Initial ProcessingThe initial processing for the Ethernet module comp

5 - 16MELSEC-FCOMMUNICATION PROCEDURE55 - 165.4.1 PING command (Personal computer Ethernet module)The following example illustrates how to confirm t

5 - 17MELSEC-FCOMMUNICATION PROCEDURE55 - 175.4.2 Loop back test (Communication using MC protocol)The loop back test can be performed with communicati

5 - 18MELSEC-FCOMMUNICATION PROCEDURE55 - 185.5 Open SettingsThis section explains the open setting.A sequence program can perform open processing (es

5 - 19MELSEC-FCOMMUNICATION PROCEDURE55 - 19(2) Open system (connection numbers 1, 2; BFM#32, 33 b15, b14)(a) Select the connection open system for e

A - 7 A - 78 COMMUNICATION USING MC PROTOCOL 8- 1 to 8- 58.1 Data Communication Function...

5 - 20MELSEC-FCOMMUNICATION PROCEDURE55 - 20(4) Fixed buffer communication (connection numbers 1, 2; BFM#32, 33 b9 to b10)(a) For this item, select th

5 - 21MELSEC-FCOMMUNICATION PROCEDURE55 - 21(6) Existence confirmation (connection numbers 1, 2; BFM#32, 33 b1)(a) This setting selects whether or not

5 - 22MELSEC-FCOMMUNICATION PROCEDURE55 - 22(9) Destination Port No. (connection numbers 1, 2; BFM#43, 50)(a) Set the port numbers of the external de

5 - 23MELSEC-FCOMMUNICATION PROCEDURE55 - 23POINTSet parameters according to the open method to be used for open connection.Communication system open

5 - 24MELSEC-FCOMMUNICATION PROCEDURE55 - 245.5.2 MELSOFT/MC protocol connections (connection No. 3 and connection No. 4)*1 Used to connect MELSOFT p

5 - 25MELSEC-FCOMMUNICATION PROCEDURE55 - 255.6 Open Processing/Close Processing of the ConnectionThis section explains the open processing/close proc

5 - 26MELSEC-FCOMMUNICATION PROCEDURE55 - 26(2) Close processing(a) The purpose of the close processing is to disconnect (cancel) the connection with

5 - 27MELSEC-FCOMMUNICATION PROCEDURE55 - 275.6.1 Active open processing/close processingThis section explains the procedure for opening and closing a

5 - 28MELSEC-FCOMMUNICATION PROCEDURE55 - 281) After communicating the parameter settings, confirm the normal completion of the Ethernet module initia

5 - 29MELSEC-FCOMMUNICATION PROCEDURE55 - 29*1 Processing when the open processing is abnormally completed (TCP) When opening from the Ethernet module