Separate Results files for each UUT run within the UUT loop

[lrlpool]

I am using TestStand 2014 with results configured to use a report file path name specified by expression.  After running the sequence the enter serial number pop up comes back up and I enter a different serial number and run again but the results for both runs are put in the same file.  The files were seperated in TS 2013.  How do I get separate files in TS 2014?

[~jiggawax~]

What do you have checked in the report options for New UUT Report File for Each UUT?

[lrlpool]

That option is not available when the file name is calculated from an expression.  However in 2013 the separate files were the default for a file name calculated from an expression.  I just don't know if they had a reason for changing this or if this is an error.  Anyway thanks for the response.  I did change to the Specific Directory option and I was able to get my results in the correct directory and in separate files.

[~jiggawax~]

Does your path include the serial number?  If not then it makes sense why you are seeing them show in the same report.  You can use the unique tag to enforce separate files:

• $(Unique)—Replaces the macro with a unique numeric value if the file already exists in the path. If you use more than one $(Unique) macro in the Report File Path expression, TestStand replaces only the first instance from left with the unique numerical value. For example, if you specify the Report File Path expression as "C:\\Temp$(Unique)\\TSReports$(Unique)\\Report$(Unique).xml" and C:\\Temp\\TSReports\\Report.xml already exists, the process model saves the report file path at C:\Temp0001\Reports\Report.xml.

  Note  You cannot use the $(Unique) macro as a stand-alone directory or filename in the Report File Path or the Batch Report File Path expression.

[Gloorious_Leader]

Hi lrlpool,

As Jigg said, using the UUT Serial number will cause seperate reports to be made. Use the $(UUT) macro to include the serial number in the report name. Note that it is invalid when using the Batch process model.

A full list of available macros and their functionality can be found here.

[lrlpool]

I found my problem when I went looking for the UUT macro.  In the old code I was using in the 2013 version there was a UUT macro used as a default in the expression.  In the current version I replaced that with my own variable without realizing what it affected.  Thanks for leading me in the right direction.