Omron Explicit messaging over Ethernet Socket between Mitsubishi Q and CIP Safety CPU Quick start guide

Omron
Brand
Omron
Model
Explicit messaging over Ethernet Socket between Mitsubishi Q and CIP Safety CPU
Type
Quick start guide

This manual is also suitable for

Mitsubishi Q series Controller
To Omron NX-CSG320 + NX-SL5700
Explicit Messaging over Ethernet Socket
Quickstart Guide
Version 1.0
11/28/2018
Section 1: Introduction
This document will allow the user to setup an Explicit Messaging Connection using Ethernet
socket between a Mitsubishi Q series PLC and an Omron NX-SL5700 safety CPU, through an
NX-CSG320 communications gateway.
In this configuration, the NX-SL5700 is performing the machine safety functions, incorporating
devices such as door switches, safety area scanners, ESTOP buttons, force guided relays,
remote safety IO blocks, robots with CIP Safety capabilities, and other safety components.
The PLC is performing only non-safety functions such as the monitoring of the safety devices for
annunciation on an HMI.
In order to establish the Explicit Messaging Connection, Tags in NX-SL5700 CPU need to be
exposed to EtherNet/IP, then the Q series PLC send EtherNet/IP Explicit Messages using the
Ethernet Socket Interface to read and write the data of Tags that are exposed.
This Explicit Messaging Connection will share:
• 2 boolean data points from the Q series PLC through the NX-CSG320 to the NX-SL5700
• 6 boolean data points from the NX-SL5700 through the NX-CSG320 to the Q series PLC
• IO Module status from local NX Safety IO from the NX-CSG320 to the Q series PLC.
Note: the names of the NX-SL5700 and NX-CSG320 as shown in Sysmac Studio have been
changed from the default for clarity.
Section 2: Mapping data from the NX-SL5700 to the NX-CSG320
Mapping data from the NX-SL5700 to the NX-CSG320 is used when internal values from the
safety program need to be exposed on EtherNet/IP, such as the state of Function Block, as
shown below. In this example ESTOP_1_Monitor only turns on when the ESTOP button is not
pressed in, and the RESET_IN signal has been applied to reset the Emergency Stop function
block.
1. In Sysmac Studio, create the 8 Global Variables in the NX-SL5700 Safety CPU. 2 are
‘Input’ and 6 are ‘Output’ in the Expose Column. The 6 outputs are intended to show
the monitoring of internal safety status in the safety CPU, and the 2 inputs are non-safe
auxiliary inputs from the PLC, used for non-safety functions such as auxiliary lamps.
Section 3: Mapping data from the NX-CSG320 to EtherNet/IP
1. At the top of the Multiview Explorer, select the Communications Gateway device, and
then double click IO Map.
2. On the IO Map, enter variable names in the NX-CSG320 that match the names shown
on the left in the NX-SL5700. It is not required that the names match, but for ease of
programming, it is recommended that they do match. This step connects the Tags it the
NX-SL5700 Safety CPU to Tags in the NX-CSG320 gateway.
3. To map the logical values (on/off state) and status of local NX Safety IO located on the
IO bus local to the NX-CSG320 and NX-SL5700, add variables to the IO Map for NX
safety modules as shown.
4. Double click Global Variables.
5. In the Global Variables, change the Network Publish to Output for the Door, Scanner,
ESTOP, Logical Values and IO Status tags, and Input for the Lamp control Tags. This
makes the Tags available to be used in an EtherNet/IP connection.
6. To begin the EtherNet/IP setup, select Tools, EtherNet/IP Connection Settings.
7. Double click on the top port (Built-in EtherNet/IP Port Settings – Port 1).
8. Click Registration All to import the Global Variables into the EtherNet/IP configuration.
9. Click Register. This creates a Tag Set (assembly) for each Tag. In steps 10 through
12, the individual Input Tag Sets will be consolidated into a single Tag set.
10. Select and Delete Tag Set Lamp_2_Control, leaving only 1 Tag Set (Lamp_1_Control).
11. Right click Lamp_1_Control and select Create New Tag.
12. Type ‘L’ to activate the drop down list of all tags beginning with ‘L’ and select
Lamp_2_Control.
13. Click twice slowly on the Tag Set Name Lamp_1_Control, and rename it ‘Inputs’. Note:
this is not a necessary step, but is done to distinguish Tags and Tag Set names.
14. On the Inputs Tag Set, click ‘Auto’ in the Instance ID column, and change it to 110. This
sets assembly 110 as the Input assembly.
15. Select the Output tab.
16. Repeat steps 10 – 12 for the Output Tag Sets, deleting Tag Sets Door_2_Monitor,
Scanner_1_Monitor, Scanner_2_Monitor, ESTOP_1_Monitor, and ESTOP_2_Monitor.
Add those Tags back to the Door_1_Monitor Tag Set.
17. Click twice slowly on the Tag Set Name Door_1_Monitor, and rename it ‘Outputs’. Note:
this is not a necessary step, but is done to distinguish Tags and Tag Set names.
18. On the Outputs Tag Set, click ‘Auto’ in the Instance ID column, and change it to 100.
This sets assembly 100 as the Output assembly.
19. Double click Built-in EtherNet/IP Port Settings.
20. Set the IP address of Port1. This document uses the default IP address.
21. Select Use for TCP/UDP Message Service Settings.
22. Synchronize all the changes made in section 3 to the NX-CSG320. Make certain that
‘Do not Transfer the EtherNet/IP connection settings…’ is not selected.
23. At the top of the Multiview Explorer, select the NX_SL5700 device.
24. Download the Safety configuration and program by putting the NX-SL5700 into Stop
Mode, followed by Debug Mode, and then performing a Safety Validation and putting it
back into Run mode.
Section 4: Q series PLC Ethernet Port Configuration
1. Open an existing project file or create a new project file for the Q series PLC in GX
Works2.
2. Double click Parameter – PLC parameter.
3. Select the Built-in Ethernet Port Setting. Configure the IP address of the Q series PLC
as 192.168.1.39 (as an example IP Address).
4. Click Open Setting.
5. Set the following Value.
Item
Set Value
Protocol
TCP
Open System
Socket communication
TCP connection
Active
Host Station port number
64000 (Any value)
Destination
IP address
192.168.1. 1 (Must match with the IP address of the NX-CSG)
Destination
Port number
64000 (Must match with the Port number of the NX-CSG)
Section 5: Q series PLC Ladder Program
Create the ladder program of the socket communication to execute the following functions.
• Open the Socket
• Read data from NX-CSG/NX-SL
• Write data to NX-CSG/NX-SL
1. Open the Socket
2. Read Data from NX-CSG/NX-SL
Set the data size of the sending command.
Address
Set Value (Hex)
Meaning
D1020
0E
Data size:14 bytes. (Send data = D1021 – D1027, 14 bytes)
Fixed value. No need to change.
Set the Sending Command.
Address
Set Value (Hex)
Meaning
D1021
1001
Sequence Number.
Any value. 1001 as an example.
D1022
0
Reserved
D1023
8
Data size:8 bytes (Data:D1024 – D1027, 8 bytes)
Fixed value. No need to change.
D1024
0E00
Service Code.
Fixed value. No need to change
D1025
4
Class ID.
Fixed value. No need to change
D1026
64
Instance ID. (100 in decimal)
Need to be matched as the value that set in the output tag of
NX-CSG EtherNet/IP setting.
D1027
3
Attribute ID.
Fixed value. No need to change.
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25

Omron Explicit messaging over Ethernet Socket between Mitsubishi Q and CIP Safety CPU Quick start guide

Omron
Brand
Omron
Model
Explicit messaging over Ethernet Socket between Mitsubishi Q and CIP Safety CPU
Type
Quick start guide
This manual is also suitable for
Download PDF
report

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI

Related papers

Other documents