# Why so many alarms at the same time? **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 3, 2024, 1:09pm UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285 "2024-06-03T13:09:09Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![lyhkch](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lyhkch/32/9381_2.png) [@lyhkch](https://forum.inductiveautomation.com/u/lyhkch)\ **Post date:** [June 3, 2024, 1:09pm UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285/1 "2024-06-03T13:09:09Z")
Hi, I create a UDT like this. ![Snipaste_2024-06-03_20-30-23](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/5/65ae54b073b05f96880acf9d1bc687ce0dad6511.jpeg) sometimes, many alarms occur at same time. But the device didn't have alarms. ---
**Author:** ![jlandwerlen](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@jlandwerlen](https://forum.inductiveautomation.com/u/jlandwerlen)\ **Post date:** [June 4, 2024, 1:34am UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285/2 "2024-06-04T01:34:55Z")
Probably cause you're evaluating a low value, I assume you mean high value. ---
**Author:** ![lyhkch](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lyhkch/32/9381_2.png) [@lyhkch](https://forum.inductiveautomation.com/u/lyhkch)\ **Post date:** [June 6, 2024, 3:18pm UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285/3 "2024-06-06T15:18:15Z")
Sorry, I don't understand. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 6, 2024, 3:23pm UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285/4 "2024-06-06T15:23:15Z")
Right now your alarms will alarm when the bit turns off. If you want it to only alarm when the bit turns on (more likely), then you need to change the condition to high instead of low. ---
**Author:** ![lyhkch](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lyhkch/32/9381_2.png) [@lyhkch](https://forum.inductiveautomation.com/u/lyhkch)\ **Post date:** [June 6, 2024, 3:32pm UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285/6 "2024-06-06T15:32:17Z")
getBit({[.]Alarm\_Int},3) = 1 ? ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [June 6, 2024, 3:58pm UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285/7 "2024-06-06T15:58:47Z")
What you should really be doing is setting the alarms on the Alarm\_Int tag (or rename the Alarm\_Int tag to just Alarms), then set the mode to "Bit State" and put in the bit you want to use for that alarm. > **[Tag Alarm Properties | Ignition User Manual](https://www.docs.inductiveautomation.com/docs/8.1/platform/tags/tag-properties/tag-alarm-properties#main-alarm-properties)** > > In 8.1.17, the Tag Editor was redesigned to improve usability. The new Tag Editor now requires fewer clicks and keeps relevant tag information visible while modifying bindings, alarms, and event scripts. ---
**Author:** ![lyhkch](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lyhkch/32/9381_2.png) [@lyhkch](https://forum.inductiveautomation.com/u/lyhkch)\ **Post date:** [June 11, 2024, 1:25pm UTC](https://forum.inductiveautomation.com/t/why-so-many-alarms-at-the-same-time/91285/8 "2024-06-11T13:25:07Z")
Thanks, I will try.