- 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.
Online Support Page: https://community.automationdirect.com/s/contactsupport?utm_source=LyeiXX8WZz8&utm_medium=VideoTeamComment
**Please check our website for our most up-to-date product pricing and availability.
Welcome to Part 3 of AutomationDirect’s series on setting up a Productivity PLC with IO-Link communication. In the previous videos we looked at the system we’re setting up and got our Productivity project set up for the IO-Link interactions. Click here for the previous videos. The Productivity is going to be communicating with the IO-Link master via an Ethernet IP connection, so let’s set that up. In the Application Tools window on the left side of your screen, go to Hardware Config and select the Ethernet/IP tab. On the right side of that tab, you’ll see a list of Ethernet IP Clients for which your Productivity software is already set up. If you do not see a Stride IO-Link Basic entry, you’ll need to add it by clicking the Import EDS File button. A Select File to Import window will open. Navigate to the unzipped PSuite Integration folder from the first video and select Stride Basic EDS. You’ll see the Stride Basic IO-Link Master in your EIP list. Expand as needed to display the versions. Drag the latest version to the left side of the Window. Double-click to open the Properties. Check the Use Structure checkbox and drop down to select IO-Link Master.EIP_Device. In the Device Name field, enter “IO-Link Master". Note that the name must be exact to work with the code we’ve been setting up. Enter the IP address assigned to the IO-Link Master. Please refer to the IO-Link Master’s documentation or the STRIDE IO-Link Master Ethernet Network Quick Start video linked below for details on setting the IO-Link Master’s IP address. For this demonstration, we’ll be using 192.168.1.15. Whatever you use, keep in mind that it must be in the same subnet as the PLC it will be talking to. In this instance, we have the PLC set up to 192.168.1.12, and the PC is set to 192.168.1.2. Lastly, we need to define the Ethernet IP messages we’ll send back and forth. Click the Add Message button here and Add Exclusive Owner. In the Extended Status field, drop down and select IO-Link Master.EIP_Device_Extended_Status. In the Target to Originator tab Data Array field, select IO-Link Master.Cyclic_Input_Data In the Originator to Target tab Data Array field, select IO-Link Master.Cyclic_Output_Data The Config Data tab can be left as default. Click OK. If you haven’t done so, this would be a great time to save the project. Connect to your Productivity PLC. Download the project to it and let's check it out. Open a Data View window and enter our program structure tags, Photoeye and Stacklight. Expanding the Photoeye structure reveals the tags it contains. We’re most interested in the Output_A1 tag. As part of the structure Photoeye, its complete designation is Photoeye.Output_A1. This is the primary tag you’ll use in your ladder logic. When you have a good beam reflecting back to the Photosensor, Output_A1 will be true. When the beam is blocked, it will be false. Expanding the Stacklight structure, you can see that there are a lot more tags here, and these are the tags we will manipulate to send commands to our eSign. For a simple example, expand the Activate_Segment tag. Edit the Activate_Segment(1) tag to True and you’ll see that the bottom segment of your stacklight comes on. What that is going to look like depends on how the segment is configured. To find out more about all of that, check out the documentation for the eSign. Let’s look at an example of ladder code using some of these tags to make a very simple non-latching alarm function. We’ve made a new Run Every Scan Task called “Operation.” If Photoeye.Output_A1 is not true, we output a Warning bit and start a 3-second timer. If that timer reaches 3 seconds, we output an Alarm bit and not the Warning bit. If neither the Alarm nor Warning bits are true, we output Stacklight.Activate_Segment(1), lighting up the bottom tier of the stacklight which has been preconfigured in a green color. If the Warning is true, we output Stacklight.Activate_Segment(2), lighting up the middle section in yellow. If the Alarm is true, we output Stacklight.Activate_Segment(3), lighting up the top section in a flashing red - also sounding the siren with Stacklight.Activate_Siren(8). There are a few steps involved, but as you can see, using IO-Link is very easy with AutomationDirect’s Productivity line of PLCs. We hope this has given you some ideas for your next PLC project. Click here to check out AutomationDirect's range of IO-Link-capable products.