[00:00] In this lesson, we will explore the configuration of alarms in complex tags or UDTs. Since UDTs are comprised of other standard tags, it is possible to configure alarms on any of the tasks inside of the UDT. The benefit of using UDTs is that they are defined in one place, and every instance of the UDT automatically inherits the configuration of its definition. In other words, if I configure an alarm on one of my tags within the UDT definition, this alarm configuration will automatically propagate to every running instances of this UDT definition. Here in my designer's Tag Browser on the left, I see, I have four instances of a Motor UDT. Motors, one, two, three and four. Heading over to the UDT Definitions tab, I will see my Motor UDT definition.

[01:06] I will double click on it to bring up its editor. Here, I can individually configure not only my UDT itself, but any member tags within it. Specifically, I want to configure an alarm on my Amps tag here. So I will select it, I'll scroll down to its alarm section and press the little pencil to configure my alarm. I will now press the little plus sign here to add a new alarm to my tag. And I will name this alarm, High Amps. For its display path, I could do something like this, High Amps Alarm. The problem with this is that every one of my motors, one through four, will share the same display path, making it more difficult to tell their alarm events apart without looking at their source path. For this reason, I can use the little chain link icon to bind my display path to an expression.

[02:08] In my expression, I want to use my Motor UDT parameter, which in this case represents my motor number. So if I set my expression to Motor space, remember these are strings, so they need quotations around them. Plus, now I can click on the little UDT icon to insert a reference to my Motor number UDT parameter. I will then do another plus and concatenate the following string. Space, High Amps Alarm. This way, my display path will be dynamic and it will work for any and all motors in my tag system. I should point out that leaving the display path blank will automatically default its value to the source tag's path followed by the alarms name that was triggered. I am happy with my display path, so I will click the Back button and I will now configure my alarms mode to Above Setpoint and give my setpoint a static value of 60.

[03:14] In future lessons, we will learn about dynamic setpoints, but a static setpoint will do for now. That's it. I'm going to press Commit and then press OK. And now the alarm I configured it in my Motor UDT Definition should have propagated to every single instance of my Motor UDT. To see this, I will quickly head back to the Tags tab and refresh my Tag Browser by using this refresh button. And I will drill into each of my Motor UDT instances where I will find a bill icon next to all my Amps Tags, which tells me that my alarm configuration worked. If I add a new motor, of course, that's also going to have the same Amps alarm configuration. As you can see from the Vision Alarm status table on the right, some of my motor alarms are getting triggered already.

[04:06] Just like that, I was able to configure four alarms for four different motors by configuring one alarm in just my UDT Definition.