LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

abortion execution property node

Hi,

 

I'd like to know if it's possible I create a property node or something like that about abort execution. I would like to use this function, for instance, If I press the abort execution I can get any information from that (I want to use like a stop button, in another words, I need to finilize my VI, so if I press the Abort Execution I cannot do that).

 

Regards

 

Kito

0 Kudos
Message 1 of 22
(7,411 Views)
Check out the "Stop" and "Quit LabVIEW" items on the Application Control Palette. The help message tells you exactly what they do. Is that what you are meaning?
0 Kudos
Message 2 of 22
(7,398 Views)

Not quite understood your question,

 

Placing a stop button in the front pannel and wiring it to the conditional terminal of while loop in block diagram wouldn't help you?

Message Edited by Vsh on 11-24-2009 08:09 AM
0 Kudos
Message 3 of 22
(7,394 Views)

I already have the stop button implemented on that. What I want to do is when I press the abort execution button I can finalize my VI's. I wanna know if it's possible to create a property node from abort execution button.

 

Regards

 

Kito

0 Kudos
Message 4 of 22
(7,383 Views)

What exactly do you mean by Finalize your vi?

 

Yes you can abort a vi programatically using an invoke node.

 

see the attachment

 

Message Edited by Vsh on 11-24-2009 08:27 AM
0 Kudos
Message 5 of 22
(7,373 Views)

I think you can capture the abort execution event with an Event Structure.  Then discard the event (so LV does not stop) and call your finalize code.

 

Lynn 

Message 6 of 22
(7,370 Views)

What do you mean by "finalize my VI's"?

 

The Abort button has no property nodes associated with it.  It is strictly for debugging purposes, i.e. stop a program that may be stuck in an infinite loop.  It should not be used (nor even accessible) as part of a normal operating routine for a LabVIEW program.

 

If there is something you need to do in your VI after your stop button is pressed (the one you placed on the front panel and have programmed for), then you would place that in a sequence structure that doesn't execute until after your program's master while loop has stopped.

 

Another alternative is that you use a state machine architecture.  Once your Stop button is pressed, it causes your "Finalize" state to run.  And that state is the one that will actually stop your while loop.

Message 7 of 22
(7,364 Views)

johnsold wrote:

I think you can capture the abort execution event with an Event Structure.  Then discard the event (so LV does not stop) and call your finalize code.

 

Lynn 


 

I know you can capture the "Application Instance Close?" and the "Panel Close?" events.  I didn't think you could capture the Abort button event.  How would you create that event?  If you could, then that could effectively kill the Abort button (pun somewhat intended) as a debugging tool.  If the application caught the "Abort?" event and cancelled it, then the Abort button would become useless for trying to stop a runaway VI.
0 Kudos
Message 8 of 22
(7,358 Views)

Ravens Fan,

 

I think you are right.  I was thinking of "Application Instance Close?" and the "Panel Close?" rather than abort.  I did not have LV open to check.

 

Lynn 

Message 9 of 22
(7,343 Views)
There is really no use of (or point in) showing Abort button to the user as it is solely meant for debugging, only and only a developer of the vi must have access to it! and no other.
Message 10 of 22
(7,341 Views)