Disabling the Test UUT button in the TS Simple UI

[rimfire44]

I am using the Teststand simple user interface that ships with TS. I am seeing a problem that operators often do mulitple clicks on the Test UUT button which creates some odd and painful behaviour that generally results in having to kill everything.

I noticed that after you start the interface this button diappears momentarily until the operator logs into TS. I'd like to duplicate this so that once the button is pushed the first time it just hides until the test completes and the next test is ready to go.

Is this possible? The simple operator interface has lots of magical stuff going with those Active X controls that just go over my head. As far as I have been to go is to create an Enable method node but I haven't seen a Visible equivalent that is available on a standard control. I also am unable to figure just where I might put such a node. The main event loop in the vi seems very simple but there is some heavy duty stuff going on someplace.

Any hints?

[Teds]

Are you using LabVIEW? If so perform the following:  I did this on the TS 2012 and LV 2012.

1.) Right click on the button lableled 'ENTRYPOINT1] and select Advanced-> Enable State -> Disabled & Greyed

2.) Now in the code open the ConfigureSequenceFileView Manager.vi

In the first ConnectCommand invoke node,the one where you are setting 'CommandKind_ExecutionEntryPoints_Set' with Index 0.  This would be the Test UUTs execution entry point.

Set the 'opts' parameter to 0x4.  Here is the help on the options parameters:

• CommandConnection_EnableImage–(Value: 0x8) The connection sets the image on the connected control.
• CommandConnection_IgnoreCaption–(Value: 0x2) The connection does not set the caption on the connected control.
• CommandConnection_IgnoreEnable–(Value: 0x4) The connection does not enable or disable the connected control.
• CommandConnection_IgnoreVisible–(Value: 0x1) The connection does not change the visibility of the connected control.
• CommandConnection_NoOptions–(Value: 0x0) No options.

So my disabling the button in LabVIEW and 'ignoring' it via the 0x4 parameter should work.  Otherwise without the 0x4 it seems to ignore the LabVIEW setting that you actually disabled the button.

Good luck,

PH