Ignition Client
00:00 Ignition's client login screen can be modified in a couple of ways, namely, the username, password and login text, and the information up at the top left corner of the screen. To do this, we're going to go into our Designer, and into the Project, Properties screen, and, under Client, Login, you can see, here's all the information that we can fill in.
- Using MQTT with Ignition SCADA. The MQTT protocol is rapidly being adopted as a reliable, efficient protocol in modern industrial data collection applications. MQTT uses a variety of techniques to provide highly efficient use of bandwidth to collect data from a wide range of sources and then make that data available to.
- Download the free Ignition trial Inductive Automation. 90 Blue Ravine, Folsom CA, 95630. 1-800-266-7798 (toll-free). 1-916-456-1045 (int'l). Email Us.
[00:00] Components and clients will resize to fit within the available space of the window in the client. You can see my client here. If I were to bring in the right-hand side over here, that this edge, this little label here, shrinks in or stretches and grows depending on how large the client is, up until a certain point. Right about here, you'll see that I have some scroll bars. And if I make this a little bit smaller, the actual size of the component no longer changes here. This is because the client has reached the minimum size. Once this occurs, we stop resizing the components and place scroll bars on the client. Now the minimum size is customizable so lets' take a look at the settings here. I'm going to move my client off to the side first, just a second here. And in the designer, I'm looking at that same project. I'mma come up to the Project menu, go to Properties, and under Client, and User Interface, we can see the Minimum Size up here.
Ignition Client Event Scripts
[01:01] Now if I were to make these much smaller, so I'll change my Width and my Height to zero, I'll click OK. And I will save and publish the project. Let me bring my client back over. We can update. Update again. And you can see I no longer have scroll bars. If I reduce the size of the client again, we can see that the component is also being resized. Furthermore, we will not see scroll bars because the client has not yet reached its minimum size. Now my docked windows, on the edges here, do have a say in the matter. If we bring our client to a size so small that it starts to cut in on to my docked windows, we will add the scroll bars. But the main lesson here is that when the client's width or height is smaller than the project's minimum size, scroll bars are added. When starting a new project, it is a good idea to plan for the minimum size your clients will be launched on and adjust the project properties accordingly.
Ignition Client Launcher Download
Ignition Client Download
[00:00] If you need to run some logic when your clients starts up or when the gateway is starting, you can use Startup Scripts. The Client Event Scripts has a Startup Script as does the Gateway Event Scripts. And of course, they run at very different times. So the Client Event Scripts version of the Startup Scripts will run every time a client is launched. This logic is run right after the login. So, right after the user logs successfully the Client Startup Script will run. Oftentimes we'll see people using this to open-up a custom set of windows, if maybe the opening set of windows should be different based on who logged in. The only thing to be really aware of for the Client Startup Script is that if you are trying to do something like logging back out or re-targeting, you should do that and then invoke later. For example, you will define what you wanted to do. Let's say under certain circumstances I wanted to log the user immediately back out. Here, I'm going to use system.security.logout but you can see I've put this call in a function definitions that I can use system.detail.invokelater. The reason to do this is because the Startup Script is run during the Client Startup it's better for the system to logout after all that startup stuff is finished. That's what invoke later does is it runs a function after the current event processing is finished. The Gateway Startup Script, of course, runs on the gateway and will run for each part that you have defined but it is important to remember that even though this script will run when the gateway first starts up, it may also run at additional times. For example, if you alter any of your Gateway Scopes Scripting or your Project Script Library, this script will get run again. So that every time any of the scripting for your project that affects the gateway changes, your project essentially restarts in the gateway. So, shut down and startup will be called. The reason this is required is that you may have made changes to scripts that this script references, so the dependencies of change, so you need to run it all again. It's really a Project Startup Script in the Gateway Scope rather than just a Gateway Startup Script. You need to remember that when you are writing this that this may run multiple times in the lifespan of a gateway.