conserve memory

[sonotk]

With OTFR and conserve memory TestStand does not produce reports in chronological order. If conserve memory is turned off then reports are in chronological order. Using TS4.1.

A reply to similar post here  but does not help much from NI response.

Any suggestions for workaround.

Thanks

[sonotk]

Attach are the report with incorrect (with conserve memory) and correct chronological (without conserve memory) order.

[RaviShrigiri]

This could be the probable reason :

When convserve memory is ON the report is generated on the fly - printed as and when sequence/sub sequence is executed.

Hence the status of the total sequence file will be known last and it is thus printed last.

In the other case when this option is disabled the report will be generated in the last stage after testing is completed so it knows the sequence file status and it can print in that order.

Conserve memory is generally useful when you have very large sequence running and lots of memory is required (Ex video applications where lots of data is collected).

[sonotk]

Thanks SunRS, yes I did contact NI and they confirmed that it is not the expected behaviour of chronological order with conserve memory. The only fix they have is in version 2012. Unfortunately I am on version 4.1!!

[Perry_S]

Hi sonotk,

The conserve memory option in TestStand 2010 SP1 and previous, causes different behaviour when saving to HTML or ASCII file formats. In the TestStand Reference manual it is documented that this is known behaviour. This is what it says:

"When you enable the Conserve Memory and Only Display Latest Results
option for HTML and ASCII reports, on-the-fly reporting periodically
purges internal data structures. As a result, the report TestStand displays in
the Report pane of the Execution window shows only the results for the
steps on-the-fly reporting has not yet purged. The persisted temporary and
final report files contain all the step results. For these files, the step results
for Sequence Call and Loop Result steps appear after the corresponding
Sequence Call and Loop Index step results, respectively."

Please refer to the TestStand Reference manual for additional details . Currently there is no work around for this behaviour. It was however updated in TestStand 2012 so that it no longer occurs. I hope that this answers your questions.

Regards,

Perry S.