10-27-2016 08:52 AM
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?
Solved! Go to Solution.
10-28-2016
04:34 PM
- last edited on
11-30-2024
05:42 PM
by
Content Cleaner
Hi hedehodo,
I recommend checking the following links for best practices with importing LabVIEW code modules:
Best Practices for Code Module Development
10-31-2016 01:58 AM
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?
10-31-2016 02:10 AM
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
10-31-2016 03:35 AM
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
10-31-2016
03:07 PM
- last edited on
11-30-2024
05:42 PM
by
Content Cleaner
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.
11-01-2016
02:45 AM
- last edited on
11-30-2024
05:43 PM
by
Content Cleaner
Maybe this article
might help
Just a note, it not wise to have two threads running reporting the same problems;
regards
Ray
11-01-2016 02:58 AM
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
11-01-2016 03:50 AM
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
11-01-2016 04:02 AM
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.