Hello Jim,
Sorry for the confusion. To answer your new question: yes, there is a much better way to accomplish your goal. For one thing, if you want an initialization routine that runs before the first UUT (and only the first), you can use the PreUUTLoop model callback. By default, this is empty and gets called by the Process Model before the loop in which UUTs are processed.
The next thing you want to do is to have a separate report for each UUT. By default, the Operator (and Sequence Editor) only allow you to display one report per execution. So you could modify your Process Model such that, instead of running each UUT in the same execution, you programmatically create a new execution for each one.
There is another way that is more difficult, but (I think) a lot more elegant. In the Sequence Editor, modify your reporting options by going to "configure >> Report Options..." and click on the "Report File Pathname" tab. Enable the option, "New UUT Report File for Each UUT". The bottom of the dialog box will show you the convention for naming reports. But this is only half of what you need to do. Even if you have a distinct report for each UUT, only the latest one will be the active report of the execution. Therefore, you will need to add your own programming to be able to display the other ones. For instance, if you are using html reports (the most common type), you can embed a "Microsoft Web Browser" ActiveX control into the front panel using an "ActiveX Container" LabVIEW control (in the Containers palette). You can programmatically invoke the method, "Navigate". This method has as an input the URL of the html page you would like to display (give it the path to the file on your computer). You will need to add user controls to allow the user to choose which UUT (s)he would like to have displayed, capture that event, and then display the appropriate html page.
I created a sample client and ran TestUUTs on it to generate 3 separate reports (on for each serial number). Then I created a VI in LabVIEW that allows the user to select a serial number and programmatically updates an embedded web browser on the front panel with the appropriate html report. You will have to modify the part of this VI that constructs the URL string to match your particular application. Please let me know if you have any questions about this example.
Either way, you are going to have to do some coding. I hope that this information is helpful to you. Take care and good luck!
Regards,
Aaron B.
National Instruments
