Benutzeranleitung / Produktwartung fx3u des Produzenten Mitsubishi Electronics
Zur Seite of 284
FX 3U -ENET-L USER'S MANUAL.
.
A - 1 A - 1 SAFETY PRECAUTIONS (Read these preca utions before use.) Before installation, opera tion, maintenance or insp ec tion of this product, thorou ghly read through and understand this manual an d all of the associated manuals. Also, take care to han dle the module properly and safely.
A - 2 A - 2 [Design Precautions] [Installation Precautions] CAUTION When the status control (remote RUN/STOP) of t he PLC is performed from the external device, select the "Always wait for OPEN" parameter set by an user in advance. (Select with the in itial timing setting (BFM#24 b8) in the operational sett ing.
A - 3 A - 3 [Wiring Instructions] DANGER Before mounting or wiring the module, make sure to shut off all of the external power supply . Failure to do so may cause elec tric 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.
A - 4 A - 4 [Setup and Maintenance Precautions] [Precautions When Disposing of This Product] [Transportation Precautions] DANGER Do not touch any terminal while the PLC's power is on.
A - 5 A - 5 CONTENTS SAFETY PRECAUTIONS .............. ................. ................ ................ ................ ................ .............. ........ A- 1 CONTENTS ............. ................ ................ ................ .......
A - 6 A - 6 5 COMMUNICATION PROCEDURE 5- 1 to 5-46 5.1 Overview of the C ommunication Procedure ..................... ................. ................ ................... ......... 5 - 1 5.2 Initial Processing ..... ................ ................
A - 7 A - 7 8 COMMUNICATION USING MC PROTOCOL 8- 1 to 8- 5 8.1 Data Communication Functi on ....... ............. ................ ................ ................ ................ ........... ........ 8- 1 8.1.1 Accessing the PLC using MC protocol .
A - 8 A - 8 11 TROUBLESHOOTING 11- 1 to 11-42 11.1 How to Check Errors U sing LED Displays ...... ............. ................ ............. ................ ................ . 11 - 2 11.1.1 Checking error display ........ ................ .........
A - 9 A - 9 About Manuals This manual explains the mounting of FX 3U -ENET -L, the specifica tions, broadcast functions and communicati on methods. For the instructions and programs of the sequence as well as the p arameter setting s by FX Configurator -EN-L, also re fer to the following manuals.
A - 10 A - 10 Applicable Standard Certification of UL, cUL stand ards The following product has UL an d cUL certification. UL, cUL File Number: E95239 Models: MELSEC FX 3U series manufactured FX 3U -E.
A - 11 A - 11 Caution to conform with EC Directiv es • Installation in Enclosur e Programmable logic controllers are op en-type device s that must be installed and used within conductive control cab inets. Please use the programmable logic controller while inst alled within a conductive shielded control cabinet.
A - 12 A - 12 The Manual's Usage and Structure How to use this manual In this manual, explanations ar e given fo r each application of the Ethernet modules (FX 3U -ENET -L). Please use this manual using the following key items below as a reference.
A - 13 A - 13 (3) Connection between the Ethernet module and external devices (a) Communica tion procedur es • Section 5.1 describes an outli ne of the communicatio n procedures (b) Connections with the external device s • Section 5.
A - 14 A - 14 About the Generic Term s and Abbreviations This manual uses the following generic terms and abbreviation s to describe the Model FX 3U -ENET -L Ethernet interface block. Generic T erm/Abbre viation Description Ethernet Address A machine-specific a ddress that is also referred to as the MAC (Media Access Control Address).
1 - 1 OVERVIEW 1 1 - 1 1 MELSEC-F 1O V E R V I E W This manual provides infor mation on the spec ifications of the Ethe rnet interface block, FX 3U -ENET -L (h ereinafter called F X 3U -ENET -L or the.
1 - 2 OVERVIEW 1 1 - 2 1 MELSEC-F 1) Collection and modification of PLC data (Communication using the MELSEC Co mmunication Protocol (referred to below as the MC Prot ocol)) 2) T ransmission and recep.
1 - 3 MELSEC-F OVERVIEW 1 1 - 3 1.2 Features of t he Ethernet Module (1) Data communication using MC protocol (Details are explained in Chapter 8 and Chapter 9) Using MC protocol, the device dat a of the PLC can be read from/written to the host system.
1 - 4 MELSEC-F OVERVIEW 1 1 - 4 (3) Sending by e-mail (Details are explained in Chapter 10) In "E-mail send", data can be sent to and from an external device at a remote location using e-ma ils via an internet connection. (a) Sending e-mail from the PLC The following dat a can be sent by e-mail.
1 - 5 MELSEC-F OVERVIEW 1 1 - 5 (4) Connecting FX Configurator-EN- L (Details are explained in the Operating Manuals for FX Configurator-EN-L) (a) Simplifying sequence p rograms using FX Configurato r.
1 - 6 MELSEC-F OVERVIEW 1 1 - 6 (b) Connecting multiple MELSOFT prod ucts (GX Developer , MX Component) This product can be connected with one or more MELSOFT pro duct, via TCP/IP communication (through the in-h ouse LAN, etc.) or UDP/IP communication (th rough the in-house L AN, etc.
1 - 7 MELSEC-F OVERVIEW 1 1 - 7 1.3 Software Configuration The Ethernet modules support the TCP/IP and UDP/IP protocols. (1) TCP (T ransmission Control Protocol) This protocol guarantees data credibil.
1 - 8 MELSEC-F OVERVIEW 1 1 - 8 (2) UDP (User Datagram Protocol) This protocol may not guarantee data cr edibility or reliabilit y in communication between a personal computer /work station and PL C that are connected via network. Thus, even if the data does no t reach the t arget n ode, it will not be retransmitt ed.
1 - 9 MELSEC-F OVERVIEW 1 1 - 9 3) PSH (Push Flag) When this bit is ON (1), the host th at has received this segment sends the data to the up per application with high priority . This bit is to be turned ON when the dat a should be sent to an external device as soon as possible.
2 - 1 SYSTEM CONFIGURATIONS 2 2 - 1 2 MELSEC-F 2 SYSTEM CONFIGURA TIONS This section explains the system configurations that may be combined with the Ethernet modules.
2 - 2 SYSTEM CONFIGURATIONS 2 2 - 2 2 MELSEC-F 2.2 Devices Required fo r Network Configuration This section explains the devices that are requ ired to configure a netwo rk. Network installation work re quires suf ficient safeguard; ask a network specialist for installation.
2 - 3 MELSEC-F SYSTEM CONFIGURATIONS 2 2 - 3 (2) Connection usi ng the 10BASE-T Use devices that satisfy the standards of IEEE802.3 and 10BASE-T . • Shielded twisted pair cable (STP cable), cate gory 3 (4, 5) * S traight cables can be used.
3 - 1 SPECIFICATIONS 3 3 - 1 3 MELSEC-F 3 SPECIFICA TIONS This section exp lains the Ethernet m odule performan ce specifications and transmission specifications. For the general spe cifications, refer to the p ackaged manual and the User’s Manual of the PLC main unit.
3 - 2 SPECIFICATIONS 3 3 - 2 3 MELSEC-F *1 The setting is required only when "POP before SMTP" is selected in the SMTP authentication met hod.
3 - 3 MELSEC-F SPECIFICATIONS 3 3 - 3 3.2 Data Codes for Communication This sectio n explains th e data codes us ed in the com munication b etween the Ethernet module and the ex ternal de vice or the PLC. (1) The dat a codes used while communicating are listed below .
3 - 4 MELSEC-F SPECIFICATIONS 3 3 - 4 2) Ethernet module PLC Data is sent and received in binary co de. (2) When commun icating using ASCII code, 1-by te bina ry code dat a is automatically converted int o 2-byte ASCII code da ta and then transmitted.
3 - 5 MELSEC-F SPECIFICATIONS 3 3 - 5 3.3 Relationship between the External De vices and Additional Functions for Each Communication Function This sectio n explains wh ich external devices data commu nication can b e perform ed with and which additional function s can be used fo r each function.
3 - 6 MELSEC-F SPECIFICATIONS 3 3 - 6 3.4 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 t able below via TCP/IP or UDP/IP communication.
3 - 7 MELSEC-F SPECIFICATIONS 3 3 - 7 3.5 L ist of Setting It ems for Ethernet Modules The following ta ble lists the p arameter settin g items that are set usin g Ethernet Module . : Must be set when the applicable funct ion is used. : Set as needed : Setting is not required.
3 - 8 MELSEC-F SPECIFICATIONS 3 3 - 8 3.6 List of Applications and A ssignments of the Buff er Memory Data tr ansmission/reception betwe en Ether net Module and PLC is performed via the Ethernet Module buf fer memory (hereinafter called BFM) .
3 - 9 MELSEC-F SPECIFICATIONS 3 3 - 9 (2) Assignments of the buf fer memory A buffer memory consists of 16 bits per ad dress. <Bit configuration diagram> The following shows the buf fer memory addresses.
3 - 10 MELSEC-F SPECIFICATIONS 3 3 - 10 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadeci.
3 - 11 MELSEC-F SPECIFICATIONS 3 3 - 11 (b) Communica tion p arameter setting ar ea (BFM #32 to 102) (Continues on the next p age) BFM number Attribute Application Name Initial value Decimal (Hexadeci.
3 - 12 MELSEC-F SPECIFICATIONS 3 3 - 12 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 40 (28 H ) R/W Communication parameters setting area Communication address setting area Connection No.
3 - 13 MELSEC-F SPECIFICATIONS 3 3 - 13 (c) Communicati on status storage area (BFM #103 to 226 ) (Continues on the next p age) *1 Initial processing writes IP and Et hernet address.
3 - 14 MELSEC-F SPECIFICATIONS 3 3 - 14 (Continued from the previous p age) *1 It varies af ter initialization. *2 V alues written to BFM #202 will become active the next time the module is powered ON. (The value returns to 0 when each running mode execut ion is complete.
3 - 15 MELSEC-F SPECIFICATIONS 3 3 - 15 (d) Error log par tition area (BFM #227 to 51 1) (Continues on the next p age) BFM number Attribute Appli cation Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 227 (E3 H ) R Error log area Number of error occurrences 0 (0 H ) Secti on 1 1.
3 - 16 MELSEC-F SPECIFICATIONS 3 3 - 16 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 376 to 377 (178 to 179 H ) R Error log area St atus for each protocol IP Received IP packet co unt 0 (0 H ) Section 1 1.
3 - 17 MELSEC-F SPECIFICATIONS 3 3 - 17 (e) Router relay p arameter setting ar ea (BFM #512 to 1599) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 512 to 513 (200 to 201 H ) R/W Router relay para met er setting area Sub-net mask 0 (0 H ) Section 5.
3 - 18 MELSEC-F SPECIFICATIONS 3 3 - 18 (f) Open/close contro l (BFM #1600 to 1663) (Continues on the next p age) *1 Requi red only whe n MC prot ocol is set.
3 - 19 MELSEC-F SPECIFICATIONS 3 3 - 19 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadeci.
3 - 20 MELSEC-F SPECIFICATIONS 3 3 - 20 (g) Fixed buf fer area (BFM #1664 to 9855) BFM number Attribute Application Name Initial value Decim al (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 1664 (680 H ) R/W Fixed buffe r data area Fixed buffer No.
3 - 21 MELSEC-F SPECIFICATIONS 3 3 - 21 (h) Mail send p arameter settings (BFM #9856 to 20479) (Continues on the next p age) BFM number Attribute Application N ame Initial value Decimal (Hexadecimal) .
3 - 22 MELSEC-F SPECIFICATIONS 3 3 - 22 (Continued from the previous p age) BFM number Attribute Application Name Initial value Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadeci.
3 - 23 MELSEC-F SPECIFICATIONS 3 3 - 23 (i) Connection st atus storage area (BFM #2 0480 to 22639) BFM number Attribute Applica tion Name Initial value Decimal (Hexadecimal) Flash ROM save Reference s.
3 - 24 MELSEC-F SPECIFICATIONS 3 3 - 24 (j) E-mail status stor age area (BFM #2264 0 to 31999) (Continues on the next p age) *1 The timestamp fo r an email that had a communication error with the mail server is store d in BCD code in the following manner .
3 - 25 MELSEC-F SPECIFICATIONS 3 3 - 25 (Continued from the previous p age) BFM number Attribute Application Name Initial valu e Decimal (Hexadecimal) Flash ROM save Reference section Decimal (Hexadecimal) 24320 (5F00 H ) R/W Mail Function SMTP server port nu mber 25 (19 H ) Section 10.
4 - 1 SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 1 4 MELSEC-F 4 SETTINGS AND PROCEDURES PRIOR T O OPERA TION This chapter explains the settings and pr ocedur es required prior to operating the Ethernet module in a system.
4 - 2 SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 2 4 MELSEC-F 4.1.2 I nstallation environment This section explains the installation en vironment for the PLC. When installing the PLC, the following environment s must be avoided: • Locations where the ambient temper ature exceed s the range of 0 to 55 .
4 - 3 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 3 4.2 Settings and Procedures Prio r to S tarting the Operation The following shows a flow of the procedur e that is re quired prior to .
4 - 4 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 4 Important (1) Do not write any dat a in the "System area" of Etherne t module buf fer memory .
4 - 5 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 5 4.3 C omponents of the Ethernet Module This section shows the component s of the Ethernet module.
4 - 6 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 6 (1) LED display contents (*1) *1 Refer to Subsection 1 1.1.1 for causes of error displays and the cor responding corrective actions. *2 The [ERR.] LED turns on in the following cases: • When the parameter written is incorrect.
4 - 7 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 7 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 obse rved while connecting the Ethernet module are also shown below .
4 - 8 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 8 4.4.1 Connecting to the 10B ASE-T/100BASE-TX network This sectio n explains ho w to connect the Etherne t module to t he 10BASE-T , 100BASE-TX network. The following shows the connection diag ram for the twisted pa id cable.
4 - 9 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 9 4.5 Ethernet Module Setting Setting the Ethernet mod ule as a network module. The settings found must always be se t in order to use the Ether net module. (1) "Operational settings" (Details are explained in Section 4.
4 - 10 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 10 4.6 Operational Settings This section explains how to set the operations p arameters. (1) Communication dat a code (BFM#24 b1) (a) Select the format of the communicati on data when commu nicating with an external device .
4 - 11 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 11 (2) TCP Existence confirma tion setting (BFM #24 b4) Select the existence check method for TCP commun ication.
4 - 12 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 12 (4) Initial T iming (BFM#24 b8) (a) Select the timing to open conn ections for w hich TCP-Passiv e open or UDP open are s elected with th e "Open set tings" parameter ( *1).
4 - 13 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 13 (5) IP Address settings - IP address (B FM #0 to 1) (a) Set the IP address of the local station according to the sp ecified input form at (decimal or hexadecima l).
4 - 14 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 14 4.7 Self-Diagnostic T ests This section expl ains the self-diagn ostic tests for checking the hardwa re and transmission and reception fu nction of the Ethernet mo dule.
4 - 15 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 15 4.7.2 Hardware test (H/W T est) This sectio n explains th e RAM and RO M test s for the Ethern et module. The procedure for the har dware test is as shown in the table be low . The test results are judg ed from the LED displays on the front of the Eth ernet module.
4 - 16 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 16 4.8 Maintenance and Inspection This section explains the ma intenance and ins pection as well as the installing and uninstalling of the Ethernet module.
4 - 17 MELSEC-F SETTINGS AND PROCEDURES PRIOR TO OPERATION 4 4 - 17 4.8.2 Installing and uni nstalling the module Before installing or uninst a lling the Ethernet module, make sure to read Section 4.
5 - 1 COMMUNICATION PROCEDURE 5 5 - 1 5 MELSEC-F 5 COMMUNICA TION PROCEDURE This chapter gives an overview of the co mmunication proced ure using the Ethernet module, as well as the requir ed initial processing of the Ethernet prior to dat a communication and the open processing fo r commu nication with an external device.
5 - 2 COMMUNICATION PROCEDURE 5 5 - 2 5 MELSEC-F NOTE The following communication can be perfor med with an open device on other end. • Communicatio n using MC protocol • Sending/receivin g in fix.
5 - 3 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 3 5.2 Initial Processing This sectio n explains th e initial process ing of the Et hernet modu le. 5.2.1 Initial processing The initial processing enables dat a communication with an external device by setting the parameters required fo r data communicat ion via the Ethernet mo dule.
5 - 4 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 4 5.2.2 Initial settings This section explains the initial s ettings. *1 Details ar e explained in Section 10.6 . Setting item name BFM number [Decima l] Description of setting Set ting range/options T imer setting TCP ULP timer 4 Set the time o f packet exis tence at TCP data transmission.
5 - 5 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 5 (1) T imer setting - TCP ULP timer (BFM#4) (a) This item sets the time of p acket existence during TCP data sending. This timer is p assed through the parameter whe n TCP opens or dat a is sent. (b) Set the value in the range fr om 2 to 32767.
5 - 6 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 6 (5) T imer setting - IP assembly timer (BFM#8) (a) Communicati on data may be divided on the IP level due to the buf fer restriction at the sendin g or receiving station. (b) Set the value in the range fr om 1 to 32766.
5 - 7 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 7 NOTE (1) Set the va lue of each timer on t he Ethernet m odule side s uch that the following relations are met. • • Furthermore, when con necting a line using Mit subishi products, you should make sure that both nodes have the same settings.
5 - 8 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 8 TCP ULP timer value TCP end timer value = TCP resend timer value = (Each timer value should be identical.) (3) When commu nication errors occur , the setting value shou ld be changed to increase the nu mber of retries .
5 - 9 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 9 1) Checking by Keep Alive This method is used for a conne ction opened via the TCP/IP protocol. The Ethernet module perfor ms an existence check by sendi.
5 - 10 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 10 5.2.3 Re-initialization Re-initialization is performe d in order to place the Ethernet module into it s startup status without actua lly restartin g the PLC. Re-initializatio n of the Ethernet module can be perfor med in a sequence prog ram.
5 - 11 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 11 (2) Programming and timi ng for re-initialization The programming and timing for re -initia lization is shown below: • Program example fo r the unit No. 1 1) It is confirmed whether the initial processing has been completed normally .
5 - 12 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 12 (3) Operation for re-initialization Operation for re-in itialization dif fers as follows, depending on the val ue written to BFM#1600. *1: When re-readin g the flash ROM, the re-i nitial ization is performed in the same status as when the pow er supply is turn ed on.
5 - 13 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 13 5.3 Router Relay Parameter This sectio n explains th e router r elay parameter . NOTE When making settings with the FX Conf igurator-EN-L, sele ct [Router Relay Parameters] from the initial screen and adjust the settings at the [Ethernet Route r Relay Parameter Settings] screen.
5 - 14 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 14 (2) Subnet mask pattern (BFM#512, 513) (a) Set the subnet mask. *1 (Setting range: C0000000 to FFFF FFFC H ) Consult the network administrator for the setting. (b) When not using the subn et mask, set any of the following table value s according to the class.
5 - 15 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 15 5.4 Confirming the Completion of the Initial Processing The initial processing for the Ethernet module completes by selectin g re-initialization, then turning the power ON again, or re-initializing via buffer memor y operations after parameters a re written to the Ethernet module.
5 - 16 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 16 5.4.1 PING command (Personal computer Ethernet module) The following example illustra tes how to confirm the co mpletion of the initial processi ng by issuing th e PING comma nd to the local s tation's Ethernet mo dule from an external device connected on the same Ethern et network.
5 - 17 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 17 5.4.2 Loop back test (Communi cation using MC protocol) The loop back test can be performed with commu nication using MC protocol in order to check the completion st atus of the initia l processing for the target Ether net module.
5 - 18 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 18 5.5 Open Settings This sectio n explains th e open set ting. A sequence progr am can perform open p roc essing (est ablishing connection ) with up to a.
5 - 19 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 19 (2) Open system (connection numbers 1, 2; BFM#32, 33 b15, b14) (a) Select the connection open syste m for each connectio n for which "TCP" is selected in "(1) Protocol". If "UDP" is se lected, the specificatio n of this item is not required .
5 - 20 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 20 (4) Fixed buffer communication (connection numbers 1, 2; BFM#32, 33 b9 to b10) (a) For this item, select the communica tion method when communicating using the fixed buffers.
5 - 21 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 21 (6) Existence confirmation (connection numbers 1, 2; BFM#32, 33 b1) (a) This setting selects whethe r or not the Ethernet module sh ould confirm that an external device still operates norma lly when there is no communication for a fixed p eriod of tim e.
5 - 22 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 22 (9) Destination Port No. (connection numbers 1, 2; BFM#43, 50) (a) Set th e port numb ers of the external de vices for eac h connectio n. (b) The port numbers of the external devices are set in the range from 1025 to 65534.
5 - 23 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 23 POINT Set parameter s according to the open meth od to be used for open connection. Communication system open system TCP UDP Active Passive Parameter A.
5 - 24 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 24 5.5.2 MELSOFT/MC protocol connections (connection No. 3 and connection No. 4) *1 Used to connect MELSOFT p roducts throu gh TCP/IP communication. It performs passive ope n processing of TCP conn ection for all MELSOFT products conne cted to the network.
5 - 25 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 25 5.6 Open Processing/Close Pr ocessing of t he Connection This sectio n explains th e open pr oces sing/close processing using sequence programs.
5 - 26 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 26 (2) Close processing (a) The purpose of the close processin g is to disconnect (cancel) th e connection with the external device est ablis hed by open processing me ntioned previously .
5 - 27 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 27 5.6.1 Active open processing/close processing This sectio n explains the proced ure for opening and closing a connection with an external device from the Ethernet module. • Program example for the un it No.
5 - 28 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 28 1) After communicating the p arameter settings, confir m the normal completion of the Ethernet modul e initial processing. (Initial completion signal BFM#27 "0 001 H ") 2) Confirm t hat the E thernet modu le and hub are connecte d.
5 - 29 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 29 *1 Processing when the open processin g is abnormally completed (TCP) When opening from the Etherne t module under a normal situa tion, if the Ethernet mod ule sends a SYN, the external de vice returns an ACK and a SYN.
5 - 30 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 30 1) The open request signal turns of f by writing "8000 H " to the BFM#1602. 2) The E thernet modu le execut es the close processing. 3) The Ethernet module sends a FIN request to th e external device.
5 - 31 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 31 Program example This example explains a prog ram for open processing/close processing when Active open is selected in the Open s ystem setting. (1) Execution environment for the program example (a) The Ethernet module i s connected to the second special module .
5 - 32 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 32 • Program example for the un it No. 1 X000 M100 M103 X000 M102 [= D100 H5 ] ] H10 D100 [= ] H0 D100 [= [MOV D100 (M100 (M101 (M102 (M103 ] ) [MOVP H0.
5 - 33 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 33 5.6.2 Passive open processing/close processing This sectio n explains the proced ure for ope ning and clos ing a connec tion with th e Ethernet module via an external device.
5 - 34 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 34 1) After the parameters ar e sent, the normal completion o f the Ethernet module initial processing is confirme d (Initial normal completion signal BFM.
5 - 35 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 35 • Program example for the un it No. 1 X000 M100 M103 X000 M102 [= D100 H15 ] [= D100 H10 ] [= D100 H5 ] [= D100 H3 ] ] H0 D100 [= [MOV D100 X0:ON Ope.
5 - 36 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 36 *1 If an open request (SYN) received af ter the normal completion of an initial processing and befor e the Ethernet module is pla ced in the open acknowledge en abled status, an error is generated, and the Ethernet module send s a connection forced close (RST).
5 - 37 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 37 NOTE (1) If the settings of the connection need modifyin g, the modifications should be done before writing th e open instruction to the buffer memory. (2) Once open processing is exe cuted, an open request cann ot be canceled befor e the open processing is completed.
5 - 38 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 38 Program example This example explains a prog ram 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 i s connected to the second special module .
5 - 39 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 39 • Program example for the un it No. 1 X000 M100 M103 X000 M102 [= D100 H15 ] [= D100 H10 ] [= D100 H5 ] [= D100 H3 ] ] H0 D100 [= [MOV D100 (M100 (M1.
5 - 40 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 40 5.6.3 UDP/IP open processing/close processing The following explains the UDP/IP open processing. The operations of the open processing/clo se processin.
5 - 41 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 41 • Program example for the un it No. 1 X000 [= D100 H15 ] [= D100 H10 ] [= D100 H5 ] [MOV D100 ] [INCP D0 ] [INCP D1 ] U1 G1602 Open request OPEN inst.
5 - 42 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 42 1) After communicating the p arameter settings, confir m the normal completion of the Ethernet modul e initial processing. (Initial normal completion signal (BEF# 27) : 0001 H ) 2) S tart the open processing by wr iting 0001 H to the BFM#1602.
5 - 43 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 43 5.7 Pairing Open The following explains communication using th e p aring open method via the Ethernet module.
5 - 44 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 44 5.7.2 Example of pairing open settings This section explains the settin gs in order to commun icate in the p airing open method by giving an ex ample. • Connection No. 1 and 2 are used. (When connection No.
5 - 45 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 45 (7) Local station Po rt No. (BFM#40, 47) Set this for the receiving connection for re ceivin g only . ( Setting is not require d for the sending conn ection.) Set the port number upo n consul ting a network administrator .
5 - 46 MELSEC-F COMMUNICATION PROCEDURE 5 5 - 46 5.8 Hub Connection S tat us Monitor Function The curren t connectio n status of the Et hernet module and hub, the transmission speed, and the numbe r of times the Ether net module detected disconnection can be checked at the following buffer me mory addresses.
6 - 1 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 1 6 MELSEC-F 6 FIXED BUFFER COMMUNICA TION (WITH THE PROCEDURE EXIST CONTROL METHOD) This chapter explains how the PLC and externa l device communicate in a 1:1 mode using the fixed buf fers (with the procedure exist control method) of the Etherne t module.
6 - 2 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 2 6 MELSEC-F (3) At data sending/receiv ing, the Et hernet module processes the following.
6 - 3 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 3 6.2 S ending Control Method This section explains the control me thod wh en dat a is sent from the Ethernet mod ule to an external device usin g the fixed buf fer No.
6 - 4 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 4 1) Confirm the normal completion of the initial processing. 2) Confirm that the link status is no rmal between the Ethernet module and the connected HUB. 3) Confirm the normal completion of the open processing of connection No.
6 - 5 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 5 POINT The destination setting (see Section 5.5) for a conn ection whos e parameters ar e set in FX Configurato r-EN-L become s valid when the open com pletion signal (BFM#20480 corr esponding bit) of the Ethern e t module switches from of f to on.
6 - 6 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 6 6.3 R eceiving Control Method This sectio n explains th e control m ethod when t he Ethernet m odule rece ives data from an external device.
6 - 7 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 7 1) Confirm the normal completion of the open pr ocessing of connection No. 2. 2) Upon rece iving data from the des ignated ex ternal device (s et in the open processing), the Ethernet module processes th e following.
6 - 8 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 8 6.4 Data Format When communicating between the Ethernet m odule and an exte rnal device, th e data format explained be low is used. The communication dat a consists of a "header" and "application dat a" as follows: 6.
6 - 9 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 9 6.4.2 Application data As shown below , the data code in the application dat a can be expressed in either binary code or ASCII code.
6 - 10 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 10 (2) Subheader The format of the subheader is as shown below . The user does not need to set the subheader when using the Ethe rnet module since the Ethernet module add s and deletes it.
6 - 11 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 11 (3) Data length setting This value indicates the dat a size of the text (command) section. (4) T ext (command) The format of the com mand/res ponse when c ommunicatin g using fixe d buffers is configured as follows.
6 - 12 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 12 (b) Communicati on using ASCII code (Example) (5) End codes For more det ails on the end codes added to a respon se when communicating using fixed buf fers, see Subsection 1 1.
6 - 13 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 13 6.5 Programming This sectio n explains th e program ming metho d when the Et hernet modu le communicates with an external device using fixed buf fers and the procedure exist control method.
6 - 14 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 14 6.5.2 Fixed buffer communic ation program example (with the procedure e xist control method) This section explains the programmin g method in order to communicate dat a (procedure exist control method) with an external device u sing the fixe d buffers.
6 - 15 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 15 (b) Receiv e program (FX 3U -2nd station) 1) Connection No. 1 is used to process th e fixed buff er receiving in the main program. 2) The unit number specified at the sequence progr am and FX Configur ator-EN-L is 0.
6 - 16 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 16 (2) Outline of the program example (a) Send progra m (Ethernet module-1 st station) 1) After setting each .
6 - 17 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 17 (Send program) (See Subsection 5.6.1) • Program example for the un it No.
6 - 18 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6 6 - 18 (Receive program) • Program example for the un it No. 0 M8000 [MOV U0 G1610 D100 ] [MOV H2 ] [INCP D102 .
7 - 1 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 1 7 MELSEC-F 7 FIXED BUFFER COMMUNICA TION (WITH THE NO PROCEDURE CONTROL METHOD) This chapter explains how the PLC and exte rnal device communicate using the fixed buffer s (with the no procedure control me thod) via the Ether net module.
7 - 2 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 2 7 MELSEC-F (2) Data can be communicated with the following external devices. • Device on the Ethe rnet to which the Etherne t module is c onnected. • Devices connected with the router relay function (see Section 5.
7 - 3 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 3 (3) At data sending/receiv ing, the Et hernet module processes the following.
7 - 4 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 4 7.2 S ending Control Method This section explains the control me thod wh en dat a is sent from the Ethernet mod ule to an external device using fixe d buffer No. 1 and the area corresponding to connection No.
7 - 5 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 5 1) Confirm normal com pletion of the initi al processing. 2) Confirm t hat the E thernet modu le is connec ted to the hub. (BFM#28 b7:ON) 3) Confirm the normal completion of the open processing for connection No.
7 - 6 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 6 7.3 R eceiving Control Method This sectio n explains th e control m ethod when t he Ethernet m odule rece ives data from an external device.
7 - 7 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 7 1) Upon rece iving data from the des ignated ex ternal device (s et in the open processing), the Ethernet module processes th e following. • S tores the received data to the fixed buf fer (No.
7 - 8 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 8 7.4 Data Format When communicating between the Ethernet m odule and an exte rnal device, th e data format explained be low is used. The communication dat a consists of a "header" and "application dat a" as shown below .
7 - 9 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 9 7.5 Programming This sectio n explains th e program ming metho d when the Et hernet modu le communicates with an external device using fixed buf fers and the no-procedure control method.
7 - 10 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 10 7.5.2 Fixed buffer communication program ex ample (with the no procedure control method) This section explain.
7 - 11 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 11 (b) Receiv e program (FX 3U -2nd station) 1) Connection No. 2 is used to process the fixed buf fer receiving. 2) The unit number specified at the sequence progr am and FX Configur ator-EN-L is 0.
7 - 12 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 12 (2) Outline of the program example (a) Send progra m (FX 3U -1st station) 1) After setting each parameter wit.
7 - 13 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 13 (Send program) • Program example for the un it No. 0 M8000 X002 M300 M307 M201 D101.
7 - 14 MELSEC-F FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7 7 - 14 (Receive program) • Program example for the unit No. 0 U0 G2688 Received data count M8000 [ADD H1 D101 Rece.
8 - 1 COMMUNICATION USING MC PROTOCOL 8 8 - 1 8 MELSEC-F 8 COMMUNICA TION US ING MC PROT OCOL This chapter gives an overvi ew of the MC pr otocol. NOTE The frame type of MC protocol (data comm unication m essages) us ed by the external device to access the PLC via this pr oduct is equiva lent to A compatible 1E frame.
8 - 2 COMMUNICATION USING MC PROTOCOL 8 8 - 2 8 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.
8 - 3 MELSEC-F COMMUNICATION USING MC PROTOCOL 8 8 - 3 8.1.3 Access T i ming 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 mo dule. 1) A command message is transmitted from th e external device to the PLC side.
8 - 4 MELSEC-F COMMUNICATION USING MC PROTOCOL 8 8 - 4 8.1.4 PLC setting for perf orming data communication Data commu nication via MC protocol is e nabled by adjusting the followi ng settings using FX Configurator-EN-L and writing the parameter s to the Ethernet module.
8 - 5 MELSEC-F COMMUNICATION USING MC PROTOCOL 8 8 - 5 MEMO.
9 - 1 WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 1 9 MELSEC-F 9 WHEN COMMUNICA TING DA T A USING THE MC PROTOCOL This chapter explains the me ssage format, how to design ate data item s in a message and restrictions for data commu nication with an Ethernet module using MC proto col with A compatible 1E frames.
9 - 2 WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 2 9 MELSEC-F (2) When an external device writes data to the PLC 1) Area C indicates transmission from the externa l device to the PLC. 2) The program of the external device is generated so that the data is transmitted sequentially from lef t to right.
9 - 3 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 3 9.1.2 Message format and control procedure This sectio n explains the messag e format a nd control pr ocedure. (1) Message format This section explains the message format for tr ansmission between the Ether net module and an external device.
9 - 4 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 4 (2) Control procedure The following diagrams illustrate the co ntrol procedure fo r communicating with the MC protocol and the order of dat a items in the application dat a field.
9 - 5 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 5 2) When writing dat a to the local station PLC from the external device side (b) Communicati on in binary code 1) When re ading dat.
9 - 6 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 6 2) When writing dat a to the local station PLC from the external device side External device side PLC side (Command message) PLC side External device side (Response message) (Normal completion) (Abnormal completion) T ext (Command) (Data name) (Example) Header Subheader PC No.
9 - 7 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 7 9.1.3 Contents of data designation items This sectio n explains th e data it ems of commands and responses when communica ting using MC protocol.
9 - 8 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 8 (6) Character field (response) This dat a contains dat a read/processing result when an external device reads/ writes data from/to the t arget PLC station. The content s and order of dat a in the C haracter field (respo nse) dif fer depen ding on the function used.
9 - 9 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 9 NOTE The following example shows th e designation of the subheader to the mon itoring timer when com municating us ing MC pr otocol unde r the following conditions.
9 - 10 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 10 (2) Format when communicating in ASCII code (a) The order when sending a comma nd (external device Ethernet module) (b) The order.
9 - 11 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 11 9.1.4 Character area transmission data This section exp lains how to transm it the bit device data and word dev ice data handled in the character ar eas, as well as the order of transmission when communicating dat a between an external device and the PLC by each command .
9 - 12 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 12 (b) When reading from or writin g to a word device memory Each word of the word device memory is expressed in he xadecimal values in 4-bit units sequentially from the h igher bit.
9 - 13 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 13 (2) Data communication using binary code (a) When reading to or writing from the bit device memory The bit device me mory can be re ad and written in bit un its (one device point) or word units (1 6 device point s).
9 - 14 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 14 (b) Reading from or writing to a word device me mory Each word of a word device memory is designated by 16 bit s and the designat.
9 - 15 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 15 9.2 List of Commands and Func tions for The MC protocol The following tab le list s the commands a nd functions when an external d evice accesses the PLC. *1 When the double word data is read using th e user program, etc.
9 - 16 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 16 9.3 Device Memory Read/Write This section explains the designations in the control procedure wh en reading from and writing to the device memor y by providing an example.
9 - 17 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 17 (2) Designation met hod 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 be low . (b) The following table outlines the device codes and numbers.
9 - 18 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 18 POINT (1) Bit devices and word devices are classified according to the following.
9 - 19 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 19 9.3.2 Batch read in bit units (command: 00) The exam ples show n in this se ction ex plain the command/response format when batch-reading the bit device memory .
9 - 20 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 20 (2) Communication in AS CII code NOTE (1) Use the designation "00 H " when the number of device points is 256 points. (2) If the number of device points designated is an odd number, one byte of dummy data (30 H ) will be added to the response data.
9 - 21 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 21 9.3.3 Batch write in bit units (command: 02) The exam ples show n in this se ction ex plain the command/response format when batch writing to the bit device memory .
9 - 22 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 22 (2) Communication in AS CII code NOTE If the number of device points to be set is an odd number, ad d one byte of dummy data (30 H ) at the end of d ata written. For e xam ple, when writing three points, add the dummy data (30 H ) at the end.
9 - 23 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 23 9.3.4 T est in bit units (r andom write) (command: 04) The exam ples show n in this se ction ex plain the command/response format when writing dat a by designating bit device memories ar bitrarily .
9 - 24 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 24 (2) Communication in AS CII code (Data name) External device side (Example) Designated device Y45 Designated device M60 S38 ON Y4.
9 - 25 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 25 9.3.5 Batch read in word units (command: 01) The exam ples show n in this se ction ex plain the command/response format when batch reading the word device memory and the bit device me mory (16 point unit s).
9 - 26 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 26 (2) Communication in AS CII code 30 H 38 H 30 H 0 31 H 41 H 35 H Y100 32/16 = 2 points 31 H 1 46 H F HL F 46 H 0 HL 00 A 5 30 H 3.
9 - 27 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 27 NOTE C200 to C255 (Current Valu es) Batch Read Since C200 to C255 are 32 bit devices, th e 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 .
9 - 28 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 28 (2) When communicating in ASCII code * 0 30 H H F 46 H * 1 31 H L F 46 H H 0 30 H - 0 30 H - 0 30 H L A 41 H 8 38 H 1 31 H L 0 30.
9 - 29 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 29 9.3.6 Batch write in wo rd units (command: 03) The exam ples show n in this se ction ex plain the command/response format when batch writing to a word device memory and bit device memor y (16 point unit s).
9 - 30 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 30 (2) Communication in AS CII code F 30 H 0 38 H D100 33 H 3 46 H 46 H 30 H 0 30 H 0 30 H 0 41 H A 34 H 4 34 H 4 32 H 2 30 H 0 30 H.
9 - 31 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 31 NOTE C200 to C255 (Current Values) Batch Write Since C200 toC255 are 32 bit de vices, 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 numbe r.
9 - 32 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 32 (2) When communicating in ASCII code * 0 30 H H F 46 H * 3 33 H L F 46 H H 0 30 H - 0 30 H - 0 30 H L A 41 H 8 38 H 3 33 H L 0 30.
9 - 33 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 33 9.3.7 T est in word units (random write) (command: 05) The exam ples show n in this se ction ex plain the command/response format when writing dat a by designating word device memories and bit device mem ories (16 point units) arb itrarily .
9 - 34 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 34 (2) Communication in AS CII code Y20 30 H 35 H 46 H 46 H 30 H 30 H 30 H 41 H 30 H 33 H 30 H 30 H 35 H 39 H 32 H 30 H 31 H 30 H 37.
9 - 35 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 35 9.4 Remote RUN/STOP , PLC model name code read This function is used to remotely RUN/ST OP a PLC and read the model name of a PLC from a n external device.
9 - 36 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 36 9.4.2 Remote RUN (command: 13) / Remo te STOP(Command: 14) The examples shown in this section explain the control pr ocedure of remote RUN.
9 - 37 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 37 POINT • When executing the remote RUN/STOP using other external device s or computer link, the remo te RUN/STOP is executed in the order o f execution.
9 - 38 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 38 9.4.3 PLC model name read (command: 15) The exam ples show n in this se ction expl ains the con trol proced ure for re ading the model name of the PLC.
9 - 39 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 39 9.5 Loopback T est A loopback test checks whether or not the communication function between an external device and the Eth ernet module op erates normally . The examples show the control procedure using th is function.
9 - 40 MELSEC-F WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9 9 - 40 (2) Performing a loopback test wh ile communicating in ASCII code POINT The number of the loopback dat a transmitted by an external device is returned to the external device it is.
10 - 1 USING THE E-MAIL FUNCTION 10 10 - 1 10 MELSEC-F 10 USING THE E-MAIL FUNCTION This chapter explains e-mail func tions of the Ethernet module. 10.1 E-mail Function The e-mail function sends e-ma ils to PCs or PLCs at a remote location using the network (via th e mail server).
10 - 2 USING THE E-MAIL FUNCTION 10 10 - 2 10 MELSEC-F (2) Dat a conversion method used by the Ethernet mo dule The following shows the dat a conversion method used by the Eth ernet module.
10 - 3 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 3 10.2 Configuration and Environment of the Applicable System This section exp lains the environ ment and system co nfiguration fo r using the e-mail function from the Ethe rnet module. (1) E-mails can be sent in an environment where the Internet service is ava ilable as shown above.
10 - 4 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 4 10.3 Precautions for Us ing the E-mail Function The following explains precautions when using the e-mail function of the Ether net module.
10 - 5 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 5 10.4 E-mail S pecifications The following table list s the specifications of the e-mail function. NOTE Mail terminology list: DNS server: Server tha.
10 - 6 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 6 10.5 Processing Procedure of the E-mail Function The following flowchart illustrates the proc edure that is requ ired before sending e-mails: Start When DNS is not used When DNS is used Register the DNS server See Section 10.
10 - 7 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 7 10.6 E-mail Settings This sectio n explains th e settings req uired to send e-mails. (1) DNS settings S pecify the IP address of the DNS server when setting the mail serve r name using the domain name from the e-mai l settings (see (2)).
10 - 8 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 8 (2) E-mail settings Set in order to use the e-mail function . [Setting item] *1 The setting is required only when "POP before SMTP " is selected in the SMTP authentication method.
10 - 9 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 9 (c) SMTP authentication setting 1) Set the authentication method for the outgoing mail server (SMTP). The steps 2) and 3) below are re quired when "SMTP-AUTH" is selected in the SMTP authentication method.
10 - 10 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 10 10.7 Sending E-mail (Attac hed Files) by the PLC This sectio n explains ho w to send attached files when sending e-ma ils. 10.7.1 When sending data as an attached file The following explains the buf fer memory addresses and program for sending e-mail.
10 - 11 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 11 The tabl e below shows the buffer memory to be used for sending mail. (1) Send using the sequence program The following explains how an e-mail is sent by the sequence program. See (3) sending dat a for detail.
10 - 12 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 12 • Program example for the un it No. 1 X000 M100 M102 M103 M101 D100.1 D100.0 D100.F M8029 M101 [MOV D100 K1000 (C1 ] [MOV D101 ] [PLS M103 ] [PL.
10 - 13 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 13 M8000 [MOV R1234 R1000 ] ] [MOV H5678 R1001 R1002 ] [MOV R9ABC ] [FEND [SRET ] [END ] P0 Head of attached data [ZRST R1000 R1002 ] Head of attache.
10 - 14 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 14 (2) Execution timing of the instruction 1) Check whe ther the init ial processing has been co mpleted norm ally .
10 - 15 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 15 (3) Receiving with a personal computer The following explains how a PC/UNIX rece ives e-mails sent from the Ethernet module. After setting an environment with application soft ware that processes e-mails, e-mails can be receive d on a receive message screen as sh own below .
10 - 16 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 16 10.7.2 Contents of the att ached files The following explains the conten ts of the att a ched file dat a. The data format of the att ached file is ASCII code (ASCII format, CSV format ) or binary code (binary form at).
10 - 17 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 17 10.8 Sending E-mail (Main T ext) by the PLC This sectio n explains ho w to send t he main text o f e-mail. 10.8.1 When sending data as main text of e-mail The following explains the buf fer memory address a nd sequence prog ram for sending e-mail.
10 - 18 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 18 The table be low shows the buffer me mory to be used for sending mail. BFM number Item Description Decimal (Hexadecimal) 10333 (285D H ) Mail send.
10 - 19 MELSEC-F USING THE E-MAIL FUNCTION 10 10 - 19 (1) Send using the sequence program Method for sending e-mails by th e sequence program is similar to the one by an attach ed file. See Subsection 10.7.1 for sample pr ograms for sending e-m ail from PLC.
11 - 1 TROUBLESHOOTING 11 11 - 1 11 MELSEC-F 1 1 TROUBLESHOOTING This section explains the co ntent s of the errors that may occur during communication between the Ethernet module a nd an external device as well as the troublesho oting procedures.
11 - 2 TROUBLESHOOTING 11 11 - 2 11 MELSEC-F 1 1.1 How to Check Errors Using LED Displays This sectio n describes th e errors th at can be c hecked with the LED displays on the front of the Ethernet module. 1 1.1.1 Checking error display The following can be checked with the LED d isplays on the fr ont of the Ethernet module.
11 - 3 MELSEC-F TROUBLESHOOTING 11 11 - 3 (Continued from the previous p age) *1 Confirm the complet ion for the init ial processing and chec k whether or not there is any prob lem in the ca ble connection and the Ethern et lines.
11 - 4 MELSEC-F TROUBLESHOOTING 11 11 - 4 1 1.1.2 How to turn off COM.ERR LED a nd 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.
11 - 5 MELSEC-F TROUBLESHOOTING 11 11 - 5 (4) How to clear error informat ion by writing to buffer memory Writing to BFM# 31800 to 31802 allows clearing the error in formation and turn ing off COM.
11 - 6 MELSEC-F TROUBLESHOOTING 11 11 - 6 1 1.2 How to Check an Error Through FX Configurator-EN-L The status of the vario us settings for the Ethernet module can be checked using th e FX Configurator-EN-L functions. (1) Ethernet diagnostics (S ee Section 1 1.
11 - 7 MELSEC-F TROUBLESHOOTING 11 11 - 7 1 1.2.1 Buffer memory that ca n be monitored with the FX Configurator-EN-L diagnostic function The following is a list o f the buf fer memory addresses that can be displayed on th e "Ethernet diagnostics" scr een of FX Configur ator-EN-L.
11 - 8 MELSEC-F TROUBLESHOOTING 11 11 - 8 BFM address Decimal (hexadecimal) Applicable buf fer memory Ethernet di agnostics display screen Display contents 408 to 409 (198 to 199 H ) ICMP Received ICM.
11 - 9 MELSEC-F TROUBLESHOOTING 11 11 - 9 1 1.2.2 Ethernet diagnostics [Purpose] The block status of an Ether net module, paramete r settings, communication st atus, error log and others can be checked usi ng the Ethern et diagn ostic function of FX Configurator-EN-L .
11 - 10 MELSEC-F TROUBLESHOOTING 11 11 - 10 1 1.3 Checking the error inform ation by the buff er memory batch monitoring function It is explained here how the Ethernet m odu le errors can be checked fr om GX Developer .
11 - 11 MELSEC-F TROUBLESHOOTING 11 11 - 11 11 . 4 E r r o r C o d e L i s t This section exp lains the erro r codes (abnorm al codes) for the error s that may occur in each processing when communicat.
11 - 12 MELSEC-F TROUBLESHOOTING 11 11 - 12 (1) Initial error code (BFM#105) (a) This address stores th e error codes g enerated when the initial processing is executed. (b) Error codes are stored as binary values when the initial abnormal completion signal (BFM#28.
11 - 13 MELSEC-F TROUBLESHOOTING 11 11 - 13 (5) Error log area (BFM#227 to 372) This area stores the following errors. • Errors whose source cannot be confirmed • Errors that occurred during commu.
11 - 14 MELSEC-F TROUBLESHOOTING 11 11 - 14 (f) Error log block - Connection No. (sta rting from BFM#232) 1) The faulty connection No. is stored in bit s 0 to 3 of the correspondin g area. ("0" is stored in bit s 4 to 15). 2) For errors below the TCP and UDP levels, "0" is stored.
11 - 15 MELSEC-F TROUBLESHOOTING 11 11 - 15 (6) E-mail status storage area (BFM#22640 to 24575) * When the storage coun t exceeds FFFF H times, the count starts from 0 H again.
11 - 16 MELSEC-F TROUBLESHOOTING 11 11 - 16 6) Sending error log write pointer ( BFM#23360) • This address stores the error log block area num ber 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 blo ck 8 area.
11 - 17 MELSEC-F TROUBLESHOOTING 11 11 - 17 1 1.4.2 End codes (Complete codes) retu rned to an external device during data communication This sectio n explains th e end code s (compl ete codes) that are added to response s when com municating u sing the fixe d buffer or the M C protocol.
11 - 18 MELSEC-F TROUBLESHOOTING 11 11 - 18 1 1.4.3 Abnormal codes returned during communication using MC protocol This section explains the abnorm al codes (error codes) that are added to responses when communicating using MC protocol (A n abnor mal code is added only when an end code is "5B".
11 - 19 MELSEC-F TROUBLESHOOTING 11 11 - 19 1 1.4.4 Error codes stored in the buffer memory When an error occurs at each da ta communi cation processing be tween the Et hernet module and an external device, the error co de (ab normal code) is stored in the buf fer memory of the Ethernet module.
11 - 20 MELSEC-F TROUBLESHOOTING 11 11 - 20 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 23361 C001 H • At initial processing, t he IP address setting value of the E thernet module i s incorrect.
11 - 21 MELSEC-F TROUBLESHOOTING 11 11 - 21 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 23361 C020 H Data l ength exceeds the a llowable range.
11 - 22 MELSEC-F TROUBLESHOOTING 11 11 - 22 *1 When this error occurs, the COM.ERR light turns on, but turns of f again about one second later . Error code (abnormal code) Description of e rror Error .
11 - 23 MELSEC-F TROUBLESHOOTING 11 11 - 23 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 23361 C05F H The request could not b e executed on the t arget PLC.
11 - 24 MELSEC-F TROUBLESHOOTING 11 11 - 24 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 23361 C0C7 H An Ethernet module system error occurred.
11 - 25 MELSEC-F TROUBLESHOOTING 11 11 - 25 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 B.
11 - 26 MELSEC-F TROUBLESHOOTING 11 11 - 26 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 23361 C1 15 H to C1 18 H System error • The OS dete cted any error .
11 - 27 MELSEC-F TROUBLESHOOTING 11 11 - 27 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 23361 C139 H System error • The OS dete cted any error .
11 - 28 MELSEC-F TROUBLESHOOTING 11 11 - 28 Error code (abnormal code) Description of e rror Error h andling S torage destination Initial Open Fixed sending Connection Error code E-mail log BFM# 105 BFM# 124 BFM# 125 BFM# 126 BFM# 229 BFM# 23361 C160 H Received a response from the DNS server af ter timeout.
11 - 29 MELSEC-F TROUBLESHOOTING 11 11 - 29 * 1 T ake corrective action using the following procedure. 1) Check wh ether the expansion conn ectors are conn ected correct ly . 2) Check whether the opera ting environmen t of the Ethernet module is within the general specifications range of the module.
11 - 30 MELSEC-F TROUBLESHOOTING 11 11 - 30 (1) When communication is performed using fixed buf fer (with procedure) (a) If the data length specified immediately af ter the subhead er is smaller than .
11 - 31 MELSEC-F TROUBLESHOOTING 11 11 - 31 (2) When communication is performed using fixed buf fer (non-procedure ) Since no message data length is specif ied in non-pro cedure commu nication, the data received is stor ed in the receive buf fer area as is.
11 - 32 MELSEC-F TROUBLESHOOTING 11 11 - 32 1 1.5 T roubleshooting Flowchart This section explains some simple troubleshooting proce dures when the Ether net module and an external dev ice have communication probl ems in a flowchart fo rmat.
11 - 33 MELSEC-F TROUBLESHOOTING 11 11 - 33 *1 See Section 1 1.1 when the value of BFM#27 is "0000 H " or when the display LED COM.ERR (communication error detection display) lights up.
11 - 34 MELSEC-F TROUBLESHOOTING 11 11 - 34 POINT (1) When the Ether net module is replaced due to an error , reboot the following external devices and rest art dat a communication: (If the external device ret ains the Ethernet address, it may be impossible to continue communica tion because when a module is repl aced the Ethernet address changes.
11 - 35 MELSEC-F TROUBLESHOOTING 11 11 - 35 1 1.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 corresponding connection LEDs (C1-C2) lit? If so, modify the program.
11 - 36 MELSEC-F TROUBLESHOOTING 11 11 - 36 POINT If the external device communicates normally , the following conditions occur . For TCP communication When the external device 's open st atus is complete, LEDs C1, C2, which are in correspondence with connections 1, 2, turn on.
11 - 37 MELSEC-F TROUBLESHOOTING 11 11 - 37 1 1.5.2 Receiving errors during fixed buffer communication (common to procedure exist and no procedure) POINT Perform erro r code reading while the connection is open . NO YES 1) NO YES Receiving err or Check the open status of the connection with an ext ernal device.
11 - 38 MELSEC-F TROUBLESHOOTING 11 11 - 38 Does the external device operate normally? YES The Ethernet module hardware on the sending side may be faulty . Consult your nearest branch office or dealer with the details of the errors. NO Check the device on the sending side.
11 - 39 MELSEC-F TROUBLESHOOTING 11 11 - 39 POINT If the external device communicates normally , the following conditions occur . For TCP communication When the external device 's open st atus is complete, LEDs C1, C2, which are in correspondence with connections 1, 2, turn on.
11 - 40 MELSEC-F TROUBLESHOOTING 11 11 - 40 1 1.5.3 Errors in communica tion using MC protocol Communication error Check the open status of the connection with the external device. Are the corres- ponding connection LEDs (C3, C4) lit? NO YES W as a command sent form the external device? NO YES Send the command to the Ethernet module.
11 - 41 MELSEC-F TROUBLESHOOTING 11 11 - 41 POINT • If the external device communicate s no rmally, the following conditions occur. For TCP communication When the external device's open st atus is complete, LEDs C3, C4, which are in correspondence with connectio ns 3, 4, turn on.
11 - 42 MELSEC-F TROUBLESHOOTING 11 11 - 42 1 1.5.4 Sending errors dur ing e-mail communication Is "0001 H " written to BFM#10333? NO YES Correct the condition for writing to BFM#10333.
App - 1 APPENDIX App - 1 App MELSEC-F APPENDIX Appendix 1 P rocessing T ime Calculate the minim um proces sing time f or each fu nction usin g the expr essions be low .
App - 2 APPENDIX App - 2 App MELSEC-F (2) Minimum processing time of communication usi ng MC protocol (batch read and batch write) Tfs = Ke + (Kdt Df) + Scr number o f scans requ ired for pr ocessing .
App - 3 MELSEC-F APPENDIX App - 3 [Calculation example 1] Calculate the require d time (unit: ms ) to complete the processing of a data req uest from a PC after rece iving it, when the Etherne t modul.
App - 4 MELSEC-F APPENDIX App - 4 Appendix 2 ASCII Code List Appendix 3 R eferences For details on TCP/IP , refer to the DDN Protocol Handbook (3 volumes).
App - 5 MELSEC-F APPENDIX App - 5 Appendix 4 Program Examples The program examples pres ented in this section test the connection between the Ethernet module and an external device (p ersonal computer) that is connected to the same Ethe rnet.
App - 6 MELSEC-F APPENDIX App - 6 Appendix 4.1 Program example for communication using MC protocol -1 The following explains a program, its e xecution environment and the contents of d ata communication .
App - 7 MELSEC-F APPENDIX App - 7 (3) FX Configurator-EN-L settings Set the PLC parameters as follows. (a) Operation settings (b) Open settings Communication dat a code : ASC II Initial timing : Always wait for OPEN (Communication possible at STOP time) IP address : 172.
App - 8 MELSEC-F APPENDIX App - 8 (4) Program on the external device side The program example o f the external device shown be low accesse s the FX 3U of the station in which the Ethe rnet module is installed.
App - 9 MELSEC-F APPENDIX App - 9 #include <std io.h> #include <winsock.h> #define FLAG_OFF 0 // Completion flag OFF #define FLAG_ON 1 // Completion flag ON #define SOCK_OK 0 // Normal com.
App - 10 MELSEC-F APPENDIX App - 10 int main() { WORD wVersionRe quested=MAKEWORD(1,1); // Winsock Ver 1.1 request WSADATA wsaData; int length; // Communication data length unsigned char s_buf[BUF_SIZ.
App - 11 MELSEC-F APPENDIX App - 11 Closeflag=FLAG_ON; // Connection c ompletion fla g ON // Go to non-blocking mode ulCmdArg = 1; ioctlsocket(socketno, FIONBIO, &ulC mdArg); // Set to non-blockin.
App - 12 MELSEC-F APPENDIX App - 12 while(1) { length = re cv(socketno, &r _buf[rbuf_ idx], (BUF_SIZE - rbuf_idx), 0); // Response data receiving if(length == 0) { // Is connection cut off? Socker.
App - 13 MELSEC-F APPENDIX App - 13 case ERROR_BIND: printf("Faile d to bind."); break; case ERROR_CONNECT: printf("Failed to establish connection."); break; case ERROR_SEND: printf("Send ing failed."); break; case ERROR_RECIEVE: printf("Receiving failed.
App - 14 MELSEC-F APPENDIX App - 14 Appendix 4.2 Program example for communication using MC protocol -2 This section ex plains an ex ample of an ex ternal device program that r eads/writs dat a from the PLC. A sample p rogram, its executio n environmen t and cont ents of data communicat ion are shown below .
App - 15 MELSEC-F APPENDIX App - 15 (4) Window example (Form 1) (5) Sample program (Form 1) Parts in italic are created automatically by Visual Basic .NET, so no input is required. Only input where written in bold. Option Explicit On Option Strict On Imports System.
App - 16 MELSEC-F APPENDIX App - 16 Memo: The following proced ure is necessary for Windows Fo rm Designer. Change by using Windows Form Designe r. Do not use code editor to change. Friend WithEvents Start As System.Windows.Forms.Button Friend WithEvents lstOutput As System.
App - 17 MELSEC-F APPENDIX App - 17 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 specific ation PortNum = 10000 Client = New TcpClient 'Line connection proces sing Try Client.
App - 18 MELSEC-F APPENDIX App - 18 End If lstOutput.Select edIndex = lstOutput.Items.Coun t - 1 End If ' Line disconnection pro cessing Client.GetStrea m().
App - 19 MELSEC-F APPENDIX App - 19 Appendix 5 Differences between the Ethernet and the IEEE802.3 The following shows the Ethernet header in the dat a link layer supported by the Ethernet module.
App - 20 MELSEC-F APPENDIX App - 20 Appendix 7 S etting V a lue Recording Sheets This secti on provides settin g value re cording sheets fo r parame ters set with FX Configurator-EN-L Make copies as ne eded. Recording sheet 1 [Block number ] Setting value recording sheet No.
App - 21 MELSEC-F APPENDIX App - 21 Recording sheet 2 [Block number ] FX Configurator-EN-L setting screen Data item Setting dat a Setting value Remark Ethernet Initial settings T imer setting TCP ULP .
App - 22 MELSEC-F APPENDIX App - 22 Recording Sheet 3 [Block number ] FX Configurator-EN-L setting screen Data item Setting dat a Setting value Remark Ethernet open settings Connection No. Protocol TCP UDP Open system Active Setting not required if UDP is selected.
App - 23 MELSEC-F APPENDIX App - 23 Recording sheet 4 [Block number ] FX Configurator-EN-L setting screen Data item Setting dat a Setting value Remark Setting the Ethernet relay parameter Sub-net mask pat tern . . . Adjust to input forma t Default rout er IP address .
App - 24 MELSEC-F APPENDIX App - 24 Recording sheet 5 [Block number ] FX Configurator-EN-L setting screen Data item Setting dat a Setting value Remark Ethernet e-mail settings General settings Password Mail address Mail Server name SMTP setting SMTP Server name IP address Decimal IP address input format Hexadecimal .
App - 25 MELSEC-F APPENDIX App - 25 Appendix 8 V ersioin Information Ethernet Module ver sion is shown as "VERSION" on the label att ached to the right side of the module as seen from the front.
App - 26 MELSEC-F APPENDIX App - 26 MEMO.
W arranty Please confirm the following product warr anty details before using this pro duct. 1. Gratis Warranty Term and Gratis Warranty Range If any faults or defects (he reinafter "Failure".
Revised History Date Revi sion Desc riptio n 10/2009 A First Edition.
.
HEAD OFFICE: TOKYO BULDING, 2-7-3 MARUNOU CHI, CHYODA-KU, TOKYO 100-8310, JAPAN HIMEJI WORKS: 840, CHIYODA CHO, HIMEJI, JAPAN JY997D38001A (MEE) Effective Oct.
Ein wichtiger Punkt beim Kauf des Geräts Mitsubishi Electronics fx3u (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie Mitsubishi Electronics fx3u noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für Mitsubishi Electronics fx3u - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von Mitsubishi Electronics fx3u reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über Mitsubishi Electronics fx3u erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon Mitsubishi Electronics fx3u besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von Mitsubishi Electronics fx3u verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit Mitsubishi Electronics fx3u. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei Mitsubishi Electronics fx3u gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.
