Using A Precondition
First I go to the Limits tab of the Step Settings to enter the high and low limit as shown in Figure 2. Next I went to the Module tab and set the VBatt Result Value expression to be Step.Result.Numeric. This is shown in Figure 3. This again is using TestStands built-in results collection. That it, then the Data Source tab is automatically set to Step.Result.Numeric as well.
Using a Post Action instead of a Precondition
Here under the Post Actions property you can see in Figure 8 we’ve left the behavior for on pass to default as go to the next step, but changed the on fail to go to step cleanup.
Making limits their own step
Here is the process to move the Sine Amplitude and Frequency Test limits to their own sequence steps:
- Change the adapter to an action rather than a multiple numeric limit test as shown in Figure 9.
- Drag two numeric limit steps after the Sine Amplitude and Frequency test and change their adapters to <None>
- Go into each of these limit steps and update the limits to the desired amplitude and frequency limits, as shown in Figure 10.
- Now we have to connect the results returned from the VI to the limit evaluation steps. To do this we will create two new local variables. Go over to the variables area and right click to add to local numeric variable. Next go to the action step that calls the Sine Amplitude and Frequency step and assign the outputs to the newly created local variables. Then, we have to go into each of the limit steps an assign those to get their results from the appropriate local variables. Do this by going to the data source and setting it to the appropriate local variable. See Figures 11, 12 and 13.
Improving the format of the test report
If I go to Configure -> Results Processing I can change the way numbers are reported on the report. Figure 15.
Now in Figure 19 our report is looking a little bit better.