teststand: programmatically select a page at the settings tab view

[aSquared]

Hi, 

(LabVIEW 2013 SP1 and Teststand 2014)

After configuring some properties of the custom step using his Edit substep, the Step Settings tab page is Configure....

I would like the page to be Module.

(see image attached if I'm not clear what is the step settings tab)

Is that possible ?

(I am not interested in the Dialog box of the module (specify Module method)) .

Amitai.

[Norbert_B]

Amitai,

if i understand your request correctly, this is not a functionality NI TestStand provides. The window of the Edit Substep module of steps does not embed into the TS SequenceEditor.

If you want to remove the Module tab, you can disable the property "Specify Module" in the step type definition (Disabled Properties tab).

Norbert

[aSquared]

Hi Norbert, 

And thank you for your prompt reply, 

I just find myself always changing manually to the Module tab (from the Edit tab) after running the Edit substep to configure some properties of the step.

and I was thinking to automate that too.... 

If there is no direct way, there might be some workaround.

Amitai.

[Norbert_B]

Amitai,

sound like you want to have a custom pre- or post-step substep module instead of a Step Module to perform tests. Use the edit substeps to modify the parameters and settings of tha pre- or post-step substep module.

Recommendation: Do not use a designated module in custom step types! Use the "None" adapter as designated adapter.

What properties are you modifying in your module configuration tab?

Norbert

[~jiggawax~]

In the step definition properties on the Disable Properties tab you can check the Specify Module.  This will get rid of the Module tab, I believe.  There are probably others on there you need to check like Edit Module Prototype.  Also, designate a specific Adapter on the General tab and possibly a Default Module if applicable.

Then in your Edit Substep you can modify the TS.SData.ViCall settings that set the parameters and such for the step module.

In this case you do not need to use Pre and Post substeps.

[Norbert_B]

Sorry jigg for contradicting here.

Using a designated module is NOT recommended as the step instance later on copies the configuration which is part of the step type definition. One of this configuration data is the path to the module.

If you modify the step type to load a different module it will only effect step instances you create AFTERWARDS. You can, of course, select "Apply to all loaded instances of this type" when performing the modification. But how can you ensure to have ALL instances loaded????

So recommendation is:

Always use pre- or post-step substep modules if you want a custom module to be called by TS during execution. Use "Designated Module" only if the user shall have the option to replace the module by himself!

Norbert

[~jiggawax~]

That's a good point Norbert.  I was making the assumption that the module and stuff would change through the Edit Substep.