11-10-2017 05:46 PM
Get into the habit of creating an initialization state where default values and appearances (show/hide, enable/disable etc) for various controls/indicators are set.
This state should be the first thing to run when your program starts (maybe after some hardware safety checks if you have those). Since it is a stand alone state, it can be called whenever you want to (say after you abort a simulation mid-process). I am using the term "abort" here rather loosely, not referring to the "ABORT EXECUTION" red stop-sign.
11-13-2017 11:54 AM
By "Stops" I mean that the execution state goes to 'Idle'.
11-13-2017 11:59 AM
@sunson29 wrote:
Hi Paul,
I tried your VI, thank your for that. I think it reset after the program finished all process, right? Btw, it was not working, I do put it one front panel. But it seems that vi will keep loading something if I abort the execution. so that I have to wait for 3- 5 sec to run it again.
I don't observe that behavior. It works fine for me.
To see where the action is look at the 'Exec State Change' case in the Facade.vi
11-13-2017 12:04 PM
Thank you!