Hey Bill,
Thanks for clarifying. The first option really isn't an option. It's more of an explanation that the steps should always use the StationGlobals as parameters if when you Specify the Module you set the parameters as StationGlobals.WhateverVariable.
It's important to note the 4 actions of creating a step-
1- Choose the Adapter (LabVIEW, CVI, C++ etc...)
2- Choose the StepType (PassFail, Action, Numeric Test, String Test etc...)
3- Specify the Module (point the step to the code you want to call)
4- Set the step properties (preconditions, post action, expressions, run options etc...)
In your case you would choose the LabVIEW adapter, Choose the StepType, Specify the Module to point to some LabVIEW code (I'm assuming these are prewritten), and then set some step properties. Now the issue here is that you want TestStand to automatically assume that you want to pass StationGlobals as parameters to your step. This is done in step 3 of the process. However, TestStand cannot assume what to put as the parameters to a LabVIEW module because most LabVIEW modules have different inputs and outputs. Do all your LabVIEW modules have the same inputs and outputs?
Option1- If you have TestStand 4.0 or later then you can use Templates. I really like this new feature of TestStand. It's very handy because all you do is follow the process to creating a step and then drag that step to your templates window. Then whenever you want to place a step with the same or very similar setup just drag it from your templates onto your sequence. This way you don't have to go through the entire process every time. And the parameters will remain the same.
Option 2- So for the 4 Test StepTypes (Pass/Fail, Numeric Limit, Multiple Numeric Limit and String Value) and the Action step there are something called Code Templates. A code template is simply a skeleton piece of code that gets created when you click the create VI button in your specify module tab. This is not new in TS 4.0 but an older feature as well. These templates are stored here: C:\Program Files\National Instruments\TestStand 4.0\CodeTemplates\NI and are managed by the StepType properties. I recommend copying them to your C:\Program Files\National Instruments\TestStand 4.0\CodeTemplates\User folder before editing them. As this is the proper way to do it and you don't lose your default templates. TS will always look in the User folder first. If it's not there then it will go to the NI folder. The names of the folder are pretty intuitive. Basically you have DefaultLabVIEW. Which is for the Action Step Type. Or you have NumericLimitLabVIEW which is for the Numeric Limit Step Type. Whichever type you want to change the template for then you open that folder and edit the LabVIEW skeleton code to resemble what you want with the correct inputs and outputs. Then you save it and go into TS and go to your type palette. No the problem I have here is that you cannot change the parameters for the default NI step types. So you will have to copy the StepTypes and create your own. Trust me though- you don't want to dink around with the NI defaults. It's messier later. So when you create your own step type you can then edit the properties by Right Click-> Edit Properties. There should be a Code Template tab. you can set up everything including the parameters for that code template. So then the next time you insert a step and click the create VI button from the Specify Module tab it will automatically contain your own parameters. In your case StationGlobals.
Ok so it's obvious that Option 2 is not ideal. But if you have TS 3.5 or older then it's the only way other than copying and pasting steps. If you want more info on Code Templates go to the TS help and read about them. Or let me know if you have specific questions.
Hopefully this info will help you out and please let me know if you are confused or need more info.
Best Regards,
