Updating a LV cluster reloads defaults in TestStand

[MJR]

Hi there,

I have a LV cluster and I have already defined all of the cluster variables in TestStand through the Specify Module window. I'd like to add a few new elements to this cluster in LV but when I do and reload the prototype in TS the cluster I changed loses all of my previously set values and defaults all of the elements. Is there a way to preserve the definition of the elements when I update the cluster?

Regards,
M

[herosphro]

M,

Unfortunately there is no way to force the Module settings to retain the previous values when you redefine a cluster.  If you notice when you reload the prototype the old definition is moved to the end of the list and marked as obsolete, and a new definition is in its place.  TestStand recognizes the new cluster replaces the old one on the connection diagram but it cannot make a guess as to map the existing pieces of the cluster to the new one.  Therefore it completely loses the values you had set prior.  There are ways to make remapping easier, like creating clusters or using the 'Create Custom Data Type' button in the parameters window but there isn't a way to change this current behavior.

[Henrik_Molsen]

John B

Does this still apply to Teststand 2012 even though we now have the tool Update VI Calls?

[Haagen-Dazs]

Hi hmo,

According to my tests the Reload VI Prototype button resolves this issue in TestStand 2012. I not only added to the cluster but completely rearranged the cluster and everything updated correctly. Even when I completely destroyed and rebuilt the cluster from scratch TestStand was able to update correctly. There may be some corner cases when reloading does not work but it seems that this button solves the problem of VI clusters changing.