06-02-2010 07:02 AM
Hi PCT,
Sorry for the delay...it was Memorial Day. However, my suggestion is to use the Latch until Release Mechanical Action and put the Booleans inside the Timeout case. I have yet to test this out though....
06-02-2010 06:24 PM
The webpage at http://zone.ni.com/devzone/cda/tut/p/id/11123 warns against setting Boolean controls to latch mechanical actions:
"One important note: For boolean controls on the front panel, they must be set to a switch mechanical action. Creating booleans that use latch mechanical actions will lead to improper behavior in NI VeriStand, and will result in an error within the custom control."
So unfortunately this does not appear to be a viable option...
06-15-2010 12:46 AM
Hi PCT,
I have escalated this issue here at NI in Austin. I'll let you know what I turn up. Sorry for the delay and thank you for your patience.
06-17-2010 02:10 AM
Hi PCT,
After working with the developer we found that there is a race condition then using Boolean controls with this framework. The race condition can lead to the stuck action that you and I are seeing. We do not have a fix for the issue, but the quickest/easiest work around is to use numeric controls instead of Booleans.
06-17-2010 04:11 PM
Hello,
We may have found a work around for this issue. If you keep track New Value through an array and a shift register you may be able to accurately track the value change without rewriting the value. I have submitted screenshots which explain the changes that should be made to track the value change. Try that out and respond back with how it works.
Regards,
Andrew
06-20-2010 08:50 PM
Hi Andrew,
Thanks for providing the suggestion and screenshots.
I have given it a try and unfortunately it does not quite work. Certainly the boolean buttons will not get stuck now, but they are not sending the proper control value to the indicator.
I have attached the relevent files for your diagnosis. Basically you will see that the boolean indicator is not changing state when the boolean buttons are pressed.