Mitsubishi Electronics fx3u - page 13

A - 11 A - 11

Caution to conform with EC Directives

• Installation in Enclosure

Programmable logic controllers are open-type devices that must be installed and

used within conductive control cabinets. Please use the programmable logic

controller while installed within a conductive shielded control cabinet. Please secure

the cabinet door to the control cabinet (for conduction).

Installation within a control cabinet greatly affects the safety of the system and aids

in shielding noise from the programmable logic controller.

• Control cabinet

- The control cabinet must be conductive.

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

- To ensure that there is electric contact between the control cabinet and its door,

connect the cabinet and its doors with thick wires.

- In order to suppress the leakage of radio waves, the control cabinet structure must

have minimal openings. Also, wrap the cable holes with a shielding cover or other

shielding devices.

- The gap between the control cabinet and its door must be as small as possible by

attaching EMI gaskets between them.

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

cabinet.

Shielding cover

Shielded cable

Wires*1 EMI gasket

Contents

Main Page SAFETY PRECAUTIONS DANGER CAUTION [Design Precautions] DANGER [Design Precautions] [Installation Precautions] CAUTION [Wiring Instructions] DANGER CAUTION Page Page Page Page Page A - 9 A - 9 Page Page How to use this manual (1) Features and utility lists (2) Processing required prior to starting the operation of the Ethernet module (3) Connection between the Ethernet module and external devices (4) Details on the data communication functions (5) Data communication functions and programming (6) Checking for error occurrences and taking corrective actions FX Configurator-EN-L (FX3U-ENET-L Configuration tool) A - 14 A - 14 1 1OVERVIEW 1.1 Overview of the Ethernet Module Page Page (3) Sending by e-mail (Details are explained in Chapter 10) Page Page 1.3 Software Configuration (1) TCP (Transmission Control Protocol) Page Page 2 2 SYSTEM CONFIGURATIONS SYSTEM CONFIGURATIONS2 2.2 Devices Required for Network Configuration (1) Connection using the 100BASE-TX SYSTEM CONFIGURATIONS2 (2) Connection using the 10BASE-T 3 3 SPECIFICATIONS 3.1 Performance Specifications 3 - 2 The following explains each of the transmission specification items. 3 - 2 [Connecting using the 10BASE-T] [Connecting using the 100BASE-TX] 3.2 Data Codes for Communication Page (1) Communicability with external devices using various functions (2) Relationship with additional functions 3 - 6 3.4 Ethernet Module Function List Checks that the Ethernet module is working and can communicate normally. This section shows a list of Ethernet module functions. (1) Basic functions of the Ethernet module (2) Additional functions of the Ethernet module 3.5 List of Setting Items for Ethernet Modules The following table lists the parameter setting items that are set using Ethernet Module. Parameters set in FX Configurator-EN-L are saved in the Ethernet module's flash ROM. 3.6 List of Applications and Assignments of the Buffer Memory (1) Configuration of the buffer memory 3 - 9 (2) Assignments of the buffer memory b15 b14 b13 b12 b11 b10 b9 b8 b7 b6 b5 b4 b3 b2 b1 b0 3 - 10 3 - 11 (b) Communication parameter setting area (BFM #32 to 102) 3 - 12 3 - 13 (c) Communication status storage area (BFM #103 to 226) 3 - 14 3 - 15 (d) Error log partition area (BFM #227 to 511) 3 - 16 3 - 17 (e) Router relay parameter setting area (BFM #512 to 1599) 3 - 18 (f) Open/close control (BFM #1600 to 1663) 3 - 19 3 - 20 (g) Fixed buffer area (BFM #1664 to 9855) 3 - 21 (h) Mail send parameter settings (BFM #9856 to 20479) 3 - 22 *1 (example)192. 168. 0. 10 C0 A8 00 0A 4) 3) 2) 1) SMTP : BFM#9922 POP3 : BFM#9955 H L 2) 1) SMTP : BFM#9923 POP3 : BFM#9956 4) 3) 3 - 23 (i) Connection status storage area (BFM #20480 to 22639) 3 - 24 (j) E-mail status storage area (BFM #22640 to 31999) to b7 b0 Day of the week (0 to 6) 3 - 25 4 4 SETTINGS AND PROCEDURES PRIOR TO OPERATION 4.1 Loading and Installation 4.1.1 Handling precautions DANGER 4 4.1.2 Installation environment CAUTION 4.2 Settings and Procedures Prior to Starting the Operation Page 4 - 5 4.3 Components of the Ethernet Module This section shows the components of the Ethernet module. (1) LED display contents 4.4 Connecting to the Network CAUTION 4.4.1 Connecting to the 10BASE-T/100BASE-TX network Page 4 - 10 4.6 Operational Settings This section explains how to set the operations parameters. (1) Communication data code (BFM#24 b1) Page (4) Initial Timing (BFM#24 b8) (5) IP Address settings - IP address (BFM #0 to 1) 4.7 Self-Diagnostic Tests 4.7.1 Self loopback test 4.7.2 Hardware test (H/W Test) 4.8 Maintenance and Inspection 4.8.1 Maintenance and inspection DANGER CAUTION 4.8.2 Installing and uninstalling the module 5 5 COMMUNICATION PROCEDURE 5.1 Overview of the Communication Procedure 5 - 2 5.2 Initial Processing 5.2.1 Initial processing (1) Parameters required for initial processing (2) Confirmation of initial processing result 5 - 4 5.2.2 Initial settings *1 Details are explained in Section 10.6. This section explains the initial settings. (1) Timer setting - TCP ULP timer (BFM#4) (2) Timer setting - TCP zero window timer (BFM#5) (3) Timer setting - TCP resend timer (BFM#6) (4) Timer setting - TCP end timer (BFM#7) Page Page Page Page 5.2.3 Re-initialization (1) Purposes of performing re-initialization 5 - 11 (2) Programming and timing for re-initialization (3) Operation for re-initialization 5.3 Router Relay Parameter (1) Router relay function (BFM#2 b4,b5) (2) Subnet mask pattern (BFM#512, 513) (3) Router IP address (BFM#514, 515) 5.4 Confirming the Completion of the Initial Processing 5.4.1 PING command (Personal computer Ethernet module) 5.4.2 Loop back test (Communication using MC protocol) 5.5 Open Settings 5.5.1 Fixed buffer connection (connection No. 1 and connection No. 2) (1) Protocol (connection numbers 1, 2; BFM#32, 33 b8) 5 - 19 (2) Open system (connection numbers 1, 2; BFM#32, 33 b15, b14) PLC main unit PLC main unit (3) Fixed buffer (connection numbers 1, 2; BFM#32, 33 b0) Ethernet module Ethernet module (4) Fixed buffer communication (connection numbers 1, 2; BFM#32, 33 b9 to b10) (5) Pairing open (connection numbers 1 only; BFM#32 b7) (6) Existence confirmation (connection numbers 1, 2; BFM#32, 33 b1) (7) Local station Port No. (connection numbers 1, 2; BFM#40, 47) (8) Destination IP address (connection numbers 1, 2; BFM#41 to 42, 48 to 49) (9) Destination Port No. (connection numbers 1, 2; BFM#43, 50) Page 5.5.2 MELSOFT/MC protocol connections (connection No. 3 and connection No. 4) (1) Local station Port No. (connection numbers 3, 4; BFM#54, 61) (2) Destination IP address (connection numbers 3, 4; BFM#55 to 56, 62 to 63) (3) Destination Port No. (connection numbers 3, 4; BFM#57, 64) 5.6 Open Processing/Close Processing of the Connection (1) Open processing (2) Close processing 5 - 27 5.6.1 Active open processing/close processing <<Open processing for connection No.1>> Page Page Page Program example 5 - 32 5.6.2 Passive open processing/close processing (1) When "Always wait for OPEN" is selected in the operational setting (2) When "Do not wait for OPEN" is selected in the operational setting 5 - 35 Page Page Program example 5 - 39 Page 5 - 41 <<Open processing for connection No.1>> <<Close processing for connection No.1>> Page 5.7 Pairing Open 5.7.1 Pairing open Page Page 5.8 Hub Connection Status Monitor Function (1) Hub connection status area (BFM#201) (2) Disconnection detection count storage area (BFM#20995) FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST 6 6 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST CONTROL METHOD) 6.1 Control Method Page 6 - 3 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST 6 - 3 6.2 Sending Control Method Page Page 6 - 6 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST Data receiving Response 6 - 6 6.3 Receiving Control Method Page FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST 6.4 Data Format 6.4.1 Header 6 - 9 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST (b) Communication using ASCII code 6 - 9 6.4.2 Application data (1) Format FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST 6 - 10 (2) Subheader FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST (3) Data length setting (4) Text (command) 6 - 12 FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST 6 - 12 (b) Communication using ASCII code (5) End codes FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST 6.5 Programming 6.5.1 Precautions when creating programs FIXED BUFFER COMMUNICATION (WITH THE PROCEDURE EXIST 6.5.2 Fixed buffer communication program example (with the procedure exist control method) Page Page 6 - 17 (Send program) (See Subsection 5.6.1) Open processing program 6 - 18 (Receive program) FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE 7 7 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE CONTROL METHOD) 7.1 Control Method Page Page 7 - 4 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE 7 - 4 7.2 Sending Control Method Page 7 - 6 FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE 7 - 6 7.3 Receiving Control Method 7.3.1 Receive processing with the main program Page FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE 7.4 Data Format (1) Header (2) Application Data FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE 7.5 Programming 7.5.1 Precautions when creating programs FIXED BUFFER COMMUNICATION (WITH THE NO PROCEDURE 7.5.2 Fixed buffer communication program example (with the no procedure control method) Page Page 7 - 13 (Send program) 7 - 14 (Receive program) Program example for the unit No. 0 8 8 COMMUNICATION USING MC PROTOCOL 8.1 Data Communication Function 8.1.1 Accessing the PLC using MC protocol (1) Data read/write (2) Remote control of the PLC 8.1.2 How to Read the Control Procedures of the MC Protocol (1) Transmission of command messages (2) When a normal completion response message to a command message cannot be received 8.1.3 Access Timing on the PLC Side 8.1.4 PLC setting for performing data communication 8.1.5 Precautions on Data Communication (1) Precautions that should be observed when performing data communication via the Ethernet module Page 9 9 WHEN COMMUNICATING DATA USING THE MC PROTOCOL 9.1 Message Formats and Control Procedures 9.1.1 How to read the command reference section (1) When an external device reads data from the PLC (2) When an external device writes data to the PLC 9.1.2 Message format and control procedure (1) Message format 9 - 4 (2) Control procedure Exists only when the complete code is "5B." Abnormal code PLC side Text (Command) 9 - 5 2) When writing data 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) 9 - 6 2) When writing data to the local station PLC from the external device side PLC side External device side (Response message) (Normal completion) (Abnormal completion) 9.1.3 Contents of data designation items (1) Header (2) Subheader (3) PC number (4) Monitoring timer (6) Character field (response) (7) Complete code (8) Abnormal code 9 - 9 (b) The order when receiving a response (external device Ethernet module) (1) Format when communicating in binary code (a) The order when sending a command (external device Ethernet module) 9 - 10 (2) Format when communicating in ASCII code (b) The order when receiving a response (external device Ethernet module) (a) The order when sending a command (external device Ethernet module) 9 - 11 9.1.4 Character area transmission data MMMMMM MM MM MM MM MM MMMMMMMM MM MM MM MM 010011001101 10101011000100100011 Indicating the ON/OFF status of 32 points from M16 9 - 12 Indicating the storage contents of data registers D350 and D351 (2) Data communication using binary code Page 9 - 15 9.2 List of Commands and Functions for The MC protocol *1 When the double word data is read using the user program, etc., read out the 32bit data at once. The following table lists the commands and functions when an external device accesses the PLC. 9 - 16 9.3 Device Memory Read/Write 9.3.1 Commands and device range (1) Commands used for reading from and writing to the device memory 9 - 17 (2) Designation method and accessible range of devices. (b) The following table outlines the device codes and numbers. Device list B15 B0 B31 B0 to to Device code Device number (Set in hexadecimal) [Example] In case of D100 D100 = 4420 00000064 Device number (hexadecimal) Device code Page 9 - 19 9.3.2 Batch read in bit units (command: 00) Use the designation "00H" when the number of device points is 256 points. Reading the on/off status of M100 to M111 of the PLC on which the FX3U-ENET-L is loaded. 9 - 20 9 - 21 9.3.3 Batch write in bit units (command: 02) Writing the on/off status of M50 to M61 of the PLC on which the Ethernet module is loaded. 9 - 22 9 - 23 9.3.4 Test in bit units (random write) (command: 04) Specifying Y45 to ON, M60 to OFF, and S38 to ON at the PLC on which the Ethernet module is loaded. 9 - 24 9 - 25 9.3.5 Batch read in word units (command: 01) 9 - 26 9 - 27 32 points x 2 = 64 word 4 bytes x 32=128 bytes L - - - - H (1) When communicating in binary code 12345678=00BC614E 45678912=02B90140 CN220 External device side (2) When communicating in ASCII code Low 16bit High 16bit Low 16bit High 16bit code Complete PC No. 9.3.6 Batch write in word units (command: 03) Writing data to D100 to D102 of the PLC on which the Ethernet module is loaded. 9 - 30 9 - 31 32 points x 2 = 64word L - - - - H L - H L - H L - H L - H (1) When communicating in binary code L H (2 bytes x 2) x 32 = 128 bytes External device side (2) When communicating in ASCII code x 2) (4 bytes points PC No. 9.3.7 Test in word units (random write) (command: 05) 9 - 34 Page 9 - 36 9.4.2 Remote RUN (command: 13) / Remote STOP(Command: 14) Monitoring PLC side For remote RUN 93 For remote STOP 94 Page 9 - 38 9.4.3 PLC model name read (command: 15) (1) Data communication in binary code (2) Data communication in ASCII code Distinguish the PLC model name by the model name code. "F3 9.5 Loopback Test 9.5.1 Loopback test (command: 16) (1) Performing a loopback test while communicating in binary code 9 - 40 (2) Performing a loopback test while communicating in ASCII code 10 10 USING THE E-MAIL FUNCTION 10.1 E-mail Function 10.1.1E-mail send by the PLC Page 10.2 Configuration and Environment of the Applicable System 10.3 Precautions for Using the E-mail Function 10 - 5 10.4 E-mail Specifications The following table lists the specifications of the e-mail function. 10 - 6 10.5 Processing Procedure of the E-mail Function The following flowchart illustrates the procedure that is required before sending e-mails: 10.6 E-mail Settings Page (3) Send mail address setting 10.7 Sending E-mail (Attached Files) by the PLC 10.7.1When sending data as an attached file 10 - 11 The table below shows the buffer memory to be used for sending mail. 10 - 12 Program example for the unit No. 1 10 - 13 Page Page 10.7.2Contents of the attached files 10.8 Sending E-mail (Main Text) by the PLC 10.8.1When sending data as main text of e-mail 10 - 18 The table below shows the buffer memory to be used for sending mail. Page 11 11 TROUBLESHOOTING 11 - 2 11.1 How to Check Errors Using LED Displays 11.1.1Checking error display 11 - 3 11.1.2How to turn off COM.ERR LED and to read/clear error information (1) How to turn off [COM.ERR] LED using buffer memory COM.ERR off (3) Reading buffer memory to read error information 11 - 5 (4) How to clear error information by writing to buffer memory Writing to BFM#31800 to 31802 allows clearing the error information and turning off COM.ERR. 11.2 How to Check an Error Through FX Configurator-EN-L (1) Ethernet diagnostics (See Section 11.2.2.) (2) Buffer memory batch monitor (See Section 11.3.) 11 - 7 11.2.1Buffer memory that can be monitored with the FX Configurator-EN-L diagnostic function 11 - 8 11.2.2Ethernet diagnostics Diagnostics Diagnostics 11.3 Checking the error information by the buffer memory batch monitoring function Start Monitor 11 - 11 11.4 Err or Co de Li st 11.4.1Type of error incident The details of errors and error handling procedures are described. Page (5) Error log area (BFM#227 to 372) Page (6) E-mail status storage area (BFM#22640 to 24575) Page 11 - 17 11.4.2End codes (Complete codes) returned to an external device during data communication 11.4.3Abnormal codes returned during communication using MC protocol 11.4.4Error codes stored in the buffer memory 11 - 20 11 - 21 11 - 22 *1 When this error occurs, the COM.ERR light turns on, but turns off again about one second later. 11 - 22 11 - 23 11 - 24 11 - 25 11 - 26 11 - 27 11 - 28 Page Page Page 11 - 32 11.5 Troubleshooting Flowchart 11 - 33 [example] When communication is performed using a fixed buffer. Page 11 - 35 11 - 36 11 - 37 1) Perform error code reading while the connection is open. 11 - 38 Page 11 - 40 11.5.3Errors in communication using MC protocol Page 11 - 42 11.5.4Sending errors during e-mail communication App APPENDIX Appendix 1 Processing Time App (2) Minimum processing time of communication using MC protocol (batch read and batch write) Page Appendix 2 ASCII Code List Appendix 3 References Appendix 4 Program Examples (1) Receive processing of target device Background Appendix 4.1 Program example for communication using MC protocol -1 (1) Execution environment of the program example (3) FX Configurator-EN-L settings (4) Program on the external device side (2) Outline of the procedure for calling the socket routine REMARK Page Page Page Page Page Page (4) Window example (Form 1) (5) Sample program (Form 1) Page Page Page App - 19 Appendix 5 Differences between the Ethernet and the IEEE802.3 Destination address Source address Length Data (46 to 1500 bytes) FCS The following shows the Ethernet header in the data link layer supported by the Ethernet module. (1) Ethernet (2) IEEE802.3 Appendix 7 Setting Value Recording Sheets Recording sheet 1 App - 21 Recording sheet 2 App - 22 Recording Sheet 3 Page App - 24 Recording sheet 5 Page Page Warranty 1. Gratis Warranty Term and Gratis Warranty Range [Gratis Warranty Term] [Gratis Warranty Range] 2. Onerous repair term after discontinuation of production