04-27-2020 07:47 PM
Using TS 2016 64bit Mulitple Numerica Limit Test, doesn't appear to be able to set the Units programmatically.
I use this parameter and no change to Units -
RunState.Step.Result.Measurement["Measurement 0"].Units .
I click the option to set to "Custom" on Units is grayed out, why? I have not been able to enable Custom setting in the drop-down box.
04-28-2020 03:43 AM
Hi Richjoh,
Quick test for below method, it's working for me.
Thanks,
Ricky
04-28-2020 09:19 AM
Ricky,
It looks like your setup is not identical to what I use. I used Labview adapter. I also used RunState...Units to set Units your using a local variable.
04-28-2020 05:09 PM - edited 04-28-2020 05:12 PM
Just provide you a method to set units programmatically. No test your method. And why I use None adapter is because it's quick test, I don,t want to waste my time to create VI and I think they have the same results. : )
04-28-2020 05:28 PM
It turn out if the "Units" field is blank the "RunState.Step.Result.Measurement["Measurement 0"] etc. "Units" doesn't exist.
If the Multiple Numeric Limit Test has something in the Units field prior to RunState, the Units can be set programmatically by
RunState.Step.Result.Measurement["Measurement 0"].Units="apple" in the Post Expression.
RunState.Step.Result.Measurement["Measurement 1"].Units="oranges"
RunState.Step.Result.Measurement["Measurement 2"].Units="berrys"
RunState.Step.Result.Measurement["Measurement 3"].Units="avocado" etc. .
04-28-2020 07:35 PM - edited 04-28-2020 07:39 PM
Yes, you are right and maybe you can give a default string then replace it.
And another method pop up in my mind is to create a value by programming.
Just try to verify my thinking but not recommend to do in this way. It's not meaningful.