Issues while executing Labview code with DLLs (.net adapter)

[Arvydas]

Hi everybody,

I have one issue with NI Teststand 2016 and have no clue what's the problem. Short summary:

I have a .seq that has only one vi. where it is used three calls to dll functions. This .dll is developed by customer and is used to communicated with product via interface program. The thing is that everything works ok in Development mode, if  i change Labview adapter to use Run time i get no errors, but this .vi gives me a negative (false) result that connection to UUT was not successful. Why there is a difference between development environment and run time? Please help.

[t@nim@t0R]

@Arvydas, 

If you make your code into a LabVIEW executable that includes the dlls, do you see the same behavior? 

[Arvydas]

@ t@nim@t0R,

Thank for the reply, but a vi in development environment and as executable works fine. In the dll i am connecting to application using "Main computer" name as "localhost". When i build an exacutable .alias file is created with this info. I was wondering maybe this name is different somehow at Teststand when labview adapter is changed to Run-time? Just a guess, but still i am out with things what to check.

[t@nim@t0R · Accepted solution]

Just to clarify, what behavior do you see when you use the executable in Teststand with the runtime environment selected? 

Also, it may be useful to you to refer to the following document: 

How TestStand Interacts with LabVIEW Application Instances

[Arvydas]

Ok  i will check the doc. By the way when i run vi as executable in teststand everything works ok, but in that i case i need somehow to extract reference from that vi. 

[Arvydas]

Huge thanks, your link helped. It is fixed now. 🙂 

[t@nim@t0R]

Great to hear! 

Can you post what you did to reach the solution, so that future users who may reference this forum can use your knowledge?