Generating Reports during execution

[DonFrevele]

Can report generation be forced to run _during_ a Batch model execution in TestStand 4.0?  The report file only seems to be generated after each batch.
I am implementing a burn-in test program which can take 100 hours to run and don't want to lose data if something happens to the computer before the test completes. The report is small - only 16 pass/fail steps. I'm running up to 4 UUTs at a time and generating an ASCII text report.

Thanks
Don Frevele

[Dillon_G]

If you turn on "On-the-fly Reporting" in report options, reports will be generated during execution.  During execution in a batch sequence each unit appears as a different individual report, with the merged final report not being generated until the end.  If TS abruptly terminates these reports will still exist for you view.

[DonFrevele]

Thanks Dillon,
   I had tried that, but I guess I didn't wait long enough for the files to be written. A few questions:

  1) What determines how often the files are written: time, number of test steps, amount of data written? Can this value be changed? I have a small amount of data and test steps written over a long period of time.

  2) How can I customize the generated report. From reading another post and snooping around, I find that the on-the-fly reports seem to be generated by TSOTFRG.dll and none of the report modification sequence callbacks are used. Is that correct?  I want to replace the report header and it seems that I would have to modify the TSOTFRG source code. Is there any documentation (other than looking at the code) for this? I am an experienced c/c++ programmer.


Thanks
Don

[Dillon_G]

Firstly, sorry it took me so long to respond.  I wanted to research a bit before I responded.

1.)  The reports are written after each step execution.  I do not know of anyway this could be changed.  If you want to log data during a step execution, it would probably be best to have that step log its own data somehow.

2.)  I believe that TSOTFRG.dll is always used when generating on-the-fly reguardless of settings.  Maybe it would be satisfactory to add the data from the header in with a step instead, since these reports are only used if the sequence does not complete correctly.

[DonFrevele]

Thanks for gettting back to me. Logging data after each step is fine. I am actually running my program now with one hour cycles and I find that the on-the-fly temp data file does contain the customize header I have placed in a modified reportget_txt.seq file.  I can look at the file while it is running and it looks like a complete report, up to the current step being executed. Just what I wanted.

Thanks for the help.
Don