TestStand prompts to Update VI calls even after doing it programatically

[Vikas_K]

Hello all,

I know this question has been asked a few times already and many have accepted using "porgramatically updating VI calls" as the solution.  However, we are having problems even after doing that a few times!

Our application uses VIs that are used as wrapper functions for calling a C# DLL, which in-turn calls a C++ DLL.  The VI calls were not a problem until recently, when we decided to standardise the folder path structures. We see that everytime we launch TestStand and click on the step calling a VI, it prompts the VI to be re-loaded, even though none of the VIs have been changed.  We went ahead and used the programatically update VI calls method to reload the prototypes and everything seemed to work fine, until we closed TestStand and reopened the *.seq file.

We have ensured the Search Folders are set correctly for TS to find the LV VIs but nothing seems to work. We can reproduce this on 3 separate PCs.

Any ideas what could be the problem?

Thanks,

Vikas

PS: I am trying to create a small sample project to reproduce this and will upload it if I can.

[david.bolt]

Dear Vikas

I look forward to you attaching the teststand files. You are correct in the approach you have tried, however, please can you see the below Knowledge Base and see if this helps for now which will update the calls in TestStand. Many thanks.

How Can I Update All The VI Calls In A TestStand Sequence?

[Vikas_K]

Hi David,

Thanks for your reply.

I have been trying to reproduce this in an example seq with the same VIs with no luck.  We have modified the process model and also use SequenceLoadFile callbacks, so, I will really need to be able to reproduce all of this within the sample seq! I am still trying!

I have run the Update VIs a number of times and save the sequence, but with no luck. Teststand still reports the VIs have changed everytime I launch teststand and load the seq.  Also, to be able to deploy the system, I will be running LabVIEW runtime on the machine, which will not allow me to do the Update VIs from the menus!

And moreover, if I open one of the VIs in LabVIEW before I have clicked on any step in teststand, it does not show the error!

Regards,

Vikas