0:01
joining us on this webinar on Controlling Ethernet IP.
0:06
We’ll do the usual run of this.
0:07
Presentations are roughly about 16 minutes but at any point if you have a question just feel free to put it in and we’ll get to that in the end.
0:13
Hello and welcome to today’s webinar.
0:16
Today we will look at Controlling Ethernet IP with a Horner Controller.
0:21
Horner has supported Ethernet IP for a number of years but only as an I.O. adapter.
0:27
Today we will look at new functionality functionality coming to Horner controllers, which allows your controller to fully control a network of its own.
0:37
Let’s look at the agenda for today.
0:39
First, we will start with a review of Ethernet IP in general, then we will look at using the new Ethernet IP scanner functionality with a Horner controller, followed by the supported models.
0:52
There will be demonstrations throughout, and we will finish with a Q &A session.
0:57
What is Ethernet IP?
0:58
Ethernet IP is an industrial network protocol that adapts the common industrial protocol, or CIP, to Ethernet.
1:08
Ethernet IP is one of the leading industrial protocols and is widely used in a range of industries.
1:14
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:25
Ethernet-IP utilizes standard Ethernet components unlike EtherCAT and PROFINET-IRT.
1:33
It utilizes both TCP-IP and UDP elements of Ethernet.
1:39
Ethernet-IP is based on an object model.
1:42
In the diagram on the right, we can see the network device, or CIP node, represented as a series of objects.
1:50
The grey box represents the CIP with functions by using each object instance inside of it.
1:59
This object model is how Ethernet IP functions.
2:04
Now we are going to look at some of the key objects that are most often used.
2:09
First, Ethernet IP represents data using assembly objects.
2:14
Known as super objects, this object acts as a convenient package for transporting data between devices.
2:23
The input assembly moves data to the scanner or network controller, and the output assembly moves data away from the scanner or network controller.
2:34
Ethernet IP also tries to standardize device setup for easier communication.
2:39
Application objects are used to define data in the device, and they are specific to each device type and function.
2:48
All CIP devices of the same type must contain the same application-specific objects, which is where we use device profiles.
2:58
These contain a set of application-specific objects for a particular device type.
3:03
Many are predefined and are made to assist users when working with devices of the same type from multiple different vendors.
3:11
Next, let’s look at the two different types of messages on Ethernet IP.
3:17
Explicit messages, or TCP messages, are Ethernet-based messages with built-in error checking.
3:25
These are best used for point-to-point requests sent on an infrequent or as-needed basis.
3:33
They follow the request-response model, and each message explicitly states data being requested. For example, imagine we have a variable frequency drive on our network.
3:46
It could have hundreds of parameters, but occasionally we will need to read or write a specific parameter.
3:53
In this case, we would likely use an explicit message, as it is an infrequent specific request.
4:00
However, for runtime, high-speed messages would use implicit messages, or UDP messages.
4:07
Ideal for continuous, real-time data, this message type follows the producer-consumer model.
4:13
These messages contain only data. The meaning of the data is pre-established.
4:18
For an example, again, imagine our variable frequency drive.
4:23
Implicit messages might be used for the start-stop status, predefined frequencies, the current frequency, and so on.
4:31
With that covered, let’s now look at what device classes might be receiving these different messages.
4:38
The device that controls the network is known as the I.O. scanner.
4:42
You must have at least one of these for your network to function.
4:46
Next, the most common member of an Ethernet IP network is the I.O. adapters.
4:52
These could be variable frequency drives, I.O.
4:56
blocks, or anything else that interfaces with the network.
5:00
Next, we have devices that exchange data using explicit messaging.
5:06
These are explicit message clients.
5:09
Usually in a network, these would be your HMIs or other devices with the capability to read and write data to the network.
5:19
Finally, we have a very simple device known as an explicit message server, which simply responds to explicit message requests when they receive them.
5:29
With Horner, we have traditionally supported several parts of this network.
5:34
All Horner all-in-one modular controllers can act as both I.O. adapters and explicit message clients.
5:40
But today, we are showcasing the new I.O. scanner functionality.
5:45
Any Canvas, Excel Prime all-in-one, or modular controller can now be used as an I.O. scanner on your network.
5:53
As long as you are using CScape version 10.2 and your Horner controller is updated to firmware version 17.4.
6:03
And with this new functionality, it is now possible to run an entire network of third-party devices with a Horner IOS scanner controlling them.
6:12
Which Horner products support Ethernet IP Scanner functionality?
6:15
To start with, all Canvas series controllers include support as standard, whether it’s canvas all-in-one, or a modular CPU, both will support this new feature as standard.
6:28
Ethernet IP Scanner functionality is also supported in the XL Prime series of controllers.
6:36
However, it does not come as standard.
6:38
Instead, it requires a one-time purchase of an Ethernet IP Scanner license.
6:44
What are the Horner Ethernet IP Scanner features?
6:48
Of course, the Ethernet IP scanner allows you to control your Ethernet IP network, but beyond this, we can also exchange I.O. data with I.O.
6:58
adapter devices in real-time, including third-party I.O. adapters.
7:03
And when configuring third-party devices, Horner controllers allow you to import device info from an EDS file.
7:11
Horner controllers also have the ability to create explicit messages for triggered data exchanges.
7:17
Both of these features will be demonstrated later in this webinar.
7:21
Let’s now look at the workflow for setting up the Ethernet IP Scanner functionality in your Horner device.
7:28
Starting with Cscape 10.2 Service Pack 2, a new option will be available in the LAN configuration menu in Cscape.
7:38
First, we enable this new option named Enable Ethernet IP Scanner from the list of resident protocols in LAN 1 or LAN 2.
7:49
Next, we highlight Ethernet IP Scanner and click on the Configure Selected Protocol.
7:56
And here we assign an Ethernet IP Disable variable and Ethernet IP Status variable.
8:03
Next, we are going to add IO adapters to the network by right-clicking on Ethernet IP resident protocol.
8:12
In this menu, navigate to the Adapter tab and fill in your adapter’s details.
8:18
Then we simply need to fill in the details for the input, output and configuration assemblies.
8:25
If you’ve imported data from an EDS file, these will all be automatically configured, but we would just need to manually assign a few things.
8:34
A local variable to transmit data from the device or receive data from it.
8:39
An RPI or Requested Packet Interval.
8:42
We have to select whether we’re using Unicast or Multicast.
8:46
And finally, we have to assign the IO data to a local variable.
8:51
Remember, not all IO adapters support all three types of assemblies.
8:57
With that covered, we’re going to switch to a demonstration of this workflow.
9:02
Here we are on the bench.
9:04
With the equipment we are going to use for today’s demonstration, we have the Horner CPU300 modular controller, which is connected to a HMI Connect touchscreen.
9:14
And to demonstrate the Ethernet IP functionality, we have an encoder products Ethernet IP compatible encoder, which will interface with our Horner controller as an IO adapter.
9:26
Now let’s look at Cscape.
9:27
First, we navigate to Hardware Configuration at the top, then we are going to click on LAN1 as this is where we are connecting our Ethernet IP network.
9:40
Starting with Cscape version 10.2 Service Pack 2, you should see an Ethernet IP Scanner checkbox under Resident Protocols.
9:49
Then we are going to click Configure Selected Protocol.
9:52
Here, we need to assign a boolean disable variable and a double integer status variable.
10:01
We have pre-configured these variables for our demonstration, so we simply select them from the list provided.
10:08
With that completed, we now need to start adding IO adapters to our network.
10:13
First, we navigate to the Ethernet IP Scanner checkbox option, but this time we right-click text instead and click add adapter from this drop down.
10:25
In this menu we will start configuring our IO adapter.
10:29
We are going to name it encoder and provide the IP address for it.
10:33
Next we need to install the assembly details.
10:37
If the manufacturer provides an EDS file then we can simply select browse for EDS file and navigate to the files location.
10:45
It will then ask if we want to import the EDS file, to which we select yes, and then we are given a few different profiles or setup options.
10:55
Remember, not all manufacturers will provide this many options, but some will.
11:01
For this demonstration, we are going to select the default option, and then we assign a connection timeout value.
11:08
We’ve chosen 500 milliseconds, but this will change depending on your operation.
11:13
Next, we need to assign a boolean disable variable and a double integer status variable for the encoder itself.
11:23
Again, for this demonstration, we have pre-configured these variables, so we will just select them from the drop-down menu provided.
11:31
With that completed, we have successfully set up our encoder.
11:35
However, we still need to configure the data coming from the encoder.
11:39
First, we decide a data type.
11:41
In this case, since the data is 4 bytes long, the best choice is a double integer.
11:48
Next, our RPI, or Requested Packet Interval, we are going to change to 50 ms, but this can be whatever you like.
11:58
Finally, we need a local variable to store the data, which we have already configured under the name EIPEncoderPosition.
12:06
We are now done with our setup for this encoder, as we have no output or configuration data to deal with.
12:14
We also don’t need to set up explicit messaging, but we will show off this functionality in the next demonstration.
12:22
For now, let’s jump back to the bench and take a look at our encoder at runtime.
12:28
Here we are on the bench.
12:30
Our program download has been completed, so this should be all working as we configured it to.
12:36
If we move our encoder, we can see the position value on our screen update in real time.
12:42
Down here, we also have some status information.
12:45
For main Ethernet IP status, the number represents how many adapters or Horner Ethernet IP scanner is communicating with.
12:53
This value should be 1, as we only have the encoder connected to our network.
12:58
and as we can see, it is indeed 1.
13:01
For the encoder EIP status, any value other than 1 would indicate a problem somewhere in the system, but as you can see, our current value is 1.
13:12
In our second and final demonstration today, we are going to look at how to configure explicit messaging in Cscape.
13:19
This will be a very simple example where we are going to configure one specific message to retrieve a parameter from our device.
13:27
in this case our encoder. Now let’s jump back to Cscape and set this up.
13:34
Here we have the screen from our previous demonstration but we have made some changes.
13:38
We still have the main EIP status and encoder EIP status boxes but we have added a third box for our encoder reported state which will be populated with data we retrieve using an explicit message.
13:53
We are going to navigate to hardware configuration at the top, click on LAN1, double click on encoder under the ethernet IP scanner checkbox and then into the explicit message tab at the top.
14:09
First we click enable explicit messaging, then since we are only retrieving a single value we are going to choose get attribute single from our drop down.
14:20
Next we need to fill in our class, instant, and attribute fields.
14:25
To get this information, we referred to the documentation.
14:29
As you can see, we are going to be looking for class 1, attribute 8, but there is no mention of an instance.
14:36
This is because for most devices, only one instance is used.
14:40
So, filling this information into Cscape, our class will be 1, our instance will be 1, and our attribute will be 8.
14:48
We leave source type as integer and length as zero.
14:54
We also leave source data blank as in this example we are only retrieving a single attribute.
15:01
Then we need to configure a trigger and status variable as before.
15:06
But then we also need a response data variable to store any data that comes back to the device.
15:14
This is a 256-bit array, so it can support quite long messages.
15:21
However, in this demonstration, our response will only be four bytes long.
15:26
And we use the response length variable to tell our machine how long our message is supposed to be.
15:32
And that’s everything configured.
15:34
Now, let’s jump to the bench and see if it works at runtime.
15:40
Here, we can see the box where the message should appear.
15:43
Currently, it says none, as we haven’t executed an explicit message yet.
15:50
If we press this Get button, we can see a change to Ready.
15:55
That is a simple example of an explicit message transaction between our Horner controller acting as an IOS scanner and our I.O. adapter.
16:05
And that concludes our webinar for today.
16:08
Thank you so much for listening and the Q &A session will begin shortly.
16:19
Okay so as usual the upcoming webinars are up on the webinar section of our website as well as in the newsletters that you have been sent.
16:31
The registration links are there now so feel free to join for the upcoming.
16:36
I don’t see any questions in on today’s webinar so I think we can leave it there. Thank you all very much and I will see you next time.
