# Alarming Delay Time Base

**URL:** <https://forum.inductiveautomation.com/t/alarming-delay-time-base/6703>\
**Category:** Ignition\
**Created:** [June 13, 2013, 2:19pm UTC](https://forum.inductiveautomation.com/t/alarming-delay-time-base/6703 "2013-06-13T14:19:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gadgetguru69](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gadgetguru69](https://forum.inductiveautomation.com/u/gadgetguru69)\
**Post date:** [June 13, 2013, 2:19pm UTC](https://forum.inductiveautomation.com/t/alarming-delay-time-base/6703/1 "2013-06-13T14:19:29Z")

</div>

I have question as to the thoughts behind the alarm delay settings in the new alarming that are in seconds. This is odd to me since most all other time base setting in ignition are ms based settings. Was this an oversight? Would really be much better if it was ms based and not seconds due to the fact if you are trying to tie this to a PLC time its more than likely a ms value in the PLC. Just wanted to see what intensions were here.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [June 13, 2013, 2:31pm UTC](https://forum.inductiveautomation.com/t/alarming-delay-time-base/6703/2 "2013-06-13T14:31:11Z")

</div>

Which part are you talking about? The consolidation tab on notification blocks? Or something else?

Edit: Oooh, probably the active and clear delays, huh?

---

<div class="post-metadata">

**Author:** ![gadgetguru69](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gadgetguru69](https://forum.inductiveautomation.com/u/gadgetguru69)\
**Post date:** [June 13, 2013, 2:33pm UTC](https://forum.inductiveautomation.com/t/alarming-delay-time-base/6703/3 "2013-06-13T14:33:45Z")

</div>

Kevin  
Yes the active and clears.

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [June 13, 2013, 3:37pm UTC](https://forum.inductiveautomation.com/t/alarming-delay-time-base/6703/4 "2013-06-13T15:37:37Z")

</div>

No, it wasn’t an oversight, it was just a decision. Most of the time the delays used are well over a second, like 1 minute, 10 minutes, etc. The number of times it would be in the milliseconds range would be very small. However, it’s worth noting that the value is actually stored as a float, and can be fractional, so if you must tie it to a tag that is stored in ms, just bind to an expression that divides that referenced value by 1000.

Regards,

---

<div class="post-metadata">

**Author:** ![gadgetguru69](https://avatars.discourse-cdn.com/v4/letter/g/e274bd/32.png) [@gadgetguru69](https://forum.inductiveautomation.com/u/gadgetguru69)\
**Post date:** [June 13, 2013, 3:42pm UTC](https://forum.inductiveautomation.com/t/alarming-delay-time-base/6703/5 "2013-06-13T15:42:14Z")

</div>

Ok thanks Colby just wanted to make sure it was the way it was going to be and not change.  
We just made adjustment to our AOI in PLC to compensate.