Creating Constant definitions across all sequence files in a VeriStand project

[RGSchmidt]

Hello,

I am trying to figure out the best way to create the equivalent of constants such as Active = True or Heartbeat = 1 to use in all sequence files within a given VeriStand project.

I have at least 2 different projects where the polarities of Active are different and I want the code to be more easily readable hence the use of a variable / constant. 

I am using TestStand for sequencing all of the real-time VeriStand sequences and could pass it in as a parameter but this would lead to some sequences having upwards of 30 passed parameters which is insane to manage. I have created a YAML file that I read these setting from in Python and created access methods that TestStand uses to read them into FileGlobals but I see of no good way to do anything equivalent in TestStand. I thought of using User Channels but they only allow numbers not Booleans for the default values.

There has to be a better way to handle this like you can in C/C++/Python (but not even this is supported in the VeriStand python library).

Any help on how you may have handled a situation like this would be appreciated.

Thanks

Randy

[joshe]

I have used "user channels" for BOOL data, just put 1 or 0 in them for defaults.  You can also created a Profile that sets up what you need and have that called when VeriStand is deployed (there is a check box for "at startup" in the profile level.

[RGSchmidt]

That is the approach I was taking but still need to create local variables in each sequence file linked to the User channel ... and adding description that this is meant to be used as a Boolean when setting them up as 1 or 0 ... not as clean as I would like but usable

Thanks

[joshe]

Another thing I saw a co-worker do is to upload a ascii file to the RT and have a model read in parameters from it.  On the flip side, since you are using Test Stand you could write a little Labview using the VeriStand API to read a file and write your parameters.