Enable Parameter Bug?

Good day all,

Just wanted to report something that I encountered. Perhaps it can be passed along to the developers if it is an actual bug.

I had a standard momentary pushbutton object and was making use of the Enable parameter by tying it to the status of a light curtain. If the light curtain is clear, the button is enabled. If the light curtain is blocked, the button is disabled.

Here is the sequence of events that took place:

  • Light curtain obstruction clear. (Button is enabled.)
  • Pressed and held button. (control tag goes Hi)
  • Light curtain obstructed. (Button is disabled. Still holding button.)
  • Released the button.
  • Light curtain obstruction cleared. (Control tag tied to button remains Hi without button being held down. Had to press and release button again to reset control tag Lo.)

Is this an actual bug? I was working under the impression that a momentary button would only hold the control tag Hi if the button was actually being physically pressed. It's almost like it's holding on to the last known value.

Sounds like a bug. But you are playing with fire. Some topics (some rather heated):

https://forum.inductiveautomation.com/search?q=stuck%20momentary%20order%3Alatest

Vision can be made to produce reliable momentary buttons, but simply connecting to a boolean isn't it.

1 Like

Thanks for the reply @pturmel Phil. Yikes, yeah, looks like there's some heat around the momentary button topic. I'll continue forward using them with caution.