reseting controls & indicators when execution stops

[SID-SysEng]

halo everyone

I was working with a project that also using the boolean indicators along with it. my prob is when i terminate the execution using the stop button available in the panel,the boolean indicator remains in the same state as it in run mode.In case of off state there will not be any prob but in case of ON state it remains glown even after i terminate.Is there any solutions for this.... 

[Mathan]

Scan the stop button key press event. Create a local variable and give a false constant when stop button press occurs.

Hope this helps?

Mathan

Message Edited by Mathan on 09-24-2009 04:03 AM

[parthabe]

Wire a NOT gate function between the Stop button in the panel & the local variable of the Boolean indicator, kept outside the loop after the execution gets finished.

[Broken_Arrow]

The local variables are a good way to go, but if you have lots of things to "reset", try the code in the picture. This'll set Everything back to the default value after stopping.  This will work for you if your indicators are False by default (which they probably are).

This is an Invoke Node set to Class VI Server > VI > VI and Method set to Default Values > Reinitialize All To Default.

Message Edited by Broken Arrow on 09-24-2009 07:27 AM

[Dennis_Knutson]

And if you were to use the correct mechanical action (Latch When Released), you would not need any locals or property nodes. If you have this and are using an event structure, you just have to place the indicator inside the event.

Note: if you right click on the termination terminal and select Create Control, you automatically get a Boolean with the correct mechanical action.

[Broken_Arrow]

---

Dennis Knutson wrote:

And if you were to use the correct mechanical action (Latch When Released), you would not need any locals or property nodes. If you have this and are using an event structure, you just have to place the indicator inside the event.

Note: if you right click on the termination terminal and select Create Control, you automatically get a Boolean with the correct mechanical action.

---

Dennis,

It depends on how you interperet the OP's post, but I think he's referring to just having some bool indicators that don't get reset, not so much the fact that the Stop button itself isn't getting reset. Maybe we'll find out....

[SID-SysEng]

thank u all but wat i actually meant is the abort execution button is there any choice for that

[Dennis_Knutson]

No. The abort button should never be used as a normal way to stop your program. You can avoid the temptation by going to VI Ppoperties>Window Appearance>Customize and uncheck the 'Show Abort Button'.

[Broken_Arrow]

---

siddhu@sands wrote:
thank u all but wat i actually meant is the abort execution button is there any choice for that

---

"O... K... "

[thoures]

Rush,

I had something similar to what you described in an earlier version of a subroutine. I was able to generate some values after running the subroutine, push them to the main program, and re-initialize the subroutine when done. I used a flat sequence (re-initilize in the last frame). I am trying to use the same subroutine in an updated version of the main program and I'm finding that the values put out from the subroutine are always the default values, i. e., the subroutine is calculating the values I need but it is re-initializing before sending the values out.

I'm using the same techinique with another subroutine and it is working fine.

Any suggestions to what might have caused this.

Note: The original software was developed in 8.6 and now I'm using 2009.

Thanks