TestStand Setup Script or Other

[TonyJ]

On the production floor we distinctly have two setups we use with TestStand.  We have a normal production/operator mode and an engineer/administrator mode.  Is there an app within TestStand or other which will automatically make numerous TestStand changes instead of going to multiple configuration menus.  These changes occur between operator and engineer modes. 

[snowpunter]

You can restrict/enable/disable functionality in TestStand based on user login privileges. See chapter 7 of the TestStand Reference Manual.

[TonyJ]

Security is not my aim or intent.  I want a way to make changes through a script instead of having to always go to numerous menu's.  This way nothing is missed and all my boxes I want checked or unchecked are where they need to be without having to review all of our settings.  Does this make sense?

[snowpunter]

You can run a script to setup a station based on the user type.

[TonyJ]

How would that be done?  Does TestStand have its own scripting language?  How would I check or uncheck a box for example "Enable Tracing"? 

Tony

[snowpunter]

TestStand has it's own API. You can find more details on it in the documentation. The specific value you're looking to set is called StationOptions.TracingEnabled

[Jacob_R]

Like snowpunter mentioned, you can use the API and the TracingEnabled property.

Drop down a Statement and use the following code: RunState.Engine.StationOptions.TracingEnabled = True

Or you can use an action step with an ActiveX/COM adapter.

[TonyJ]

We're getting warmer.  Is there something I can use outside of TestStand to make these modifications?  I never thought of using an action step.  I suppose in my PreUUTLoop I could come up with a dialog box that asks the user to select one or the other.Can you comment on the question above?  Thanks.

Tony

[snowpunter]

You can do this in a number of locations:

• Override a model callback in your client sequence file that checks user privledges and sets the tracing accordingly
• Add a step in your process model to do the same
• Add a step in the FrontEndCallbacks.seq that will do the same when the user logs into TestStand

[TonyJ]

Ok, getting a bit warmer here.  Can you elaborate more on the FrontEndCallbacks.seq? 

Tony