TestStand 1.0.3 upgrade to 2.0 FileGlobals not visable

[Bill (Phoenix)]

Under TestStand 1.0.3, I create a set of data types to define my entire test environment. One example is:

AnalogDeviceType
DeviceType String
Device Number
DeviceIndex Number
ResourceName String
HighLimit Number
LowLimit Number

and then

AnalogDevices
NumberOfDevices Number
Configuration Array of Type
'AnalogDeviceType'[0..2]

I set up types like this for all the various types of instruments being used. Under FileGlobals, I then defined the different instruments being used. Under TestStand 1.0.3,
I could go to FileGlobals and edit all of the fields.

However, with TestStand 2.0, I can edit the Number
OfDevices but it will not expand the Configuration and allow me to edit those fields. I have been looking through the new features to see if I can determine if I need to set a property flag or something but have not been able to determine what needs to be done. Any thoughts on the subject?

Also, while I have found some books on LabVIEW 6i, etc. does anyone know good books TestStand.

[KittF]

There is a known problem that might be related to what you are seeing, however, you should still be able to edit the value you describe.

The known problem is that selecting Browse Sequence Context from the context menu of an array element or it subproperties will reulst in error -17308 if the array element does not have a name.

An example of an array element that does not have a name looks something like this

-MyCustomArray
|
|_[0]
|

while an array element that has a name looks something like this.

-MyCustomArray
|
|_["MyArrayElement"]([0])
|

You will arrays of named elements if you browse RunState.Sequence.Main for any sequence that has named steps in its Main step group.

By default custom data types you create do not have names. Therefore this
problem will always occurr in arrays of custom data types.

This problem has been corrected for future versions of TS.

The workaround is to select Browse Sequence Context on the array instead of the array element. You can then browse down to the element in the sequence browser.

However, this problem should not affect the ability to change the values of the array element. I have just created a custom data type as you have described (container of numbers and strings). I then created a file global variable array of this type. After selecting the first element in the tree view of the file globals, the contents of the element are displayed in the list view to the right. If I double click (or select Modify Value from the context menu) on any member of the array element, then I get a dialog box which allows me to change the value.

[Bill (Phoenix)]

Thank you for the information!

In case this was not clear, the sequence was originally created using version 1.0.3.
After installing 2.0, I noticed this problem. I did take your recommendation and try
to use the Browse Sequence Context, but still can not see the array elements.
Perhaps these data structures were not converted properly when 2.0 opened the
sequence. I do have both versions of TestStand running on my machine so that
I can switch back to something that works until I redesign the LabVIEW code to
use INI files rather than rely on TestStand.

[KittF]

I thought you ment that you did it in 1.0.3 and it worked and then you repeated the entire process again under TS 2.0 and it didn't work.

You say that you created the data type "AnalogDeviceType". I assume this is a container but perhaps this was not a correct assumption. The best way to resolve this problem is to include a TS 1.0.3 sequence that demonstrates this problem so that I can see exactly what you mean.

The only thing that comes to mind was the TS 2.0 change mentioned in the 2.0 releasenotes.pdf file:

TestStand 2.0 no longer allows you to create subproperties under a property that is not a container. If your application depends on the ability to create subproperties within non-container properties, you can set the NoSubPropertiesAllowedIn N
onContainers entry in TestExec.ini to False. However, to ensure
compatibility with future versions of TestStand, National Instruments recommends that you contact TestStand support for assistance in restructuring your application to avoid the use of this obsolete feature.


Obviously if you array element is container then this change would not apply.