TestStand 2.0 on the fly reports

[steve h]

I am using TestStand 2.0 and the batch model. I have unchecked the 'record results' checkbox for all the irrelevant steps, however the results takes ages for TestStand to process (takes hours),the PC is relatively new and ram is 500Mb.

I guess I need to use 'on the fly' results processing but TestStand 2.0 does not have this as an option. Is there a batch model for TestStand 2.0 that does on the fly results, or a method of modifying the batch model/sequence for on the fly?

[RayFarmer]

Hi steve,

TS 2.0 doesn't have on the fly report as standard but if you look in the Examples\OnTheFlyReports and follow the word doc you can get an On the Fly setup.

I am sure TS2.0 has this example but I can only see TS2.0.1 examples.

Regards

Ray Farmer

[steve h]

I tried that method, although I am using the batch model rather than sequential, and it came up with a bug - 'unknown variable ReportOptions' , see attachment.

[RayFarmer]

Hi,

Should it not be "Locals.ReportOptions" or "Parameters.ReportOptions".

Or is there such a variable declared in the right location or your Sequence.

I have used this along time ago a did get it working.

Ray Farmer

[steve h]

I am not sure what it should read, I just copied it from the 'on the fly' sequence example as instructed. I guess the NI 'on the fly' example is wrong, maybe it was updated on a lated version of TestStand (I have 2.0.1)?

[RayFarmer]

Steve,

The problem is that you are using the Batch Process Model but the OnFlyReport documentation give a set of instruction to modify the Sequential Model.

In the Batch and Parallel models. ReportOptions doesn't exist in the same place as the Sequential Model ie Locals.ReportOptions.

Therefore you need to modify the various step that obtain the ReportOptions information from:

RunState.Root.Locals.ReportOptions

To:

RunState.Root.Parameters.ModelData.ReportOptions

Hope this helps

Regards

Ray Farmer

[steve h]

Yes this works for a sequential batch, but seems to crash using the non sequential batch. It appears that on the second run of the 'ProcessModelPostResultListEntry'    -  'Format Result: Text' call it appears to add an extra '.parameter' which results in the error as below:

RunState.Root.Parameters.ModelData.ReportOptions.ResultFilterExpression:

Parameters.Parameters.Result.Status != "Done" && Parameters.Parameters.Result.Status != "Skipped"