Home

Safety Controller Ethernet Interface Module User`s Manual

1. 60 MELSEC WS Technical specifications 6 Technical specifications Table 20 Technical specifications of Ethernet interface module Table 21 Technical specifications supply circuit Table 22 General technical specifications 61 6 1 Technical specifications of Ethernet interface module Interface Fieldbus Ethernet TCP IP Integrated switch 3 port layer 2 managed switch with Auto MDI X for automatic detection of crossed Ethernet cable Connection technique RJ45 socket Transfer rate 10 Mbps 10Base T or 100 Mbps 100Base TX autosensing Update rate heartbeat rate Configurable from 40 to 65535 ms update rate Change of state COS 10 ms Addressing factory setting IP address 192 168 250 250 Subnet mask 255 255 0 0 Default gateway 0 0 0 0 MAC address Printed on type label example 00 06 77 02 00 A7 6 2 Technical specifications supply circuit Item Specifications Supply voltage 24 V DC 16 8 to 30 V DC Power consumption Max 2 4 W 6 3 General technical specifications Terminals Fieldbus Ethernet TCP IP FLEXBUS 10 pin connector for internal safety bus plug Climatic conditions Ambient operating temperature Ta 25 C to 55 C Storage temperature 25 C to 70 C Relative humidity 10 to 95 non condensing Climatic cond
2. Write the configuration data to the module with Setting and Monitoring Tool Create a ladder program Execute a PING test to check for existence of the WSO GETH Check operations 1 For details refer to the Q Corresponding Ethernet Interface Module User s Manual Basic 66 MELSEC WS Figure 30 Procedure before operation communications with the Built in Ethernet port QCPU 67 Built in Ethernet port QCPU Connect an Ethernet cable Configure PLC parameters with GX Developer Create a ladder program Procedures before operation Procedure before operation b Communications with the Built in Ethernet port QCPU The following is a procedure to establish communications between the WS0O GETH and the Built in Ethernet port QCPU WS0 GETH Connect the WSO GETH to the MELSEC WS CPU module Connect an Ethernet cable Check operations End Configure configuration data with Setting and Monitoring Tool Write the configuration data to the module with Setting and Monitoring Tool Procedures before operation MELSEC WS 2 Communication modes This part describes communication modes used between the WSO 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 For the acquisition of sample programs provided i
3. 72 MELSEC WS 73 Procedures before operation 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 4 Place the cables in a duct or clamp them If not dangling cable may swing or inadvertently be pulled resulting in damage to the module or cables or malfunction due to poor contact 5 When laying the cables do not touch the contact surfaces of the connector of the cable and the connector of the module nor let dirt or dust collect on the contact surfaces If oil from the hands dirt or dust adheres to the cores the transmission loss may increase resulting in communication failure 6 When connecting disconnecting the cable to from the module hold the connector part 7 Connect the connectors of the cable and the module until they click 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 WSO 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 WS0 GETH Port 9100
4. Check the code of an error occurred by executing the OPEN instruction and eliminate the error Eliminate the error referring to the error code stored in DO Execute a PING test from the QJ71E71 100 to the WS0 GETH Check the network totally including the communication path between Is a response returned the WS0 GETH and the QJ71E71 100 a noise and installation status YES Check if the programs and network parameters including a port number are correctly written to the CPU module on the QJ71E71 100 side Execute the BUFSND instruction and send the command Turn on the send execution device M400 Check the code of an error occurred by executing the BUFSND instruction and eliminate the error Eliminate the error referring to the error code stored in D1 Troubleshooting MELSEC WS From the previous page Check if the response command has been received from the WSO GETH No responses including error responses from the WS0 GETH Check if the pairing open has been configured for the QJ71E71 100 Check the network totally including the communication path between the WSO GETH and the QJ71E71 100 a noise and YES installation status NO Was the BUFRCV instruction executed Was the value added in C20 NO M511 is on Was the BUFRC instruction normally completed Is M510 on Check the code of an error occurred by executing the BUFRCYV i
5. Open system Active Unpassive Fixed buffer communication No procedure procedure Pairing open Disable Existence confirmation Confirm Host station Port No hex 238Cu 9100 238Cy 9100 Transmission target device IP 192 168 250 250 address Transmission target device Port 238Cu 9100 No hex 4 Network parameter Initial settings Click the Initial settings button to open the configuration dialog and configure 120 for Destination existence confirmation starting interval The QJ71E71 100 can quickly detect a communication stop due to cable disconnection by configuring a smaller value for this option Timer setting Module will operate with default values if setting is left blank Setting value Defaut value In units po TCP LP timer XEDOS Pp TCP zero windowtimer 20 X500ms PTR resendtimer 20 XDI _ po TP endtimer O Pp IPassemblytimer oo y Response monitoring timer __ Destination existence conformation interval timer Destination existence conformation resend x500ms x5 Ti 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 WO 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 M
6. Input 3 external test signal failure 1 No error 0 Error Reserved Reserved 47 Data sets MELSEC WS 1 No error 0 Error 0 Error Byte Bit Safety I O modules CPU modules Network modules ih e g WS0 XTIO WSO0 XTDI e g WS0 CPUx e g WS0 GETH 2 3 Input 4 external test signal failure 1 No error 0 Error 4 Input 5 external test signal failure 1 No error 0 Error 5 Input 6 external test signal failure 1 No error 0 Error 6 Input 7 external test signal failure 1 No error 0 Error 7 Input 8 external test signal failure 1 No error 0 Error 3 0 Output 1 stuck at high error 1 No error 0 Error 1 Output 1 stuck at low error 1E Norns Reserved Reserved 0 Error 2 Output 2 stuck at high error 1 No error 0 Error 3 Output 2 stuck at low error 1 No error 0 Error 4 Output 3 stuck at high error 1 No error 0 Error 5 Output 3 stuck at low error 1 No error 0 Error 6 Output 4 stuck at high error 1 No error 0 Error 7 Output 4 stuck at low error Note Reserved for future use static 1 no status change f no module is present all values including the reserved values are set to logical 1 If no module is present all values including the reserved values are set to logical 1 In input data set 3 the status value will be O only when an error occurs in the correspondin
7. 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 Output values Active Inactive for all safety I O modules and EFI devices connected see Section 4 1 2 Output data from another network i e data received by a second network module in the safety controller see Section 4 1 3 Diagnostics Checksums CRCs see Section 4 1 4 Error and status information for all modules except the safety relay output module see Section 4 1 5 Data sets Input data sets to be sent from the Ethernet interface module to the network consist of logic results I O state data diagnostics data e g module status CRC and other data These data are organized into four input data sets Input data set Description Size Customization 1 Logic result 50 bytes Available Module and EFI input and output values Data set of the second network module 2 CRC 32 bytes N A 3 Error and status information 60 bytes N A of the module 4 Reserved 60 bytes N A For details of data to be sent to the network see Table 15 and Table 16 You can customize the contents of input data set 1 in units of 1 byte In the delivery status the input data set 1 is pre configured default settings See Section 4 3 and Section 4 4 Data sets Table 15 Overview input data s
8. Listen to Connect to Enabled Checked Listen to Selected Deselected Port 9100 238Cy default Connect to Deselected Selected IP address 192 168 250 251 Port 9100 238Cu Enable COS update Enable auto update and COS Enable auto update and COS Update rate ms 5000 default Update Dataset 1 Checked Update Dataset 2 Checked Update Dataset 3 Checked Update Dataset 4 Unchecked To switch the communication mode to the polling mode activate the Enable COS update radio button 4 Editing data sets Refer to Section 8 2 2 1 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 Figure 68 Built in Ethernet port dialog 192 168 250 __251 L 255 255 oj ol 192 168 250 _255 116 MELSEC WS Procedures before operation 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 Port No input format HEX v settings 5 Host station Transmission target Transmission Pro
9. Response command verification normal completion Data size error device CLOSE instruction success device CLOSE instruction failure device CLOSE instruction normal completion 81 CLOSE instruction abnormal completion Procedures before operation MELSEC WS Co Open instruction Number of executions C1 Number of successes C2 Number of failures C10 BUFSND instruction Number of executions C11 Number of successes C12 Number of failures C20 BUFRCYV instruction Number of executions C21 Number of successes C22 Number of failures C31 Verification check Number of successes C32 Number of failures C33 Number of response errors writing C40 Close instruction Number of executions C41 Number of successes C42 Number of failures 1 C device is used to check the operation of the communication program 82 MELSEC WS Procedures before operation 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 WS0 GETH QJ71E71 100 BUFSND instruction send data areas D700 to D705 Request for Send data length reading input data sets Command Parameter 1 Parameter 2 Parameter 3 Parameter 4 Input data set 1
10. The WS0 CPU1 module has 2 EFI interfaces An EFI interface is a safe communication interface between SICK devices It allows to read out information from the safety devices e g SICK C4000 S3000 transfer commands to the safety devices The Ethernet interface module allows these EFI devices connected to the WS0 CPU1 to transmit their data into the network It is only possible to select the EFI data in byte arrays 4 byte arrays for each connected EFI device are available Some of the data contents are reserved and can not be used at the programmable controller Further information about the properties functions and benefits of the EFI interfaces can be found in the Safety Controller User s Manual 4 1 3 Routing of data from a second network If your MELSEC WS safety controller contains two network modules it is possible to route information received by the first network module from one network e g from a programmable controller into a second network via the second network module e g to an HMI and vice versa 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 System CRC SCID Each checksum is four bytes long Data set 2 can not be customized 4 1 5 Error and status information of the modules
11. For both directions MELSEC WS to Ethernet as well as Ethernet to MELSEC WS inactive bits are displayed grey while active bits are highlighted green 0 Module 1 TIO M Input gt 1 Module 2 Input 2 2 Module rt a 03 BEGGH0080 w BEGG8080 BEEGG8080 on ARANAN In the MELSEC WS to Ethernet view bits that are inactive due to an error are displayed red This could be the case e g for the outputs of a WS0 XTIO module if the power supply of this module is faulty w gogogaga w BEBG08080 00 BEGG0080 nnn mAAMAirar I kadia A Thiam hl In the Ethernet to MELSEC WS view bits that have no tag name assigned so that they can not be used in the logic editor but which are included in the process image that the Ethernet interface module receives from the programmable controller are highlighted yellow Byte 0 2 BBBBEEG80 Byte 1 xw BBEBG8880 Byte 2 xw BBEBG8880 non ARANAN The Ethernet interface module always reflects the actual physical status of the inputs and outputs on the connected modules and devices This means that even when Force mode is active and inputs that are physically Inactive Low are forced Active High or vice versa the actual physical status of these inputs will be transmitted to the programmable controller instead of the virtual forced status If however as a result of forcing of one or several inputs one or several out
12. LED MS Green for 0 25s J LED MS O Off 16 MELSEC WS 17 ATTENTION ATTENTION Ethernet interface module 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 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 Prevent unintended start up of equipment during connection of an Ethernet interface module 3 2 1 Steps for mounting the modules The MELSEC WS safety controller is only suitable for mounting in a control cabinet with at least IP 54 degree of protection While supply voltage is applied modules must not be plugged to nor be removed from the MELSEC WS safety controller To ensure full electromagnetic compatibility EMC the DIN mounting rail must be connected to functional earth FE Additionally connect all network cable shields directly at the control cabinet entrance to a common FE ground line Ina MELSEC WS safety controller the WSO CPUO or WS0 CPU1 module is positioned at the extreme left The two optional network modules follow directly to the right of the CPU module Connect further MELSEC WS safety I O modules e g WSO XTIO or WSO XTDI onto the right side of the network modules and any additional safety relay out
13. Set Byte Bit0 GETH 13 1 0 0 PH Set1 Byte0 Bit1 GETH 13 51 0 1 9 Seti Byte0 Bit2 GETH 13 51 0 2 PH Set1 Byte0 Bit3 GETH 13 51 0 3 a 9 Setl Byte0 Bit4 GETH 13 51 0 4 9 Set1 Byte0 Bit5 GETH 13 51 0 5 9 Set1 Byte0 Bit6 GETH 13 51 0 6 49 Seti Byte0 Bit7 GETH 13 51 0 7 49 Set Byte1 Bit0 GETH 13 1 1 0 e Sett Bytet Bit GETH 13 1 1 1 PH Sett Bytet Bit2 GETH 13 1 1 2 PH Set Bytet Bit3 GETH 13 1 1 3 PH Set1 Bytet Bit4 GETH 13 1 1 4 PH Sett Byte Bit5 GETH 13 91 1 5 PH Sett Byte1 Bit6 GETH 13 51 1 6 PH Seti Byte1 Bit7 GETH 13 51 1 7 49 Set Byte2 Bit0 GETH 13 1 2 0 PH Set Byte2 Bitl GETH 13 1 21 PH Set1 Byte2 Bit2 GETH 13 51 2 2 PH Set1 Byte2 Bit3 GETH 13 51 2 3 49 Set Byte2 Bit4 GETH 13 1 2 4 PH Set Byte2 BitS GETH 13 1 2 5 PH Set Byte2 Bit GETH 13 1 2 6 PH Set Byte2 Bit7 GETH 13 1 2 7 PH Set Byte3 Bit0 GETH 13 1 3 0 Hi Set1 Byte3 Bit1 GETH 13 51 3 1 x Inputs Function block Outouts 0 FB preview In Out summary page 56 MELSEC WS 57 Note Data sets 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 4 5 2 Importing and exporting a configuration With the Import and Ex
14. IP address 192 168 250 250 IP address 192 168 250 251 QJ71E71 100 mounted in Slot 0 Port 9100 74 MELSEC WS Figure 39 Hardware configuration dialog 75 Procedures before operation 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 Read target data Logic result 0 input data set 1 CRC input data set 2 Each module status input data set 3 1 Parameter configuration a Configuration required for the WSO GETH Configuration examples of network parameters required for communications in polling mode are shown below Configure these parameters using Setting and Monitoring Tool The WS0 GETH requires no program for communications 1 Creating a hardware configuration for reading writing Read the hardware configuration data from the actual MELSEC WS safety controller to Setting and Monitoring Tool or place modules in Setting and Monitoring Tool according to the actual configuration amp CPU modules FY V 2 00 FW 1 00 Rev V 23x Rev V 130 A1 A2 Revision E EFI B Network Modules LA1_A2 J MITSUBISHI GETH GCC1 Revision V Lan Y1 amp 1 0 modules xTIO XTDI Revision Yis oy Vis oy in
15. Machine Operator 1 0ffline A Setting and Monitoring Tool configuration is not verified On the left side of the dialog you will find the area for the Ethernet interface module IP configuration f desired enter a Device name for the Ethernet interface module Enter a valid IP address for the Ethernet interface module and if required a valid Subnet mask and a valid IP address for a Default gateway Or If your network uses a DHCP server activate the DHCP checkbox If your project is online you can use the Read button at the upper left corner of the Ethernet interface module IP configuration area to retrieve the current IP settings of the Ethernet interface module The out of the box default IP address of the Ethernet interface module is 192 168 250 250 gt Ethernet interface module MELSEC WS Figure 10 Found network modules in the Network scan dialog Note 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 Network scan EE i Hj Scan QySet device contie Ma Bootloader MAC address IP address Type key Serial number Application revision ears Board revision Device amp 00 06 77 020D BE 10 97 1954 WS0 GETH 1105 00140 1 05 Eth TCP IP
16. a Current IP address Edit IP address Defa iP addres ionet mas Vet ate L10 19 264 1097 19 54 255 255 255 0 10 97 19 254 P Use DHCP Intel R 82566DM 2 Gigabit Network Connection MAG address 00 1 E 4F D3 31 AC IP address 10971958 Click on the Ethernet interface module you want to edit Enter the new settings in the Edit IP address area Click on the Set device config button to transfer the new settings to the Ethernet interface module Uuu if multiple Ethernet interface modules are connected to the PC network scanning may fail In that case disable the unused modules The Open web browser button is unavailable for Ethernet interface modules 3 4 3 Configuration of the Ethernet interface module For the configuration of the Ethernet interface module please refer to Section 3 5 For the configuration of the input data set 1 data transfer from and to the network please refer to Section 4 4 and Section 4 5 24 MELSEC WS 25 Note Note Ethernet interface module 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 gt Click Connect to go online The Setting and Monitoring Tool connects to the MELSEC WS safety controller gt Click Transfer to transfer the configuration to the MELSEC WS
17. data bytes 34 MELSEC WS Note Table 9 Output data set write response 35 Ethernet interface module Each output data set length of the Ethernet interface module is 10 bytes long The response message is returned to the application by the Ethernet interface module The response message telegram is structured as shown below Parameter Length Value Command WORD 002FH Response to write output data set settings message Status WORD 0 Success Output data sets written correctly 1 Error Can not write output data sets due to any of Stop state of the CPU module Loss of backplane communication Incorrect routing information Configuration via Setting and Monitoring Tool In order to configure the polling mode of the Ethernet interface module via the Setting and Monitoring Tool perform the following steps Open the Setting and Monitoring Tool and load the hardware configuration including the Ethernet interface module 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 view to open the network module configuration dialog gt Click on TCP IP configuration on the left hand menu The following dialog appears Ethernet interface module MELSEC WS Figure 17 TCP IP config
18. for a period of eighteen 18 months after date of delivery from the point of manufacture or one year from date of Customer s purchase whichever is less Mitsubishi Safety Controller the Products will be free from defects in material and workmanship b At MELCO s option for those Products MELCO determines are not as warranted MELCO shall either repair or replace them or issue a credit or return the purchase price paid for them For this warranty to apply 1 Customer shall give MELCO i notice of a warranty claim to MELCO and the authorized dealer or distributor from whom the Products were purchased ii the notice shall describe in reasonable details the warranty problem iii the notice shall be of its Products for a period of four 4 years after production is discontinued MELCO generally announces discontinuation of Products through MELCO s Technical Bulletins Products discontinued and repair parts for them may not be available after their production is discontinued properties or other characteristics of the equipment systems or production lines into which the Products may be incorporated including any safety fail safe and shut down systems using the Products MELCO is not responsible for determining the suitability of the Products for their intended purpose and use including determining if the Products provide appropriate safety margins and redundancies for the applications equipment or systems i
19. the IP address is assigned WSO0 GETH or reserve a fixed IP address for no longer supplies data from a DHCP server After the the WSO GETH in the DHCP server manual LED PWR Green WSO GETH or the DHCP server has assignment by means of the MAC address of LED LINK ACT Green been restarted a different IP address the WSO GETH LED MS Red Green that is unknown to the programmable controller has been assigned to the WSO0 GETH WSO0 GETH safety controller is WSO GETH is not plugged properly Plug the WSO GETH in correctly in Critical fault mode into the other MELSEC WS module Clean the connecting socket plug LED PWR Green Module connection plug is soiled or Repower the safety controller LED LINK ACT Green damaged Check the error MELSEC WS module and LED MS Red Other MELSEC WS module has remove the error cause internal critical error Check the Ethernet line status If a load is Ethernet communication with the excessively placed to the line reduce the load WSO GETH is under excessive load using a device such as a router WS0 GETH is in Critical fault WS0 GETH internal device error Switch off the power supply of the safety mode controller and switch it on again LED PWR Green Check if the WSO GETH is mounted in correct LED LINK ACT Green position LED MS Red 2 Hz Check the diagnostics messages with the Setting and Monitoring Tool If the error remains replace the Ethernet interface module
20. Byte 3 Network 13 Byte 3 lt p Byte 4 W4A Byte 2 t Byte 1 Byte 1 Byte 2 W4B Byte 4 lt gt Byte 3 83 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 WSO 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 The BUFRCV instruction is executed automatically upon data reception The byte order of the receive data is changed and input data sets are stored to the corresponding input data set storage areas WO to W4D refer to 3 in Figure 47 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped Note that the byte order of the input data set 1 and output data set 1 does not need to be changed because these data are one byte long lt Data need to be swapped gt Command and parameters word data 16 bits Input data set 2 and 3 double word data 32 bits The following table lists data to be sent at reading Table 30 Configuration Byte EA Data to be sent at Device tale hax Swapping Description Sg
21. D700 000A Not required Send data length 10 bytes D701 OOF 14 Command D702 00014 Read data specification Input data set 1 reading D703 00014 Read data specification Input data set Required 2 reading D704 00014 Read data specification Input data set 3 reading D705 0000 Read data specification Input data set 4 not reading 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped 84 MELSEC WS Procedures before operation Sample program polling mode input data set reading Figure 48 Sample program polling mode input data set reading SM400 E UO ae MOV G20480 K4M0 Open complete signal acquisition 7 UO A LMOV G20482 K4M20 Open request signal acquisition E UO p LMOV G20485 K4M40 Reception status signal Mpo MPAP j Map We FMOVP HO D300 OPEN instruction control data storage zoru K D300 M301 OPEN instruction execution RST M311 INCP CO J M301 M302 SET M310 OPEN instruction normal completion INCP C1 M302 i SET M311 OPEN instruction abnormal completion INCP C2 LE MOVP D301 DO HOPEN instruction error code strage M400 M420 X19 MO A Ti K MOV K10 D700 Send data size specification byte Command Input data set s MOV HOF1 D701 request message SWAP D701 MOV H1 D702 Input data set 1 reading SWAP D702 MOV H1 D703 Input data set
22. Products in designed incompatible or defective hardware or question offsite or at the premises where they are software installed or used and 5 that fails because consumable parts such as relay 3 If MELCO requests Customer shall remove batteries backlights or fuses were not tested Products it claims are defective and ship them to serviced or replaced MELCO or MELCO s authorized representative for 6 operated or used with equipment production lines examination and if found defective for repair or or systems that do not meet applicable and replacement The costs of removal shipment to and commensurate legal safety and industry accepted from MELCO s designated examination point and standards reinstallation of repaired or replaced Products shall 7 operated or used in abnormal applications be at Customer s expense 8 installed operated or used in contravention of 4 If Customer requests and MELCO agrees to effect instructions precautions or warnings contained in repairs onsite at any domestic or overseas location MELCO s user instruction and or safety manuals the Customer will pay for the costs of sending repair technical bulletins and guidelines for the Products personnel and shipping parts MELCO is not 9 used with obsolete technologies or technologies not responsible for any re commissioning maintenance fully tested and widely accepted and in use at the or testing on site that involves repairs or replacing of time of the Prod
23. TCP IP command for example Configuration via TCP IP interface This command message is sent by an application to the Ethernet interface module to configure the auto update mode This message can be used to either disable or enable the auto update mode directly through the TCP IP interface 36 MELSEC WS Table 10 Auto update mode configuration command Note Table 11 Auto update mode configuration response 37 Ethernet interface module Parameter Length Value Command WORD 00E1H Auto update control Request data set 1 WORD 0 Donotsend data set 1 1 Send data set 1 Request data set 2 WORD 0 Donotsend data set 2 1 Send data set 2 Request data set 3 WORD 0 Donotsend data set 3 1 Send data set 3 Request data set 4 WORD 0 Donotsend data set 4 1 Send data set 4 update rate Auto update mode WORD 0 Disable auto update messages Non zero Enable auto update message at specified rate in ms If the value is 40 or less data sets are sent at 40ms interval Minimum 40 ms Maximum 65535 ms Auto update is disabled if all Request Input Data Set flags are set to zero The response message returned to the application by the Ethernet interface module Parameter Length Value Command WORD 001EH Response to the auto update control message Configuration via Setting and Monitoring Tool In order to configure
24. and each module status from the safety controller through communications between the WSO GETH and the Ethernet ports of Built in Ethernet port QCPU Read target data Logic result 0 input data set 1 CRC input data set 2 Each module status input data set 3 1 Parameter configuration a Configuration required for the WSO GETH Refer to Section 8 2 2 1 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 Figure 64 PLC parameter Built in Ethernet port 108 MELSEC WS Procedures before operation 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 Port No input format HEX PLC parameter Open ee eee settings PAGEA o t TCP ti Host station Transmission target y Jolene rotocol pen system connection port No device IP address Tea Na The TCP connection setting differs depending on the connection open status e When connection is opened by the Built in Ethernet port QCPU
25. 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 2009 MITSUBISHI ELECTRIC CORPORATION CONTENTS SAFETY PRECAUTIONS salies renar iiir ATA REEERE A PAAA E RD 1 CONDITIONS OF USE FOR THE PRODUCT nesnic rer riirn en anean ran EAEn AREE 4 REVIHON Sa E E T E T E S 5 CONTEN ISa fie eth atta a da vedas Sa Ta wt esd as Scena a EASA nena IAA a AEAEE Ad Ea RA 6 GENERIC TERMS AND ABBREVIATIONS 0 ccccccceeceeeeseeneeeeeeeeeeeeseeeeeeeteenaeeeeeeaaees 8 1 About this document nesnesinin i iei 9 1 1 Function of this COCUMENE siss iri erseiirpindi iranis riori iaaii e eiaa 9 1 2 MELSEC WS manuals S creira Ta TAAT 9 1 3 Tar Qet QrOU pin sac icetskecs ieee iei ri ei eis SEEE ae ei eee A 10 1 4 Depth Of intonation i cosceeled cece a e aea a aeai 11 1 5 CODEC wastes ci eats at setect oz paren renee aerate Send Os accmee eae aaa Meant Recerca a 2 11 1 6 Abbreviations USC 2c c cccccecceeeeeeneeedeceeeeeddhaeeeeeddeenededdduaeeeddeenseedeeeneees 11 1 7 Symbols used i iteiccivsdicccusiadeccs Tain AAE AEE EEA ANE 11 2 OEE IE OEE A T E T NEE A te ied 12 2 1 Qualified safety personnel 0 cceceeceeeeeeeeeeeeeeeeeeeeeseaeeeeeenaeeeseetaeeeeeeaes 12 2 2 COmeCt USC EEEE ig ead E E E A E 12 2 3 Environmental protection cccccceeeeeeeeneeceeeeeeeseceecaeeeeeeesessnniaeeeeees 1
26. bit for data to the network When the Ethernet interface module detects an invalid communication the contents of the data sets will be set to zero logical 0 and the corresponding module status bit will also be set to zero logical 0 Incase the communication is dropped the data of the output data sets will be set to zero logical 0 and the module input status bit will also be set to zero logical 0 These modules may only be used by qualified safety personnel and only on the machine where they have been installed and initialized by qualified safety personnel in accordance with the manual Do not use the same output data set number for two different interface connections or TCP IP sockets The output data set can be written to the Ethernet interface modules in parallel by all communication interfaces or TCP IP sockets if they use the same output data set number In that case the last message overrides data received earlier Data sets Table 18 Default configuration for the input data set 1 transmitted into the network 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 Byte Default assignment Input data set 0 Log
27. configuration dialog Click on the MELSEC WS to Ethernet tab on the left hand menu to display the network module configuration dialog The default setting is as follows u Safety Controller Setting and Monitoring Tool 1 3 0 New project Available data 4 i GF led ify Reset to default Cle Show only available data 5 Input data Module 1 Tion Module 2 XTDIL2 Module 3 Module 4 Module 5 Module Module Pee Module 8 modu configuration Module fa Module b Module 11 Module 12 TOPAP configuration Network Module 2 input data J Module status EFI 1 input EFI 2 input 2 Input Output CPU1 module Dutput Logic result 2 Logic result 4 p 3 input Input Module 4 Module 5 Module 6 Module 7 Module 8 Module 9 Module 10 Module 11 Module 12 B Module 1p TIONN Module 2 KTDI 2 ile Fio jo 10 jo jo jo jo 10 jo o RERS o o I cmon MiniTwin XTIO Boouegsoggs Update interval ms 4 Enabling switch XTIO L7iB Safety switchXTIO 1 BI6 IBH Single channel NOXTIO 1 N 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 aoacEeasao oGGGE0080 BGGG80080 OGGG8280 oGaGuE880 oGEuo8e00 oOGEGE8080 QBGEG8800 oGGG8080 pogogan oGGG8080 QBGB088080 oGG08280 oogogaag OGGG8080 BGGGE8000 oGGG88
28. profile Check all profiles js Network settines Active connection To configure the connection please proceed as follows Standard Choose connection type amp Serial port Indeterminate connection state Check connection Serial COM auto detection Port COM auto detection Baud rate Auto scan Press this button if you want to save Connection is not stored in project file the prbtie te cE Activate profile Edit profile Click on Add TCP IP profile The following dialog appears Figure 12 Create new profile Create new TCP IP Entry name profile dialog i Intel 21140 Based PCI Fast Ethernet Adapter Generic MAC address 00 03 F F 01 06 36 IP address 192 168 131 665 IP address C Enable TCP IP routine Subnet address 965 955 55 Gateway address Search for devices i H Scan MAC address IP address Device name Select your Ethernet network adaptor from the drop down list Click on Scan to search for Ethernet interface modules on your Ethernet network Ethernet interface modules located will be displayed as shown in the dialog below The IP address will be displayed as well as MAC address and device name Note If multiple Ethernet interface modules are connected to the PC network scanning may fail In that case disable the unused modules 28 MELSEC WS Figure 13 Create new TCP IP profile dialog after scan has b
29. the QJ71E71 100 at 5000 ms intervals Read target data Logic result 0 input data set 1 CRC input data set 2 Each module status input data set 3 Figure 71 System configuration example QJ71E71 100 IP address 192 168 250 251 Port 9100 WS0 GETH The default settings are used for the input data set 1 127 1 Parameter configuration a Configuration required for the WSO GETH Configuration examples of network parameters required for communications in auto update mode are shown below Configure these parameters using Setting and Monitoring Tool The WSO0 GETH requires no program for communications 1 Creating a hardware configuration Refer to Section 8 2 2 1 2 Assigning an IP address Refer to Section 8 2 2 1 3 Configuring TCP IP Refer to Section 8 2 4 1 4 Editing data sets Refer to Section 8 2 2 1 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 Operational settings Refer to Section 8 2 4 1 3 Network parameter Open settings Refer to Section 8 2 4 1 4 Network parameter Initial settings Refer to Section 8 2 4 1 2 Sample program This manual describes only devices
30. the auto update mode of the Ethernet interface module via the Setting and Monitoring Tool perform the following steps Open the Setting and Monitoring Tool and load the hardware configuration including the Ethernet interface module 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 network module or double click on the desired network module in the hardware configuration view to open the network module configuration dialog gt Click on TCP IP configuration on the left hand menu The following dialog appears Ethernet interface module Figure 18 TCP IP configuration for auto update MELSEC WS i Safety Controller Setting and Monitoring Tool 1 3 0 New project GPU to Ethernet T Ethernet to CPU Network module configuration Socket 1 v Enabled Listen to pt mo g Connect to O Enable COS update Enable auto update and COS Update rate ms poo g Update Dataset 1 Update Dataset 2 Update Dataset 3 la 4 192 168 250 250 9100 Socket 2 Socket 3 Enabled Enabled 2 8 u amp a EID Data at Connect Port Dx a v Machine Operator 13Offline A Setting and Monitoring Tool configuration is not verified Check the Connect to checkbox Enter th
31. to Section 8 2 2 1 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 Refer to Section 8 4 2 2 124 MELSEC WS Procedures before operation 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 ae Configuration Byte 7 Ze Bete to be sent at evice wale hes aping escription E D800 003E Not required Send data length 62 bytes D801 00F24 Command D802 000A Write data specification Output data set 1 writing 10 bytes D803 000A Write data specification Output data set 2 writing 10 bytes D804 000A Required Write data specification Output data set 3 writing 10 bytes D805 000A Write data specification Output data set 4 writing 10 bytes D806 000A Write data specification Output data set 5 writing 10 bytes D807 Output data set 1 Byte 0 and Byte 1 D808 Output data set 1 Byte 2 and Byte 3 D809 Any Not required Output data set 1 Byte 4 and Byte 5 D810 Output data set 1 Byte 6 and Byte 7 D811 Output data set 1 Byte 8 and Byte 9 D812 to D816 Any Not required Output data set 2 D817 to D821 Any Not requ
32. update of the data as well regardless of the set heartbeat rate l e COS is always active For both methods the following structure of messages applies 32 MELSEC WS Table 4 Telegram structure Table 5 Error response message 33 Ethernet interface module 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 Parameter Length Description Command WORD 0000H Undefined no command Polling mode input data set reading OOF1H Input data set s request message 001FH Input data set s response message Polling mode output data set writing OOF2H Write output data set settings 002FH Response to write output data set settings Auto update mode Q00E1H Auto update control 001EH Auto update control response 002EH Auto update input data set s message Parameter s Length determined As defined in specific command by command Data Length determined As defined in specific command by command Error response to invalid messages The Ethernet interface module will set the most significant bit of the command word in the event that an invalid or improperly formatted message is received Parameter Length Description Command WORD Bit 15 of receive
33. 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 48 Devices used in the sample program WO 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 po Mevice evice S M500 Receive execution D2 BUFRCYV instruction failure error code M501 BUFRCYV instruction success device D500 and BUFRCV instruction control data D501 M502 BUFRCYV instruction failure device D520 Response command check device M510 BUFRCV instruction normal completion D900 to D976 BUFRCYV instruction receive data area M511 BUFRCV instruction abnormal completion M520 Response command verification normal Fixed buffer reception status signal completion M521 Data size error device Open complete signal M1000 to Device area used for byte swapping Initial processing normal completion signal M1023 BUFRCV instruction Number of executions Number of successes Number of failures Verification check Number of successes Number of failures 1 C device is used to check the operation of the communication program 128 MELSEC WS 129 Note Procedures before operation If the QSCPU connected to the QJ71E71 100 stops during communications in aut
34. 0 238Cu 9100 Transmission target device IP 192 168 250 250 address Transmission target device 2380 0100 Port No hex a 00 4 Network parameter Initial settings for reading writing Fixed buffer communication No procedure procedure Click the Initial settings button to open the configuration dialog and configure 120 for Destination existence confirmation starting interval The QJ71E71 100 can quickly detect a communication stop due to cable disconnection by configuring a smaller value for this option Figure 46 Network parameter Initial settings Timer setting Module will operate with default values if setting is left blank ee Setting vate Default value In units PB X500ms P TCP zero windowtimer 20 X500ms P TCP resendtimer 20 X50 TCP end timer IP assembly timer 10 X500ms 80 Response monitoring timer x500ms Destination existence conformation starting interval 1200 Destination existence conformation interval timer Destination existence conformation resend 80 MELSEC WS WO to W18 2 Sample program 1 Device assignment for reading writing Procedures before operation The following tables list devices used in the sample program Table 29 Devices used in the sample program W device Input data set 1 storage area W20 to W2F Input data set 2 storage area W30 to W4D Input data set 3 storage area MO to M15
35. 0 250 9100 Machine Operator 13 offline A Setting and Monitoring Tool configuration is not verified F Table 26 Configuration value Configuration value TCP IP configuration Option Listen to Connect to parameters Enabled Checked Listen to Selected Deselected Port 9100 238Cy default Connect to Deselected Selected IP address 192 168 250 251 Port 9100 238Cy Enable COS update Enable Any All Update Dataset checkboxes need to be auto update and COS unchecked Update rate ms Update Dataset 1 Unchecked Update Dataset 2 Unchecked Update Dataset 3 Unchecked Update Dataset 4 Unchecked 77 Procedures before operation Figure 42 CPU to Ethernet dialog Figure 43 Ethernet to CPU dialog 4 Editing data sets MELSEC WS 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 Safety Controller Setting and Monitoring Tool 1 3 0 New project Input data Module 1 Tion Module 2 xTDIL2 Module 3 Module 4 Module 5 Module amp Module 7 Module 8 Module 3 Module 10 Module 11 Module 12 Network Module 2 input data GGEGo880 B200 Input input Output goagoe8a0 aasaaaa0 nm RaAnNAATM Module status EFI 1 input Resuk 0 7 Result 0 6 Result 0 5 Result 0 4 Result 0 3 Result 0 2 Res
36. 01 D521 INCP C32 Mazo io Detecting time out of the response command TO RST M420 M300 X19 MO J i i H 1 ZP CLOSE uo K1 D600 M601 CLOSE instruction execution M310 MO 7 z f INCP C40 ii Mp2 SET meio CLOSE instruction normal i completion RST M310 INCP C41 Mp2 set ett J CLOSE instruction abnormal i completion INCP C42 MOV D601 D3 7 CLOSE instruction error code storage END 96 MELSEC WS Table 32 Execution result example in polling mode output data set writing Figure 55 Monitoring result in the Ethernet to CPU dialog 97 Procedures before operation The following table shows an example of the execution result of the program for writing output data sets in polling mode Storage value Byte Device g yt 4 Description hex swapping D900 000AH Not required Receive data length D901 0004 Response command Status Required D902 0000 0 Successful 1 Error 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped 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 The following window shows the execution result of the program for writing output data set in polling mode Byte 0 Byte 1 Byte 2 a0 BBEB8000 w BBEB80080 w BGEG0880 BBEG8000
37. 133 Troubleshooting 9 3 When data cannot be exchanged in auto update mode Troubleshooting when data cannot be exchanged in auto update mode Check if the connection has been opened s the Open complet signal MO on NO YES Check if data has been received in auto update mode from the WSO GETH Was the BUFRCV instruction executed Was the value added in C20 NO YES NO Was the BUFRCYV instruction normally completed Is M510 on YES M510 is on Check if the response command is correct NO auto update control response command received Was the value added in C31 YES The value was added in C31 Was the expected NO value read YES End M511 is on The value was added in C32 Execute a PING test from the QJ71E71 100 to the WSO GETH Check the network totally including the communication path between the WSO iS aresponse etumed GETH and the QJ71E71 100 a noise and installation status YES Check if the WS0 GETH is configured as a master module Check if the IP address and the port number for the WSO GETH are correct No responses including error responses from the WS0 GETH Check if the auto update mode has been configured for the WSO GETH Check the network totally including the communication path between the WSO GETH and the QJ71E71 100 a noise and i
38. 2 bits 104 Procedures before operation MELSEC WS Sample program auto update mode Figure 62 Sample program auto update mode SM402 MOV H2E SWAP SM400 B UO MOV G20480 Uo MOV G20482 7 UO MOV G20485 X19 MO M40 M501 H A PLS M500 ZP BUFRCV Uo K1 D500 D900 RST RST INCP M501 M502 i LSET s lNO M502 H SET s incr MOVP D501 M510 t D901 D520 J swaPP SWAPP s EN SWAPP SET INCP lt gt D901 D520 INCP 105 D520 D520 K4M0 K4M20 K4M40 M500 M501 M510 M511 C20 M510 C21 F M511 C22 J D2 D902 D903 D904 D905 M520 C31 C32 Preparing command data 002E for verification with the response command J Open complete signal acquisition J Open request signal acquisition y Reception status signal Reception processing Receives the Auto update input data set s message command J 002E Executing the BUFRCV instruction automatically upon data reception BUFRCV instruction execution BUFRCV instruction normal completion BUFRCYV instruction abnormal completion BUFRCYV instruction error code storage Verifies if the received data is the J expected response command 002E Procedures before operation MELSEC WS MP i Ds Ko i eee WEH 1 Checking the size of each i
39. 2 reading SWAP D703 MOV H1 D704 Input data set 3 reading SWAP D704 Mov H0 D705 Input data set 4 not reading SWAP D705 M400 M420 X19 Mo Preparing command data 001F H MOV HIF D520_ s for verification with the response command SWAP D520 85 Procedures before operation M400 M420 VI Lx 19 MO 1 ZP BUFSND uo K2 D400 D700 RST RST INCP SET RST LSET INCP j SET MOVP D401 INCP PLS ZP BUFRCV Uo K1 D500 D900 RST RST INCP r n SET INCP SET INCP MOVP D501 M401 M410 M411 C10 M420 M400 M410 c11 M411 D1 C12 M500 M501 M510 M511 C20 M510 C21 M511 C22 D2 MELSEC WS BUFSND instruction execution BUFSND instruction normal completion BUFSND instruction abnormal completion BUFSND instruction error code storage Reception processing Receives the Input data set s response message command 001F Executing the BUFRCV instruction automatically upon data reception JBUFRCV instruction execution BUFRCYV instruction normal completion BUFRCY instruction abnormal completion BUFRCYV instruction error code storage 86 MELSEC WS 87 Procedures before operation D901 D520 SWA
40. 4 2 3 1 Disposal cece cages eats ce eee a ees eat Na sen rename aan eee 14 2 3 2 Material Separation e tecue caetedlagsecta a a eaea 14 3 Ethernet interface module asssseessssesesrnesennnnssenneennnnasnnnnnnnnnnntennntennannnna 15 3 1 D TE E EEEE EEEN A EE EEEE E E E 15 3 1 1 Interfaces and operation cccceccceeeceeeeeeeeeceeaeeeeeeeeeeeetteaeeeeeeeeeeeees 15 3 2 Mounting Dismantling ccceeeeeeeeeeeeeeeeeeeeeeeeeaeeeseeaeeeeeeaeeeseenaeeeeeeaaes 17 3 2 1 Steps for mounting the modules sssseseeseeeeerneeeerresetrreseennssrrneseena 17 3 2 2 Steps for dismantling the modules sessseeeeeeeeeeseerreseerreserrssrrnsseena 19 3 3 Electrical installation setena a A E ae 20 3 4 First Configuration Steps iere eoa e EAT ETa a 20 3 4 1 Establishing a connection between MELSEC WS safety controller and PO r Bo nai cA ron a det ata 20 3 4 2 Assignment of an IP AddreSS 0 0 0 eeeteeeeeeneeeeeeeaeeeeeenaeeeeeeneeeeeeaes 22 3 4 3 Configuration of the Ethernet interface Module n 24 3 4 4 Transfer of a configuration e ee eeeee ce enteeeeeeeeeeeeeaeeeeeeeaeeeeeenaeeeeeeaas 25 3 4 5 Verification of a configuration 0 eee eeteeeeeeteeeeeeeeeeeeenaeeeeeetaeeeeeeaaas 26 3 4 6 Upload of a configuration ce ceeecceeeeeeeeeeneeeeeeeeeeeeeeneeeseenaeeeeeeeaas 26 3 5 Features of the Ethernet interface module eeeeeeeeeeeeeeeeetteeeeeeneees 27 3 5 1 TCP IP configuration interface eccee
41. 50 bytes BUFRCV instruction receive data areas BUFRCV instruction receive data areas Logic result 0 D900 to D2000 D900 to D2000 Logic result 1 Logic result 2 90 Receive gt Receive data length Logic result 3 Module 1 output Module 2 output Command Input data set 1 length Not assigned Input data set 2 length Not assigned In et 3 le Input data set 3 length In Input data set 4 length put data set 2 32 bytes Byte 1 Overall Byte 2 CRC Byte 3 Byte 4 Response to the input data set Logic result 1 Logic result 0 Logic result 1 Logic result 0 read request Logic result 3 Logic result 2 Logic result 3 Logic result 2 Module 2 output Module 1 output Module 2 output Module 1 output put data set 3 60 byt Byte 1 z E Byte 2 Not assigned Not assigned Not assigned Not assigned CPU 0 Bie 5 F Byte 4 Data are stored Byte 1 in Little Endian Pa nout data set 2 CRC Byte 2 e Byte 4 W20 Byte 2 Byte 1 Byte 3 Byte 2 W21 Byte 4 lt Byte 3 Byte 4 put data set 3 module status CPU 0 Byte 1 Byte 3 S Byte 4 W30 Byte 2 Sm Byte 1 Network Byte 2 Byte 1 Byte 2 W31 Byte 4 lt Byte 3 13 Byte 3 Byte 4 VO 1 Network Byte 3 a Byte 4 W32 Byte 2 Byte 1 14 I Byte 1 Byte 2 W33 Byte 4 lt S
42. 8 8 YV Out 4 i Procedures before operation Figure 40 Network module configuration dialog Table 25 Network module configuration parameters MELSEC WS 2 Assigning an IP address for reading writing Assign an IP address of the WSO GETH in the Network module configuration dialog CPU to Ethernet Ethernet to CPU TCP IP configuration C DHCP Device name GETH IP address 192 168 250 250 Subnet mask 255 255 O Default gateway 0 0 0 Option Configuration value DHCP Unchecked Device name GETH any given name IP address 192 168 250 250 default Subnet mask 255 255 0 0 default Default gateway 0 0 0 0 default 76 MELSEC WS Procedures before operation 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 WSO GETH is configured as slave Figure 41 Safety Controller Setting and Monitoring Tool 1 3 0 New project TCP IP configuration dialog CPU1 module o oo Ethemet to BM iesenii Update rate ms Update Dataset 1 v Update Dataset 2 Update Dataset 3 Update Dataset 4 192 168 25
43. 80 gasgaaao v Machine Operator 130ffline Setting and Monitoring Tool configuration is not verified Basically this dialog is divided into three areas Available data 1 Network Module Data 2 and Tag names 3 The upper left corner of the dialog holds the toolbar 4 Data sets Figure 20 Toolbar for the routing configuration Note MELSEC WS 4 4 1 The toolbar BF led Gy Reset to Default Clear all jj i Cl 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 You can not undo this action With the Import and Export buttons you can import and export the used tag names as a CSV comma separated values file This allows you to import and use the assigned tag names in a programmable controller program To edit the CSV file use a text editor When importing the exported network module data after editing the data in a text editor such as Notepad select CSV Files Shift JIS encoded for Files of type in the Open dialog box if the data is saved in ANSI format If not characters in the data may get garbled The Import button is only available for the Ethernet to MELSEC WS routing configuration Reset to defa
44. 808000 aouGua80 20808000 20gogang apanan Network modul configuration El w GBE08880 2 w BGEG00080 w BGEG0880 Tora ae l w pggogang configuration I w gogogo 1 Setl Byte1 Bit Bit B6 Bit4 Bit3 Bit2 Bitl Bitd Update interval ms 4 Machine Operator 2 Offline Setting and Monitoring Tool configuration is not verified Basically this dialog is divided into two areas Network Module Data 1 and Tag names 2 The Network Module Data area shows the current configuration of the output modules The Tag names area shows the tag names associated to the byte selected in the Network Module Data area Selecta byte in the Network Module Data area For each bit of the selected byte that you wish to use enter a tag name in the Tag names area 55 Data sets MELSEC WS Figure 22 Tag names of incoming bits of the WS0 GETH in the logic editor dialog 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 Safety Controller Setting and Monitoring Tool 1 3 0 Sample oy Com settings M43 Connect 13 Disconnect g Transfer a pload X i Hardware configuration 2t33 zy GETH Network module 13 2 Report g Diagnostics 75 2 Sj 100 z ZO matrix Inputs cru Q GeETHI13 PH
45. BBEB8000 w BBEB88080 w BBEB8000 x00 BGEG8880 w BEEG80080 20 BBEB8000 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 WSO GETH and the QJ71E71 100 The WSO GETH automatically sends input data sets to the QJ71E71 100 at 5000 ms intervals Read target data Logic result 0 input data set 1 CRC input data set 2 Each module status input data set 3 Figure 56 System configuration example eerie 100 WS0 GETH IP address 92 168 250 250 Port 9100 IP address 192 168 250 251 Port 9100 The default settings are used for the input data set 1 1 Parameter configuration a Configuration required for the WSO GETH Configuration examples of network parameters required for communications in auto update mode are shown below Configure these parameters using Setting and Monitoring Tool The WSO0 GETH requires no program for communications 1 Creating a hardware configuration Refer to Section 8 2 2 1 2 Assigning an IP address Refer to Section 8 2 2 1 98 MELSEC WS Figure 57 TCP IP configuration dialog Table 33 TCP IP configuration parameters 99 3 Configuring TCP IP Procedures before operation Confi
46. D816 Byte 9 Byte 8 Byte 9 Output data set 3 D817 Byte 1 Byte 0 Output data set 3 D818 Byte3 Byte 2 Byte 0 oe Byte 1_ D821 Byte9 Byte 8 Output data set 4 y D822 Byte 1 Byte 0 D823 Byte3 Byte 2 Output data set 4 Byte 0 Byte 1 D826 Byte 9 Byte 8 Output data set 5 D827 Byte 1 Byte 0 D828 Byte 3 Byte 2 D831 Byte9 Byte 8 Output data set 5 High order byte Low order byte Byte 0 Byte 1 BUFRCV instruction receive data areas Response to the D900 to D2000 output data set write request Receive data length Command Status 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 The WSO GETH responds to the command The response data are stored to the BUFRCYV instruction receive data areas D900 to D976 refer to 2 in Figure 53 The BUFRCV instruction is executed automatically upon data reception The following table lists data to be sent at writing Table 31 Devi Configuration Byte D NE D to be sent at evi
47. DEHCPU Q26UDEHCPU Q50UDEHCPU and Q100UDEHCPU GX Developer The product name of the software package for the MELSEC programmable controllers GX Works2 The product name of the software package for the MELSEC programmable controllers Programming tool A generic term for GX Works2 and GX Developer MELSEC WS About this document 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 module The manual does not provide instructions for operating the machine in which the MELSEC WS safety controller and Ethernet interface module are or will be integrated Information of this kind will be found in the manuals for the machine 1 2 MELSEC WS manuals For the MELSEC WS safety controller there are three manuals with clearly distinguished fields of application as well as user s manuals hardware for each module This manual describes the Ethernet interface module and its functions in detail The user s manuals hardwar
48. Data set 3 contains the module status information transferred to the network Four bytes are used for each module e g WSO XTIO These four bytes are being transferred in Big Endian format i e in 16 bit word format with the first byte placed in the least significant or rightmost byte of the integer and the second byte placed in the most significant or leftmost byte of the integer Data set 3 can not be customized Meaning of the module status bits Table 16 Meaning of the module status bits Safety I O modules CPU modules Network modules 1 Power supply o k 0 Power supply out of range range 1 Power supply o k 0 Power supply out of range Byte Bit e g WS0 XTIO WS0 XTDI e g WS0 CPUx e g WS0 GETH 0 0 Module operating state Module operating state Module operating state 1 Executing 1 Executing 1 Executing 0 Any other state 0 Any other state 0 Any other state 1 Internal error Internal tests failed Internal error Internal tests Internal error Internal tests 1 No error failed failed 0 Error 1 No error 1 No error 0 Error 0 Error 2 External error Summary of bit 0 5 3 7 Power supply out of range or External error Summary of bit 1 No error EFI communication failure 0 5 3 7 0 Error 1 No error 1 No error 0 Error 0 Error inactive 3 Reserved Reserved Reserved 4 Configuration is incompatible or invalid Configuration of a module Configurat
49. E71 100 a noise and installation status LED on the WS0 GETH Check if no other devices on the network has the same IP address Check the communication state of the QU71E71 100 Is the LINK ACT LED on the cable connected side flashing or on Check if the cable is properly connected Replace the cable YES Check the communication state of the QJ71E71 100 Go to the flowchart Go to the flowchart when data cannot be exchanged when data cannot be exchanged in polling mode reading writing in auto update mode 130 MELSEC WS Figure 73 Troubleshooting flowchart when data cannot be exchanged in polling mode 131 Troubleshooting 9 2 When data cannot be exchanged in polling mode reading writing Troubleshooting when data cannot be exchanged in polling mode w2 Check if the connection has been opened The value was Was the added in C2 OPEN instruction normally completed Is M310 on YES M310 is on NO Is the Open complete signal M0 on YES Check if the QJ71E71 100 has sent a command to the WS0 GETH NO Was the BUFSND instruction executed Was M400 turned on YES NO Was the M411 is on BUFSND instruction normally completed Is M410 on VES M410 is on To the next page Execute the OPEN instruction to open the connection Turn on the open execution device M300
50. European Waste Code 16 02 14 2 3 2 Material separation Material separation may only be performed by qualified safety personnel Exercise care when disassembling the devices The danger of injury is present Before you can turn over the devices for environmental friendly recycling you must separate the different materials of the Ethernet interface module from one another Separate the housing from the remaining components especially the PCB Send the separated components to the corresponding recycling centers see the following table Component Disposal Product Electronics recycling Housing PCBs cables plugs and electrical connection pieces Packaging Paper cardboard recycling Cardboard paper 14 MELSEC WS Ethernet interface module 3 Ethernet interface module Figure 1 Interfaces and display elements of the WS0 GETH 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 Exchange configuration data and programs of aMELSEC WS safety controller by connecting to Setting and Monitoring Tool via TCP IP Exchange non safety related data by connecting to an external application e g MELSEC programmable controller PC via TCP IP 3 1 1 Interfaces and operation The Ethernet interface module is equipped with
51. Hardware configuration dialog Once all modules have been identified correctly the Setting and Monitoring Tool will ask whether the configuration shall be uploaded Click Yes to upload the configuration Ethernet interface module MELSEC WS As an example the following hardware configuration may appear Figure 8 p entr i E 3 EE Hardware configuration r dialog Module 0 WSO CPLI 1124 0145 1107 0295 v201 0 200 1 310 240 V 23x Onine Module 13 GETH WS0 GETH 1011 0005 E X v1 050 1 00 x 13 0 240 V 1x 6006 status Online Module 1 xmo WSO XTIO 11196553 d y1130 102 13 0240 V1xx Module 2 gt 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 lf your project is online click on the Disconnect button to go offline gt 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 gt Click on Network module configuration on the left hand menu The following dialog appears 22 MELSEC WS Figure 9 Network module configuration dialog 23 Note Ethernet interface module DHCP Device name GETH IP address to 192 168 250 250 Subnet mask 25 25 0 0 Default gateway o 0 TOP IP configuration
52. IP address Connect a PC or notebook to the RS 232 interface of the CPU module Power on the MELSEC WS safety controller Open the Setting and Monitoring Tool installed on the PC and load the hardware configuration including the Ethernet interface module If your project is online click on the Disconnect button to go offline Assign an IP address For details see Section 3 4 2 Click on the Connect button to go online and transfer the new settings to the MELSEC WS safety controller UU Step 2 Add a TCP IP profile to your project Connect one of the two Ethernet ports of the Ethernet interface module with your Ethernet network using a shielded Ethernet cable Connect a PC or notebook to the same Ethernet network Ensure the IP address settings of the PC match the network setup You can also connect your PC directly to one of the two Ethernet ports of the Ethernet interface module In this case you can either adapt the IP address settings of your PC or the IP address settings of the Ethernet interface module to match the other device s IP setup Open the Setting and Monitoring Tool installed on the PC and load the hardware configuration including the Ethernet interface module If your project is online click on the Disconnect button to go offline Click on Com settings The following dialog appears Ethernet interface module MELSEC WS Figure 11 Connection settings Com settings dialog iy Gey Add TCP IP
53. MELSEC WS Sample program polling mode output data set writing Figure 54 Sample program polling mode output data set writing sm400 i U0 MOV G20480 3 UO MOV G20482 i UO MOV G20485 M300 M310 X19 MO M20 ai r n r n MOVP HO zore K1 D300 RST RST INCP M301 M302 g j t LSET INCP M302 f SET LINCP MOVP D301 93 DO OPEN instruction error code strage Procedures before operation M400 M420 X19 MO H MOV K62 MOV HOF2 t S SNS SS _ SwaP MOV HOA SWAP MOV HOA SWAP MoV HOA tRNA swap MOV HOA SWAP MOV HOA SWAP M400 M420 X19 MO 1 f 6 SET SET SET SET M400 M420 X19 MO H 1 f H MOV H2F SWAP MELSEC WS D800 Send data size specification byte Command Write output data set D801 settings D801 J D802 Output data set 1 writing D802 D803 Output data set 2 writing D803 D804 Output data set 3 writing D804 D805 D805 D806 D806 D807 0 D807 9 D808 2 D808 B D521 D521 Output data set 4 writing jOutput data set 5 writing _ Output data set 1 status change Bit O of Byte 0 is set to Active _ Output data set 1 status change Bit 1 of Byte 1 is set to Active _ Output data set 1 status change Bit 2 of Byte 2 is set to Active Output data set 1 status change Bit 3 of Byte 3 is set to Active _ Preparing comm
54. MITSUBISHI ELECTRIC MELSECTVS erie Safety Controller Ethernet Interface Module User s Manual WS0 GETH Powered by SICK MELSEC WS series products were jointly developed and manufactured by Mitsubishi and SICK AG Industrial Safety Systems in Germany Note that the warranty on MELSEC WS series products differs from that on MELSEC Q or MELSEC QS series products Refer to WARRANTY written in this manual MITSUBISHI Ai_A2j 4 11 12 13 14 X1 X2 X3 X4j MS XTDI 5 16 7 18 X5 X6 x7 xel 13 23 33 43 Y14 Y1 Y24 Y3 ARO B1 Y2 B2 Y4 14 24 34 44 This document is protected by the law of copyright whereby all rights established therein remain with the company Mitsubishi Electric Corporation Reproduction of this document or parts of this document is only permissible within the limits of the legal determination of Copyright Law Alteration or abridgement of the document is not permitted without the explicit written approval of the company Mitsubishi Electric Corporation Precautions regarding warranty and specifications MELSEC WS series products are jointly developed and manufactured by Mitsubishi and SICK AG Industrial Safety Systems in Germany Note that there are some precautions regarding warranty and specifications of MELSEC WS series products lt Warranty gt The gratis warranty term of the product shall be for one 1 year after the date of delivery or for eighteen 18 months after man
55. O to M15 Open complete signal BUFRCYV instruction failure error code M20 to M35 Open request signal D500 and D501 BUFRCV instruction control data M40 to M55 Fixed buffer reception status signal D520 Response command check device M500 Receive execution D900 to D976 BUFRCYV instruction receive data area M502 BUFRCYV instruction failure device Initial processing normal completion signal M510 BUFRCYV instruction normal completion M511 BUFRCYV instruction abnormal completion M520 Response command verification normal completion M521 Data size error device BUFRCYV instruction Number of executions Number of successes Number of failures Verification check Number of successes Number of failures 1 C device is used to check the operation of the communication program Note Ifthe QCPU 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 WSO GETH This may cause the receive buffer of the QJ71E71 100 to overflow and data transmission of the WS0 GETH to stop Ifthe scan time of the QCPU connected to the QJ71E71 100 is longer than the transmission interval of the WSO GETH update of received data delays For this reason configure the auto update interval much longer than the scan time 102 MELSEC WS Procedures before operation The following shows details of data
56. Open complete signal OPEN instruction abnormal completion error code M20 to M35 Open request signal BUFSND instruction abnormal completion error code M40 to M55 Fixed buffer reception status signal BUFRCYV instruction abnormal completion error code M300 Open execution OPEN instruction success device D300 to D309 CLOSE instruction abnormal completion error code OPEN instruction control data OPEN instruction failure device D400 and D401 BUFSND instruction control data OPEN instruction normal completion D500 and D501 BUFRCYV instruction control data OPEN instruction abnormal completion D520 Response command check device reading Send execution D521 Response command check device writing BUFSND instruction success device D600 and D601 CLOSE instruction control data BUFSND instruction failure device D700 to D705 BUFSND instruction send data area reading BUFSND instruction normal completion D800 to D831 BUFSND instruction send data area writing BUFSND instruction abnormal completion Command in execution Receive execution D900 to D976 BUFRCYV instruction receive data area reading and writing Initial processing normal completion signal BUFRCYV instruction success device BUFRCYV instruction failure device BUFRCYV instruction normal completion BUFRCYV instruction abnormal completion
57. PP D902 SWAPP D903 SWAPP D904 H S WAPP D905 SET M520 INCP C31 RST M420 lt gt D901 D520 INCP C32 L SRST M420 M520 lt gt D902 K50 J SET M521 lt gt D903 K32 lt gt D904 K60 M520 M521 Vf BMOVPD906 WO K25 FOR K23 M520 M521 P H SWAP D931Z0 _ Ma Swap 193220 MOV D931Z0 W21Z0 MOV D932Z0 Ww20Z0 K2 ZO NEXT M520 E LRST ZO RST M520 RST M521 M420 K150 it To TO _ DDNY NNN frst 420 Verifies if the received data is the expected response command 001F Checking the size of each input data set Storing input data set 1in W device WO to W18 Storing input data set 2 CRC in W device W20 to W2F Storing input data set 3 module status in W device W30 to W4D Detecting time out of the response command Procedures before operation MO po uo K1 D600 INCP SET RST INCP SET INCP MOV D601 M601 C40 M610 M310 C41 M611 C42 D3 END J J I MELSEC WS CLOSE instruction execution CLOSE instruction normal completion ICLOSE instruction abnormal completion CLOSE instruction error code storage 88 MELSEC WS Figure 49 Input data set 1 a logic result Figure 50 Input data set 2 overall CRC Figure 51 Input data set 3 CPU module status Figure 52 Input data set 3 network module status 89 Proced
58. SEC WS safety controller The Ethernet interface module does not have a dedicated voltage supply The Ethernet interface module is not suitable for operation on a safety fieldbus The Ethernet interface module only generates non safety related fieldbus data status bytes for control and diagnostics purposes Do not use non safe data from an Ethernet interface module for safety related applications With the Ethernet interface module it is possible to integrate non safe data into the logic editor such that the safety function of the MELSEC WS safety controller is compromised Never implement the Ethernet interface module into a MELSEC WS safety controller without having this danger checked by a safety specialist The Ethernet interface module may only be used by qualified safety personnel and only on the machine where they have been installed and initialized by qualified safety personnel in accordance with the manual 12 MELSEC WS ATTENTION Note ATTENTION On safety Pay attention to the safety notes and safety measures on the Ethernet interface module 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 When mounting installing and using the Ethernet interface module observe the standards and directives applicable in your country The national international rules and regulations apply t
59. Section 8 2 2 1 b Configuration required for the QJ71E71 100 Refer to Section 8 2 2 1 120 MELSEC WS Procedures before operation 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 WO 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 M device OPEN instruction abnormal completion EE e a A erorene on ema corneen m1 BUFSND SUSTO abnormal Histo OPEN eruen nemai corean comeron rarcode 5z BUFROV instruction abnormal E E 53 CLOSE struction anora rice BUFRO merueion are eves _ ompictonenercode M411 BUFSND instruction abnormal completion D401 E D501 reading writing D600 and CLOSE instruction control data D601 D700 to D705 BUFSND instruction send data area reading M510 BUFRCV instruction normal completion D800 to D831 BUFSND instruction send data area writing reading and writing TA Fined buffer SOOD TON SESIA M601 CLOSE instruction success device Open complete signal M520 Response command verification normal X device completion M602 CLOSE instruction failure device Initial processing normal
60. all connect to the Ethernet interface module perform the following configuration steps Activate the Listen to radio button Enter the Port number for the application Suggested port numbers are 9100 to 9103 default values Port 0 and port 9000 are reserved and can not be used faulty configuration Port numbers 0 to 1023 are managed by the Internet Assigned Numbers Authority IANA and can not be used See http www iana org assignments port numbers Finally determine how the data is transferred Follow the steps outlined in the following section Data transfer method how the data is transferred Whenever the TCP IP socket connection has been established either by an application on a PC or by the Ethernet interface module itself there are two possible methods how the data sets can be transferred The application requests the data set s per command message Application requests Polling mode or the Ethernet interface module auto updates the data sets as per configuration Ethernet interface module writes to Address Port Auto update mode In the auto update mode there are two update modes how the Ethernet interface module update the data Update COS Change of state when any data of the input data set change status Heartbeat interval data will be sent automatically according to the configured Heartbeat rate in ms If Heartbeat interval is enabled a change of state will trigger an immediate
61. amages as well as damages of a pecuniary nature the disclaimers and limitations contained in these terms shall apply to all three types of damages to the fullest extent permitted by law If however the personal injury wrongful death and or physical property damages cannot be disclaimed or limited by law or public policy to the extent provided by these terms then in any such event the disclaimer of and limitations on pecuniary or economic consequential and incidental damages shall nevertheless be enforceable to the fullest extent allowed by law f In no event shall any cause of action arising out of breach of warranty or otherwise concerning the Products be brought by Customer more than one year after the cause of action accrues g Each of the limitations on remedies and damages set forth in these terms is separate and independently enforceable notwithstanding the unenforceability or failure of essential purpose of any warranty undertaking damage limitation other provision of these terms or other terms comprising the contract of sale between Customer and MELCO 4 Delivery Force Majeure a Any delivery date for the Products acknowledged by MELCO is an estimated and not a promised date MELCO will make all reasonable efforts to meet the delivery schedule set forth in Customer s order or the purchase contract but shall not be liable for failure to do so b Products stored at the request of Customer or because Customer refuses
62. an integrated three port switch for connection with the Ethernet network Two RJ45 sockets are available for the connection The switch functionality allows the Ethernet interface module to be used for connection to another Ethernet component e g connection to a notebook without having to interrupt the Ethernet connection to the network One IP address can be configured RJ45 Ethernet socket LED power supply green ees LED network activity for Ethernet port 1 or port 2 green LED MS red green RJ45 Ethernet socket Ethernet interface module Table 3 Meaning of the LED displays Note MELSEC WS LED Meaning PWR O No power supply Green Power supply switched on LINK ACT 1 O No Ethernet connection LINK ACT 2 Green Ethernet connection active no data transmission amp Green Ethernet connection active data transmission MS O No power supply or immediately after the module start Green Executing live process data from to CPU Green Idle Red 1 Hz Configuring configuration required 2 Hz Critical fault on Ethernet interface module Red Critical fault on another module Red Green Executing but Ethernet communication not established or faulty Error elimination is described in Chapter 5 Power up sequence On power up the following LED test sequence is performed LED MS LED MS Red for 0 25 s O Off for 6 s J
63. and data 002F for verification with the response command 94 MELSEC WS M400 M420 Procedures before operation x19 MO m ZP BUFSND Uo K2 D400 D800 RST RST INCP SET RST SET INCP SET MOVP D401 INCP X19 j M500 MO j iT H PLS kE BUFRCV U0 K1 D500 D900 RST RST M502 INCP 95 SET INCP SET J TF Incr MOVP D501 M401 M410 M411 C10 M420 M400 M410 C11 M411 D1 C12 M500 M501 M510 M511 C20 M510 C21 M511 C22 D2 BUFSND instruction execution BUFSND instruction normal completion BUFSND instruction abnormal completion Reception processing Receives the Response to writhe output data set settings command 002F Executing the BUFRCV instruction automatically upon data reception BUFRCV instruction execution BUFRCV instruction normal completion BUFRCYV instruction abnormal completion BUFRCYV instruction error code storage Procedures before operation MELSEC WS M420 M510 M410 _ Verifies if the received data is the 1 1 D901 D521 D902 HO SET M520 expected response command 002F and the status is normal INCP C31 RST M420 lt gt D902 HO I INCP C33 RST M420 lt gt D9
64. area Or gt Select the byte you want to delete by clicking it with the left mouse button Then click on the Delete routing button in the toolbar Or Call up the context menu by clicking the respective byte with the right mouse button In the context menu select the Delete routing command How to move a data byte to another place in the routing table Drag and drop the byte you want to move to the desired position If the desired position is not free you will have to clear it first by deleting or moving the byte currently assigned to it 4 4 4 Tag names area This area shows the tag names associated with each bit of the byte currently selected in the Available data or the Network Module Data area You can enter these tag names in the tag name editor In the Tag names area of the CPU to Ethernet configuration dialog you can only edit tag names for unassigned data sets by activating the Use direct editing checkbox with CPU module firmware version V2 00 0 or higher 54 MELSEC WS Data sets 4 5 Tag names for incoming data Ethernet to MELSEC WS In order to enable incoming data bits gt Click on Ethernet to MELSEC WS on the left hand menu The following dialog appears Figure 21 i Safety Controller Setting and Monitoring Tool 1 3 0 New project Ethernet to eee eres MELSEC WS dialog of i akat the WS0 GETH Report g amp Diaenostics CPU1 module aGaceaso aoaaceaso aGaceaso aoaceaso aoaua0800 20
65. ation In that case click on the Disconnect button to go offline make the correct configuration in the Connection settings dialog and then retry the connection 30 MELSEC WS ATTENTION Figure 16 TCP IP configuration dialog 31 Ethernet interface module 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 The output data set can be written to the Ethernet interface modules in parallel by all communication interfaces or TCP IP sockets if they use the same output data set number In that case the last message overrides data received earlier The Ethernet interface module processes the data of a MELSEC WS safety controller and makes it available in different compilations the data sets These data sets are available over the TCP IP interface For a detailed description of the data sets please refer to Chapter 4 In order to configure the Ethernet TCP IP socket interface perform the following steps Open the Setting and Monitoring Tool and load the hardware configuration including the Ethernet interface module Click on the GETH Network module 13 button Network Modules button when two network mo
66. available from another network module in the system 1 In the default configuration only the first logic result byte Logic Result 0 is active and available You can activate more logic result output bits in the logic editor Sources currently not configured will be displayed in grey Activating the Show only available data checkbox in the upper left corner hides the unused sources from the view Sources that offer live data are marked with a little icon next to the text How to add a data byte to the routing table Drag and drop an element i e byte from the Available data area to a free slot in the Network Module Data area If the desired position is not free you will have to clear it first by deleting or moving the byte currently assigned to it It is possible to use the same byte several times in the routing table 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 How to delete a data byte from the routing table Drag and drop the byte you want to delete to the trashcan icon in the bottom left corner of the Network Module Data
67. ce value hex swapping escription ii D800 003E Not required Send data length 62 bytes D801 00F24 Command D802 000A Write data specification Output data set 1 writing 10 bytes D803 000A Write data specification Output data set 2 writing 10 bytes D804 000A Required Write data specification Output data set 3 writing 10 bytes D805 000A Write data specification Output data set 4 writing 10 bytes D806 000A Write data specification Output data set 5 writing 10 bytes D807 Output data set 1 Byte 0 and Byte 1 D808 Output data set 1 Byte 2 and Byte 3 D809 Any Not required Output data set 1 Byte 4 and Byte 5 D810 Output data set 1 Byte 6 and Byte 7 D811 Output data set 1 Byte 8 and Byte 9 D812 to D816 Any Not required Output data set 2 D817 to D821 Any Not required Output data set 3 D822 to D826 Any Not required Output data set 4 D827 to D831 Any Not required Output data set 5 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped 92 Procedures before operation K4M0 K4M20 K4M40 D300 M301 M310 M311 co M310 C1 M311 C2 Open complete signal acquisition Open request signal acquisition Reception status signal OPEN instruction control data storage J OPEN instruction execution HOPEN instruction normal completion OPEN instruction abnormal completion
68. completion M610 CLOSE instruction normal completion M611 CLOSE instruction abnormal completion M1000 to Device area used for byte swapping M1023 M2000 OPEN execution 1PLS oOo M2001 OPEN request signal 121 Procedures before operation MELSEC WS z Qpan stigin BURSND TANAR BUFRON Sing Veaineatncie Cleeineiucion 1 C device is used to check the operation of the communication program For details of data transmission and reception processing in a program for reading input data sets in polling mode refer to Section 8 2 2 2 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped Note that the byte order of the input data set 1 and output data set 1 does not need to be changed because these data are one byte long lt Data need to be swapped gt Command and parameters word data 16 bits Input data set 2 and 3 double word data 32 bits 122 MELSEC WS Table 45 Data to be sent at reading 123 Procedures before operation The following table lists data to be sent at reading A Configuration Byte Ra Device neh Description value hex swapping D700 000AH Not required Send data length 10 bytes D701 OOF 14 Command D702 00014 Read data specification Input data set 1 reading D703 00014 Read data specification Input data set Required 2 reading D704 00014 Read data specification Input data se
69. cribes 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 Ethernet interface module ina MELSEC WS safety controller system gt WS0 GETH MELSEC QJ71E71 100 Ethernet interface module in a MELSEC programmable controller system QJ71E71 100 7 1 Features achieved by the connection MELSEC programmable controllers can acquire MELSEC WS safety controller information over Ethernet The QJ71E71 100 connected to a MELSEC programmable controller or the Built in Ethernet port QCPU can read MESLEC WS safety controller information e g operation results of the CPU module safety input output data over Ethernet Two communication modes are available polling mode and auto update mode Figure 27 Acquiring MELSEC WS safety controller information lt Setting and Monitoring Tool gt lt MELSEC Q series programmable controller gt WS0 GETH QJ71E71 100 1 2 ee I ntroller gt 64 MELSEC WS 65 Connecting to MELSEC programmable controllers 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 Etherne
70. ction success device D500 and D501 SOCRCYV instruction control data SOCSND instruction failure device D520 Response command check device reading SOCSND instruction normal completion D521 Response command check device writing SOCSND instruction abnormal completion D600 and D601 SOCCLOSE instruction control data Command in execution D700 to D705 SOCSND instruction send data area reading Receive execution D800 to D831 SOCSND instruction send data area writing SOCRCYV instruction success device D900 to D976 SOCRCYV instruction receive data area reading and writing SOCRCV instruction failure device SOCRCYV instruction normal completion SOCRCYV instruction abnormal completion Response command verification normal completion Data size error device SOCCLOSE instruction success device SOCCLOSE instruction failure device SOCCLOSE instruction normal completion SOCCLOSE instruction abnormal completion 110 MELSEC WS Procedures before operation Co SOCOPEN instruction Number of executions C1 Number of successes C2 Number of failures C11 Number of successes C12 Number of failures C21 Number of successes C22 Number of failures C31 Verification check Number of successes C32 Number of failures C33 Number of response errors writing C40 SOCCLOSE inst
71. d command will be set i e command of 00F2H would become 80F21 Following Length Unchanged Returned as it was received data determined by command Application requests Polling mode In this mode the Ethernet interface module will only send any data upon request e g polling Therefore the application shall send request telegrams as per definition below and the Ethernet interface module will respond with telegrams structured as per definition below Input data set reading The request message is sent by an application to the Ethernet interface module The request message telegram shall be structured as shown below Ethernet interface module Table 6 Input data set read request Table 7 Input data set read response Table 8 Output data set write request MELSEC WS set 4 Parameter Length Value Command WORD 00F1H Data set s request message 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 set 2 1 Send data set 2 Request data WORD 0 Do not send data set 3 set 3 1 Send data set 3 Request data WORD 0 Do not send data set 4 1 Send data set 4 The response message is returned to the application by the Ethernet interface module The response message telegram will be structured as shown below Parameter Length Value Command WORD 001FH Data se
72. dered by the Arbitrator shall be final and binding and may be entered by any court having jurisdiction thereof The place of the arbitration shall be New York City New York The language of the arbitration shall be English The neutral organization designated to perform the functions specified in Rule 6 and Rules 7 7 b 7 8 and 7 9 shall be the CPR Microsoft Windows Windows Vista Windows NT Windows XP Windows Server Visio Excel PowerPoint Visual Basic Visual C and Access are either registered trademarks or trademarks of Microsoft Corporation in the United States Japan and other countries Ethernet is a registered trademark of Xerox Corp All other company names and product names used in this manual are either trademarks or registered trademarks of their respective companies SH NA 080857ENG E SICK SICKAG Tel 49 7681 202 0 _http www sick com SH NA 080857ENG E 1306 MEE MODEL WS ET U E MODEL CODE 13JZ33 MITSUBISHI ELECTRIC CORPORATION 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 Specifications subject to change without notice
73. dules are used above the main window and select the desired network module or double click on the desired network module in the hardware configuration view to open the network module configuration dialog Click on TCP IP configuration on the left hand menu The following dialog appears Safety Controller Setting and Monitoring Tool 1 3 0 New project Socket 1 Socket 2 Socket 3 7 Enabled Enabled Listen to CPU to Ethernet Port aa mo g g O Connect to Ethernet to CPU Enable COS update Network Enable auto update and COS configuration Update rate ms Update Dataset 1 v Update Dataset 2 Update Dataset 3 Update Dataset 4 192 168 250 250 9100 Machine Operator l Offline Setting and Monitoring Tool configuration is not verified Ethernet interface module MELSEC WS Note Note Note 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 Enter the Port number for the application The configuration is considered faulty if either the connect socket port and or the connect IP address is zero when in Connect mode If the external application sh
74. e 972 4 9990590 E Mail info sick sensors com Italia Phone 39 02 27 43 41 E Mail info sick it Japan Phone 81 0 3 3358 1341 E Mail support sick jp Nederlands Phone 31 0 30 229 25 44 E Mail info sick nl Norge Phone 47 67 81 50 00 E Mail austefjord sick no Osterreich Phone 43 0 22 36 62 28 8 0 E Mail office sick at Polska Phone 48 22 837 40 50 E Mail info sick pl Republic of Korea Phone 82 2 786 6321 4 E Mail kang sickkorea net Republika Slovenija Phone 386 0 1 47 69 990 E Mail office sick si Romania Phone 40356171120 E Mail office sick ro Russia Phone 7 495 775 05 34 E Mail info sick automation ru Schweiz Phone 41 41 619 29 39 E Mail contact sick ch Singapore Phone 65 6744 3732 E Mail admin sicksgp com sg Suomi Phone 358 9 25 15 800 E Mail sick sick fi Sverige Phone 46 10 110 10 00 E Mail info sick se Taiwan Phone 886 2 2375 6288 E Mail sales sick com tw Turkiye Phone 90 216 587 74 00 E Mail info sick com tr United Arab Emirates Phone 971 4 8865 878 E Mail info sick ae USA Canada Mexico Phone 1 952 941 6780 1800 325 7425 tollfree E Mail info sickusa com 134 2 Limits of Warranties a MELCO does not warrant or guarantee the design specify manufacture construction or installation of the materials construction criteria functionality use WARRANTY 1 Limited Warranty and Product Support a Mitsubishi Electric Company MELCO warrants that
75. e are enclosed with each MELSEC WS module They inform on the basic technical specifications of the modules and contain simple mounting instructions Use the user s manuals hardware when mounting MELSEC WS safety controllers The Safety Controller User s Manual describes all the MELSEC WS modules and their functions in detail Use the manual in particular to configure MELSEC WS safety controller The Safety Controller Setting and Monitoring Tool Operating Manual describes the software supported configuration and parameterization of the MELSEC WS safety controller In addition the manual contains the description of the diagnostics functions that are important for operation and detailed information for the identification and elimination of errors Use the manual in particular for the configuration commissioning and operation of MELSEC WS safety controllers About this document Table 1 Overview of the MELSEC WS manuals MELSEC WS The following shows the relevant manuals Title Number Safety Controller User s Manual WS CPU U E 13JZ32 Safety Controller Ethernet Interface Module User s WS ET U E Manual 13JZ33 Safety Controller CC Link Interface Module User s WS CC U E Manual 13JZ45 Safety Controller Setting and Monitoring Tool Operating SW1DNN WSOADR B O E Manual 13JU67 Safety Controller CPU Module User s Manual Hardware WS CPU U HW 13J200 Safety Controller Safety I O Module Us
76. e 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 If you have selected Enable auto update and COS select the Update rate in ms Configurable range 40 to 65535 Select which data sets shall be updated Check the Update Dataset n checkbox 38 MELSEC WS Table 12 Auto update mode normal operation message Table 13 TCP IP process image example 39 Normal operation Ethernet interface module The following message is sent from the Ethernet interface module to the application while operating in auto update mode Parameter Length Value Command WORD 002En Auto update data set s message Data set 1 length WORD 0 Data set not returned in data set s data field Non zero Length of data set Data set 2 length WORD 0 Data set not returned in data set s data field Non zero Length of data set Data set 3 length WORD 0 Data set not returned in data set s data field Non zero Length of data set Data set 4 length WORD 0 Data set not returned in data set s data field Non zero Length of data set Data set s data Array of bytes Data set s information Details see Section 4 1 and length dependent Section 4 3 on set definition 3 5 3 TCP IP process image example The following example shows a possible process image sent by an Ethernet interface module via TCP IP in auto
77. eeeeeeeeeeeeeeeneeeeeenneeeeetneeeerena 27 3 5 2 Ethernet TCP IP socket interface eee eeeeeeeeeeneeeeeeeeeeeeeeneeeeeeaas 31 3 5 3 TCP IP process image example ccccccceeeeeceeeeeeeeeeeeeeeeeeeeeeeeees 39 4 Data SOUS orr e e aa Beles daae ea ae cc deaptera eaea t 42 4 1 Data transmitted into the network network input data sets 43 4 1 1 LOGIC results coussinet oe dove acces 2 daveeedacevev bln dowel Na E sd d aiis 45 4 1 2 Module and EFI input and output values eccceeceeeeeeeeteeeeeeeees 45 4 1 3 Routing of data from a second network 1 0 0 eeeeeeeeeteeeeeeeeeeeseeneeeeeeeaees 45 4 1 4 Configuration checksums CRCS eeeeeceeeeeeneeeeeetneeeeeeneeeeeenaeeeeeeaaes 46 4 1 5 Error and status information of the MOUIES cceeeeeeenteeeeeenees 46 4 2 Data received from the network network output data sets 49 4 3 Default settings for the input data Set 1 oo ee eeeeeeeeeteeeeeeneeeeeenaes 50 4 4 Customizing the input data set 1 MELSEC WS to Ethernet 51 4 4 1 The tool bale titeeee thts ceetestiehs Saracens ee eee 52 4 4 2 Available data area oe ee eeee cece tenets eeecaeeeeeeaeeeeeenaeeeeeenaeeeeeeaaes 53 4 4 3 Network Module Data area eccecceeneeeeceenneeeseeeaeeeeeenaeeeeeeneeeeneaaes 54 444 Taginames area csi neer Melee el Pe E EREE AEREE 54 4 5 Tag names for incoming data Ethernet to MELSEC WS ee 55 4 5 1 Saving and loading a configuration 000 ee eete
78. eeeeeteeeeeetteeeeeeneeeeeenaes 57 4 5 2 Importing and exporting a configuration ee eeeeeeteeeteeeteeteeeeteeeeees 57 4 6 Monitoring the data Set online 0 ee eeeeeeeeeeneeeeeeeneeeeeeaeeeeeenaeeeeseaaes 58 5 TEPOUBICSMOOUIAG ri tien tests neteccee sedans tieaeter be T tieastatemadiandy 59 6 Technical Specifications cccecccceccececeeeseceeeaeceeeeeeeseceneaeeeeeeeseesnnieaeeeeeess 61 6 1 Technical specifications of Ethernet interface module 08 61 6 2 Technical specifications Supply circuit eccceeececeeeeeeeeeeeeeeeeeeeeeteees 61 6 3 General technical specifications ccccccceceecceceeeeeeeeeeneeeeeeeeeteeeeenaeees 61 6 4 Dimensional CrawingS cccceeeeeeeeeeeeeeeeneeeeeeeaeeeseecaeeeseenaeeeseenaeeeeeeaaes 63 6 5 Module information z bisiet eaa a i eea aT 63 7 Connecting to MELSEC programmable controllers 0 0 eeceeeeeteeeeeeeee 64 7 1 Features achieved by the CONNECTION ceeeeeceeeenteeeeeeteeeeeenaeeeeeenaes 64 7 2 Applicable System ccccccseececceceeeeeeeeeeacaeeeeeeeeesesanaeceeeeeeesennaaeeeeees 65 8 Procedures before Operation ccceceececeeceeeceeeeeeenaeeeeeeeeeseneacaeeeeeeeeeeees 66 8 1 WV IAG PERRE PEEP E E E E teed antes avin TE TERS 71 8 1 1 Wiring precaution naniineica aae a a 73 8 2 Communications with the QJ71E71 100 QCPU ccccesceeeesteeeeeeees 74 8 2 1 System configuration sai
79. een performed Figure 14 Connection settings dialog with new TCP IP profile 29 Ethernet interface module Create new profile Entry name i Intel R 82566DM 2 Gigabit Network Connection MAG address 00 1 E 4F D3 31 ACG IP address 10 97 19 58 IP address 10 97 19 54 C Enable TCP IP routing Subnet address 255 265 255 0 Gateway address Search for devices IP address Device name 20D BE 10 971954 GETH gt 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 Click OK The profile has now been created and is shown in the connection dialog Connection settings i idd COM profile g ky Add TOP IP profile Check all profiles 4 Network settings COM auto detection Auto scan Active connection Pe Standard Yo Serial port Indeterminate connection state Serial COM auto detection Port COM auto detection Baud rate Auto scan Connection is not stored in project file Choose connection type Check connection Activate profile Press this button if you want to save the profile to the project file Edit profile To configure the connection please proceed as follows Yo Yo v H s Cancel In order to use this profile it needs to be activated Click on the Activate profile icon white arrow in green circle
80. eesseeseseeeeeineeserrisisnneetinanstnnnesnnaaddnnnneetanaaaeana 74 8 2 2 Polling mode input data set reading ceceeeeseeeeeeeteeeeeetteeeeeeaes 75 8 2 3 Polling mode output data set writing eeeseeeeessseeeseereseerrssrerrsseeres 90 8 2 4 Auto update mode ccccceceeeeeeeeeececeeeeeeeeaeaeeeeeeeeesensanaeeeeeeeeeeeees 98 8 3 Communications with the Built in Ethernet port QCPU 107 8 3 1 System COMPIQUIATION siecia iir eai AAT E 107 8 3 2 Polling mode input data set reading cccceeeeeeeeeesteeeeeetteeeeeeaes 107 8 3 3 Polling mode output data set writing eeeeeseeeseseeeeesreseerrsseernssenes 112 8 3 4 Auto update mode ccccceeeeeeeceecceeeeeeeseeeeeaeceseeeeeseseeeaeeeeeeeeneeees 114 8 4 Communications with the QJ71E71 100 QSCPU eceeeeeeeee 120 8 4 1 Systemi CONMPIQUIALION nire a r E A AEE 120 8 4 2 Polling mode input data set reading cccceeeeseeeeeeeteeeeeetteeeeeeaes 120 8 4 3 Polling mode output data set Writing 0 0 cece eeeeeeeeeeteeeeeenteeeeeees 124 8 4 4 Auto update modes ie a a a a abe 127 9 Frouble hooting ve52 cc cese lstease tens cesses casas A A T AAA TERSA a 130 9 1 When data cannot be normally exchanged seessseeeeesesrsseerreseerreses 130 9 2 When data cannot be exchanged in polling mode reading writing 131 9 3 When data cannot be exchanged in auto update mode 133 10 POX 558s a sea iar tee cova rad
81. er s Manual WS IO U HW Hardware 13201 Safety Controller Safety Relay Output Module User s WS SR U HW Manual Hardware 13202 Safety Controller Ethernet Interface Module User s WS ET U HW Manual Hardware 134203 Safety Controller CC Link Interface Module User s WS CC U HW Manual Hardware 13J209 1 3 Target group This manual is addressed to planning engineers machine designers and the operators of systems in which a MELSEC WS safety controller is integrated and who want to exchange data with a fieldbus a controller via a network module It also addresses people who integrate the network module into a machine commission it initially or who are in charge of servicing and maintaining the unit 10 MELSEC WS 11 ATTENTION Note EFI Note Red Red OGreen gt Action ATTENTION About this document 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 status information planning and related mapping part numbers Warning Pay attention to the safety notes and safety measures on the Ethernet interface module For the acquisition of Setting and Monitoring Tool please contact your local Mitsubishi representative 1 5 Scope This manual applies to the WSO GETH Ethernet interface module This docume
82. ese data are one byte long lt Data need to be swapped gt Command and parameters word data 16 bits Input data sets 2 and 3 double word data 32 bits 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 119 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 WSO 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 WS0 GETH QJ71E71 100 mounted in Slot 0 IP address 192 168 250 250 IP address 192 168 250 251 Port 9100 Port 9100 8 4 2 Polling mode input data set reading This section describes an example of communications in polling 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 Read target data Logic result 0 input data set 1 CRC input data set 2 Each module status input data set 3 1 Parameter configuration a Configuration required for the WSO GETH Refer to
83. ets 1 to 3 Note MELSEC WS Table 15 shows the overview of data sets available for the Ethernet interface module Data set 1 default Data set 2 Data set 3 Byte 0 Logic result 0 Overall CRC Module status module 0 Byte 1 Logic result 1 Module 0 is always the CPU Byte 2 Logic result 2 For detailed information about Byte 3 Logic result 3 the module status see Table 16 Byte 4 Input values module 1 System CRC Module status module 1 Byte 5 Input values module 2 SCID Byte 6 Input values module 3 Byte 7 Input values module 4 Byte 8 Input values module 5 Reserved Module status module 2 Byte 9 Input values module 6 Byte 10 Input values module 7 Byte 11 Input values module 8 Byte 12 Input values module 9 Verified Module status module 3 Byte 13 Input values module 10 configuration Byte 14 Input values module 11 CRC Byte 15 Input values module 12 Byte 16 Output values module 1 Reserved Module status module 4 Byte 17 Output values module 2 Byte 18 Output values module 3 Byte 19 Output values module 4 Byte 20 Output values module 5 Module status module 5 Byte 21 Output values module 6 Byte 22 Output values module 7 Byte 23 Output values module 8 Byte 24 Output values module 9 Module status module 6 Byte 25 Output values module 10 Byte 26 Output values module 11 Byte 27 Output values module 12 Byte 28 Not ass
84. ety measures other than the Product MELCO is not liable for damages that could have been prevented by compliance with any applicable safety standard regulation or law 2 MELCO prohibits the use of Products with or in any application involving and MELCO shall not be liable for a default a liability for defect warranty a quality assurance negligence or other tort and a product liability in these applications 1 power plants 2 trains railway systems airplanes airline operations other transportation systems 3 hospitals medical care dialysis and life support facilities or equipment 4 amusement equipments 6 handling of nuclear or hazardous materials or chemicals 5 incineration and fuel devices 7 mining and drilling 8 and other applications where the level of risk to human life health or property are elevated REVISIONS The manual number is given on the bottom left of the back cover Print date Manual number Revision September 2009 SH NA 080857ENG A First edition March 2010 SH NA 080857ENG B Correction of errors in writing August 2011 SH NA 080857ENG C Correction of errors in writing August 2012 SH NA 080857ENG D Setting and Monitoring Tool was upgraded June 2013 SH NA 080857ENG E Correction of errors in writing Japanese manual version SH 080854 E This manual confers no industrial property rights or any rights of any other kind nor does it confer
85. g module You will find an example process image in Section 3 5 3 48 MELSEC WS Data sets 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 Table 17 Output data blocks 1 to 5 for the Ethernet interface module Output Output Output Output Output data block data block data block data block data block 1 size 2 size 3 size 4 size 5 size WS0 GETH 10 bytes 10 bytes 10 bytes 10 bytes 10 bytes 49 Note ATTENTION The contents of the output data blocks can be used within the Setting and Monitoring Tool logic editor and can also be made available to another network via a second network module in the MELSEC WS safety controller In order to make the data from the network available in the logic editor or as input to another network you will have to define a tag name for each bit that shall be used Bits without a tag name will not be available in the logic editor nor for routing via another network module For detailed information on how to define tag names for the data received please see Section 4 5 The status of the communication to and from the network can be monitored in the logic editor using the module input status bit for data from the network and the module output status
86. gure 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 WSO GETH is configured as master Safety Controller Setting and Monitoring Tool 1 3 0 New project a O Listen to Etheiet 2 po 3 z Connect to Ethernet to IP address CPU 192 168 250 251 amp Port Network O Enable COS update module configuration Enable auto update and COS Update rate ms so S B Update Dataset 1 a Update Dataset 2 v Update Dataset 3 V Update Dataset 4 192 168 250 250 192 168 250 251 9100 CPU1 module v Machine Operator l offine A Setting and Monitoring Tool configuration is not verified Configuration value Configuration value open Listen to Connect to Enabled Checked Listen to Selected Deselected Port 9100 238Cn default Connect to Deselected Selected IP address 192 168 250 251 Port 9100 238Cu Enable COS update Enable auto update and COS Enable auto update and COS Update rate ms 5000 default Update Dataset 1 Checked Update Dataset 2 Checked Update Dataset 3 Checked Update Dataset 4 Unchecked 4 Editing data sets Refer to Section 8 2 2 1 To switch the communication mode to the polling mode acti
87. h the most significant byte byte 3 placed in the leftmost position Status module 0 WSO CPU0 WS0 CPU1 OK Status module 1 e g WSO XTDI OK Status module 2 e g WSO0 XTIO Byte 0 FF 11111111 No errors Byte 1 FF 11111111 No errors Byte 2 FB 11111011 Input 3 external test signal failure Byte 3 FD 11111101 Output 1 stuck at low error Status modules 3 6 OK Status modules 7 12 no modules present Status module 13 e g WSO GETH OK Status module 14 no module present 40 MELSEC WS 41 Ethernet interface module Byte values hex Part of message Meaning 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 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 Data sets 4 Data sets Note ATTENTION MELSEC WS 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 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 Therefore data sent from the MELSEC WS safety controller into the network will be referred to as input data while data received from
88. hange of any input data set value QJ71E71 100 Connection open Input data set transmission Input data set transmission Input data set transmission 1 If the Enable COS update parameter is selected the input data sets are also sent whenever any input data set value is changed 70 MELSEC WS Table 24 Ethernet cable Figure 34 Cable connection diagram 71 Procedures before operation 8 1 Wiring This section describes the wiring of the WSO 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 Name Remarks Shielded twisted pair cable STP with RJ45 jack Straight cable of Category 5 or higher The following figure shows connection of the cable and the connector Procedures before operation Figure 35 Wiring example line topology Figure 36 Wiring example star topology Figure 37 Wiring example line topology and star topology 2 Network topologies MELSEC WS Two network topologies using Ethernet cables are available line topology and star topology using a hub QJ71E71 100 QJ71E71 100 QJ71E71 100
89. hrough communications between the WS0 GETH and the QJ71E71 100 Write target data Output data sets 1 to 5 In the sample program bit 0 of Byte O bit 1 of Byte 1 bit 2 of Byte 2 and bit 3 of Byte 3 in output data set 1 are set to Active High 1 Parameter configuration a Configuration required for the WS0 GETH Refer to Section 8 2 2 1 b Configuration required for the QJ71E71 100 Refer to Section 8 2 2 1 2 Sample program 1 Device assignment Refer to Section 8 2 2 2 90 MELSEC WS 91 Procedures before operation 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 WS0 GETH QJ71E71 100 BUFSND instruction send data areas D800 to D831 Output data set 1 Byte 0 D800 Send data length Byte 1 Byte 2 D801 Command Byte 3 Byte 4 Request for D802 Parameter 1 Byte 5 writing output D803 Parameter 2 Byte 6 data sets D804 Parameter 3 Byte 7 D805 Parameter 4 Byte 8 D806 Parameter 5 Byte 9 Output data set 1 Output data set 2 D807 Byte 1 Byte 0 Byte 0 D808 Byte 3 Byte 2 Byte 1 D809 Byte 5 Byte 4 Byte 2 D810 Byte 7 Byte 6 Byte3 D811 Byte 9 Byte 8 Byte 4 Output data set 2 Byte 5 D812 Byte 1 Byte 0 Byte 6 D813 Byte 3 Byte 2 Byte 7 Lo Byte 8
90. ic result 0 1 Logic result 1 2 Logic result 2 3 Logic result 3 4 Module 1 input 5 Module 2 input 6 Module 3 input 7 Module 4 input 8 Module 5 input 9 Module 6 input 10 Module 7 input 11 Module 8 input 12 Module 9 input 13 Module 10 input 14 Module 11 input 15 Module 12 input rt 50 bytes 16 Module 1 output 17 Module 2 output 18 Module 3 output 19 Module 4 output 20 Module 5 output 21 Module 6 output 22 Module 7 output 23 Module 8 output 24 Module 9 output 25 Module 10 output 26 Module 11 output 27 Module 12 output 28 to 35 Not assigned 36 to 47 Not assigned 48 to 49 Not assigned The default byte assignment can be freely customized as will be described in the following section 50 MELSEC WS Figure 19 MELSEC WS to Ethernet dialog of the WS0 GETH 51 Data sets 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 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
91. icable 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 MELCO is not liable for damages that could have been prevented by compliance with any applicable safety standard regulation or law c MELCO prohibits the use of Products with or in any application involving power plants trains railway systems airplanes airline operations other transportation systems amusement equipments hospitals medical care dialysis and life support facilities or equipment incineration and fuel devices handling of nuclear or hazardous materials or chemicals mining and drilling and other applications where the level of risk to human life health or property are elevated d MELCO SHALL NOT BE LIABLE FOR SPECIAL INCIDENTAL CONSEQUENTIAL INDIRECT OR PUNITIVE DAMAGES FOR LOSS OF PROFITS SALES OR REVENUE FOR INCREASED LABOR OR OVERHEAD COSTS FOR DOWNTIME OR LOSS OF PRODUCTION FOR COST OVERRUNS OR FOR ENVIRONMENTAL OR POLLUTION DAMAGES OR CLEAN UP COSTS WHETHER THE LOSS IS BASED ON CLAIMS FOR BREACH OF CONTRACT OR WARRANTY VIOLATION OF STATUTE NEGLIGENCE OR OTHER TORT STRICT LIABILITY OR OTHERWISE e In the event that any damages which are asserted against MELCO arising out of or relating to the Products or defects in them consist of personal injury wrongful death and or physical property d
92. ified You have to be logged in as an Administrator in order to mark the device as verified Ifthe verification is completed successfully a Read in and compare report that provides the most important project information is created subsequently You can print out or store this report The status verified not verified is indicated in the lower right hand corner of the Setting and Monitoring Tool and by the CV LED of the CPU module turning on Only if the device and the corresponding configuration have been marked as verified the Auto RUN Mode is active in the configuration of the CPU module If the configuration is not set to verified the safety controller stays in Idle mode CV LED on the CPU module flashing after power up and needs to be set to Run Mode using the Setting and Monitoring Tool If differences between the project data and the read back configuration data are detected a corresponding message including information about possible actions is displayed Verification of the configuration is not possible then Observe the information in the error message for the further procedure Terminate the dialog box by clicking Close If you change a verified configuration the status is reset to not verified Exception If you make only non safety related changes such as modifying the Ethernet interface module name the Ethernet interface module s IP address or the port number for a TCP IP socket connection the conf
93. igned Module status module 7 Byte 29 Not assigned Byte 30 Not assigned Byte 31 Not assigned Byte Not assigned Byte 49 Not assigned Byte No data ae Byte 56 Module status module 14 Byte 57 Module 13 and 14 are always the Byte 58 network modules Byte 59 Length 50 bytes 32 bytes 60 bytes If a dual channel element is connected to a safety I O module the low order bit of the redundant I O signals shows the active I O state ON OFF of the element 44 MELSEC WS 45 Note Data sets 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 For detailed information see Section 4 4 4 1 2 Module and EFI input and output values The Ethernet interface module can transmit all input and output states of all MELSEC WS modules and EFI devices connected to the MELSEC WS safety controller into the network Data set 1 containing the input and output values and the EFI information can be customized For detailed information see Section 4 4 Module input and output states The input and output states of the modules are transmitted using one byte for each module s inputs and one byte for each module s outputs where each bit represents the state of one input or output on off EFI system information
94. iguration required for the WSO GETH Configuration examples of network parameters required for communications in auto update mode are shown below Configure these parameters using Setting and Monitoring Tool The WSO0 GETH requires no program for communications 1 Creating a hardware configuration Refer to Section 8 2 2 1 2 Assigning an IP address Refer to Section 8 2 2 1 114 MELSEC WS Figure 67 TCP IP configuration dialog Table 41 TCP IP configuration parameters 115 3 Configuring TCP IP Procedures before operation 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 WSO GETH is configured as master Safety Controller Setting and Monitoring Tool 1 3 0 New project Broject Device Extras Z Com settings Dd J CPU to Ethemet Connect to IP address 192 168 250 251 PU iS Port E ao g Nona O Enable COS update configuration Enable auto update and COS Update rate ms 5 a Update Dataset 1 Update Dataset 2 Update Dataset 3 Update Dataset 4 192 168 250 250 CPU1 module Machine Operator 13 offline A Setting and Monitoring Tool configuration is not verified Option Configuration value Configuration value
95. iguration status remains verified More information can be found in the Safety Controller Setting and Monitoring Tool Operating Manual 3 4 6 Upload of a configuration When in online mode you can upload a configuration from the connected MELSEC WS safety controller gt Click on Upload The current configuration of the safety controller will be loaded into the Setting and Monitoring Tool and can be edited after going offline 26 MELSEC WS 27 ATTENTION Note Ethernet interface module 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 The MELSEC WS safety controller can only communicate with one instance of the Setting and Monitoring Tool at one time Connecting to the safety controller using multiple instances of the Setting and Monitoring Tool either on a single PC or multiple PCs may result in inconsistencies of the configuration and the diagnostics as well as in operational errors This applies to both RS 232 and Ethernet connections equally In order to configure an interface for TCP IP configuration for the first time perform the following steps Step 1 Assign an
96. ion is incompatible 1 Configuration valid within the system is or invalid 0 Conf invalid or unknown incompatible or invalid 1 Configuration valid 1 Configuration valid 0 Conf invalid or unknown 0 Conf invalid or unknown 5 Output power supply out of range Power supply out of specified Input status changed to invalid 1 Valid network communication 0 Invalid or no communication 46 MELSEC WS Data sets Byte Bit Safety I O modules CPU modules Network modules y e g WS0 XTIO WS0 XTDI e g WS0 CPUx e g WS0 GETH 0 6 Output fast shut off logic control time out EFI 1 communication failure Output status 1 No error 0 Time out exceed because the control signal from CPU logic has not switched off within 1s 1 No error 0 Error 1 Valid network communication 0 Invalid or no communication Reserved EFI 2 communication failure 1 No error 0 Error Reserved Input 1 2 dual channel input evaluation error 1 No error 0 Error Input 3 4 dual channel input evaluation error 1 No error 0 Error Input 5 6 dual channel input evaluation error 1 No error 0 Error Input 7 8 dual channel input evaluation error 1 No error 0 Error Reserved Reserved Reserved Reserved oOIN O a Input 1 external test signal failure 1 No error 0 Error Input 2 external test signal failure 1 No error 0 Error
97. ired Output data set 3 D822 to D826 Any Not required Output data set 4 D827 to D831 Any Not required Output data set 5 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped 125 Procedures before operation Table 47 Execution result example in polling mode output data set writing The following table shows an example of the execution result of the program for writing output data sets in polling mode MELSEC WS 1 Error Storage value Byte Device 3 yi 4 Description hex swapping D900 00044 Not required Receive data length D901 2F00 Response command Status Required D902 0000 0 Successful swapped 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be 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 126 MELSEC WS Procedures before operation 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 WSO GETH and the QJ71E71 100 The WSO GETH automatically sends input data sets to
98. iting output data sets in polling mode refer to Section 8 2 3 2 Please replace the BUFSND and BUFRCYV instructions with the SOCSND and SOCRCYV instructions The following table lists data to be sent at writing Configuration Byte Pat Device Pan Description value hex swapping D800 003E Not required Send data length 62 bytes D801 00F24 Command D802 000A Write data specification Output data set 1 writing 10 bytes D803 000A Write data specification Output data set 2 writing 10 bytes D804 000A Required Write data specification Output data set 3 writing 10 bytes D805 000A Write data specification Output data set 4 writing 10 bytes D806 000A Write data specification Output data set 5 writing 10 bytes D807 Output data set 1 Byte 0 and Byte 1 D808 Output data set 1 Byte 2 and Byte 3 D809 Any Not required Output data set 1 Byte 4 and Byte 5 D810 Output data set 1 Byte 6 and Byte 7 D811 Output data set 1 Byte 8 and Byte 9 D812 to D816 Any Not required Output data set 2 D817 to D821 Any Not required Output data set 3 D822 to D826 Any Not required Output data set 4 D827 to D831 Any Not required Output data set 5 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped The following table shows an example of the execution result of the pr
99. itions In accordance with EN61131 2 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 Il 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 Weight Light grey 125g Data interface FLEXBUS backplane bus Ethernet interface One connector on the top and one connector on the bottom Mounting rail Mounting rail according to EN 60715 62 MELSEC WS Figure 26 Dimensional drawings of WS0 GETH mm Table 23 Module information 63 Technical specifications 6 4 Dimensional drawings 58 78 fl ba a a a 67 85 pamm fl Unit mm 6 5 Module information Type Module name Abbreviation WS0 GETH00200 MELSEC WS safety controller Ethernet interface WS0 GETH Connecting to MELSEC programmable controllers MELSEC WS 7 Connecting to MELSEC programmable controllers This chapter des
100. lure to do so may cause malfunction due to poor contact Place the cables in a duct or clamp them If not dangling cable may swing or inadvertently be pulled resulting in damage to the module or cables or malfunction due to poor contact Tighten the terminal screw within the specified torque range Undertightening can cause short circuit or malfunction Overtightening can damage the screw and or module resulting in drop short circuit or malfunction When disconnecting the cable from the module do not pull the cable by the cable part When disconnecting the cable with connector from the module hold the connector part When disconnecting the cable connected to a terminal block loosen the terminal screws first Failure to do so may result in damage to the module or cable or malfunction Prevent foreign matter such as dust or wire chips from entering the module Such foreign matter can cause a fire failure or malfunction CONDITIONS OF USE FOR THE PRODUCT 1 Although MELCO has obtained the certification for Product s compliance to the international safety standards IEC61508 EN954 1 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 saf
101. 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 The MELSEC WS safety controller fulfils the requirements of Class A industrial applications in accordance with the Interference emission basic specifications The MELSEC WS safety controller is therefore only suitable for use in an industrial environment and not for private use Installation Precautions CAUTION Use the MELSEC WS safety controller in an environment that meets the general specifications in the user s manual for the CPU module used Failure to do so may result in electric shock fire malfunction or damage to or deterioration of the product Latch the module onto the DIN rail Incorrect mounting may cause malfunction failure or drop of the module To ensure full electromagnetic compatibility EMC the DIN mounting rail has to be connected to functional earth FE Ensure that the earthling contact is positioned correctly The earthling spring contact of the module must contact the DIN rail securely to allow electrical conductivity Additionally connect all network cable shields directly at the control cabinet entrance to a common FE ground line Tighten the screw within the specified torque range Undertightening can cause drop of the screw short circuit or malfunction Overtightening can damage the screw and or module resulting in drop short circuit o
102. n this manual please contact your local Mitsubishi representative 68 MELSEC WS Figure 31 Polling mode input data set reading Figure 32 Polling mode output data set writing 69 Procedures before operation Polling mode Example QJ71E71 100 Polling mode input data set reading command OOF 1 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 WSO GETH QJ71E71 100 WS0 GETH Connection open Read Request execution Response Input data sets Response Input data sets Read execution Polling mode output data set writing command 00F2 002F The QJ71E71 100 sends the Write output data set settings command to the MELSEC WS safety controller to write data to the output data sets in the WSO0 GETH QJ71E71 100 WS0 GETH Connection open Request Write Output data sets execution Response Request Write Output data sets execution i Response Procedures before operation MELSEC WS Figure 33 Auto update mode Auto update mode Example QJ71E71 100 Input data set auto update command 002E The WSO GETH automatically sends input data sets MELSEC WS safety controller information to the QJ71E71 100 at the following timing At fixed intervals Upon c
103. ng 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 The Built in Ethernet port QCPU writes MELSEC WS safety controller information e g logic result CRC and each module status to the safety controller through communications between the WSO0 GETH and the Ethernet ports of Built in Ethernet port QCPU Write target data Output data sets 1 to 5 In the sample program bit 0 of Byte O bit 1 of Byte 1 bit 2 of Byte 2 and bit 3 of Byte 3 in output data set 1 are set to Active High 1 Parameter configuration a Configuration required for the WSO GETH Refer to Section 8 2 2 1 b Configuration required for the Built in Ethernet port QCPU Refer to Section 8 3 2 1 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 Refer to Section 8 3 2 2 112 MELSEC WS Table 39 Data to be sent at writing Table 40 Execution result example in polling mode output data set writing 113 Procedures before operation For details of data transmission and reception processing in a program for wr
104. nput A Idata set lt gt D903 K32 lt gt D904 K60 M520 M521 Storing input data set 1 in W device H A BMOVPD906 wo K25 WO to W18 Storing input data set 2 CRC in W device For k23 W20 to W2F Storing input data set 3 module status in M520 M521 W device W30 to W4F H SWAP D931Z0 SWAP D93220 MOV D931z0 W21z0 MOV D932Z0 wz20z0 K2 Zo s L M520 RST ZO RST M520 RST M521 END 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 106 MELSEC WS Procedures before operation 8 3 Communications with the Built in Ethernet port QCPU This section describes parameter configuration examples and sample programs for communications between the WSO 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 WS0 GETH mTeuBisia oooe Built in Ethernet port QCPU 107 IP address 192 168 250 250 IP address 192 168 250 251 Port 9100 Port 9100 8 3 2 Polling mode input data set reading This section describes an example of communications in polling mode The Built in Ethernet port QCPU reads MELSEC WS safety controller information e g logic result CRC
105. nstallation status Check the code of an error occurred by executing the BUFRCV instruction and eliminate the error Eliminate the error referring to the error code stored in D2 Check if the response data are correctly verified in the verification processing Check that the data have been sorted in Little Endian format Check if the Update Dataset checkboxes are correctly selected Check if the MELSEC WS CPU module is in Run state 1 For details of the sample program refer to Section 8 3 2 For troubleshooting of the QJ71E71 100 refer to the Q Corresponding Ethernet Interface Module User s Manual Basic 10 Annex 10 1 SICK contact MELSEC WS More representatives and agencies in all major industrial nations at www sick com Australia Phone 61 3 9497 4100 1800 33 48 02 tollfree E Mail sales sick com au Belgium Luxembourg Phone 32 0 2 466 55 66 E Mail info sick be Brasil Phone 55 11 3215 4900 E Mail sac sick com br CeskaRepublika Phone 420 2 57 91 18 50 E Mail sick sick cz China Phone 852 2763 6966 E Mail ghk sick com hk Danmark Phone 45 45 82 64 00 E Mail sick sick dk Deutschland Phone 49 211 5301 260 E Mail info sick de Espana Phone 34 93 480 31 00 E Mail info sick es France Phone 33 1 64 62 35 00 E Mail info sick fr GreatBritain Phone 44 0 1727 831121 E Mail info sick co uk India Phone 91 22 4033 8333 E Mail info sick india com Israel Phon
106. nstruction and eliminate the error Eliminate the error referring to the error code stored in D2 YES M510 is on Check if the response command is correct NO The value was i added in C32 Check if no Update Dataset checkbox is checked for the WS0 GETH with Setting and Monitoring Tool Check if the response data are correctly verified in the verification processing Check if the data have been sorted in Little Endian format Was a response command for the reques command received Was the value added in C31 YES The value was added in C31 NO The value was added in C33 In polling mode output data set writing is the status of the response command 0 Check if the MELSEC WS CPU module is not in Stop state The MELSEC WS safety controller may be in Idle state initial processing Re execute write processing NO Check if the read write request data sent from the QJ71E71 100 have been correctly sorted In polling mode output data set writing check if the MELSEC WS CPU module is in Run state Was the expected value read written YES 1 For details of the sample program refer to Section 8 3 End 2 For troubleshooting of the QJ71E71 100 refer to the Q Corresponding Ethernet Interface Module User s Manual Basic 132 MELSEC WS Figure 74 Troubleshooting flowchart when data cannot be exchanged in auto update mode
107. nt is the original manual 1 6 Abbreviations used Enhanced Function Interface 1 7 Symbols used Notes provide special information on the device LED symbols describe the state of a diagnostics LED Examples Red_ The red LED is illuminated constantly Red The red LED is flashing OGreen The green LED is off Instructions for taking action are shown by an arrow Read carefully and follow the instructions for action ATTENTION An ATTENTION indicates an actual or potential risk or health hazard They are designed to help you to prevent accidents Read carefully and follow the attention notices On safety MELSEC WS 2 On safety ATTENTION 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 Qualified safety personnel are defined as persons who have undergone the appropriate technical training and have been instructed by the responsible machine operator in the operation of the machine and the current valid safety guidelines and have access to the manuals of the Ethernet interface module and safety controller and have read and familiarized themselves with them 2 2 Correct use The Ethernet interface module can only be operated with a MEL
108. nto which they are incorporated c Customer acknowledges that qualified and experienced personnel are required to determine the suitability application design construction and proper installation and integration of the Products MELCO does not supply such personnel provided promptly and in no event later than thirty d MELCO is not responsible for designing and 30 days after the Customer knows or has reason conducting tests to determine that the Product to believe that Products are not as warranted and functions appropriately and meets application iv in any event the notice must given within the standards and requirements as installed or warranty period incorporated into the end user s equipment 2 Customer shall cooperate with MELCO and production lines or systems MELCO s representatives in MELCO s investigation e MELCO does not warrant any Product of the warranty claim including preserving evidence 1 repaired or altered by persons other than MELCO or of the claim and its causes meaningfully its authorized engineers or FA Centers responding to MELCO s questions and investigation 2 subjected to negligence carelessness accident of the problem grant MELCO access to witnesses misuse or damage personnel documents physical evidence and 3 improperly stored handled installed or maintained records concerning the warranty problem and allow 4 integrated or used in connection with improperly MELCO to examine and test the
109. o the installation commissioning use and periodic technical inspection of the MELSEC WS safety controller in particular EMC directive 2004 108 EC Provision and Use of Work Equipment Directive 89 655 EC the work safety regulations safety rules This manual must be made available to the operator of the machine where the MELSEC WS safety controller is used The machine operator is to be instructed in the use of the device by qualified safety personnel and must be instructed to read the manual Since an Ethernet interface module is powered from the CPU module connect a Class 2 power supply or a Class 2 transformer in accordance with UL310 or UL1585 to the CPU module The MELSEC WS safety controller fulfils the requirements of Class A industrial applications in accordance with the Interference emission basic specifications The MELSEC WS safety controller is therefore only suitable for use in an industrial environment and not for private use On safety ATTENTION Table 2 Overview of disposal by components 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
110. o update mode the BUFRCV instruction will not be executed even when data are transmitted from the WSO GETH This may cause the receive buffer of the QJ71E71 100 to overflow and data transmission of the WSO GETH to stop If the scan time of the QSCPU connected to the QJ71E71 100 is longer than the transmission interval of the WSO GETH update of received data delays For this reason configure the auto update interval much longer than the scan time 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 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped Note that the byte order of the input data set 1 and output data set 1 does not need to be changed because these data are one byte long lt Data need to be swapped gt Command and parameters word data 16 bits Input data sets 2 and 3 double word data 32 bits 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 Troubleshooting MELSEC WS 9 Troubleshooting Figure 72 Troubleshooting flowchart when data cannot be normally exchanged 9 1 When data cannot be normally exchanged Refer to the following flowchart when the WSO GETH cannot normally exchange data wi
111. ogram for writing output data sets in polling mode Storage value Byte Device g yte 4 Description hex swapping D900 00044 Not required Receive data length D901 2FO0u Response command Status Required D902 00004 0 Successful 1 Error 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped 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 8 3 4 Auto update mode This section describes an example of communications in auto update mode The Built in Ethernet port QCPU reads MELSEC WS safety controller information e g logic result CRC and each module status from the safety controller through communications between the WSO GETH and the QJ71E71 100 The WS0 GETH automatically sends input data sets to the QJ71E71 100 at 5000 ms intervals Read target data Logic result 0 input data set 1 CRC input data set 2 Each module status input data set 3 Figure 66 System configuration example IP address 192 168 250 251 Port 9100 The default settings are used for the input data set 1 IP address 192 168 250 250 gt Port 9100 1 Parameter configuration a Conf
112. on the far right The entry point will then be activated and marked as such Ethernet interface module MELSEC WS Figure 15 Connection settings Connection settings ile h Add TCP IP profile Check all profiles Network settings dialog with new TCP IP i profile activated pen Cees GE 10 9728250 Active connection To configure the connection please proceed as follows ad Ethernet E Choose connection type D fo o TCP IP Indeterminate connection state Ca x Check connection Ethernet TOP IP i IP address 10 97 28250 ined STIL Press this button if you want to save the profile to the project file a a Port 9000 a a Intel 21140 Based PCI Fast Ethernet Adapter Generic 00 03 F F 01 06 36 192 168 131 65 e TCP IP routing is not used Edit profile Connection is not stored in project file Cancel 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 Note The port number for the TCP IP configuration interface is pre set to port 9000 and can not be changed Step 3 Connect via TCP IP Click on the Connect button to go online Note While Setting and Monitoring Tool is connected via TCP IP do not transfer the parameters in which the IP address of the connected Ethernet interface module has been changed Doing so will result in disconnection of communic
113. open the configuration dialog and configure the options as follows Ethernet operations Communication data code r Initial timing Do not wait for OPEN Communications impossible at STOP time ASCII code e Always wait for OPEN Communication possible at STOP time IP address m Send frame setting Input format DEC Ethernet 2 0 IP address 192 168 250 251 e IEEE 302 3 Enable Write at RUN time m TCP Existence confirmation setting Use the Keepdlive C Use the Ping 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 Port No input format HEX Network parameter f Fixed buffer Pairi Exist Host stati Transmission Transmission Open settings Protocol Open system Fixed buffer communication elle wate Pe tN el target device IP target device procedure lain TA NS address Port No PE free N Sond eats N outs Sarl asta 2 TCP Active v Send No procedure Enable Confim 238C 192 168 250 250 238 Table 28 Configuration value Configuration value Network parameter Active Unpassive Protocol TCP Open system Open settings Pairing open Enable Existence confirmation Host station Port No hex 238Cu 910
114. or delays shipment shall be at the risk and expense of Customer c MELCO shall not be liable for any damage to or loss of the Products or any delay in or failure to deliver service repair or replace the Products arising from shortage of raw materials failure of suppliers to make timely delivery labor difficulties of any kind earthquake fire windstorm flood theft criminal or terrorist acts war embargoes governmental acts or rulings loss or damage or delays in carriage acts of God vandals or any other circumstances reasonably beyond MELCO s control 5 Choice of Law Jurisdiction These terms and any agreement or contract between Customer and MELCO shall be governed by the laws of the State of New York without regard to conflicts of laws To the extent any action or dispute is not arbitrated the parties consent to the exclusive jurisdiction and venue of the federal and state courts located in the Southern District of the State of New York Any judgment there obtained may be enforced in any court of competent jurisdiction 6 Arbitration Any controversy or claim arising out of or relating to or in connection with the Products their sale or use or these terms shall be settled by arbitration conducted in accordance with the Center for Public Resources CPR Rules for Non Administered Arbitration of International Disputes by a sole arbitrator chosen from the CPR s panels of distinguished neutrals Judgment upon the award ren
115. or the Products h These terms and conditions constitute the entire agreement between Customer and MELCO with respect to warranties remedies and damages and supersede any other understandings whether written or oral between the parties Customer expressly acknowledges that any representations or statements made by MELCO or others concerning the Products outside these terms are not part of the basis of the bargain between the parties and are not factored into the pricing of the Products i THE WARRANTIES AND REMEDIES SET FORTH IN THESE TERMS ARE THE EXCLUSIVE AND ONLY WARRANTIES AND REMEDIES THAT APPLY TO THE PRODUCTS j MELCO DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 3 Limits on Damages a MELCO S MAXIMUM CUMULATIVE LIABILITY BASED ON ANY CLAIMS FOR BREACH OF WARRANTY OR CONTRACT NEGLIGENCE STRICT TORT LIABILITY OR OTHER THEORIES OF RECOVERY REGARDING THE SALE REPAIR REPLACEMENT DELIVERY PERFORMANCE CONDITION SUITABILITY COMPLIANCE OR OTHER ASPECTS OF THE PRODUCTS OR THEIR SALE INSTALLATION OR USE SHALL BE LIMITED TO THE PRICE PAID FOR PRODUCTS NOT AS WARRANTED b Although MELCO has obtained the certification for Product s compliance to the international safety standards IEC61508 and EN954 1 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 appl
116. port buttons you can import and export a configuration including the tag names used as a CSV comma separated values file This allows you to import and use tag names you have assigned in the MELSEC WS safety controller project in another programmable controller program and vice versa To edit the CSV file use a text editor If you import a configuration all previously made changes that have not been saved will be lost You can not undo this action The Import button is only available for the Ethernet to MELSEC WS routing configuration Data sets Figure 23 Active and inactive bits in the online process image Figure 24 Inactive Network input bits as a result of an error Figure 25 Network output bits with no tag names assigned in the online process image Note 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 dialog Click on the MELSEC WS to Ethernet or the Ethernet to MELSEC WS tab on the left hand menu to display the routing view for the input or output data you want to monitor
117. put modules WS0 4RO to the extreme right of the entire MELSEC WS safety controller Mount the modules in accordance with EN 50274 The modules are located in a 22 5 mm wide modular system for 35 mm DIN rails according to EN 60715 Ensure that suitable ESD protective measures are taken during mounting Otherwise the FLEXBUS backplane bus may be damaged The connection between the modules is effected by means of the plug connection integrated in the housing Take into account that when replacing a module the MELSEC WS modules have to be pushed approx 10 mm apart before the corresponding module can be removed from the DIN rail Take suitable measures to ensure that foreign matter does not penetrate the connector openings in particular that of the memory plug Ethernet interface module MELSEC WS Figure 2 Mounting the module onto the DIN rail Figure 3 Installing the end clips 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 Up to two network modules per system are possible Ensure that the earthing spring contact is positioned correctly 2 The earthing spring contact of the module must contact the DIN rail securely to allow electrical conductivity Latch the module onto the DIN rail by pressing i
118. puts change their status the changed status of these outputs will be transmitted to the programmable controller since the actual physical status of the outputs on the devices has changed 58 MELSEC WS 5 Troubleshooting 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 Note Check the LEDs of the module during troubleshooting Table 19 Troubleshooting for the WSO GETH Error Cause Possible remedy The Setting and Monitoring Tool does not connect to the Ethernet interface module WSO0 GETH has no power supply WSO0 GETH is not in the same physical network as the PC The PC is configured to another subnet mask in the TCP IP settings WSO GETH has already been configured once and has a fixed set IP address or an IP address assigned by a DHCP server that is not recognized Establish the power supply Check the Ethernet wiring and network settings on the PC and correct if necessary Set the subnet mask on the PC to 255 255 0 0 factory setting of the WSO GETH Check the communication settings in the Setting and Monitoring Tool WSO GETH does not supply any data LED PWR Green LED LINK ACT Green LED MS Red Green WSO0 GETH is configured for data transfer to programmable controller but Ethernet communication is not yet established or faulty Duplicate IP address de
119. r malfunction Shut off the external power supply all phases used in the system before mounting or removing the module Failure to do so may result in damage to the product Do not directly touch any conductive part of the module Doing so can cause malfunction or failure of the module The MELSEC WS safety controller is only suitable for mounting in a control cabinet with at least IP 54 degree of protection Failure to meet the installation method may cause the module to fail or malfunction due to the deposition of dust or the adhesion of water Make sure that the connection of the Ethernet interface module cannot lead to hazardous situations during installation Ensure that the connection of the Ethernet dedicated cables and power cables cannot lead to a hazardous situation when implementing the unit on to the MELSEC WS safety controller and Ethernet network Prevent unintended start up of equipment during connection of a Ethernet interface module Failure to do so may cause the system to malfunction 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 Connect the connectors to the module securely Fai
120. reception processing in a program for receiving input data sets in auto update mode Figure 61 Data reception processing in auto update mode WS0 GETH QJ71E71 100 Input data set 1 50 bytes BUFRCV instruction receive data areas BUFRCV instruction receive data areas 0 Logic result 0 D900 to D2000 D900 to D2000 1 Logic result 1 2 Logic result 2 D900 Receive data length D900 Receive data length 3 Logic result 3 4 Module 1 output Command D901 Command 5 Module 2 output Input data set 1 length D902 Input data set 1 length 48 Not assigned Input data set 2 length D903 Input data set 2 length 49 Not assigned Input data set 3 length D904 Input data set 3 length Input data set 4 length D905 Input data set 4 length put data set 2 32 byt Byte 1 Input data set 1 storage areas Overall Byte 2 WO to W4D CRC Byte 3 Byte 4 Response to Input data set 1 input data set Logic result 1 Logic result 0 Logic result 1 Logic result 0 J auto update Logic result 3 Logic result 2 Logic result 3 Logic result 2 Module 2 output Module 1 output Module 2 output Module 1 output Input data set 3 60 bytes Byte 1 Byte 2 Not assigned Not assigned Not assigned Not assigned Byte 3 Data are stored Byte 4 in Little Endian format Byte 1 2 ut data
121. ruction Number of executions C41 Number of successes C42 Number of failures 1 C device is used to check the operation of the communication program For details of data transmission and reception processing in a program for reading input data sets in polling mode refer to Section 8 2 2 2 Please replace the BUFSND and BUFRCYV instructions with the SOCSND and SOCRCY instructions Since the Built in Ethernet port QCPU treats application data in Little Endian format the byte order needs to be swapped Note that the byte order of the input data set 1 and output data set 1 does not need to be changed because these data are one byte long lt Data need to be swapped gt Command and parameters word data 16 bits Input data set 2 and 3 double word data 32 bits The following table lists data to be sent at reading Table 38 ae Configuration Byte ti evice escription Data to be sent at value hex swapping 1 p reading D700 000A Not required Send data length 10 bytes D701 OOF 14 Command D702 00014 Read data specification Input data set 1 reading D703 00014 Read data specification Input data set Required 2 reading D704 00014 Read data specification Input data set 3 reading D705 0000 Read data specification Input data set 4 not reading 111 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped Procedures before operation MELSEC WS 3 Monitori
122. s iatine ated ara eatessa et od ae Sasa ee ea te seed 134 10 1 SICK Contactisi secs odie ee Sa bara atest a ete 134 GENERIC TERMS AND ABBREVIATIONS Generic term abbreviation Description WSO0 MPL Abbreviation for the WSO MPL000201 MELSEC WS safety controller memory plug WS0 CPUO The abbreviation for the WS0 CPU000200 MELSEC WS safety controller CPU module WS0 CPU1 The abbreviation for the WS0 CPU130202 MELSEC WS safety controller CPU module WSO0 XTIO The abbreviation for the WS0 XTI084202 MELSEC WS safety controller safety I O combined module WS0 XTDI The abbreviation for the WSO XTDI80202 MELSEC WS safety controller safety input module WS0 4RO The abbreviation for the WS0 4RO4002 MELSEC WS safety controller safety relay output module WS0 GETH The abbreviation for the WSO GETH00200 MELSEC WS safety controller Ethernet interface module CPU module A generic term for the WSO CPU0 and WS0 CPU1 Safety I O module A generic term for the WSO XTIO and WSO XTDI Ethernet interface module Another name for the WS0 GETH Network module A generic term for the WSO GETH and WS0 GCC1 Q series programmable controller The abbreviation for the Mitsubishi MELSEC Q series programmable controller QJ71E71 100 The abbreviation for the MELSEC QJ71E71 100 Ethernet module Built in Ethernet port QCPU A generic term for the QO3UDEHCPU QO4UDEHCPU QO6UDEHCPU Q10UDEHCPU Q13UDEHCPU Q20U
123. safety controller Depending on your current user level you will be prompted to log on as Administrator to be able to transfer a configuration For details please see the Safety Controller Setting and Monitoring Tool Operating Manual Once the transfer has been completed you will be asked whether you want to run the CPU module Depending on your choice click Yes or No to leave the dialog You can also start and stop the application in the Hardware configuration view using the Run application or Stop application buttons while the project is online More information can be found in the Safety Controller Setting and Monitoring Tool Operating Manual Ethernet interface module MELSEC WS Note 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 If the user confirms that they are correct the safety controller is considered to be verified In the Hardware configuration view click the icon Upload and verify configuration and compare the configuration The Upload and verify result window is opened Click Yes below at the question Set device to verified if the displayed configuration is the expected configuration The safety controller is then considered to be ver
124. set Active e When connection is opened by the WSO GETH set Unpassive Table 36 Configuration value Configuration value PLC parameter Open Active Unpassive settings Protocol Open system Socket communication TCP connection Host station port No 9100 238Cy Transmission target device IP 192 168 250 250 address Transmission target device 9100 238Cy port No hex 109 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 WO 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 M device D device Open execution DO SOCOPEN instruction abnormal completion error code SOCOPEN instruction success device D1 SOCSND instruction abnormal completion error code SOCOPEN instruction failure device D2 SOCRCYV instruction abnormal completion error code SOCOPEN instruction normal completion D3 SOCCLOSE instruction abnormal completion error code SOCOPEN instruction abnormal completion D300 to D309 SOCOPEN instruction control data Send execution D400 and D401 SOCSND instruction control data SOCSND instru
125. set 2 CRC Byte 2 W20 Byte 2 Byte 1 Byte 3 W21 Byte 4 lt Byte 3 Byte 4 v ut data set 3 module status CPU 0 Byte 1 Byte 3 lt p Byte 4 W30 Byte 2 Byte 1 Byte 2 Byte 1 Byte 2 W31 Byte 4 lt Byte 3 Byte 3 Byte 4 VO 1 Byte 3 lt gt Byte 4 W32 Byte 2 Byte 1 Byte 1 Byte 2 W33 Byte 4 lt P Byte 3 CPU 0 VO 1 Network 13 Byte 3 lt gt Byte 4 W4A Byte 2 Byte 1 Byte 1 Byte 2 W4B Byte 4 Byte 3 103 Procedures before operation MELSEC WS The WSO0 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 The byte order of the receive data is changed and input data sets are stored to the corresponding input data set storage areas WO to W4D refer to 2 in Figure 61 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped Note that the byte order of the input data set 1 and output data set 1 does not need to be changed because these data are one byte long lt Data need to be swapped gt Command and parameters word data 16 bits Input data sets 2 and 3 double word data 3
126. t 3 reading D705 00004 Read data specification Input data set 4 not reading 1 Since the QJ71E71 100 treats application data in Little Endian format the byte order needs to be swapped Since the QSCPU does not support the SWAP instruction the upper and lower bytes are swapped in the following way 1 Store the swap target data into the areas M1000 to M1015 2 Move the lower byte data in the areas M1000 to M1007 to the other areas M1016 to M1023 3 Return the data in the areas M1008 to M1023 to the original device 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 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 WSO GETH and the QJ71E71 100 Write target data Output data sets 1 to 5 In the sample program bit 0 of Byte O bit 1 of Byte 1 bit 2 of Byte 2 and bit 3 of Byte 3 in output data set 1 are set to Active High 1 Parameter configuration a Configuration required for the WS0 GETH Refer to Section 8 2 2 1 b Configuration required for the QJ71E71 100 Refer
127. t lightly in the direction of the arrow 3 Ifthere are several modules slide the modules together individually in the direction of the arrow until the side plug connection latches in Install the end clips on the right and left The following steps are necessary after mounting Complete the electrical connections See Section 3 3 Configuration See Section 3 4 and the Safety Controller Setting and Monitoring Tool Operating Manual Checking the installation see the Safety Controller User s Manual 18 MELSEC WS Ethernet interface module 3 2 2 Steps for dismantling the modules Figure 4 Disconnecting the plug connections Disconnect the cables and remove the end clips Ilfthere are several modules slide the modules away from each other individually in the direction of the arrow until the side plug connection is separated Figure 5 p Removing modules from the DIN rail Press the module downwards at the rear 1 and remove it from the DIN rail in the direction of the arrow while keeping it pressed down 2 19 Ethernet interface module MELSEC WS ATTENTION Note 3 3 Electrical installation Switch the entire machine system off line The system could start up unexpectedly while you are connecting the devices The Ethernet interface module fulfills the EMC requirements in accordance with the basic specification EN 61000 6 2 for industrial use To ens
128. t port QCPU can send data e g device state or other information of external devices to the MELSEC WS safety controller over Ethernet The send data can be used as input data for a function block in the logic editor of Setting and Monitoring Tool Figure 28 Sending data to the MELSEC WS safety controller WS0 GETH QJ71E71 100 lt MELSEC Q series programmable controller gt lt MELSEC WS safety controller gt Setting and Monitoring Tool Logic editor In Out Summary Page Page 1 7 2 Applicable system For configurations of MELSEC programmable controller systems refer to the following QnUCPU User s Manual Communication via Built in Ethernet Port Q Corresponding Ethernet Interface Module User s Manual Basic 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 WSO0 GETH and the QJ71E71 100 Procedure before operation Figure 29 Procedure before operation communications with the QJ71E71 100 QJ71E71 100 Connect the WS0 GETH to the MELSEC WS Mount the QJ71E71 100 on the base unit CPU module Connect an Ethernet cable Connect an Ethernet cable Configure network Configure configuration parameters for Ethernet data with Setting and with GX Developer Monitoring Tool
129. t s response message Data set 1 WORD 0 _ Data set not returned in data set s data field length Non zero Length of data set Data set 2 WORD 0 _ Data set not returned in data set s data field length Non zero Length of data set Data set 3 WORD 0 Data set not returned in data set s data field length Non zero Length of data set Data set 4 WORD 0 Data set not returned in data set s data field length Non zero Length of data set Data set s Array of Data set s information data bytes Output data set writing The following command message is sent by the application to the Ethernet interface module to write to the output data sets Parameter Length Value Command WORD 00F2H Set output data set s command message Output data WORD 0 Output data set not included in data set s data field set 1 length Non zero Length of data set 10 bytes Output data WORD 0 Output data set not included in data set s data field set 2 length Non zero Length of data set 10 bytes Output data WORD 0 Output data set not included in data set s data field set 3 length Non zero Length of data set 10 bytes Output data WORD 0 Output data set not included in data set s data field set 4 length Non zero Length of data set 10 bytes Output data WORD 0 Output data set not included in data set s data field set 5 length Non zero Length of data set 10 bytes Data set s Array of Data set s information
130. tected Another device on the network has the same IP address Minimum one Ethernet connection needs to be established Set up Ethernet connection on programmable controller side check Ethernet cabling check Ethernet connection settings on programmable controller and in the Setting and Monitoring Tool If no Ethernet communication is required disable the Ethernet connections PLC interfaces on the WSO0 GETH Adjust IP address and power cycle device WSO GETH does not supply any data LED PWR Green LED LINK ACT Green LED MS Red 1 Hz Configuration required Configuration download is not completed Configure the WSO GETH and download the configuration to the safety controller Wait until the configuration download has been completed WSO GETH does not supply any data LED PWR Green LED LINK ACT Green LED MS Green No data set is activated No Ethernet communication interface is enabled Activate at least one data set for communication in auto update mode WSO GETH does not supply any data LED PWR Green LED LINK ACT Green LED MS Green 1Hz WS0 GETH is in Idle mode CPU application is stopped Start CPU change into Run mode 59 Troubleshooting MELSEC WS Error Cause Possible remedy WSO0 GETH functioned correctly WSO GETH is operated in slave Either assign a fixed IP address to the after configuration but suddenly mode
131. th the communication target module Data cannot be normally exchanged Check the status of the CPU module connected to the WSO GETH s the CPU module operating normally Eliminate the error referring to the Safety Controller User s Manual YES Check the status of the PWR LED on the WS0 GETH Is the PWR LED on Check if power is supplied to the CPU module Remove the WSO GETH mount it again and then restart the system YES Off Remove the WSO GETH mount it again and then restart the system Check the status of the MS LED If the LED remains off even after restarting the module may have failed on the WSO GETH Flashing in red 1Hz If the configuration data has not yet transferred transfer it If the configuration data is being transferred wait for the completion Is the MS LED on i y greens Flashing in red 2Hz Restart the system If the LED flashes even after restarting the module may have failed YES On in red Another module in the system may have a critical error Search for the error module with Setting and Monitoring Tool and eliminate the error Flashing in red and green Check if either the QJ71E71 100 or the WSO GETH has been configured as a master module Check if the parameter configuration such as an IP address is correct Check the network totally including the communication path between Check the status of the LINK ACT the WS0 GETH and the QJ71
132. the network will be referred to as output data Do not operate an Ethernet interface module on a safety fieldbus The Ethernet interface module is not suitable for operation on a safety fieldbus It does not support any safety mechanism which would be mandatory to communicate within a safety network Configuration of the Ethernet interface module is performed using the Setting and Monitoring Tool on a PC or notebook connected to the CPU module over RS 232 interface or connected to the Ethernet interface module over Ethernet TCP IP Configuration data can be exported imported and saved The safety relevant logic of the MELSEC WS safety controller operates independently from the Ethernet interface module If however the MELSEC WS safety controller has been configured to integrate non safe information from the fieldbus into the logic editor a decoupling of the Ethernet interface module can result in availability problems An Ethernet interface module can only be operated on a MELSEC WS safety controller It does not have a dedicated voltage supply It is possible to use two network modules per system The Ethernet interface module is fitted in a 22 5 mm wide housing for 35 mm rails in accordance with EN 60715 42 MELSEC WS Table 14 Description of input data sets 1 to 4 43 Data sets 4 1 Data transmitted into the network network input data sets Available data The Ethernet interface module can provide the following data
133. tocol Open system TCP connection portal dava pinches eae z The TCP connection setting differs depending on the connection open status e When connection is opened by the Built in Ethernet port QCPU set Active e When connection is opened by the WSO GETH set Unpassive Table 42 Configuration value Configuration value PLC parameter Open Active Unpassive settings Protocol Open system Socket communication oman connection Host station Host station port No No 9100 238Cy Transmission target device IP 192 168 250 250 address Transmission target device 9100 238C port No hex H 117 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 WO 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 M device D device Receive execution D2 SOCRCYV instruction failure error code SOCRCYV instruction success device D500 and D501 SOCRCYV instruction control data SOCRCYV instruction failure device D520 Response command check device SOCRCYV instruction normal completion D900 to D976 SOCRCYV instr
134. ty controller and PC Connect a PC or notebook to the RS 232 interface of the CPU module Power on the MELSEC WS safety controller Open the Setting and Monitoring Tool installed on the PC Click on Com settings to ensure the correct communication interface has been selected The following dialog appears UUU 20 MELSEC WS Figure 6 Connection settings dialog Figure 7 Modify profile dialog 21 Ethernet interface module Connection settings Network settings ES Add COM profile Gy Add TCP IP profile Check all profiles Active connection P Standard Go Setis port Indeterminate connection state To configure the connection please proceed as follows Choose connection type D o Check connection y Port COM auto detection Activate profile Baud rate Auto scan Connection is not stored in project file Press this button if you want to save the profile to the project file Edit profile a a Serial COM auto detection a a a Cancel gt To edit the settings click on the pencil icon to the right The following dialog appears Modify profile Entry name Standard Serial port o e COM auto detection Auto scan Cancel gt Modify the settings if required Click OK The dialog closes Click on Connect The Setting and Monitoring Tool will search for connected MELSEC WS safety controller and load the hardware configuration into the
135. uct s manufacture the Products 10 subjected to excessive heat or moisture abnormal Repairs of Products located outside of Japan are voltages shock excessive vibration physical accepted by MELCO s local authorized service facility damage or other improper environment or centers FA Centers Terms and conditions on 11 damaged or malfunctioning due to Acts of God which each FA Center offers repair services for fires acts of vandals criminals or terrorists Products that are out of warranty or not covered by communication or power failures or any other MELCO s limited warranty may vary cause or failure that results from circumstances Subject to availability of spare parts MELCO will offer beyond MELCO s control Product repair services for 4 years after each f All Product information and specifications contained Product model or line is discontinued at MELCO s or on MELCO s website and in catalogs manuals or its FA Centers rates and charges and standard terms technical information materials provided by MELCO in effect at the time of repair MELCO usually are subject to change without prior notice produces and retains sufficient spare parts for repairs g The Product information and statements contained on MELCO s website and in catalogs manuals technical bulletins or other materials provided by MELCO are provided as a guide for Customer s use They do not constitute warranties and are not incorporated in the contract of sale f
136. uction receive data area SOCRCYV instruction abnormal completion Response command verification normal completion Data size error device C device SOCRCV instruction Number of executions Number of successes Number of failures Verification check Number of successes Number of failures 1 C device is used to check the operation of the communication program Note Ifthe Built in Ethernet port QCPU stops during communications in auto update mode the SOCRCYV instruction will not be executed even when data are transmitted from the WSO GETH This may cause the receive buffer of the Built in Ethernet port QCPU to overflow and data transmission of the WSO GETH to stop ifthe scan time of the Built in Ethernet port QCPU is longer than the transmission interval of the WSO GETH update of received data delays For this reason configure the auto update interval much longer than the scan time 118 MELSEC WS Procedures before operation 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 BUFRCYV instructions with the SOCSND and SOCRCYV instructions Since the Built in Ethernet port QCPU treats application data in Little Endian format the byte order needs to be swapped Note that the byte order of the input data set 1 and output data set 1 does not need to be changed because th
137. ufacturing whichever is less The onerous repair term after discontinuation of production shall be for four 4 years Mitsubishi shall mainly replace the product that needs a repair it may take some time to respond to the problem or repair the product depending on the condition and timing lt Specifications gt General specifications of the products differ MELSECWS MELSEC Q MELSEC QS Operating ambient temperature Operating ambient et 10 to 95 RH 5 to 95 RH 5 to 95 RH humidity 25 to 55 C 0 to 55 C 0 to 55 C Storage ambient 25 to 70 C 25 to 75 C 40 to 75 C temperature Storage ambient si 10 to 95 RH 5 to 95 RH 5 to 95 RH humidity 1 When the WS0 GCC100202 is included in the system operating ambient temperature will be O to 55 C EMC standards that are applicable to the products differ MELSEC Q EMC standards EN61000 6 2 EN55011 EN61131 2 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 For the safety precautions of the MELSEC WS safety controller system refer to the user s manual for the CPU module used In this manual the safety preca
138. ult 0 1 Result 0 0 EFI 2 input Ge0oogeaogcs Input Output Update interval ms Machine Operator I offline A Setting and Monitoring Tool configuration is not verified Editing output data sets for writing Open the Ethernet to CPU dialog and configure tag names for each output data set as required Safety Controller Setting and Monitoring Tool 1 3 0 New project GGEG0880 a Geaceeaso w BEEGe080 oo BBE00880 w BEEG8000 oy SBauqgeagcs Setting and Monitoring Tool configuration is not verified 78 MELSEC WS Table 27 Network parameter configuration for Ethernet Figure 44 Network parameter Operational settings 79 Procedures before operation 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 Option Configuration value Network type Ethernet Starting I O No 0000 Network No 1 Group No 1 Station No 2 2 Network parameter Operational settings for reading writing Click the Operational settings button to
139. ult restores the default routing configuration You will be prompted for confirmation If you click Yes all previously made changes that have not been saved will be lost You can not undo this action Clear all clears the configuration i e deletes all assigned bytes in the Network Module Data area You will be prompted for confirmation Delete routing deletes the selected byte from the Network Module Data area The Undo and Redo buttons allow you to undo or redo changes you made to your configuration 52 MELSEC WS 53 Note Data sets 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 The Input types view contains the input values for the connected MELSEC WS modules and EFI devices If your MELSEC WS safety controller contains a second network module the input data of this network module i e data received from the network the second network module is connected to will be available here as well The Output view offers the output values for the connected MELSEC WS modules and EFI devices as well as the Logic results from the logic editor All sources supported by the current configuration are displayed in black connected MELSEC WS modules connected EFI devices configured logic results input data
140. update mode Byte values Part of message Meanin hex g g 00 2E Command Auto update data sets see Table 12 00 32 Length of data set 1 50 bytes 00 20 Command Length of data set 2 32 bytes 00 3C parameters Length of data set 3 60 bytes 00 3C Length of data set 4 60 bytes 03 FF 03 03 Logic results 0 3 co Input values module 1 CO 11000000 Inputs 18 and I7 Active 03 Input values module 2 03 00000011 Inputs I2 and 11 Active 3F 05 05 05 00 00 Input values module 3 12 00 00 00 00 Data set 1 default byte 00 00 00 00 assignments see 00 00 00 00 Output values module 1 12 Table 15 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Not assigned 00 00 00 00 00 00 00 00 00 00 Ethernet interface module MELSEC WS Byte values hex Part of message Meaning 52 A1 10 4C 52 A1 10 4C 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 2 see Table 15 Overall CRC same as system CRC System CRC Reserved FF FF FF FF FF FF FF FF FD FB FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Data set 3 see Table 15 and Table 16 Data set 3 data is transferred in Big Endian format i e in 32 bit double word format wit
141. uration for polling mode Safety Controller Setting and Monitoring Tool 1 3 0 New project v CPU to Listen to Ethernet T Ethernet to CPU Port Enable COS update Enable auto update and COS Update rate ms Update Dataset 1 Update Dataset 2 Update Dataset 3 Update Dataset 4 192 168 250 250 9100 Machine Operator 1 Offline Setting and Monitoring Tool configuration is not verifie 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 If you have selected Enable auto update and COS select the Update rate in ms Configurable range 40 to 65535 Select which data sets shall be updated Check the Update Dataset n checkbox Ethernet interface module writes to Address Port Auto update mode The Ethernet interface module can be configured to automatically update the data set information i e the application does not need to send any request messages as it would do in polling mode once the connection to the application has been made The configuration settings are available via the Setting and Monitoring Tool or via the TCP IP interface itself Using one interface does not disable the other The auto update mode could be enabled via Setting and Monitoring Tool and disabled via
142. ure full electromagnetic compatibility EMC the mounting rail has to be connected to functional earth FE The control cabinet or assembly casing of the MELSEC WS safety controller must comply at least with enclosure rating IP 54 Mount the modules in accordance with EN 50274 Electrical installation in accordance with EN 60204 1 The voltage supply of the devices must be capable of buffering brief mains voltage failures of 20 ms as specified in EN 60204 1 The voltage supply has to fulfill the regulations for extra low voltages with safe separation SELV PELV in accordance with EN 60664 and DIN 50178 equipment of electrical power installation with electronic devices Ensure that all the modules of the MELSEC WS safety controller the connected protective devices as well as the voltage supplies are connected with the same earth GND The GND of the RS 232 interface is connected internally to the GND of the supply of the CPU module A2 Connect all fieldbus and Ethernet cable shields directly at the control cabinet entrance to the functional earth FE 3 4 First configuration steps This chapter describes the basic steps you have to perform for the configuration of the Ethernet interface module Establish a first connection between the MELSEC WS safety controller and a PC or notebook Upload or transfer of a configuration Verification of a configuration 3 4 1 Establishing a connection between MELSEC WS safe
143. ures before operation 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 Device F EDC mase 7654 3210 wo oooodo oooo oooo oool 000l Wl ooo0oo0 oooo oooo oo0oo 0000 Device 7 EDC Hage 7654 4220 wzo oOli1iil o0o0o0 oool 001l 47897013 wWZl 0100 oli1il loll lool Device F EDC mass 47654 3Z10 w30 Loi ai amp liill liill liliil FFFF W31 Ld dk liill liill pe ae oe FFFF Reference When the CPU module is in the STOP state the value will be FFFF FFFE Example of network module 13 status input data set 3 Input status Inactive Low Device F EDC mase 47654 zio WAA l 1 11 Ilil 1 10 1 oe oe ee FFDF W4B liill liill liill ne oe eae FFFF Reference The input status becomes Active High after a write command is executed to the WS0 GETH 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 t
144. utions are classified into two levels A WARNING and A CAUTION I Indicates that incorrect handling may cause hazardous conditions l N WARNING resulting in death or severe injury l f ba l Indicates that incorrect handling may cause hazardous conditions A CAUTION resulting in minor or moderate injury or property damage J Under some circumstances failure to observe the precautions given under N CAUTION may lead to serious consequences Observe the precautions of both levels because they are important for personal and system safety Make sure that the end users read this manual and then keep the manual in a safe place for future reference Design Precautions NWARNING The Ethernet interface module is not suitable for operation on a safety fieldbus The Ethernet interface module only generates non safety related fieldbus data status bytes for control and diagnostics purposes Do not use non safe data from an Ethernet interface module for safety related applications With the Ethernet interface module it is possible to integrate non safe data into the logic editor such that the safety function of the MELSEC WS safety controller is compromised Never implement the Ethernet interface module into a MELSEC WS safety controller without having this danger checked by a safety specialist CAUTION Do not install the control lines or communication cables together with the
145. vate the Enable COS update radio button 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 Operational settings Click the Operational settings button to open the configuration dialog and configure the options as follows Figure 58 Network parameter Operational settings Ethernet operations _ Sse ee 100 MELSEC WS Figure 59 Network parameter Open settings Table 34 Network parameter Open settings Figure 60 Network parameter Initial settings 101 Procedures before operation 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 Port No input format HEX X Fixed buffer Transmission Transmission Pairing Existence Host station i 5 Protocol Open system Fixed buffer communication target device IP target device procedure opon confirmation Port No address Port No v Unpassive v Receive No procedure Disable Confirm Configuration value Active Configuration value Option Unpassive Protocol TCP

Safety Controller Ethernet Interface Module User`s Manual

Contents

Download Pdf Manuals

Related Search

Related Contents