Quantcast
Channel: NI TestStand topics
Viewing all articles
Browse latest Browse all 6563

Dynamically calling a daemon or actor VI in TestStand

$
0
0

Hi all,

 

The context:

  • I have a non-reentrant VI that needs to run in parallel of a sequence
  • This VI is opened and closed several times during testing.
  • I'm closing the VI by sending it a queued request such that it closes itself.

 

It seems to me that there are a couple of ways to launch the VI:

  • Have TestStand call a LabVIEW VI that launches the dynamic VI. This could be via the ACBR node or an invoke node using a static VI ref.
  • Use the "Run VI Asynchronously" step type in TestStand.

Right now I'm using the "Run VI Asynchronously" step. I'm not using the "Reserve Loaded VIs for Execution" option, and every once in a while I get the "TestStand Sequence Editor has stopped working" crash.

 

My questions:

  1. With respect to memory management, what's the best way to implement my use case? Is it better to have LabVIEW make the dynamic call, or have TestStand make the dynamic call?
  2. What's the difference in how the memory management works between these two methods?

Thanks a lot - any suggestions are much appreciated.

 

Mr. Jim


Viewing all articles
Browse latest Browse all 6563

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>