- IO-Link is a standardized protocol that enables easy connection of field devices such as sensors and actuators to a controller like a PLC.
An IO-Link Master connects point-to-point to one or more intelligent field devices while connecting to the controller via a fieldbus connection such as Ethernet IP. The IO-Link master relays commands and status information between the controller
and the field devices but in addition provides the controller with detailed status and diagnostic information not available with conventional field connections.
In this video series, AutomationDirect will demonstrate the use of an IO-Link network to connect a Productivity 2000 PLC to two representative field devices, using methods and resources that can be adapted to users' needs for implementation in their projects.
Setting IP address on Stride IO-Link Master: https://www.automationdirect.com/videos/video?videoToPlay=TH930JnxtZk?utm_source=M5o6bcOJXnU&utm_medium=VideoTeamDescription
Online Support Page: https://community.automationdirect.com/s/contactsupport?utm_source=M5o6bcOJXnU&utm_medium=VideoTeamComment
**Please check our website for our most up-to-date product pricing and availability.
Welcome to Part 2 of AutomationDirect’s series on setting up IO-Link communications with a Productivity PLC. The previous video provided an overview of the demonstration. Click here for that video. Open the latest version of the Productivity Suite software and Start a New Project. In this demonstration, we’ll be featuring a P2-622 CPU mounted in a 4-slot chassis. To build this program, let's incorporate some pre-made tasks from the Task Library we downloaded in the first video. Start by pulling in the Task Library itself. In the Task Management window on the left side of the screen, find Task Library and right click. Select Import Group. Navigate to the unzipped PSuite Integration Stride Murr IOL folder. Select the library AutomationDirect IO-Link.adtkl. You’ll now see a number of tasks have populated your task library. At the top of that list, under the AutomationDirect IO-Link folder, find tasks IO-Link Data Mapping and Call Device Code. Drag each of these into the Run Every Scan folder under Tasks. A dialogue box will let you know the program has created all the tags required by each task. Click OK for each. The rest of these tasks are device specific, and as mentioned, for this demonstration we’ll be using 2 devices, the Werma eSign stacklight and the Wenglor OPT2133 photoeye sensor. Drag the tasks for each of these devices, Werma eSign and Wenglor OPT2133 through 2140, into the Run When Called folder. Let’s look at the Call Device Code task we just dropped into the Run Every Scan folder. We’ll need to tailor the code here to the specific devices we’ll be talking to. As downloaded, the task is set up for use with a Murrelektronik DIO Hub. We’ll change this, but before we do let's break down what is happening in the code. In the first instruction, data from a Source structure tag DIO Hub is copied to a Destination structure CALL Murr MVP. The Tag DIO Hub is what we’ll call a “program instance” of the CALL device structure, meaning that this is the copy or instance of the data that our program will monitor and manipulate. The CALL Murr MVP structure we’ll call a “working instance” of the structure that will be used more in the background, interacting with other structures that exchange data with our field devices, for example. This program instance of the CALL structure for each field device is the only tag you’ll need to create – we’ll come back to that. The second instruction copies data from a port-specified Source tag IO-Link Master.Port to a Destination tag CALL Murr MVP.IO-Link, used by the device-specific Murr DIO Hub task when it is called. In this instance, the DIO hub is intended to be connected to the IO-Link Master’s first port, referred to in the program as Port 1. When you are using different ports, you will need to change the reference here. Depending on the IO-Link Master in your system, the port numbering scheme may start at 1 or 0. On both the Stride basic and the Murrelektronik premium IO-Link Masters, the first port is labeled 0. This is something to watch out for. In the base program, we are calling out Port 1, but physically connecting to a port labeled X0. The third instruction calls the device task where the data loaded into the working structures in the first two instructions is exchanged with data from other structures being communicated back and forth with the IO-Link Master through the Ethernet IP process. The fourth and fifth instruction boxes are mirror images of the first two. Now data in the working structures is copied into the program structures for monitoring and use by your project. As mentioned, we’ll need to create a “Program” structure tag for each of the two field devices in this project. Open the Tag Database and select Add Tags. Let's call the first new tag Stacklight for the Werma eSign. Select User Structure. In the list that populates, select Werma eSign. Click Add and make a Photoeye tag the same way. Enter Tag Name Photoeye and select the Wenglor OPT2133 through 2140 device. Add and Close. All of our tags are now in place. In the Call Device Code task, we’ll finish the ladder setup. In each of the 5 instruction boxes, make the changes specific to our devices as shown. Since we are adding a 2nd device, make a copy of this whole rung and paste it right below the original. Modify this rung for our photo eye. Keep in mind this device will be connected to the second port of the IO-Link Master. Our ladder is now all set up. In the next video, we’ll set up the Ethernet IP side of things and put the whole thing together. Click here for Video 3. Click here to check out AutomationDirect’s range of IO-Link capable products.