0:01
on this webinar on hands-on with the CPU 300.
0:06
As usual we’ll go into the presentation and if you have any questions at any point just pop them in and we’ll get them at the end.
0:12
Hello and welcome to today’s webinar. In this webinar we will take a hands-on look at the new CPU 300.
0:20
Here’s the agenda for today.
0:22
We’ll start with an introduction to the CPU 300, what it is and what makes it We will showcase assembly and installation, the onboard screen, getting connected with Cscape 10.2, program downloads, the firmware update procedure and connecting a HMI Connect touchscreen.
0:46
Let’s begin.
0:47
The CPU 300 is part of the Canvas series of controllers.
0:51
The Canvas series gives you the choice between a more traditional route with an all-in-one unit, or a new, more modular route made possible by the new CPU-300.
1:03
This modular route requires OCSIO and a HMI Connect touchscreen, making the installation and use of it feel very similar to other PLCs.
1:17
But despite each component being separated with Horner, these are all programmed as an in one unit, making setup and maintenance quick and easy.
1:27
Next let’s take a look at some of the hardware on the CPU-300.
1:31
Starting at the top, we have a micro SD card slot next to a USB-C port.
1:37
These can be used for programming and connection to C-Scape 10.
1:41
Then you have two ethernet ports and a display connector port, which is used for the HMI Connect touchscreen.
1:49
It also features a USB-A port for connecting to a wide range of devices and add-ons, along with a CAN port and a few serial ports.
1:59
In terms of I.O., you can add up to 7 OCS I.O. modules directly to the side of the controller.
2:05
Or, through the CAN port, you can add even more remote I.O.
2:09
The CPU300 requires a 12 or 24 volt DC power supply and features a built-in display.
2:16
This display is not for user interface purposes.
2:20
The built-in system menu is geared towards maintenance purposes, with quick access to status information and live readings.
2:28
For user interface purposes, we’ll be installing a HMI Connect touchscreen, which we will demonstrate later in this webinar.
2:37
What about networking and graphics on the CPU 300?
2:41
The CPU 300 features all the capabilities you would expect from a Canvas series controller.
2:46
meaning support for everything from Ethernet IP to MQTT to CanOpen is included by default for no extra cost.
2:57
It also carries over the advanced Canvas graphics, allowing for advanced trending and recipes, video objects, modern gauges, switches and all the other Canvas UI.
3:09
And if you choose to add an OCS360 subscription, all the features of OCS360 can be taken into advantage of by default with the CPU 300. How does HMI Connect work?
3:22
We have alluded to it a few times already in this presentation but the HMI Connect touchscreens are very easy to install.
3:31
They plug directly into the display port on the controller using a single rugged cable which carries DC power, video signal and touch feedback.
3:42
Every HMI Connect touchscreen comes with a 1m cable included, but an 8m version is also available for purchase if required.
3:53
With that covered, we can now begin on our demonstrations, starting with the assembly and installation of the CPU-300.
4:05
Here we are on the bench.
4:06
This is the box the CPU-300 will arrive in.
4:09
Opening it up, inside we can find the CPU-300 itself, along with a package of materials.
4:16
In this small bag we have a few things.
4:19
One power plug for connecting power to the device, one backplane connector for installation on DIN rail, and two clamps for keeping the stack of CPU and IO modules connected and secure. Assembly is very straightforward.
4:35
First, decide how many IO modules you are going to connect. We have chosen four for this demonstration.
4:41
and connect their backplane connectors together on the DIN rail.
4:45
Then we add the backplane connector for the CPU300 to this stack.
4:51
Now we add it to the rail and clip the clip to keep it in place.
4:55
After that you can go ahead and add on all of your I.O. modules.
4:59
Remember you can install up to seven by default.
5:02
Once you have added all your I.O.
5:04
modules we can take these clamps and first we snap them to either side of our stack.
5:11
Then, using a small screwdriver, we tighten both clamps just enough until they have a good hold on our stack, but not too much that we might damage the CPU or the I.O. modules.
5:24
Finally, we have our power connector, which we’ll plug in here once it’s been assembled.
5:30
And that is all that’s required for the assembly and installation of the CPU 300.
5:37
Next, let’s look at the onboard screen.
5:39
Back on the bench, we have everything connected and powered on.
5:43
Here is the onboard screen, which, as we mentioned before, is primarily used for maintenance purposes.
5:50
It displays the time and date, your CAN ID, your firmware version, as well as your current IP address.
5:59
Then, if we need more information, we can enter the full system menu by pressing the Enter key here.
6:07
This brings up our system menu screen which will look very familiar to anyone who has used a Horner OCS product before.
6:16
To navigate through this menu we will use the arrow keys to highlight different options. Then we press the enter key to open that option.
6:25
Again we navigate down to land settings using the arrow keys and we open it by hitting enter.
6:32
Then when we are finished in this To go back in the menu structure, we simply hold the left arrow and after a second we will start backing up.
6:43
All of the options you would expect on a controller like this are available to you through this menu.
6:50
That is basically everything you need to know about the onboard screen.
6:56
Let’s look at how we connect the CPU 300 to Cscape 10.
7:01
Here we are in Cscape 10, and if we check the about menu, we can verify that we are using Cscape version 10.2.
7:10
We need this version or later if we want to connect to the CPU 300.
7:15
If we go back to the home area, we need to start by adding a new program.
7:20
Click on the wave icon at the top and select new program.
7:25
Choose whichever programming language you prefer.
7:27
We will go with advanced ladder with variable based addressing.
7:32
Now in our new blank program we can check hardware config to see that we have the wrong controller connected.
7:40
Let’s move to the bench and fix that by connecting the CPU 300 using the USB-C port.
7:48
Here we are on the bench and we can simply plug our USB-C cable into the slot here in top left corner of our controller.
7:58
Then, moving back to Cscape, a new connection wasn’t automatically made. Instead, we need to manually configure it. Navigate to the Connection Wizard.
8:07
And you might notice that in Cscape 10.2 Service Pack 2 and later, the look of the Connection Wizard has changed. We now have more connection options.
8:18
And we are going to select one of new options, USB.
8:23
Then we click next and here using the provided drop down we will select the correct COM port which has our USB-C connection into it. Once satisfied we can click finish.
8:37
Now we have successfully connected to our controller as you can see by the new local and target values in the bottom right corner.
8:45
However there is one more thing we need to If we navigate back to Hardware Config, you can see that we are still configured for an XL4 Prime.
8:54
To fix this, we simply click Auto Config and, just like that, we are now configured correctly for the CPU 300.
9:03
We can also connect to the CPU 300 via Ethernet. The setup process is almost identical.
9:09
First, on the bench, we will disconnect our USB-C connection and plug in our ethernet cable instead.
9:18
Remember to note down your controller’s IP address, which can be found at the bottom of the on-board screen here.
9:25
Then, back in Cscape, we will navigate to Connection Wizard and this time we will select LAN instead, before clicking Next.
9:35
On this screen, the IP address of our controller should automatically populate this box here.
9:42
However, if it doesn’t, we could also type it in manually.
9:46
Once satisfied, we will hit finish and, once again, we will notice a successful connection has been made.
9:53
It really is that easy to establish a connection between the CPU 300 and CScape version 10.2 Service Pack 2 or later.
10:06
There are many ways to connect the CPU300 to Cscape, as we have just shown, but there are even more ways of downloading your program to your controller.
10:16
In this segment, we are going to demonstrate and compare the downloading speed of a large program over Ethernet, USB-C, and MicroSD.
10:25
Firstly, however, let’s cover how we establish a connection for each method.
10:30
With Ethernet, we are going to ensure that we have an Ethernet cable plugged in to our Then, in Cscape, we go through the connection process we’ve just demonstrated.
10:41
By going to Connection Wizard, then selecting LAN, and then verifying the IP address before clicking Finish.
10:49
Now, with a connection successfully established, all we need to do to start a download is click this Download button at the top.
10:58
This will bring up a menu of settings, which we will leave as default.
11:02
then we are shown an alert advising us to not tamper with the connection during the downloading process. Once we click yes our download will begin.
11:13
With USB-C we are going to ensure that we have a USB-C plugged in to our CPU 300.
11:19
Then in Cscape we go through the connection process we just demonstrated by going to connection wizard then selecting USB and then selecting the correct COM port before clicking finish.
11:31
Now, with a connection established, all we need to do to start a download is to click this download button at the top.
11:38
This will bring up a menu of settings, which we will leave as default, and clicking OK on this menu would begin our download.
11:47
Finally, with MicroSD, we are going to insert our MicroSD card into our computer.
11:53
Then we will click on the wave icon at the top and select Export to PGM.
11:59
Give this a name you see fit, and then click Save.
12:03
This process usually takes only a few seconds, but once complete, Zscape will give you this alert, which says the program has been successfully exported.
12:14
Now, back on the bench, we will insert our micro SD card into the provided slot in the top here.
12:21
Then, on the CPU 300, we hit the Enter button to access our system menu.
12:27
We will then navigate to removable media and this will open the folder structure on our SD card.
12:35
Now we will select our program file and hitting enter will initiate our download. Now we are going to do something a little different.
12:44
Here we have all three methods we just demonstrated and we are going to do a live comparison of the download time on each.
12:53
We have paused the footage just before the download begins and we will use these timers to track which one completes fastest. So on a count of three we will begin.
13:05
One, two, three, go!
13:14
First, winning by a wide margin is the MicroSD.
13:18
This took only 16 seconds to complete a full download of this fairly large program.
13:24
Next, not long afterwards, we have Ethernet, completing in a swift 34 seconds.
13:30
And finally, we will cut ahead a bit on USPC as it took a full two minutes to complete. While all three are very quick, USPC is a clear outlier.
13:41
Whilst a very convenient connection method, it isn’t the greatest if you’re looking for fast program downloads. Next, we are going to show you how to perform a firmware update.
13:53
First, off camera, we have loaded the firmware files onto our micro SD card.
14:00
We will plug this into the provided slot in the top left.
14:03
Our controller has been powered off, which is important for this process.
14:09
Next, using a paperclip or other short piece of wire, we need to press the load button at the bottom.
14:17
Insert your paperclip into this slot and press firmly until you hear a small click.
14:24
Then while holding this button down we are going to power on our controller.
14:29
You should hold this button down until you see text appear on the onboard screen.
14:35
Next on the onboard screen the text is telling us that it is performing a firmware update.
14:41
The time this takes is dependent on the size of the firmware update but in general this shouldn’t longer than a few minutes. Now, our firmware update has just completed.
14:52
As shown by the on-screen text, we now need to power cycle our controller so it can launch into the new firmware.
15:00
And, after a moment, we can see our controller will power up to a normal state with the new firmware successfully installed.
15:11
For our final demonstration, we are going to show you how to connect a HMI Connect touchscreen to the CPU 300.
15:21
Here we are on the bench, and for this process it is vital that the controller is turned off.
15:27
Connecting or disconnecting a HMI Connect touchscreen should never be done while the controller is powered on.
15:34
Here we have the connector cable for the HMI Connect touchscreen. It features four connectors, alongside a locking tab.
15:43
We are going to plug in to this slot here, taking extra care to line up the locking tab with the provided slot on the controller.
15:52
Once lined up correctly, firmly press the cable into place until you hear a click.
15:58
Repeat this process for plugging the connector into the screen, and once complete we can power on our controller.
16:06
The boot up procedure will be virtually identical as before, except now shortly after the onboard screen powers on, we should see an image appear on our HMI Connect screen.
16:19
After a moment, we will see our screen start to loading.
16:23
This is the exact same procedure you will observe with any canvas controller.
16:28
And there we go.
16:30
We now have screens displayed on the HMI Connect touchscreen.
16:34
If we tap on it, we can see touchscreen functionality is also working as expected.
16:39
That really is all that’s required to set up and use a HMI Connect touchscreen with your CPU 300.
16:50
That concludes our webinar for today.
16:53
Thank you so much for listening and the Q &A session will begin shortly.
17:20
on that one but feel free to get in contact with TechSport if something does come up in the meantime I think with that we can leave it there thank you all very much and we’ll see you next time
