# Push button stuck alternative

**URL:** <https://forum.inductiveautomation.com/t/push-button-stuck-alternative/21468>\
**Category:** Ignition\
**Created:** [December 18, 2018, 12:39am UTC](https://forum.inductiveautomation.com/t/push-button-stuck-alternative/21468 "2018-12-18T00:39:23Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 18, 2018, 11:39pm UTC](https://forum.inductiveautomation.com/t/push-button-stuck-alternative/21468/6 "2018-12-18T23:39:10Z")

</div>

> [@alex.cordova.ee](#):
>
> Please tell me your opinion

You can use repeating signaling at a fast pace with a little bit of PLC code to handle the secure release of many bits in an array. See this comment for a suggestion:

> [@Momentary Pushbutton latching ON](http://forum.inductiveautomation.com/t/momentary-pushbutton-latching-on/5373/61):
>
> A signalling approach to consider to minimize the PLC code required: Allocate a PLC array tag / file with enough integers to cover all of the momentary button bits you need for your application, plus two more for transmit counter/comparison at the end. Do not create Ignition tags for these PLC tags. Create a script module in Ignition that holds an array of timestamps for the number of bits needed, plus a persistent counter in a module global. Write two functions: A message handler that takes…

---

_[View the full topic](https://forum.inductiveautomation.com/t/push-button-stuck-alternative/21468)._
