04-16-2015 11:57 AM
@AKA_TG wrote:
AS others have said
One thing about AE's is that they are just VI's
So if the caller goes idle LabVIEW will close all resources in the AE, including any references.
This also happens when you run the AE by itself without a caller, although certain references can stay open from one execution to the next.The thing is LabVIEW always removes references from memory once it establishes they are no longer needed. Its something to be aware of when stuff like this happens.
Yeah, I often make my DAQ code into AEs and I can initialize, configure, set variables, collect data, etc. all by just selecting the actions and running though them without a MAIN VI so the DAQmx tasks stick around BUT apparently LabVIEW closes file references. Live and Learn I guess. Thanks!
04-16-2015 12:16 PM
I don't think I really earned this kudo.
Perhaps I can trade it in for a candy bar 🙂
04-16-2015 12:30 PM
@AKA_TG wrote:
...Perhaps I can trade it in for a candy bar 🙂
No need: The parent class of a Kudos is already candy bar.
04-16-2015 12:39 PM
@AKA_TG wrote:
I don't think I really earned this kudo.
You don't deserve a kudo, I like that, have a kudo.
(BTW thank you OP for the kind kudos)
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord