Hey Sam,
What I understand that you are trying to do is send in parameters to your sequence from the operator interface.
First of all, this is not typically a good idea due to the concept of how operator interfaces are intended. Typically, an operator interface should be modular in nature so that the same operator interface can be used with any sequence. Similarly, the sequence should be able to function successfuly in different operator interfaces. If you specify parameters to be sent in from an operator interface to a particular sequence, the operator interface no longer is modular and the sequence is dependent on that operator interface.
That being said, I would suggest that the best (and easiest) way to get parameters from the user into the sequence is by using a step to get the information. For instance, a message box could pop up to ask the user for information or you could call an external code module from your sequence that gets the data.
If you absolutely need to send in data from the operator interface, however, you can do this using custom user interface messages from the sequence. Essentially, what happens is that the TestStand engine sends out a message to the operator interface to which the OI can respond with the parameters. This is done using the function PostUIMessageEx and then creating a callback function to handle the events from your operator interface.
Finally, you could always use a file as a pipe to send in data into a sequence file execution.
Hope I answered your question.
Thanks,
Andy McRorie
NI R&D