Annulla,
The answer depends on whether you are using TestStand 1.0.x or 2.0. I will assume you are using TS 2.0. Let me know if otherwise.
It is important to understand how report generation works. There are two parts to report generation - collection of the step results and creating a report for the collected data. As a sequence executes the values of subproperties in the Step.Result container of each step are AUTOMATICALLY collected in the Locals.ResultList array. In addition, I few extra step properties are collected including Step.Limits and Step.Comp. These extra step properties are collected because of the steps "Include Limits in Results" and "Include Comparison Type in Results", which are located in your process model.
So, one solution to your problem is to open your process model, right click on the "Include Comparison Type in Results" step, and select Run Mode>>Skip. If the comparison type isn't collected then it can't be included in the report.
After step values have been collected in the Locals.ResultList array, the array is recursively searched for values that should go into the report. What deterimes whether a value should go into a report is the flags of its property.
In TestStand 2.0 the Step.Comp and Step.Limits properties of the Numeric Limit Test step type have the IsLimits and IncludeInReport flags enabled. You can view this by going to these properties, right clicking and selecting Properties from the properties context menu, and then clicking on the Advanced button on the Properties dialog box.
The IncludeInReport flag tells the default report generation to inlude the property in the report. The IsLimits flag tells the report generation that the property is associated with a set of limits. You will notice that in the report options (select Configure>>Report Options) you have the option of including or excluding limits of a step. This option only affects step properties that have the IsLimits flag enabled.
So, now you know some of the details involved. Other solutions include
-Choosing not include any limit values by configuring the Report Options accordingly.
-Copying the NI Numeric Limit Test step type and disabling the IncludeInReport flag for the Step.Comp property in your copy.
-You could also do things programmatically to turn off the property at runtime, but I wouldn't recommend this.
The solution depends on what you really want. Let me know.
