0:08
Hello and welcome to today’s webinar.
0:12
In this webinar we will look at Valve Control using Horner’s Ethernet IP Scanner.
0:18
Here is the agenda for today.
0:20
First we will start with a quick review of Ethernet IP.
0:24
Then we will discuss which Horner products support Ethernet IP Scanner functionality.
0:30
Then, we will look at the Festo Valve Manifold that we will be using in today’s webinar, there will be demonstrations throughout, and we will finish with a Q &A session at the end.
0:41
Let’s begin.
0:42
Ethernet IP is one of the leading industrial protocols in the United States, and is widely used in a range of industries.
0:50
While most often associated with the American Automation Control Company, Rockwell, Allen Bradley, EtherNet IP is an open protocol, based on a much older protocol named ODVA.
1:02
There are two common device types with EtherNet IP, the I.O.
1:05
Scanner, which is the PLC that controls the network, and the I.O.
1:09
Adapters, which include any automation devices controlled over the network.
1:14
Wat Horner controllers support EtherNet IP Scanner functionality.
1:18
This functionality comes standard in the Canvas series controllers and the CPU 300.
1:24
It simply requires CScape version 10.2 Service Pack 2 or later, with an extension code required for Service Pack 2 specifically.
1:34
This extension code is available through tech support.
1:37
Your controllers also require firmware version 17.4 or later.
1:42
In the XL Prime series, this comes as a licensed feature.
1:46
For a one-time upgrade fee, you can add this functionality to any of your XL Prime controllers.
1:51
You will also require Cscape 10 Surface Pack 3 or later and Controller Firmware 17.5 or later.
2:01
Next, for today’s demonstration we’ll be using this Festo VTUX Valve Manifold.
2:08
It’s designed to integrate pneumatic and electrical components such as valve manifolds and sensors into automation networks.
2:15
It’s perfect for today’s webinar as it uses an Ethernet-based AP backplane.
2:20
This real-time backplane supports high bandwidth and shorter cycle times.
2:27
This is the valve manifold we have chosen to use, but the workflow we showcased today should work with any valve manifold on the market today.
2:36
And that’s all of the preliminary information covered for today.
2:39
Let’s now move to Cscape and start on the demonstrations.
2:45
Here we are in Cscape 10, and to start, we’re going to show you how to connect a valve bank to Cscape 10.
2:52
First, navigate to Hardware Configuration.
2:55
Here we have the Canvas 7 controller that we will be using today, and we are going to set up our network on LAN 1, so we click on LAN 1.
3:05
If this is your first time setting up a network, you will need to configure the IP address and netmask fields here, but for the sake of this demonstration, we have already set this up.
3:17
With your network configured, navigate under Resident Protocols to Ethernet IP Scanner and check the box to enable it.
3:25
Then with it highlighted, click on Configure Selected Protocol.
3:29
Here we must assign a Disable variable, which will allow us to enable and disable the network.
3:35
We also need a Status variable, which will return information about the network.
3:40
Since these didn’t exist before, Cscape will automatically create these once we hit OK.
3:45
Next, we can start adding adapters.
3:48
And let’s begin with the most crucial one for today’s demonstration, the Valve Bank.
3:53
Right click on the Ethernet IP Scanner options, and click Add Adapter.
3:57
Here we can start configuring the Valve Bank.
4:00
First we assign a name, and we will go with Valve Bank.
4:04
Then we assign its IP address.
4:07
We are going to type in the exact value, but this can also be a variable if needed.
4:12
Then, connection timeout, this can be any value you want, but we have chosen 100 ms, which should work for most cases.
4:21
Finally, we need to assign a disable and a status variables.
4:26
We have not created these variables ahead of time, so we will type in their names here, and they will be created automatically once we close this menu.
4:34
With that complete, we are going to go back up in our list and add an EDS file.
4:39
Here we have some EDS files and we’re going to select the correct one for this the valve bank Cscape will ask us to confirm and we’ll click. Yes.
4:47
Now we have a new option Here under connections.
4:51
We have a drop-down list of different connections for this demonstration We will use the default configuration But any of these would be valid for different applications with that selected We have now done everything we need to to set up the valve bank from here we could navigate back to the previous menu and start adding any other adapters on our network.
5:14
However, to save time in this demonstration, we have already configured our network and all the devices on it.
5:20
Here we have our completed network, with all our devices connected.
5:24
Let’s take a look at the finished configuration for this Valve Bank.
5:28
As shown, we elected to use the default connection in the EDS file.
5:33
Then, when it comes to input, we selected integers as our data type.
5:38
These are the most convenient data type to use when working inside a Horner-controlled network.
5:44
The data length was automatically set to 8, and we set the RPI to 50ms, as that works best for our application.
5:54
Finally, we assigned a local variable array, to receive in all these input variables.
6:00
Our output tab looks identical. Once again, we chose integers as our data type, with a length of 8 and an RPI of 50, along with another variable array to store all these outputs.
6:16
Next, let’s look at the variable handling for the valve bank. Here we have the two variable arrays from the valve bank.
6:23
For this demonstration, we are only concerned with the output data, or the data that will control the valves.
6:31
By default, this variable has 8 words of data, which we have mapped to a single 8-word array variable.
6:39
Then, to work with individual variables inside this array, we’ve created boolean variables that are assigned to specific bits inside the array.
6:48
Here, we have the individual booleans that are each mapped to different bits within the data.
6:54
As you can see, we have done this by mapping each of them to the correct register number.
7:00
Our first bit in the big bank of data is mapped to OR 2101.1, and this controls the first valve.
7:09
Then, for the second valve, it actually requires two bits to control it correctly.
7:14
So we have mapped two individual bits at the correct locations.
7:19
This is how we handle variable data for the valve bank in Cscape 10.
7:24
Finally, let’s look at our ladder logic.
7:26
Here we have our first cylinder with only one bit and our second cylinder with two bits.
7:32
Cylinder 1 is connected to a cylinder with a spring return.
7:36
Turning on the first bit will cause it to extend and turning off the same bit will cause it to retract. The second bit is not used.
7:46
Then at the end we have our status variable which will return the current status of our cylinder.
7:53
Then we have cylinder 2 which requires both bits for control.
7:58
Turning on the first bit will cause it to extend and turning on the second bit will cause it to retract.
8:04
We also have two status variables here that will tell us the current status of our cylinder, and with that covered, let’s now move onto the bench and demonstrate how this works at runtime.
8:17
Here we are on the bench, and here on our screen is an image of our valve bank.
8:23
We have two valves, each with two bits.
8:26
Then over here, we have valve 1, which is connected to cylinder 1, and valve 2, which is connected to cylinder 2.
8:34
Valve1 features a spring return, so it only requires one bit to control.
8:40
Whereas for Valve2, we need to control both bits to manage extending and retracting the cylinder. So, let’s see if our configuration works.
8:49
We will press this button for Cylinder1, and as you can see, it has extended.
8:54
Here, we can see our status variable has turned green, and when we hit the button again, our cylinder will retract, and our status variable will return to being red.
9:06
Cylinder 1 is working as intended, and without any issues.
9:10
Now for cylinder 2, if we look over here, the status variables are currently telling us that it is retracted.
9:17
If we hit the extend button, you can see those bits swap, and if we then hit retract, it will return to its original state.
9:26
Cylinder 2 is also working as intended.
9:30
That is everything you need to know to set up valve control using Horner’s Ethernet IP scanner.
9:37
And that concludes our webinar for today.
9:40
Thank you so much for listening, and the Q &A session will begin shortly.
9:51
Okay, so we’ll have no webinar next week because we will be at SPS Italia, but we will be back the week after, so the registration links will be up for those.
10:02
I don’t see any questions in as yet but if you do have any feel free to get in contact with TechSports and we’ll help you out there.
10:09
Okay thank you all for joining us and we’ll see you next time.
