NI TestStand
Can I change report options programatically through Teststand?
Hi Dave,
Here is a stab at answering your query.
This is probably going to envolve modifying your Process Model ie SequentialModel.seq. to achieve what you want to do.
So before you start -
If you do make changes to the process model. Then dont change the file in the Components\NI folder but copy it to a corresponding folders to the Components\User folder, then change this one.
In the ReportOptions you would put your code to obtain the previous log file. You would need to load the data from the file an store this in say a string variable in FileGlobals so that its available back in the process model. You will have to store the full path to that log file as well. Close the file before returning from the ReportOptions.
After the step 'Get Report Options' i
n the process model, you will need to determine if a new file or using a previous file.
About half way down the Test UUT sequence in the process model sequence file is a step 'Determine Report File Path'. This would have to be skipped. You could do your check to use previous log file here.
If a previous file then obtain the data and store into Locals.Report and also get the Path and store into Locals.ReportFilePath. If you use a new log file then do the step 'Determine Report File Path'.
Remember to modify all entry points in the process model sequence file. eg Test UUT's and Single Pass.
Hope this helps.
Ray Farmer
Here is a stab at answering your query.
This is probably going to envolve modifying your Process Model ie SequentialModel.seq. to achieve what you want to do.
So before you start -
If you do make changes to the process model. Then dont change the file in the Components\NI folder but copy it to a corresponding folders to the Components\User folder, then change this one.
In the ReportOptions you would put your code to obtain the previous log file. You would need to load the data from the file an store this in say a string variable in FileGlobals so that its available back in the process model. You will have to store the full path to that log file as well. Close the file before returning from the ReportOptions.
After the step 'Get Report Options' i
n the process model, you will need to determine if a new file or using a previous file.
About half way down the Test UUT sequence in the process model sequence file is a step 'Determine Report File Path'. This would have to be skipped. You could do your check to use previous log file here.
If a previous file then obtain the data and store into Locals.Report and also get the Path and store into Locals.ReportFilePath. If you use a new log file then do the step 'Determine Report File Path'.
Remember to modify all entry points in the process model sequence file. eg Test UUT's and Single Pass.
Hope this helps.
Ray Farmer
Hi Dave,
Ignore the modifications to the process model ....
The standard TestStand set does already allow for appending to a previous report so long as you have the correct settings in the ReportOptions, i.e. Append, Dont make unique, Dont added the Time/Date to file name.
Therefore all you need to do is add your code in the Override ReportOptions sequence call to prompt of an existing report to set up the report path and whether you what to append or not.
This means you dont have to modify the process model.
What you will see at the end of the test sequence execution displayed for the Report is only the current runs, but all results will have been appended to previous result in the file and will be seen if the report is launched in the viewer.
R
egards
Ray Farmer
Ignore the modifications to the process model ....
The standard TestStand set does already allow for appending to a previous report so long as you have the correct settings in the ReportOptions, i.e. Append, Dont make unique, Dont added the Time/Date to file name.
Therefore all you need to do is add your code in the Override ReportOptions sequence call to prompt of an existing report to set up the report path and whether you what to append or not.
This means you dont have to modify the process model.
What you will see at the end of the test sequence execution displayed for the Report is only the current runs, but all results will have been appended to previous result in the file and will be seen if the report is launched in the viewer.
R
egards
Ray Farmer
