[00:00] In this lesson we'll talk about system tags. System tags simply report information about the system, specifically the gateway or vision clients and designer sessions. If we take a look at the tag browser here, which I have expanded in the middle of my screen, we can see there's a system tag provider. This is where system tags live and we have some tag folders available, those being client and gateway. One important thing to note is that we can't create any new system tags. If I try to add a new tag, I don't have any available options to do so. If I expand the client folder here, we receive additional sub folders about the client's system. Just to be clear, these do differ from these similarly named vision clients tag provider, as those tags are specific to vision clients during runtime. So these tags here report information about vision clients or the designer. They do not report any information about other entities.

[01:04] So for example, in the perspective module, you have sessions. These tags do not report information to the sessions. Sessions can't actually use the tags in this folder. If you wanted something similar to these tags here in a perspective session, that's what the session props are used for. Session props basically fill that role. They provide similar functionality, and again, they're really only available inside of the session. So if I open our system folder here, we receive information about our current system. We get things like the systems current date and time, the default database connection, which operating system we are using and so on. Now, these client tags are unique in that they are not able to be modified. For example, if I try to write to this project update available tag, we'll get an error message letting us know the tag is read only if we try to edit the tag by double clicking on it, we are not brought to the tag editor, however we receive additional information about the tag. Right clicking on the tag doesn't give me the option to edit either as it's disabled.

[02:06] However, you can utilize these tags in component bindings. For example, we could go to a vision window like this system tags window and set our tag provider to system. We could then open the same system folder and drag in the current date time to the window, and we'll bind it to a label component and you'll see the current daytime displayed on the window. Let's go back to our tag browser and move on to the gateway tags, which report information about the gateway. We can see, for example, the uptime seconds, so the number of seconds since the gateway last started. There's also some sub folders based on different functionality. So for example, if I go down to the redundancy folder, we see information such as the role of the gateway that's active. In this case, the master is active. If I go up to the performance folder, we can actually see resource wise how the gateway is doing. So for example, memory usage. Now a similarity between other types of tags and the system tags here is if I double click on the system tag, we do see our tag editor.

[03:07] So I can make some configuration changes to these as well as create some alarms or turn on history. So if I wanted some trends of resource usage, I could simply turn on history here. Now, I'm not going to cover all of the different folders. A lot of them are somewhat self-explanatory, but we'll have them listed in the user manual, which I've linked below this video. Now, hopefully that gives you a good idea about what the system tags are. Again, there's not really a lot of configuration you need to apply to them. They do offer some useful information that otherwise is somewhat difficult to obtain.