LabVIEW
Asynchronous VI Call on RT
I am developing a large RT application with an embedded UI.
It takes a long time to compile so the development cycle is slowing down as the application needs to be rebuilt to debug things.
We are having to build the application to debug because running the RT code from LabVIEW is handling asynchronous calls differently. As an example asynchronous VI's are not visible in subpanels when running from LabVIEW but are fine when run as an embedded application.
I implement calling a VI asynchronously with this general structure. If I run this from LabVIEW the async subVI is running but its FP is not visible in the subpanel.
I am also having issues with named queues being recreated in the async VI rather than using the one which has already being created in the calling VI. This makes me suspect that when being run from LabVIEW rather than as a standalone RT application the async VI's are running in a different memory space, maybe even on my development machine rather than the RT target.
Can anyone explain what is going on under the hood here and offer any advice as to how I can alter this code to run via LabVIEW on my development machine to speed up debugging.
