# 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:** 7

<div class="post-metadata">

**Author:** ![sbrannen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/sbrannen/32/3459_2.png) [@sbrannen](https://forum.inductiveautomation.com/u/sbrannen)\
**Post date:** [December 19, 2018, 11:46am UTC](https://forum.inductiveautomation.com/t/push-button-stuck-alternative/21468/7 "2018-12-19T11:46:22Z")

</div>

Hello Alex…[quote=“alex.cordova.ee, post:5, topic:21468”]  
I just think this kind of apllyies to all SCADA?HMI  
[/quote]

Although all SCADA/HMI are susceptible to a momentary bit “latch lapse” under certain conditions, testing has shown that Ignition seems to be prone to this anomaly in all conditions at a rather alarming rate (no pun intended). You may find [THIS](http://forum.inductiveautomation.com/t/momentary-pushbutton-latching-on/5373/40?u=sbrannen) thread interesting. It has a workaround that at least evens the field for Ignition with other direct comm protocols.

In any case… taking preventive measures, such as outlined by **pturmel** , to mitigate all conditions will always be the best course of action.

As you were…  
Steve

---

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