Mitsubishi Electric Melsec WS Series User Manual
  1. Manuals
  2. Brands
  3. Mitsubishi Electric Manuals
  4. Controller
  5. Melsec WS Series
  6. User manual

Mitsubishi Electric Melsec WS Series User Manual

Safety controller ethernet interface module
Hide thumbs Also See for Melsec WS Series:
Table of Contents

Advertisement

Quick Links

Download this manual
Safety Controller Ethernet Interface Module
User's Manual
-WS0-GETH

Advertisement

Table of Contents
loading

Related Manuals for Mitsubishi Electric Melsec WS Series

Summary of Contents for Mitsubishi Electric Melsec WS Series

  • Page 1 Safety Controller Ethernet Interface Module User's Manual -WS0-GETH...
  • Page 3 Copyright Law. Alteration or abridgement of the document is not permitted without the explicit written approval of the company Mitsubishi Electric Corporation.

  • Page 4: Safety Precautions

     SAFETY PRECAUTIONS  (Read these precautions before using this product.) Before using this product, please read this manual, the relevant manuals, and the safety standards carefully and pay full attention to safety to handle the product correctly. The precautions given in this manual are concerned with installation of this product and wiring with the external application only.
  • Page 5 CAUTION  Do not install the control lines or communication cables together with the main circuit lines or power cables. Keep a distance of 100 mm or more between them. Failure to do so may result in malfunction due to noise. ...
  • Page 6 [Wiring Precautions] CAUTION  Switch the entire machine/system off line. The system could start up unexpectedly while you are connecting the devices.  Connectors for external devices must be crimped or pressed with the tool specified by the manufacturer, or must be correctly soldered. Incomplete connections could result in short circuit, fire, or malfunction. ...

  • Page 7: Conditions Of Use For The Product

     CONDITIONS OF USE FOR THE PRODUCT  (1) Although MELCO has obtained the certification for Product's compliance to the international safety standards IEC61508, ISO13849-1 from TUV Rheinland, this fact does not guarantee that Product will be free from any malfunction or failure. The user of this Product shall comply with any and all applicable safety standard, regulation or law and take appropriate safety measures for the system in which the Product is installed or used and shall take the second or third safety measures other than the Product.

  • Page 8: Revisions

    This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot be held responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.

  • Page 9: Table Of Contents

    CONTENTS SAFETY PRECAUTIONS .................... 1 CONDITIONS OF USE FOR THE PRODUCT ............4 REVISIONS ......................... 5 CONTENTS ......................... 6 GENERIC TERMS AND ABBREVIATIONS ..............8 About this document ..................9 Function of this document ................. 9 MELSEC-WS manuals ................9 Target group .....................
  • Page 10 Default settings for the input data set 1 ........... 50 Customizing the input data set 1 (MELSEC-WS to Ethernet) ....51 4.4.1 The toolbar ................... 52 4.4.2 Available data area ................53 4.4.3 Network Module Data area ..............54 4.4.4 Tag names area ...................

  • Page 11: Generic Terms And Abbreviations

    Ethernet interface Another name for the WS0-GETH module Network module A generic term for the WS0-GETH and WS0-GCC1 Q series The abbreviation for the Mitsubishi Electric MELSEC-Q series programmable programmable controller controller QJ71E71-100 The abbreviation for the MELSEC QJ71E71-100 Ethernet module...

  • Page 12: About This Document

    About this document MELSEC-WS 1. About this document Please read the SAFETY PRECAUTIONS, Chapter 1, and Chapter 2 carefully before working with this documentation and the MELSEC-WS safety controller Ethernet interface module. 1.1 Function of this document This manual only applies in conjunction with the other MELSEC-WS manuals (see Section 1.2) and instructs the technical staff of the machine manufacturer and/or of the machine operator on safe mounting, adjustment, electrical installation, commissioning as well as operation and maintenance of the Ethernet interface...

  • Page 13: Target Group

    About this document MELSEC-WS The following shows the relevant manuals. Title Number Table 1: Overview of the WS-CPU-U-E Safety Controller User’s Manual (13JZ32) MELSEC-WS manuals Safety Controller Ethernet Interface Module User's WS-ET-U-E (13JZ33) Manual Safety Controller CC-Link Interface Module User's WS-CC-U-E Manual (13JZ45)

  • Page 14: Depth Of Information

    About this document MELSEC-WS 1.4 Depth of information This manual contains information on the Ethernet interface module in the following subjects:  mounting  implementation into a network  configuration via Setting and Monitoring Tool  data transfer to and from the network ...

  • Page 15: On Safety

    On safety MELSEC-WS 2. On safety This chapter deals with your own safety and the safety of the equipment operators.  Please read this chapter carefully before working with an Ethernet interface module. 2.1 Qualified safety personnel The Ethernet interface module may only be installed, commissioned and serviced by qualified safety personnel.
  • Page 16 Pay attention to the safety notes and safety measures on the Ethernet interface module! ATTENTION If the device is used for any other purposes or modified in any way - also during mounting and installation - any warranty claim against Mitsubishi Electric Corporation shall become void. Note ...

  • Page 17: Environmental Protection

    On safety MELSEC-WS 2.3 Environmental protection The Ethernet interface module has been designed to minimize environmental impact. It uses only a minimum of power and natural resources.  At work, always act in an environmentally responsible manner. 2.3.1 Disposal Disposal of unusable or irreparable devices should always occur in accordance with the applicable country-specific waste-disposal regulations (e.g.

  • Page 18: Ethernet Interface Module

    Ethernet interface module MELSEC-WS 3. Ethernet interface module This chapter describes the Ethernet interface module (WS0-GETH). 3.1 Overview The Ethernet interface module is connected to Setting and Monitoring Tool, a MELSEC programmable controller, and PC via TCP/IP. The module can: ...
  • Page 19 Ethernet interface module MELSEC-WS Table 3: Meaning Meaning of the LED No power supply  displays  Green Power supply switched on LINK/ACT 1 No Ethernet connection  LINK/ACT 2  Green Ethernet connection active, no data transmission Green Ethernet connection active, data transmission No power supply or immediately after the module start ...

  • Page 20: Mounting/Dismantling

    Ethernet interface module MELSEC-WS 3.2 Mounting/Dismantling This chapter describes the mounting of the Ethernet interface module. Make sure that the connection of the Ethernet interface module cannot lead to hazardous situations during installation! ATTENTION Ensure that connecting an Ethernet interface module cannot lead to a hazardous situation when implementing the unit on to the MELSEC-WS safety controller and Ethernet network.
  • Page 21 Ethernet interface module MELSEC-WS Figure 2: Mounting the module onto the DIN rail  Make sure that the voltage supply of the MELSEC-WS safety controller is switched off.  Hang the device onto the DIN rail (1)).  Connect the Ethernet interface module directly onto the right side of the CPU module of the MELSEC-WS safety controller.

  • Page 22: Steps For Dismantling The Modules

    Ethernet interface module MELSEC-WS 3.2.2 Steps for dismantling the modules Figure 4: Disconnecting the plug connections  Disconnect the cables and remove the end clips.  If there are several modules, slide the modules away from each other individually in the direction of the arrow until the side plug connection is separated.

  • Page 23: Electrical Installation

    Ethernet interface module MELSEC-WS 3.3 Electrical installation Switch the entire machine/system off line! The system could start up unexpectedly while you are connecting the devices. ATTENTION  Note The Ethernet interface module fulfills the EMC requirements in accordance with the basic specification EN 61000-6-2 for industrial use. ...
  • Page 24 Ethernet interface module MELSEC-WS Figure 6: Connection settings dialog  To edit the settings click on the pencil icon to the right. The following dialog appears: Figure 7: Modify profile dialog  Modify the settings if required.  Click OK. The dialog closes. ...

  • Page 25: Assignment Of An Ip Address

    Ethernet interface module MELSEC-WS As an example, the following hardware configuration may appear: Figure 8: Hardware configuration dialog  Click Disconnect to go into the offline mode if you want to change the configuration of the MELSEC-WS modules. 3.4.2 Assignment of an IP address ...
  • Page 26 Ethernet interface module MELSEC-WS Figure 9: Network module configuration dialog On the left side of the dialog you will find the area for the Ethernet interface module IP configuration.  If desired, enter a Device name for the Ethernet interface module. ...

  • Page 27: Configuration Of The Ethernet Interface Module

    Ethernet interface module MELSEC-WS You can assign an IP address from Network settings in the Connection settings dialog.  Click on the Network settings button. The Network scan dialog is opened.  Click on the Scan button. Your network is scanned for connected network modules and the network modules found are displayed in the list.

  • Page 28: Transfer Of A Configuration

    Ethernet interface module MELSEC-WS 3.4.4 Transfer of a configuration Once you have finished the configuration, you have to transfer the configuration to your MELSEC-WS safety controller. In order to transfer a configuration, perform the following steps:  Click Connect to go online. The Setting and Monitoring Tool connects to the MELSEC-WS safety controller.

  • Page 29: Verification Of A Configuration

    Ethernet interface module MELSEC-WS 3.4.5 Verification of a configuration After the configuration has been transferred successfully, the MELSEC-WS safety controller can be verified. To this purpose, the downloaded configuration data are read back out from the safety controller and compared with the project data. If they match, the data are displayed in a report.

  • Page 30: Features Of The Ethernet Interface Module

    Ethernet interface module MELSEC-WS 3.5 Features of the Ethernet interface module 3.5.1 TCP/IP configuration interface The Ethernet interface module offers a TCP/IP configuration interface which allows the configuration of the MELSEC-WS safety controller over Ethernet TCP/IP. This runs parallel to the Ethernet TCP/IP. Do not connect to the MELSEC-WS safety controller via the RS-232 and the Ethernet interface at the same time! ATTENTION...
  • Page 31 Ethernet interface module MELSEC-WS Figure 11: Com settings dialog  Click on Add TCP/IP profile. The following dialog appears: Figure 12: Create new TCP/IP profile dialog  Select your Ethernet network adaptor from the drop down list.  Click on Scan to search for Ethernet interface modules on your Ethernet network.
  • Page 32 Ethernet interface module MELSEC-WS Figure 13: Create new TCP/IP profile dialog after scan has been performed  Select the Ethernet interface module that you want to use for the new profile.  Enter a name for the entry point to the Entry name edit field. ...
  • Page 33 Ethernet interface module MELSEC-WS Figure 15: Connection settings dialog with new TCP/IP profile activated  Click OK. All communication to the MELSEC-WS safety controller will now happen via TCP/IP. In order to use the entry point via the serial interface again, you will have to re-activate it.

  • Page 34: Ethernet Tcp/Ip Socket Interface

    Ethernet interface module MELSEC-WS 3.5.2 Ethernet TCP/IP socket interface Each Ethernet interface module supports a total number of four TCP/IP socket interfaces. This allows up to four different applications to communicate with the Ethernet interface module at the same time over Ethernet TCP/IP. Do not use the same output data set number for two different programmable controller connections or TCP/IP sockets! ATTENTION...
  • Page 35 Ethernet interface module MELSEC-WS Configuration of the TCP/IP interface - who establishes the connection If the Ethernet interface module shall connect to the external application, perform the following configuration steps:  Activate the Connect to radio button.  Set IP address to the IP address of the computer the application is running on. ...
  • Page 36 Ethernet interface module MELSEC-WS General telegram structure The request/response message (e.g. telegram) is structured as shown below: … … … … … … … … … … … … Command Parameter(s) Data (content depends on type of command) Each element in the request/response messages is transferred in Big Endian format. Table 4: Parameter Length...
  • Page 37 Ethernet interface module MELSEC-WS Table 6: Parameter Length Value Input data set read Command WORD 00F1 Data set(s) request message request Request data WORD 0 = Do not send data set 1. set 1 1 = Send data set 1. Request data WORD 0 = Do not send data set 2.
  • Page 38 Ethernet interface module MELSEC-WS Each output data set length of the Ethernet interface module is 10 bytes long. Note The response message is returned to the application by the Ethernet interface module. The response message telegram is structured as shown below: Table 9: Parameter Length...
  • Page 39 Ethernet interface module MELSEC-WS Figure 17: TCP/IP configuration for polling mode  Check the Listen to checkbox.  Enter the Port number on which the application will connect.  Select the update mode: Enable COS update or Enable auto update and COS.
  • Page 40 Ethernet interface module MELSEC-WS Table 10: Parameter Length Value Auto update mode Command WORD 00E1 Auto update control configuration command Request data set 1 WORD 0 = Do not send data set 1. 1 = Send data set 1. Request data set 2 WORD 0 = Do not send data set 2.
  • Page 41 Ethernet interface module MELSEC-WS Figure 18: TCP/IP configuration for auto update  Check the Connect to checkbox.  Enter the IP address and the Port number the Ethernet interface module shall write to.  Select the update mode: Enable COS update or Enable auto update and COS.

  • Page 42: Tcp/Ip Process Image Example

    Ethernet interface module MELSEC-WS Normal operation The following message is sent from the Ethernet interface module to the application while operating in auto update mode. Table 12: Parameter Length Value Auto update mode Command WORD 002E = Auto update data set(s) message normal operation Data set 1 length WORD...
  • Page 43 Ethernet interface module MELSEC-WS Byte values Part of message Meaning (hex) 52 A1 10 4C Overall CRC (same as system CRC) 52 A1 10 4C System CRC 00 00 00 00 Data set 2 00 00 00 00 (see Table 15) 00 00 00 00 Reserved 00 00 00 00...
  • Page 44 Ethernet interface module MELSEC-WS Byte values Part of message Meaning (hex) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Data set 4 Reserved 00 00 00 00...

  • Page 45: Data Sets

    Data sets MELSEC-WS 4. Data sets The Ethernet interface module allows the MELSEC-WS safety controller to send and receive non-safety related data to and from the external fieldbus system for control and diagnostics purposes. Note In this manual, the data exchanged between the MELSEC-WS safety controller and the respective network will be considered always from the network master (programmable controller) point of view.

  • Page 46: Data Transmitted Into The Network (Network Input Data Sets)

    Data sets MELSEC-WS 4.1 Data transmitted into the network (network input data sets) Available data The Ethernet interface module can provide the following data:  Operational data – Logic results from the CPU module (see Section 4.1.1) – Input values (Active/Inactive) for all safety I/O modules in the system and EFI devices connected (see Section 4.1.2) –...
  • Page 47 Data sets MELSEC-WS Table 15 shows the overview of data sets available for the Ethernet interface module. Table 15: Data set 1 (default) Data set 2 Data set 3 Overview input data Byte 0 Logic result 0 Overall CRC Module status module 0. sets 1 to 3 Module 0 is always the CPU.

  • Page 48: Logic Results

    Data sets MELSEC-WS 4.1.1 Logic results Logic results generated by the logic editor of the CPU module can be made available to the network. Up to 20 bytes are available where each bit represents one logic result from the logic editor. Data set 1 containing the logic results can be customized.

  • Page 49: Configuration Checksums (Crcs)

    Data sets MELSEC-WS 4.1.4 Configuration checksums (CRCs) Data set 2 contains the following configuration CRCs for the MELSEC-WS safety controller:  Overall CRC (same as system CRC). The overall CRC is the checksum displayed in the Setting and Monitoring Tool report. ...
  • Page 50 Data sets MELSEC-WS Safety I/O modules CPU modules Network modules Byte (e.g. WS0-XTIO, WS0-XTDI) (e.g. WS0-CPUx) (e.g. WS0-GETH) Output fast shut off logic control time EFI 1 communication failure Output status 1 = No error 1 = Valid network 1 = No error 0 = Error communication 0 = Time out exceed because the...
  • Page 51 Data sets MELSEC-WS Safety I/O modules CPU modules Network modules Byte (e.g. WS0-XTIO, WS0-XTDI) (e.g. WS0-CPUx) (e.g. WS0-GETH) Input 4 external test signal failure. 1 = No error 0 = Error Input 5 external test signal failure. 1 = No error 0 = Error Input 6 external test signal failure.

  • Page 52: Data Received From The Network (Network Output Data Sets)

    Data sets MELSEC-WS 4.2 Data received from the network (network output data sets) The data received from the network are organized in output data sets (max. 50 bytes). These data have been subdivided in five data blocks holding 10 bytes each for the Ethernet interface module.

  • Page 53: Default Settings For The Input Data Set 1

    Data sets MELSEC-WS 4.3 Default settings for the input data set 1 In the delivery status, the input data set 1 of the Ethernet interface module is pre- configured. The following table gives an overview which bytes are assigned to the default configuration and how the data are modularized.

  • Page 54: Customizing The Input Data Set 1 (Melsec-Ws To Ethernet)

    Data sets MELSEC-WS 4.4 Customizing the input data set 1 (MELSEC-WS to Ethernet) This section outlines briefly how you can customize the input data set 1 that the Ethernet interface module transmits to the network. In the delivery status, the data routing configuration of the Ethernet interface module is shown in the network module configuration dialog.

  • Page 55: The Toolbar

    Data sets MELSEC-WS 4.4.1 The toolbar Figure 20: Toolbar for the routing configuration The toolbar contains buttons for the following actions (from left to right):  The Load user configuration and Save user configuration buttons allow you to load and/or save a configuration including the used tag names in XML format. If you load a configuration, all previously made changes that have not been saved will be lost.

  • Page 56: Available Data Area

    Data sets MELSEC-WS 4.4.2 Available data area This area offers all sources from which data may be routed into the network. It is divided in two views holding the available Input types and Output data. You can switch between these views using the file cards at the bottom. ...

  • Page 57: Network Module Data Area

    Data sets MELSEC-WS 4.4.3 Network Module Data area This area contains the routing table. It shows the current content of the Ethernet interface module’s input data modules. Bytes and bits highlighted blue will hold “live” data from the system since the hardware configuration does support the source. Bytes highlighted grey actually do not have data associated with them since the hardware configuration does not support the sources.

  • Page 58: Tag Names For Incoming Data (Ethernet To Melsec-Ws)

    Data sets MELSEC-WS 4.5 Tag names for incoming data (Ethernet to MELSEC- In order to enable incoming data bits:  Click on Ethernet to MELSEC-WS on the left hand menu. The following dialog appears: Figure 21: Ethernet to MELSEC- WS dialog of the WS0- GETH Basically this dialog is divided into two areas: Network Module Data (1)) and Tag names (2)):...
  • Page 59 Data sets MELSEC-WS Each bit you enter a tag name for here will be available within the logic editor or for the process image of a second network module: Figure 22: Tag names of incoming bits of the WS0-GETH in the logic editor dialog...

  • Page 60: Saving And Loading A Configuration

    Data sets MELSEC-WS 4.5.1 Saving and loading a configuration Using the buttons Load user configuration and Save user configuration you can save and load your configuration in XML format. If you load a configuration, all previously made changes that have not been saved will be lost. You can not undo this action.

  • Page 61: Monitoring The Data Set Online

    Data sets MELSEC-WS 4.6 Monitoring the data set online When the MELSEC-WS safety controller is online and running, you can monitor the data set online in the network module configuration dialog.  Click on the GETH Network module [13] button (Network Modules button when two network modules are used) above the main window and select the desired Ethernet interface module or double click the desired Ethernet interface module in the hardware configuration to open the network module configuration...

  • Page 62: Troubleshooting

    Troubleshooting MELSEC-WS 5. Troubleshooting For information how to perform diagnostics on the MELSEC-WS safety controller please refer to the Safety Controller Setting and Monitoring Tool Operating Manual. Check the LEDs of the module during troubleshooting. Note Table : Troubleshooting for the WS0-GETH Error Cause Possible remedy...
  • Page 63 Troubleshooting MELSEC-WS Error Cause Possible remedy WS0-GETH functioned WS0-GETH is operated in slave Either assign a fixed IP address to the WS0- correctly after configuration, but mode, the IP address is assigned GETH, or reserve a fixed IP address for the suddenly no longer supplies from a DHCP server.

  • Page 64: Technical Specifications

    Technical specifications MELSEC-WS 6. Technical specifications 6.1 Technical specifications of Ethernet interface module Table 20: Interface Technical specifications Fieldbus Ethernet TCP/IP of Ethernet interface Integrated switch 3-port layer-2 managed switch with Auto-MDI-X for module automatic detection of crossed Ethernet cable Connection technique RJ45 socket Transfer rate...
  • Page 65 Technical specifications MELSEC-WS Mechanical strength Vibration resistance, shock resistance Tested in accordance with IEC 61161-2. Electrical safety (see WS0-CPUx) Protection class Electromagnetic compatibility IEC 61000-6-2/EN 55011 Class A Mechanical and assembly Housing material Polycarbonate Housing type Device for control cabinet installation Housing enclosure rating/terminals IP 40/IP 20 Housing color...

  • Page 66: Dimensional Drawings

    Technical specifications MELSEC-WS 6.4 Dimensional drawings Figure 26: 114.4 Dimensional drawings of WS0-GETH (mm) 93.7 22.5 120.8 Unit : mm 6.5 Module information Table 23: Type Module name Abbreviation Module information WS0-GETH00200 MELSEC-WS safety controller Ethernet interface WS0-GETH module...

  • Page 67: Connecting To Melsec Programmable Controllers

    Connecting to MELSEC programmable controllers MELSEC-WS 7. Connecting to MELSEC programmable controllers This chapter describes how to exchange non-safety related data (input/output data) between the MELSEC-WS safety controller and MELSEC programmable controllers via TCP/IP. In this or later chapters, each Ethernet interface module in a MELSEC-WS safety controller system and MELSEC programmable controller system is referred to as follows: ...

  • Page 68: Applicable System

    Connecting to MELSEC programmable controllers MELSEC-WS MELSEC programmable controllers can send data to the MELSEC-WS safety controller over Ethernet. The QJ71E71-100 connected to a MELSEC programmable controller or the Built-in Ethernet port QCPU can send data (e.g. device state or other information of external devices) to the MELSEC-WS safety controller over Ethernet.

  • Page 69: Procedures Before Operation

    Procedures before operation MELSEC-WS 8. Procedures before operation (1) Procedures before operation (a) Communications with the QJ71E71-100 The following is a procedure to establish communications between the WS0- GETH and the QJ71E71-100. Procedure before operation Figure 29: Procedure before operation (communications with the QJ71E71-100) WS0-GETH...
  • Page 70 Procedures before operation MELSEC-WS (b) Communications with the Built-in Ethernet port QCPU The following is a procedure to establish communications between the WS0- GETH and the Built-in Ethernet port QCPU. Procedure before operation Figure 30: Procedure before operation (communications with the Built-in Ethernet Built-in Ethernet port QCPU WS0-GETH...
  • Page 71 Procedures before operation MELSEC-WS (2) Communication modes This part describes communication modes used between the WS0-GETH and the Qj71E71-100 or Built-in Ethernet port QCPU. Two communication modes are available: polling mode and auto update mode. For system configuration, refer to the section for the communication-target module.
  • Page 72 Procedures before operation MELSEC-WS Polling mode (Example: QJ71E71-100) Polling mode (input data set reading) (command: 00F1/001F) The QJ71E71-100 sends the Input data set request message command to the MELSEC-WS safety controller to read input data sets (MELSEC-WS safety controller information) from the WS0-GETH. Figure 31: Polling mode (input data set reading)
  • Page 73 Procedures before operation MELSEC-WS Auto update mode (Example: QJ71E71-100) Input data set auto update (command: 002E) The WS0-GETH automatically sends input data sets (MELSEC-WS safety controller information) to the QJ71E71-100 at the following timing.  At fixed intervals  Upon change of any input data set value Figure 33: Auto update mode...

  • Page 74: Wiring

    Procedures before operation MELSEC-WS 8.1 Wiring This section describes the wiring of the WS0-GETH. For the wiring of the communication-target module, refer to the following.  Q Corresponding Ethernet Interface Module User's Manual (Basic)  QnUCPU User's Manual (Communication via Built-in Ethernet Port) (1) Cables and connectors Prepare the cable shown in the following table.
  • Page 75 Procedures before operation MELSEC-WS (2) Network topologies Two network topologies using Ethernet cables are available: line topology and star topology (using a hub). Figure 35: Wiring example: line topology Figure 36: Wiring example: star topology Figure 37: Wiring example: line topology and star topology...

  • Page 76: Wiring Precautions

    Procedures before operation MELSEC-WS 8.1.1 Wiring precautions Observe the following wiring precautions. (1) Use either port 1 or port 2 for star connection. (2) Use Ethernet cables specified in Section 8.1 (1). (3) The Ethernet cable has restrictions on the bend radius. The maximum bend radius is four times of the cable outside diameter.

  • Page 77: Communications With The Qj71E71-100 (Qcpu)

    Procedures before operation MELSEC-WS 8.2 Communications with the QJ71E71-100 (QCPU) This section describes parameter configuration examples and sample programs for communications between the WS0-GETH and the QJ71E71-100 connected to the QCPU. 8.2.1 System configuration The following is the system configuration used for sample programs. Figure 38: System configuration example...

  • Page 78: Polling Mode (Input Data Set Reading)

    Procedures before operation MELSEC-WS 8.2.2 Polling mode (input data set reading) This section describes an example of communications in polling mode. The QCPU reads MELSEC-WS safety controller information (e.g. logic result, CRC, and each module status) from the safety controller through communications between the WS0-GETH and the QJ71E71-100.
  • Page 79 Procedures before operation MELSEC-WS 2) Assigning an IP address [for reading/writing] Assign an IP address of the WS0-GETH in the Network module configuration dialog. Figure 40: Network module configuration dialog Option Configuration value Table 25: Network module DHCP Unchecked configuration Device name GETH (any given name) parameters...
  • Page 80 Procedures before operation MELSEC-WS 3) Configuring TCP/IP [for reading/writing] Configure the communication mode (polling mode) in the TCP/IP configuration dialog. Select Enable COS update and Listen to for socket 1. (In the sample program, the WS0-GETH is configured as slave.) Figure 41: TCP/IP configuration dialog...
  • Page 81 Procedures before operation MELSEC-WS 4) Editing data sets Editing input data set [for reading] Open the CPU to Ethernet dialog and edit input data set 1. In the sample program, the default settings are used. (Input data sets 2 to 4 cannot be edited since their data formats are fixed.) Figure 42: CPU to Ethernet dialog Editing output data sets [for writing]...
  • Page 82 Procedures before operation MELSEC-WS (b) Configuration required for the QJ71E71-100 Configuration examples of network parameters required for communications in polling mode are shown below. Configure these parameters using a programming tool. 1) Configuring network parameters [for reading/writing] Select Ethernet/CC IE/MELSECNET to open the network parameter dialog and configure the following options.
  • Page 83 Procedures before operation MELSEC-WS 3) Network parameter– Open settings [for reading/writing] Click the Open settings button to open the configuration dialog and configure the options as follows. (In the sample program, the QJ71E71-100 is configured as master.) Figure 45: Network parameter - Open settings Table 28: Configuration value...
  • Page 84 Procedures before operation MELSEC-WS (2) Sample program 1) Device assignment [for reading/writing] The following tables list devices used in the sample program. Table 29: Devices used in the sample program W device W0 to W18 Input data set 1 storage area W20 to W2F Input data set 2 storage area W30 to W4D...
  • Page 85 Procedures before operation MELSEC-WS C device Open instruction Number of executions Number of successes Number of failures BUFSND instruction Number of executions Number of successes Number of failures BUFRCV instruction Number of executions Number of successes Number of failures Verification check Number of successes Number of failures Number of response errors (writing)
  • Page 86 Procedures before operation MELSEC-WS The following shows details of data transmission and reception processing in a program for reading input data sets in polling mode. Figure 47: Data transmission and reception processing in polling mode (input data set reading)
  • Page 87 Procedures before operation MELSEC-WS  The command and parameters for reading input data sets are stored to the BUFSND instruction send data areas (D700 to D705), and the BUFSND instruction is executed (refer to 1) in Figure 47).  The WS0-GETH responds to the command. The response data (input data sets) are stored to the BUFRCV instruction receive data areas (D900 to D976) (refer to 2) in Figure 47).
  • Page 88 Procedures before operation MELSEC-WS Sample program: polling mode (input data set reading) Figure 48: Sample program: polling mode (input data set reading)
  • Page 89 Procedures before operation MELSEC-WS...
  • Page 90 Procedures before operation MELSEC-WS...
  • Page 91 Procedures before operation MELSEC-WS...
  • Page 92 Procedures before operation MELSEC-WS (3) Monitoring data with a programming tool The read input data sets can be monitored using the device monitor function of a programming tool. The following windows show the execution results of the program for reading input data sets in polling mode. Example of a logic result (input data set 1) (The bit 0 of the logic result 0 is Active (High).) Figure 49:...

  • Page 93: Polling Mode (Output Data Set Writing)

    Procedures before operation MELSEC-WS 8.2.3 Polling mode (output data set writing) This section describes an example of communications in polling mode. The QCPU writes MELSEC-WS safety controller information (e.g. logic result, CRC, and each module status) to the safety controller through communications between the WS0-GETH and the QJ71E71-100.
  • Page 94 Procedures before operation MELSEC-WS The following shows details of data transmission and reception processing in a program for writing output data sets in polling mode. Figure 53: Data transmission and reception processing in polling mode (output data set writing)
  • Page 95 Procedures before operation MELSEC-WS  The command and parameters for writing output data sets and the output data set information are stored to the BUFSND instruction send data areas (D800 to D831), and the BUFSND instruction is executed (refer to 1) in Figure 53). ...
  • Page 96 Procedures before operation MELSEC-WS Sample program: polling mode (output data set writing) Figure 54: Sample program: polling mode (output data set writing)
  • Page 97 Procedures before operation MELSEC-WS...
  • Page 98 Procedures before operation MELSEC-WS...
  • Page 99 Procedures before operation MELSEC-WS...
  • Page 100 Procedures before operation MELSEC-WS The following table shows an example of the execution result of the program for writing output data sets in polling mode. Table 32: Storage value Byte Device Description Execution result (hex) swapping example in polling D900 000A Not required Receive data length...

  • Page 101: Auto Update Mode

    Procedures before operation MELSEC-WS 8.2.4 Auto update mode This section describes an example of communications in auto update mode. The QCPU reads MELSEC-WS safety controller information (e.g. logic result, CRC, and each module status) from the safety controller through communications between the WS0-GETH and the QJ71E71-100.
  • Page 102 Procedures before operation MELSEC-WS 3) Configuring TCP/IP Configure the communication mode (auto update mode) in the TCP/IP configuration dialog. Select Enable auto update and COS and Connect to for socket 1. (In the sample program, the WS0-GETH is configured as master.) Figure 57: TCP/IP configuration dialog...
  • Page 103 Procedures before operation MELSEC-WS (b) Configuration required for the QJ71E71-100 Configuration examples of network parameters required for communications in auto update mode are shown below. Configure these parameters using a programming tool. 1) Configuring network parameters Refer to Section 8.2.2 (1). 2) Network parameter –...
  • Page 104 Procedures before operation MELSEC-WS 3) Network parameter – Open settings Click the Open settings button to open the configuration dialog and configure the options as follows. (In the sample program, the QJ71E71-100 is configured as slave.) Figure 59: Network parameter - Open settings Configuration value Configuration value...
  • Page 105 Procedures before operation MELSEC-WS (2) Sample program 1) Device assignment The following tables list devices used in the sample program. Table 35: Devices used in the sample program W device W0 to W18 Input data set 1 storage area W20 to W2F Input data set 2 storage area W30 to W4D Input data set 3 storage area...
  • Page 106 Procedures before operation MELSEC-WS The following shows details of data reception processing in a program for receiving input data sets in auto update mode. Figure 61: Data reception processing in auto update mode...
  • Page 107 Procedures before operation MELSEC-WS  The WS0-GETH automatically sends input data sets. The send data are stored to the BUFRCV instruction receive data areas (D900 to D976) (refer to 1) in Figure 61). (The BUFRCV instruction is executed automatically upon data reception.) ...
  • Page 108 Procedures before operation MELSEC-WS Sample program: auto update mode Figure 62: Sample program: auto update mode...
  • Page 109 Procedures before operation MELSEC-WS (3) Monitoring data with a programming tool The read input data sets can be monitored using the device monitor function of a programming tool. For the execution results of the program for auto update mode, refer to Section 8.2.2 (3).

  • Page 110: Communications With The Built-In Ethernet Port Qcpu

    Procedures before operation MELSEC-WS 8.3 Communications with the Built-in Ethernet port QCPU This section describes parameter configuration examples and sample programs for communications between the WS0-GETH and the Built-in Ethernet port QCPU. 8.3.1 System configuration The following is the system configuration used for sample programs. Figure 63: System configuration example 8.3.2 Polling mode (input data set reading)
  • Page 111 Procedures before operation MELSEC-WS (b) Configuration required for the Built-in Ethernet port QCPU Configuration examples of network parameters required for communications in polling mode are shown below. Configure these parameters using a programming tool. 1) Configuring PLC parameters – Built-in Ethernet port [for reading/writing] Click the Built-in Ethernet port tab to open the configuration dialog and configure the options as follows.
  • Page 112 Procedures before operation MELSEC-WS 2) PLC parameter – Open settings [for reading/writing] Click the Open settings button to open the configuration dialog and configure the options as follows. Figure 65: PLC parameter - Open settings The TCP connection setting differs depending on the connection open status.
  • Page 113 Procedures before operation MELSEC-WS (2) Sample program This manual describes only devices used in sample programs and details of the processing. For the acquisition of sample programs, please contact your local Mitsubishi representative. 1) Device assignment [for reading/writing] The following tables list devices used in the sample program. Table 37: Devices used in the sample program W device W0 to W18...
  • Page 114 Procedures before operation MELSEC-WS C device SOCOPEN instruction Number of executions Number of successes Number of failures SOCSND instruction Number of executions Number of successes Number of failures SOCRCV instruction Number of executions Number of successes Number of failures Verification check Number of successes Number of failures Number of response errors (writing)

  • Page 115: Polling Mode (Output Data Set Writing)

    Procedures before operation MELSEC-WS (3) Monitoring data with a programming tool The read input data sets can be monitored using the device monitor function of a programming tool. For the execution results of the program, refer to Section 8.2.2 (3). 8.3.3 Polling mode (output data set writing) This section describes an example of communications in polling mode.
  • Page 116 Procedures before operation MELSEC-WS For details of data transmission and reception processing in a program for writing output data sets in polling mode, refer to Section 8.2.3 (2). Please replace the BUFSND and BUFRCV instructions with the SOCSND and SOCRCV instructions. The following table lists data to be sent at writing.

  • Page 117: Auto Update Mode

    Procedures before operation MELSEC-WS (3) Monitoring data with Setting and Monitoring Tool The written output data sets can be monitored in the Ethernet to CPU dialog of Setting and Monitoring Tool. For the execution result of the program, refer to Section 8.2.3 (3).
  • Page 118 Procedures before operation MELSEC-WS 3) Configuring TCP/IP Configure the communication mode (auto update mode) in the TCP/IP configuration dialog. Select Enable auto update and COS and Connect to for socket 1. (In the sample program, the WS0-GETH is configured as master.) Figure 67: TCP/IP configuration dialog...
  • Page 119 Procedures before operation MELSEC-WS (b) Configuration required for the Built-in Ethernet port QCPU Configuration examples of network parameters required for communications in auto update mode are shown below. Configure these parameters using a programming tool. 1) Configuring PLC parameters – Built-in Ethernet port Select Built-in Ethernet port on the PLC parameter window and configure the following options.
  • Page 120 Procedures before operation MELSEC-WS 2) PLC parameter – Open settings Click the Open settings button to open the configuration dialog and configure the options as follows. Figure 69: PLC parameter – Open settings The TCP connection setting differs depending on the connection open status.
  • Page 121 Procedures before operation MELSEC-WS (2) Sample program This manual describes only devices used in sample programs and details of the processing. For the acquisition of sample programs, please contact your local Mitsubishi representative. 1) Device assignment The following tables list devices used in the sample program. Table 43: Devices used in the sample program W device W0 to W18...
  • Page 122 Procedures before operation MELSEC-WS For details of data reception processing in a program for receiving input data sets in auto update mode, refer to Section 8.2.4 (2). Replace the BUFSND and BUFRCV instructions with the SOCSND and SOCRCV instructions. Since the Built-in Ethernet port QCPU treats application data in Little Endian format, the byte-order needs to be swapped.

  • Page 123: Communications With The Qj71E71-100 (Qscpu)

    Procedures before operation MELSEC-WS 8.4 Communications with the QJ71E71-100 (QSCPU) This section describes parameter configuration examples and sample programs for communications between the WS0-GETH and the QJ71E71-100 connected to the QSCPU. 8.4.1 System configuration The following is the system configuration used for sample programs. Figure 70: System configuration example 8.4.2 Polling mode (input data set reading)
  • Page 124 Procedures before operation MELSEC-WS (2) Sample program This manual describes only devices used in sample programs and details of the processing. For the acquisition of sample programs, please contact your local Mitsubishi representative. 1) Device assignment [for reading/writing] The following tables list devices used in the sample program. Table 44: Devices used in the sample programs W device W0 to W18...
  • Page 125 Procedures before operation MELSEC-WS C device Open instruction Number of executions Number of successes Number of failures BUFSND instruction Number of executions Number of successes Number of failures BUFRCV instruction Number of executions Number of successes Number of failures Verification check Number of successes Number of failures Number of response errors (writing)
  • Page 126 Procedures before operation MELSEC-WS The following table lists data to be sent at reading. Table 45: Configuration Byte Device Description Data to be sent at value (hex) swapping reading D700 000A Not required Send data length (10 bytes) D701 00F1 Command D702 0001...

  • Page 127: Polling Mode (Output Data Set Writing)

    Procedures before operation MELSEC-WS 8.4.3 Polling mode (output data set writing) This section describes an example of communications in polling mode. The QSCPU writes MELSEC-WS safety controller information (e.g. logic result, CRC, and each module status) to the safety controller through communications between the WS0-GETH and the QJ71E71-100.
  • Page 128 Procedures before operation MELSEC-WS For details of data transmission and reception processing in a program for writing output data sets in polling mode, refer to Section 8.2.3 (2). The following table lists data to be sent at writing. Table 46: Configuration Byte Device...
  • Page 129 Procedures before operation MELSEC-WS The following table shows an example of the execution result of the program for writing output data sets in polling mode. Table 47: Storage value Byte Device Description Execution result (hex) swapping example in polling D900 0004 Not required Receive data length...

  • Page 130: Auto Update Mode

    Procedures before operation MELSEC-WS 8.4.4 Auto update mode This section describes an example of communications in auto update mode. The QSCPU reads MELSEC-WS safety controller information (e.g. logic result, CRC, and each module status) from the safety controller through communications between the WS0-GETH and the QJ71E71-100.
  • Page 131 Procedures before operation MELSEC-WS (b) Configuration required for the QJ71E71-100 Configuration examples of network parameters required for communications in auto update mode are shown below. Configure these parameters using a programming tool. 1) Configuring network parameters Refer to Section 8.2.2 (1). 2) Network parameter –...
  • Page 132 Procedures before operation MELSEC-WS Note  If the QSCPU connected to the QJ71E71-100 stops during communications in auto update mode, the BUFRCV instruction will not be executed even when data are transmitted from the WS0-GETH. This may cause the receive buffer of the QJ71E71-100 to overflow and data transmission of the WS0-GETH to stop.

  • Page 133: Troubleshooting

    Troubleshooting MELSEC-WS 9. Troubleshooting 9.1 When data cannot be normally exchanged Refer to the following flowchart when the WS0-GETH cannot normally exchange data with the communication-target module. Figure 72: Data cannot be normally Troubleshooting exchanged. flowchart when data cannot be normally exchanged Check the status of the CPU module connected...

  • Page 134: When Data Cannot Be Exchanged In Polling Mode (Reading/Writing)

    Troubleshooting MELSEC-WS 9.2 When data cannot be exchanged in polling mode (reading/writing) Figure 73: Troubleshooting when data cannot be exchanged Troubleshooting *1,*2 in polling mode flowchart when data cannot be exchanged in Check if the connection has been opened. polling mode Was the OPEN Execute the OPEN instruction to open the connection.
  • Page 135 Troubleshooting MELSEC-WS (From the previous page) Check if the response command has been received from the WS0-GETH. No responses (including error responses) from the WS0-GETH Was the - Check if the pairing open has been configured for the BUFRCV instruction QJ71E71-100.

  • Page 136: When Data Cannot Be Exchanged In Auto Update Mode

    Troubleshooting MELSEC-WS 9.3 When data cannot be exchanged in auto update mode Figure 74: Troubleshooting when data cannot be exchanged Troubleshooting *1,*2 in auto update mode flowchart when data cannot be exchanged in Check if the connection has been opened. auto update mode Is the Open complete signal (M0) on?

  • Page 137: Annex

    Annex MELSEC-WS 10. Annex 10.1 SICK contact More representatives and agencies in all major industrial nations at www.sick.com Australia Norge Phone +61 3 9497 4100 Phone +47 67 81 50 00 1800 33 48 02 – tollfree E-Mail austefjord@sick.no E-Mail sales@sick.com.au Österreich Belgium/Luxembourg Phone +43 (0)22 36 62 28 8-0...
  • Page 138 MELCO does not warrant or guarantee the design, 1. Limited Warranty and Product Support. specify, manufacture, construction or installation of a. Mitsubishi Electric Company ("MELCO") warrants the materials, construction criteria, functionality, use, properties or other characteristics of the equipment,...
  • Page 139 h. These terms and conditions constitute the entire damages as well as damages of a pecuniary nature, agreement between Customer and MELCO with the disclaimers and limitations contained in these respect to warranties, remedies and damages and terms shall apply to all three types of damages to the supersede any other understandings, whether written fullest extent permitted by law.
  • Page 140 The company names, system names and product names mentioned in this manual are either registered trademarks or trademarks of their respective companies. In some cases, trademark symbols such as '™' or ' ® ' are not specified in this manual. SH(NA)-080857ENG-G...
  • Page 142 SICK AG www.sick.com SH(NA)-080857ENG-G(1912)MEE MODEL: WS-ET-U-E MODEL CODE: 13JZ33 HEAD OFFICE : TOKYO BUILDING, 2-7-3 MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN NAGOYA WORKS : 1-14 , YADA-MINAMI 5-CHOME , HIGASHI-KU, NAGOYA , JAPAN When exported from Japan, this manual does not require application to the Ministry of Economy, Trade and Industry for service transaction permission.

This manual is also suitable for:

Melsec ws0-geth0020

Table of Contents