NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

TestStand 2014

Solved!
Go to solution

Hi,

I need to call a VI develop to use NI 6001 DAQ module. The VI was developed in Labview 2015. I compiled it in LV 2014. I installed latest DAQMx, 2014RTE, 2014RTE SP1 on target computer. When i try to call the VI, Teststand tries to search for some other VI's in Teststand's sub folders?

Can anyone tell me some rule of thumbs to call VI's from Teststand?

0 Kudos
Message 1 of 12
(4,274 Views)

Hi hedehodo,

 

I recommend checking the following links for best practices with importing LabVIEW code modules:

Best Practices for Code Module Development

On the LabVIEW Adapter

 

0 Kudos
Message 2 of 12
(4,239 Views)

Thanx for prompt reply but these general informations actually don't help. I already passed through  them and couldn't figure out the solution. Somehow Teststand doesn't recognise the VI but why?

0 Kudos
Message 3 of 12
(4,220 Views)

What TestStand system have you got deployed on the target system, is it the full version or a runtime version?

What errors or being displayed?

Regards

Ray

0 Kudos
Message 4 of 12
(4,217 Views)

Hi Mr. Farmer,

We're working on Teststand 2014 development at the moment and we'll deploy deployment licence if we can overcome this issue. I provided some screenshots at my previous mail. The problems occurs if we use our dll for RS232 communication as far as i debugged. But in general .net dll's are problematic

0 Kudos
Message 5 of 12
(4,213 Views)

Hi hedehodo,

 

I'm not sure what you mean when you refer to screenshots in a "previous mail", but if your program is having trouble locating a .NET dll I'd make sure you're following the guidelines in this article

0 Kudos
Message 6 of 12
(4,203 Views)

Maybe this article

might help

 

Just a note, it not wise to have two threads running reporting the same problems;

previously reported problem

 

regards

Ray

0 Kudos
Message 7 of 12
(4,192 Views)

Hi Ray,

That article is about how Labview handles .net calls but we don't have any Labview component in our Teststand flow. But if you mean anything behind the scene maybe that may help.

Actually i am trying to understand how is Teststand handling .net 

0 Kudos
Message 8 of 12
(4,187 Views)

ok now I am confused.

[I need to call a VI develop to use NI 6001 DAQ module. The VI was developed in Labview 2015. I compiled it in LV 2014. I installed latest DAQMx, 2014RTE, 2014RTE SP1 on target computer. When i try to call the VI, Teststand tries to search for some other VI's in Teststand's sub folders?

Can anyone tell me some rule of thumbs to call VI's from Teststand?]

Above was your original question?

So the problem is???

regards

Ray

0 Kudos
Message 9 of 12
(4,184 Views)

Hi Ray,

As per the article you sent has a .net content i thouht you're replying one of my other subject about .net dll crashes which is still open

Actually the VI calling issue isn't also solved yet, but i compiled it as a dll and now it works.

0 Kudos
Message 10 of 12
(4,181 Views)