Modify Report for accuracy

[Maz]

When performing a numeric test whose Comparison type is LT or LE, T/S uses the Low Limit value. The report then generates as follows:

Measurement: 9
Low Limit: 10

In reality, this is an Upper limit and should read:

Measurement: 9
High Limit: 10

How can I change the report to dynamically describe the limit accurately. (ie, use "Low Limit" for GT or GE comparisons and use "High Limit" for LT or LE comparisons)?

Thanks for your help. This newbie appreciates the attention.

[RayFarmer]

Hi Maz,

You need to look at the sequence file reportgen_txt.seq or reportgen_html.seq depending on which report format.

The sequence you need to look at is PutOneResultInReport. The step in question is about halfway down the main called 'Add Flagged Values'. This is a call to a function in the modelsupport2.dll.
If you dont want to modify the DLL, you could modify the returned value from the function based on the a decission of the Comparison string.

Alternative, you will notice a sequence callback towards the bottom called 'ModifyReportEntry callback'. This a sequence you can add to you Test Sequence file that will override this callback. This means you could make the changes you require without having to modify the reportgen_ .seq's.

One thing yo
u will have to set, is in the Configure | Report Option under the Contents Tab is the 'Select a Report Generator for Producing the Report Body'. You will need to set this to Sequence. You can also set this in the Override Callback ReportOptions by setting the value in Parameters.ReportOptions.BodyGenerator from "DLL" to "Sequence".

Ive attached an example that uses the uses the ModifyReportEntry callback and I have include the ReportOptions callback to set the Parameters.ReportOptions.BodyGenerator.

Hope this helps
Regards
Ray Farmer

[Mark_Ireton]

TestStand's use of the lower limit for LE/LT comparisons can also be a problem when using property loader and database logging. A test engineer expects the LE/LT comparison to use the high limit. See this posting for a work-around when using database logging.

http://exchange.ni.com/servlet/Redirect?id=8534018