NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

I need to keep a .net object open after a VI (test step) is closed

Solved!
Go to solution

I am creating a .NET object from an assembly which was provided by the manufacturer of a power source that we use for test.  The problem is that when I set up communications to the source in one VI, I then want to close that VI and go to the next step to retrieve parameters for the following test steps.  The problem is that when I close the first VI that established the object, the object and the connection to the ethernet port of the device closes.  How can I keep the object from deleting between step calls?

0 Kudos
Message 1 of 2
(2,882 Views)
Solution
Accepted by topic author mcfrenzy36

There are several options. I picked two for posting here:

a) Do not use a LV module but include the .NET assembly directly in TS. This may result in additional overhead in TS so this can be a "step back".

b) Change your LV module to be a FGV or Action Engine. Make sure that the VI is not unloaded between steps.

 

hope this helps,

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 2 of 2
(2,855 Views)