Refresh all labview calls in a Sequence file after VI change

[OpenECU]

Hello,

I am not sure if this is how Teststand is supposed to work, or is there a workaround for this.

I have a VI that I eventually add enumerated values to a drop down list on the front panel. When I do so, then I will not be able to run any sequence that calls this VI unless I reload the VI. This will not be a problem if I have to do it once or twice, but I am using this VI all over the place and it becomes tedious in this case.

Is there a better way to automatically update all the VI calls in a sequence file at once ?

Thanks,

Sam

[PhillipBrooks]

Have you tried Tools >> Update VI Calls... ?

You should be able to update the enum by setting the "Reload Prototype if Changed" checkbox.

[Teds · Accepted solution]

Older versions of TestStand do not contain the Tools -> Update VI Calls... feature.

See the following instead...

http://zone.ni.com/devzone/cda/epd/p/id/5267 

Thanks,

PH

[OpenECU]

Thanks. The >Update VI under >tools worked just fine.

[jparikh]

I have TS 4.2.1 and don't see the Tools-> Update VIs option.  Am I missing something in setup?

[OpenECU]

It should be under Tools > Update VI Calls. I have the same TS version. Maybe the tool is missing from your installation.

[bwv1043]

Is "Update VI Calls.." available on a deployed version?

Thanks

hello from chicago

[Michael_W.]

Hi hellochicago,

I beleive this depends on which UI you are using to run the sequence.  Why are your VIs changing on your deployed system?  It may be possible to use the programmatic method mentioned above.

[bwv1043]

Michael W,

I thought that once a test application has been deployed with TestStand along with source module VI's, I could update individual VI's on deployment target without going through TestStand deployment utility.  I thought I could simply copy the updated VI's to the target folder that contains source module VI's.  This turned out to be not true.

This article says the deployment utility does more than simply copying VI's (http://digital.ni.com/public.nsf/websearch/49A380D75C705AE1862575DB0005503D?opendocument&Submitted&&node=133020_US ).  Therefore my concept of updating VI's on target machine by simple file transfer would not work because TestStand would lose dependencies information between test sequence and VI's (and their sub VI's).

Would test sequence still run on deployment machine if the change in VI is limited to code inside the VI (meaning, inputs and outputs don't change)?

Thanks

Steve

p.s. I was going to start a new thread with my question but I explained here since you asked why I would update VI's on deployed system.

[Michael_W.]

Hi Steve,

I don't beleive you'll be able to just copy VIs over, even if the inputs and outputs remained the same.  Every reference in a SubVI is rewired as it states in the KnowledgeBase you mentioned.  Therefore, if your VI calls any SubVIs, the deployement utility will have changed these references which means replacing a VI directly will break the chain.  However, I'm not completely sure if this applies to all SubVIs or just your SubVIs.