How are RunState property values assigned and can I add a step?

[BCH63]

I am assuming that Test Stand must run a sequence that loads up the RunState properties when a sequence is loaded.  Is that accessable to add a step to it?

I would like to add a steps that would store the root of RunState.SequenceFile.Path to a StationGlobal and use that station global as the root in the path for all other sequence files.  So that I can have different versions of my test files in whatever root directory and they will be able to be found.  I frequently run multiple instances of Test Stand on the same machine and I would like to be test multiple targets as well.  I'm open to other suggestions of how to accomplish this.  I'm sure someone else wanted to be able to do this.

Thanks

[Basil-B]

Hi BCH63,

Thanks for your question. I would caution against modifying the process model, and I think that the runstate is populated by the teststand engine upon execution (I will double check on this), but I think simply writing that path to a station global within your sequence file would give you what you are looking for. Just use a function step that writes the value of the parameter to a station global container. Please let me know if I have missed something or haven't understood your intent.

[BCH63]

Thanks for the response Basil.  I did that about that and every test sequence starts with a sub-sequence that opens a comm port and establishes comms with our controller.  I could put a step in that sequence.  I was just figuring that Test Stand must be using its own sequence to populate those run state variables and it might have been cleaner to just add the necessary steps in there.  But as I'm looking at that sub-sequence again, I'm not seeing a problem with adding steps in it.  Initially, I was thinking I'd have to have that sub-sequence always live in a defined location, but that's not true as long as I set my own variable immediately.

Thanks again,

Bryan