Asynchrone VI execution doesn't work when built into executable

[Tofr4n]

Hi everyone,

I was trying to open a SubVi multiple times in parallel execution by calling this SubVi asynchronous from top-level VI (see added example).

If I run this from the development environment it works. It doesn’t work if I run the builted application.

Any ideas?

I'm on LabVIEW NXG 3.1.0

[fblerg]

Hi Tofr4n,

I will test with LabVIEW NXG 3.1 later but what error are you seeing when you run the executable? 

Thanks,
Frank

[Tofr4n]

Hi Frank,

No error massage at all. If I run the executable it just didn't opening the SubVi.

[fblerg]

Ok, thanks for the info. I am seeing the same issue in LabVIEW NXG 3.1, and investigating a little further. Would something like a sub-panel work instead of the separate window? 

Thanks,
Frank

[Bob_Schor]

For what it might be worth, this has worked in "classic" LabVIEW since at least LabVIEW 2012, and continues to work in the current versions of LabVIEW.  LabVIEW Next Generation is where NI is (gradually) migrating LabVIEW, but it is still in "development mode".  Is there any reason not to build your application in the version where everything functions without (too many) problems?

Bob Schor

[Tofr4n]

In general, I like to develop on Labview NXG and until now, I haven’t too many problems. For sure, maybe on some point the functionality of Labview NXG isn’t enough to go beyond and I have to go back to classic Labview.

But otherwise I like to push the issues that I seeing, to make Labview NXG moves closer.

Thanks for your help!

[fblerg]

Hi Tofr4n and Bob_Schor,

Thanks for the feedback. This functionality should work in NXG 3.1, and it is a bug. I have filed a bug report for this in 3.1. I was suggesting the sub-panel as a work around for the immediate future. I am tested this with a preview version of NXG 4.0, and this functionality does work in 4.0. 

Thanks,
Frank