From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
I want to disable a workspace custom control in Veristand whenever a test is active and then enable it whenever a test is inactive. The logic on the block diagram of the control is simple. I use the Veristand API vi's to monitor a User Channel ("Test Active") that is set to a one when a test is active and a zero when inactive. The value of "Test Active" is wired to a Case structure that contains the "Disable" property node in each frame with the appropriate constant (Disable and Grayed out or Enabled) wire to it. The problem is that the while loop on the block diagram of workspace controls only executes when the control is "clicked", much like an Event structure. The result being that when a test is active the control isn't disabled until it is "clicked" and once disabled any subsequent clicks are ignored so it remains disabled regardless of test activity. Enabling and disabling a control is pretty basic functionality. I can't believe this hasn't been encountered before. Does anyone have a way to do this or know of a work around?
The Case structure that contains the property node is inside the While loop. The problem is the While loop only executes when the custom control (modified Boolean control) is "clicked". I verified this by wiring an indicator to the loop iteration terminal. It incremented only when the control was "clicked".
I resolved this issue by placing a parallel while loop on the block diagram of the control. This loop executes constantly and contains the enable/disable logic. It works exactly as I wanted.
