NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Can ASAM XIL steps for Wait for State use a local variable

I dropped an ASAM XIL step Wait for State with a state of Finished. The Wait Timeout (s) variable is dynamic based on the test conditions that I load in a previous step and is calculated into Locals.StepTimeout. Whenever I try to use the variable, it gives me an error that it is not a valid number. I have looked at Properties -> Run Options and do not see a way to have it use a variable. I do not want to use a pre-defined number since the value is dynamic. I also do not want to use -1 since it could cause the sequence to hang indefinitely if VeriStand hangs.

 

I am using TestStand 2023 Q4 32-bit with VeriStand 2020 R6 32-bit. Unfortunately, I cannot upgrade to TS 2024 Q4 since it will not load the ASAM XIL steps palette or upgrade VeriStand until I rebuild the entire HIL system.

 

Any assistance would be greatly appreciated.

0 Kudos
Message 1 of 2
(215 Views)

I was able to solve this by using the pre-condition. We cannot use the Property Loader since it is too limiting. I use YAML files that are read by Python into TestStand containers so that I have the time required for the test which I then double to avoid any race conditions. I am able to use an expression in the pre-condition to set the Step.Timeout variable.

0 Kudos
Message 2 of 2
(174 Views)