Is there a way to add to the existing values in a container when a LabVIEW prototype (cluster) changes?

[Ray.R]

Is there a way to add to the existing values in a container when a LabVIEW prototype (cluster) changes?

I have a cluster with 90 values..  ninety!  yes that many.

Change one bloody value and the prototype changes in the TestStand step...  Reload the prototype and guess what happens??!!??

All the bloody values get reset to defaults!  AAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGHHHHHHHHHHHH!

If it was in one place, I could survive the ordeal.  But I have to change bloody prototypes in many places!!!!

more AAAAAAAAAAARRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!!!!!

I can't even copy the bloody values!!!!!!!  AAAAAAAAAAAARRRRRRRRRRRRRRGGGGGGGGGGGHHHHHHHHHHHH!!!!!!!!!!!!!!!!!!

Are there any tricks that I am not aware of, or have forgotten over the years, or...  ...   something??!!??!???!!

If there are none, I will have to post an improvement to TestStand..  I should mention I am using an older version (4.1).

😞

[j_dodek]

Hmmmmmmmmmmmmmmmm,

I am not not very famous with LV and its cluster types.

So no idea if this works (it works for DataTypes updates very well and a LV cluster is Data Type so.... maybe)

Make a copy of the step that has to be modified to an new sequencefile. 

Make modifications the in the copy.

Now you should have the same DataType Name but other contents in the container. Save it.

Normally there should be a message box that tells you that version has been incremented. - Accept it.

Set in StationOptions-File "Allow Automatic ...." to Never.

Open original sequencefile. Now the there must be a type conflict. Accept/Apply to all  "Use Current Loaded.."

You have updated the type.....

Hope this worked,

Juergen

[Ray.R]

Hi Juergen,

I am not working on the TestStand project at the moment, but what you recommended makes sense.  I think my problem was the setting in the StationOptions.

I've been away from TestStand for a while, but I do recall the "Use Currently Loaded..." selection.

I will let you know if this worked.

Many thanks,

RayR

[Ray.R]

The issue was actually the adapter setting from Development to using Run-Time Engine.

Doesn't make sense to me, but that was the cure... 

Strange

[Ray.R]

My last post was not entirely true..  The real solution was to simply save the vi again.  Although that vi was not recently modified.  It was OK with the development adapter, but not the run-time engine for the sane version of LabVIEW..

Strange... 

... and annoying...