How to close a subvi programmatically

[aartjan]

And much appreciated. I will make me one of these for sure. I guess I wanted to add the remarks for completeness sake. I also appreciate people making the effort to make a document for people without LV 7/7.1.

[ian_fung]

Oops! My apologies 😛

Pls find attached for LV6.1

Regards

[mikeporter]

Something else you should consider is handing the errors properly. You have error clusters passing through, but they don't do anything...

Mike...

[BJD1613]

Like I said I build this really quick and didn't take the time to follow the guidlines that have been set forth.  If I were developing this for a project I would do so.  Overall it can be very flexible and can be called from anywhere.  The main point to get across is the LV2 style global to hold the reference.  This is what really makes it flexible.

[mikeporter]

I understand that this was a quick thing, but when you start handging titles after your name people start look to you for examples and guidance. So if they see you doing (or in this case, not doing) something they will think it's alright too. I hate to think how many problems I've helped people fix that came about because they were modeling their programming style after what they saw in the examples that ship with LV.

Mike...

[BJD1613]

Since when did the developer zone become a beauty contest... it is for us to help people out.  Most of us don't have time to answer questions as it is because of work and are just doing this to help promote LV and help new developers become better.  Here, my examples have been corrected... Sorry for any confusion. 

I am proud of my titles by the way... I am not boasting about my abilities...

[mikeporter]

I'm sorry if I offended you, it wasn't intended. The point is that the yellow bars by our names--and in your case the titles (which you have every right to be proud of) make us role-models, like it or not. That's just the way things are.

Mike...

[Gustep12]

Ian, thanks for the example, I found this really helpful.

I am working on a similar program, where the subVI is a continuous wavefunction generator which outputs to Ao - this is a case where there is no predictable "done" condition, so the subVI can't terminate itself. Instead, the main program determines when the wavefunction needs to be changed, started, stopped, etc.

Of course, I could probably keep the function generator code in the main VI, such as in a "wave function change" case structure. Then I wouldn't need to control a running subVI. However, I like having a stand-alone subVI for the wavefunction generation which I can run and test independently of the main code.

[ian_fung]

---

@Gustep12 wrote:

Ian, thanks for the example, I found this really helpful.

I am working on a similar program, where the subVI is a continuous wavefunction generator which outputs to Ao - this is a case where there is no predictable "done" condition, so the subVI can't terminate itself. Instead, the main program determines when the wavefunction needs to be changed, started, stopped, etc.

Of course, I could probably keep the function generator code in the main VI, such as in a "wave function change" case structure. Then I wouldn't need to control a running subVI. However, I like having a stand-alone subVI for the wavefunction generation which I can run and test independently of the main code.

---

Hi Gustep12,

It is great that it helped 🙂

And, what surprises me is that this VI(s) still helping after nearly 7 years since it was uploaded... lol Cheers!