0:01
Good morning everyone, thanks for joining this webinar on WebMI plus with Canvas.
0:07
It’s a straightforward enough 15 minutes presentation, if you have any questions we can get to those at the end. Hello and welcome to today’s webinar.
0:15
Today we will be looking at Canvas WebMI plus in Cscape 10. Let’s look at our agenda for today.
0:22
We will start with a quick review of WebMI.
0:25
Then we will discuss the enhancements made for WebMI plus for Canvas in Cscape 10, as well as what has stayed the same as with standard WebMI.
0:34
Finally, we will go through the configuration for WebMI Plus in Cscape 10.
0:39
There will be demonstrations throughout, and we will finish with the Q &A session.
0:44
WebMI is the capability for the Horner OCS product lines to serve over webpages over ethernet from its local memory slots, which is usually done using MicroSD.
0:55
The webpages are typically used for remote monitoring and can also be used for control if the system designer chooses.
1:02
These webpages are created within Cscape and they are based on HTML5, which makes them highly compatible with nearly all web browsers on mobile devices, computers, and other devices.
1:15
Some WebMI applications include monitoring machinery and equipment in a factory setting for operational purposes, accessing data from machinery and equipment for maintenance and production efficiency programs, as well as monitoring and controlling equipment and processes in a campus environment, or an environment where you may have equipment that’s scattered throughout an area, such as an agricultural site.
1:40
If you wanted to use WebMI within a facility, then you would simply use standard IT security methods to secure the system, because you would only have access to WebMI through the local factory LAN.
1:52
So whatever security has been applied to the local factory LAN will also protect the WebMI.
1:58
The WebMI username and password credentials would then be assigned to whoever will be using WebMI with the system and would allow them to log in from nearly any web browser from a mobile device or computer system such as Windows, Mac or Linux.
2:13
If you want to use WebMI from outside a facility, then there are multiple options that you can use for security.
2:19
For example, you could have IT-managed access through the firewall using standard VPNs.
2:25
There are also several dedicated gateways or cell modems that could be tied to specific OCS controllers.
2:32
From a gateway standpoint, there are manufacturers such as Secomea, MBConnect, E1, and TosyBox.
2:39
Then for cell modems, which often have built-in routers included, you have options such as Multitech, Digi, SixNet, and Phoenix.
2:48
Now we will look at WebMI+.
2:50
This is an enhanced version of WebMI that is standard on Canvas controllers.
2:55
The basics of WebMI functionality have stayed the same.
2:58
However, there have also been a number of requested enhancements implemented for WebMI+.
3:04
First, we will discuss what has stayed the same for WebMI+.
3:07
For one, WebMI-Plus screens can be duplicates of the OCS screens.
3:12
WebMI-Plus screens can be duplicates of the OCS screens.
3:16
So whatever is running on your OCS screen can be duplicated and used as your WebMI Plus screen if you choose.
3:22
You can also create unique web pages using the Web Designer feature in Cscape, so that the screens being viewed remotely using WebMI Plus do not exactly match what’s on the OCS.
3:34
For example, if you have a Preventative Maintenance Program or a Production Control Department that are remotely logging into the equipment, and what they’re interested in is different to what the operator needs to see, you could create custom web pages using the Web Designer feature in Cscape to provide that information from the same piece of equipment, customized for anyone that isn’t the operator.
3:56
If you decide to have your WebMI Plus screens as exact duplicates of what’s running on the OCS screen, then you can choose to make the WebMI screens and the operator screens synchronized.
4:07
So when the operator changes screens on the OCS, the WebMI Plus screens will also change and vice versa.
4:13
From a login credential standpoint, WebMI Plus also uses the user access feature for its credentials.
4:20
The connection timeouts and the session timeout are also effectively the same for WebMI and WebMI Plus.
4:27
Next, we will look at the enhancements implemented.
4:30
WebMI Plus has been rewritten from the ground up to be more efficient.
4:33
One of the ways this has been done is with WebMI Plus webpages, as they are now transferred online or over ethernet from the OCS to the web browser at login.
4:44
These webpages reside on the browser after the upload, improving communication and time efficiency.
4:51
The WebMI Plus webpages don’t have to be hosted on the OCS from MicroSD. They can now also be hosted from internal memory.
4:59
You can also completely eliminate the user login using WebMI Plus if you choose, or you can fully customize the user login if you decide to keep it.
5:09
This also applies to the terms and conditions of the login.
5:12
Finally, object support for WebMI Plus is significantly better.
5:16
More objects are supported, and the user interface appearance better matches the object as it would appear on the OCS.
5:23
From a Cscape configuration standpoint, we will note that there isn’t any licensing configuration required with Canvas and WebMI +, because Canvas supports WebMI +, as standard, so it can be considered as pre-licensed.
5:37
The main configuration for WebMI +, is performed in the User Interface tab under Options.
5:43
Once again, the user login is highly configurable, and the timing parameters and the HTTPS configuration, which is available with WebMI +, is available through the Advanced button.
5:55
With the User Login Configuration dialog, you have the option to disable it completely, as well as the option to import custom images such as a company logo for the OCS that is being deployed on the machine.
6:08
You also have complete flexibility to modify the login configuration and the ability to completely customize the terms and conditions.
6:16
If you choose to keep login credentials then you also have many options to configure these.
6:21
These credentials are performed from the user interface tab under systems and user as highlighted.
6:28
Unlike standard WebMI, WebMI Plus allows user credentials which have been assigned as variables or assigned to variables to be edited at runtime.
6:37
So with standard WebMI all user credentials have to be hard coded in Cscape but with WebMI Plus you can instead choose to use variables for usernames passwords.
6:47
However, before you can log in remotely using a set of user credentials, that set of user credentials has to have been logged in locally ahead of time.
6:56
So once that’s happened on the OCS, then the user can log in either locally or remotely using those credentials that were assigned using a variable. Now we will demonstrate WebMI Plus with Canvas and Cscape 10.
7:10
We have a demo project we created open, completed with several screens and logic.
7:15
First, to find the information on WebMI, we will go to the User Interface tab in the ribbon toolbar where we have a WebMI group with several different features.
7:25
We will start by selecting Options.
7:28
At the top of this dialog box, we have the banner for the web page name that will appear in your web browser.
7:34
This will typically be a company’s name or the name of the machine being used.
7:38
In addition to the banner that shows up at the top of the web browser, when WebMI first loads on the browser, a logo will be displayed, and the user has the ability to pick that particular image for this.
7:50
We will choose the Horner APG logo for this.
7:53
Next, we have the timeout parameters for session timeouts and connection timeouts.
7:58
This is how long within activity we want to wait before you automatically log out any users.
8:04
We will leave these at the default settings for now.
8:06
If we want to completely prevent sessions from ending due to inactivity, we can select this checkbox here, which will inhibit session timeouts.
8:15
We also have a status we can assign here, which is 80 bytes long, as well as some information on the status structure, which tells us what users are logged in at any given moment.
8:26
Then the Enable Screen Sync Settings enables you to have the screen displayed in WebMI and the screen displayed by the user on the OCS to be synchronized.
8:35
So if you’re actively monitoring the unit over WebMI and you change screens locally, that screen will also change for the operator and vice versa.
8:44
If you want the screens to act independently, then you can leave Enable Screen Sync off.
8:50
So far, the configuration settings here are very similar to what was available with standard WebMI, with the exception of the ability to select an image when WebMI starts up on the web browser.
9:02
Next, we will look at the user login.
9:04
Once again, with WebMI +, you have the ability to completely disable the user login if you choose.
9:10
So when the IP address of the OCS is called up on a browser, you can choose to have that webpage automatically load without any kind of login.
9:19
If you want to keep the user login, then you still have a lot of flexibility in terms of how you configure the login box.
9:26
For example, you can configure a legend for the login box, as well as configure the colors and size, and add an image for your company logo.
9:35
For our demonstration, we will choose to disable the login page.
9:39
As well as the user login configuration, there are now a lot more options to customize the terms and conditions.
9:46
Most users, when they first log in, have to accept terms and conditions before they start using WebMI from their web browser, and if you select the first option here, then this will still happen.
9:57
However, if you do not want the user to have to accept the terms and conditions every time they log in you can select the second option instead and then you can choose to accept the Horner Terms and Conditions on their behalf.
10:10
If you want the user to accept your own custom Terms and Conditions you can select the third option then you would accept the Horner Terms and Conditions and then add the name of the file for your custom Terms and Conditions.
10:23
So this is our user login configuration.
10:26
Next we will look at the user credential settings which can be found in the Systems group of the User Interface tab.
10:33
This is where we can hardcode users if we choose, or we could add in variable arrays here instead.
10:39
So once we’ve made the changes that we want to make to our screens and our user logins, then we can publish our webpages to the OCS.
10:46
We can do this from the WebMI section group by selecting Publish to Removable Media.
10:52
One option that has always been available here is that you can publish to your computer and then manually copy the files over or you can publish to OCS.
11:01
If you choose to publish to OCS then it will use FTP to download these files to the OCS.
11:08
However with Cscape 10 the OCS itself doesn’t have to have FTP credentials configured in order to download it.
11:15
So if you’re doing the WebMI download from Cscape then you only need the IP address of the OCS that you are downloading to.
11:22
We will note that the final part of the WebMI download with both Cscape 10 and earlier versions usually takes a while to finish, as the status bar on the screen can appear to be frozen here.
11:34
Now let’s look at our bench setup for this demonstration.
11:37
On our OCS we have a collection of demo screens that we have created, such as this IO simulator screen where we can change inputs from our IO simulator.
11:47
Some of the inputs also cause alarms to be generated as we can see here.
11:51
then we can also view the current alarms and acknowledge them, as well as access our alarm history, which tells us everything that has happened with our alarms in general.
12:03
From here, we can also adjust our analog values on our I.O.
12:07
simulator and watch the meters change accordingly, as well as adjust the frequency of the flashing lights here in terms of Hertz.
12:15
So this is our first screen.
12:17
We will switch to our second screen, which is a conveyor belt simulator.
12:21
From here we can load cartons onto the conveyor belt which causes this animation of a box moving across the screen.
12:29
We can also change the speed that the object is moving across the conveyor belt. We also have four different trend graphs.
12:36
First we have a scope graph which has a quick update rate of about every 50 milliseconds.
12:42
Then we have the have a multi-point graph, as well as a scatter graph.
12:53
Now we will look at our Emosh WebMI.
12:56
From our web browser, we will enter the IP address of our OCS into the search engine.
13:01
Once we do this, the Horner logo we session our configuration appears on the startup screen, as well as text that says downloading slash compiling.
13:11
This is a fundamental difference in how WebMI works.
13:14
Here the web browser was receiving the web pages from the OCS, and now those web pages reside in the web browser.
13:21
And now we are exchanging data between the web browser and the OCS in real time, which might result in some changes in operation.
13:29
First we will look at our IO status screen.
13:32
As we can see, this screen looks very similar to the IO status screen shown on our OCS.
13:38
we can still change our inputs and outputs and as the inputs change we can see their status change and we still have our alarms triggered on the screen.
13:47
We also have our alarm object which allows us to view our list of current alarms and remotely acknowledge any alarms.
13:54
We can also look at our alarm history.
13:57
As our analog IO is changing we are adjusting these dials a little bit and as we can the needles change accordingly. So we can operate this WebMI screen very similarly to our OCS screen.
14:10
Now let’s look at the scope object.
14:12
If we look at our bench setup, this is what our scope graph currently looks like with data being graphed and moving across the screen.
14:20
Now let’s switch back to our WebMI screen of our scope graph.
14:24
We will note that it only starts to graph data once we This scope object is sampling data every 50 to 100 milliseconds, but still graphs a reasonable amount of data.
14:36
Also with a scope graph, the graph will only sample data until the screen is full and does not scroll across.
14:44
Next, we will look at our standard trend graph.
14:47
Once again, when we look at the graph on our OCS, we have data moving across the screen.
14:53
Now let’s look at our graph in WebMI.
14:55
As we can see, we don’t have historical data here and our graph slowly starts to trend once we switch to this screen.
15:02
So once again, there is some trend capability built into WebMI, however this does not cover historical data at this stage.
15:10
Next, we will return to the home page again and select our WebMI multi-point graph.
15:16
Only once we select the graph button, our graph starts to trend.
15:20
This also applies to our scatter graph.
15:22
Our graph only starts to trend once we select the graph button.
15:27
So from this demonstration we can see that there are some limitations in historical trending with WebMI +, however many of its other functions are full featured.
15:37
That concludes our webinar for today.
15:39
Thank you so much for listening and the Q &A session will begin shortly.
15:56
Okay, so next week we just have a comparison video for the micro OCS’s against the XL Prime, all the differences that you see on both, and again the following week with Prime against Canvas.
16:12
I’m not seeing any questions in on this, it’s much the same as it always has been with WebMy.
16:20Okay, on that note, thank you all for joining and I will see you again soon.
