09-13-2018 06:44 AM
I'm testing 12 UUTs within a loop in a subsequence. Each UUT has a different Serial Number.
I would like to have a separate report for each UUT.
Does anyone have an Idea how this can be done?
DOK
Solved! Go to Solution.
09-13-2018
08:10 AM
- last edited on
11-30-2024
06:07 PM
by
Content Cleaner
What process model are you using? Usually the best way to achieve this is to use a Parallel or a Batch process model.
Check out these links to learn more about process models:
http://www.ni.com/product-documentation/54531/en/
09-13-2018 08:13 AM
Your're using Sequential PM. Discard my previous reply.
09-13-2018
08:19 AM
- last edited on
11-30-2024
06:08 PM
by
Content Cleaner
You are absolutely right, I should be able to do this using the Batch Model.
However, while reading https://www.ni.com/en/support/documentation/supplemental/06/report-generation-explained.html it identified that, in Teststand Version 2012 and above,
" This architecture is more complex, but has a number of benefits over the previous design; for example:
So, in theory, I should be able to have a sub-sequence generate a report.
I've created 2 small files to try to do this. The idea being to have "Inner Sequence" create a report for each UUT
09-13-2018
08:31 AM
- last edited on
11-30-2024
06:08 PM
by
Content Cleaner
Hi DeOdderKeith,
You would have to override the TestReport Model Callback and provide a custom way to read each DUT serial num and create a test report for each with a code module. Check this link for more info about this callback:
https://www.ni.com/en/support/documentation/supplemental/06/report-generation-explained.html
09-13-2018 08:45 AM
I'm already changing the UUT Serial Number by setting
RunState.Root.Locals.UUT.SerialNumber = StationGlobals.UUT_Serial[Parameters.UUT_Num]
Now how do I tell the Report Plugin that this is a new UUT and it should create a new Report?
09-13-2018 08:52 AM
You would have to cerate a new custom Report plugin. The solution that NI TestStand implemented for what you need is solved in the Batch or Parallel Process Models. I dont know how much effort would it take for you to switch to any of those. If you still want to keep using the Sequential PM then that is the only way I can see for now which by the way is not very friendly.
09-13-2018
09:25 AM
- last edited on
11-30-2024
06:08 PM
by
Content Cleaner
Have you considered launching the subsequence in a new execution?
When to Run a Sequence in a New Execution versus in a New Thread
09-13-2018 01:43 PM
Running as "New Execution" works !!
I've had to make some changes to the PreUUT and PostUUT and TestReport on both the TopLevel.seq and Inner Loop.seq
Thank You WireWeaver
DOK