I have alarm setpoints on UDT instances that I allow the client to set. However, every time after a gateway restart, these alarm setpoints reset back to their UDT values, rather than keeping the values that they had prior. When configuring the alarm in the UDT, I cannot set the setpoints to nothing, it makes it 0, which is why I’m guessing it overrides it… My only idea on how to fix this is to bind the setpoints to parameters, and allow the client to change the parameters. Is the way these alarm setpoints work intentional? If so, what is the best way to go about it?
(I found this thread, but no answer in it… :Make Alarm setpoint tag retentive)