You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing training@inductiveautomation.com.
Version:
LESSON LIST
-
4:21Configure an Alarm
-
2:50Dynamic Alarm Setpoints
-
2:23Configure Alarm in UDT
-
1:54UDT Alarm Dynamic Setpoints
Take Topic Challenge
Supplemental Videos
-
3:24Multiple Alarms on a Tag
-
1:54Alarm Grouping
Description
Learn how to configure alarms with dynamic setpoints inside of a UDT definition.
Video recorded using: Ignition 7.7
Transcript
(open in window)[00:00] In the previous lesson we looked at how we could configure an alarm on a tag inside of a UDT. We did that on our motor UDT, I configured the alarm on the AMPS tag. If I got back to the configuration here, On the AMPS I went down to my alarming and I added an alarm called the Hi Amps. And I basically set the mode to be above setpoint and I hard code the value of 60 here. Now it's very common that you want to have dynamic setpoints on your alarms within a UDT, and so there's two ways you can actually do this. Of course each way is going to use the binding feature, where you bind the setpoint to a tag, to an expression or, and 'cause I'm a UDT, a UTD parameter. Now typically we want to bind these to tags. Since my PLC doesn't have a high and low setpoint for my AMPS, I'm going to go ahead and create one manually. So I'm going to come out to my definition, I am going to add a new memory tag. I'm going to call this memory tag a HI SP, and I'll make it integer and I'll set the value here to be 60. Then I go back to my AMPS tag, go down to the configuration of the alarming, and rather than hard coding the value 60 here, I'm going to bind this to a tag and I'm going to select the HI SP within the UDT. So that way, if I stay within the UDT, every instance is automatically going to have that new memory tag and every instance is automatically going to be using that in the alarm. So I come back here and you can see that it's now bound, it's bold, it's going to the high setpoint, and now we're using that new setpoint. The setpoints memory tag, so the value will be 60 by default for every instance. If I go ahead and press okay you'll see that it now exists in every instance down below, and now it's possible that you can actually change the value for every instance. So here, if on this one up here, let's say I set the high setpoint to a value of 25. I should now see the AMPS go into, the alarm should be active because it is above 25.