NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

VI runs well in Labview2015 but wrong in TS2013 VI call

Solved!
Go to solution

Hello~

Firstly, I want to use MUXdll.dll in TS, but TS can't recognize them, I think it's has no library.

muxdll.png    

So I have to build LIN bus configuration VI by labview2015 and it runs well in lv, but when i call this vi in TS2013 with VI call, it can't perform it's function and show 2nd connection wrong message(the 1st message is in the sequence structure before this one) I write in the vi:

ScreenHunter_1.jpg

my VI call is:

ScreenHunter_2.jpg

It seems i lost some steps before doing the VI call? what can i do for this?

 

0 Kudos
Message 1 of 3
(2,920 Views)
Solution
Accepted by topic author johnnnywang

Hi Johnnnywang,

 

First thing you can try to to ensure that TestStand 2013 is calling LabVIEW using the development enviroment. You can configure this in Configure >> Adaptors >> Configure >> LabVIEW Development System. This should call the VI the exact same way as when you run it in LabVIEW. If you do not get the error at that point, then there is probably an issue when trying to call your VI in Run-Time. 

 

If the error still occures, then there could be an issue with TestStand calling the VI. If that is the case, can you break the VI down to it's least reproducable case? 

 

Respectfully,

Ben H.
Systems Engineer
National Instruments
0 Kudos
Message 2 of 3
(2,887 Views)

Hello benthere:

     thanks for your reply, I tried to change the configuration of the adapter, wrong message remains. then after i add a boolean value to show the result in the vi, the message dissapeared in calling with default TS labview adapter configuration.

I still don't know why but issue removed fortunately.

Thank you anyway!

ScreenHunter_3.jpg

ScreenHunter_4.jpg

ScreenHunter_5.jpg

0 Kudos
Message 3 of 3
(2,883 Views)