09-02-2014 02:29 AM
Hi,
I have a Case structure within an Event Structure which actuates when there is a value change for a button. But this button is located originally in another event structure. So when I handle the button during execution, it remains latched even after the case structure is executed. I realised the problem was because I had linked the button from another event structure. Is there any way I can release this latch after the execution of the case structure?
Solved! Go to Solution.
09-02-2014 02:46 AM - edited 09-02-2014 02:47 AM
09-02-2014 02:51 AM
Hello GerdW,
Yes I tagged you in the message. I don't want another button. I want a single button which can be called to different Case or Event structures. Is that possible?
09-02-2014 02:52 AM
09-02-2014 02:59 AM
Hi GerdW,
Could you tell me how that is possible. The Case structure within another event structure is handled by this button. Every time the Case structure is actuated and ends, the button is still latched on. That wouldn't happen if there was a seperate button in this Case structure but I want a single button that can handle several case structures. Can you tell me how to do it?
I tagged you with your Alias name.
09-02-2014 03:02 AM
Hi rvkamat,
I tagged you with your Alias name.
You tagged your own message with my nickname. Why did you do this?
The Case structure within another event structure is handled by this button. Every time the Case structure is actuated and ends, the button is still latched on.
Easy solution: put all case structures in just one event case. You might even combine them into one case structure…
It is not recommended to have more than one event structure in a VI. It is not recommended to have several event structures looking for the very same event…
09-02-2014 03:12 AM
Hi GerdW,
Sorry, I thought you are supposed to tag people who can help you out. Lesson learnt
Sadly, I have several event structures with Case structures within them and I can't change it since that what my Boss wants. I guess I might have to use a new button. Thanks!
09-02-2014 03:19 AM
Do you mean you have several event structures in one vi.
If it is so tell your boss that this not the right way of doing things.
09-02-2014 03:32 AM
why would you need several event cases? what is the reason for that? My guess, you would like to have several cases run simultaneously. But multiple event cases are not the solution.
regards,
yan
09-02-2014 03:44 AM - edited 09-02-2014 03:46 AM
Its apparently easier to automate scripts when you have an event structure. So for each automated script an event structure can do the job just by choosing on the front panel the respective event structure. Its easier to debug or modify as well if something goes wrong since each automated script is within one event structure. I don't know. I am just writing my Thesis on creating a Stepper Motor VI with built in Signal Acquisition and Injector Control.
BTW I found the solution. Just used the property node for the button and Changes its Value property back to false after it was done.