Programatically Loading Several Sequences Using LV Simple Operator Interface

[mswalker]

I am playing around with the supplied LV(2009) Simple Operator Interface for running TestStand (4.2) and hoping that someone can point me in the right direction.  I know this may be too generic for a concise solution, but hopefully I can get some suggestions on the best approach for this. Here is a short description of what I am trying to accomplish. 

I am testing 2 unique UUTs on a single test fixture that is controlled by a PCI-7831R DAQ.  Each UUT will have a unique serial number and report generated.  Therefore, I am using 2 unique sequence files created using TestStand.  Basically, I want to be able to read in a barcode on the test fixture and have the operator interface load the 2 unique sequence files based on information contained in the barcode.  The operator will then hit a button to start the sequence file executions.  I want the first sequence file to run and test the first UUT.  Once the first sequence file is finished, I want the second sequence file to load and run on the second UUT.

I can use the simple operator interface to load both sequence files.  I then have to select the combo box to select which one I want to run.  This works fine, however, I am trying to automate this so that the operator doesn't have to open the files and continually use the combo box to select sequence files.

Any ideas or suggestions would be greatly appreciated.

[Teds]

I designed something similar in my company,  an automated Operator Interface, where the operator first scans a barcode that automatically loads the correct sequence file.  It also gives the operator a picture and instructions on how to connect the CCA in the customized fixture.  Then by clicking on a START button it starts the sequence using Single Pass.  We found that all the confusing jargon of Single Pass, Test UUTs make no sense to most operators hence giving them a simple START button works much better.

One of the key aspects we used was a lookup table where the barcode scanned is parsed into it pieces and used to determine which software to run.   If you only have to support two CCAs, this may not be need for your application.

We now support over 30+ sequence files to run different CCAs.

I remember when I started I was in the same thought process as you, in that the examples shipped with TestStand always make the operator select a file to begin.  I was looking for something more automated, unfortunately there is not an easy solution.  I remember looking for some postings on the dicussion forum, but nothing right now sticks out as the one solution.  The operator interface I designed took months to work out all the details.  I started with the Advanced Operator Interface in TS 3.5 ( now running in TesStand 4.0.1 ) and worked from that as I liked the menu selections and thought the simple interface was too basic.

So my question to you would be, are they going to have both UUTs loaded on the fixture at the same time?  Or will they scan one barcode, load the CCA into the fixture, and then select Single Pass or Test UUTs?  Then when completed will they scan the barcode of the next one and start the sequence in the same way?

Thanks,

Paul Holzrichter

Test Equipment Software Engineer

Astronautics Corporation of America

[mswalker]

I have figured out a solution (for my initial application at least) of programmatically loading the sequence files.  When the operator interface first starts, there is a prompt where the user will scan a barcode that is loaded on the front of the fixture.  For all of our product lines, we will have a unique format for the fixture barcode.  Included in this barcode is a product specific software ID number.  I create a folder with the same software ID number and store the sequence files there.  I then parse the barcode and open all *.seq files in that folder.  I have this working correctly now. 

Once the sequence files are opened, the user must scan each UUT ID barcode before installing them on the fixture.  The intent is to have both UUTs installed on the fixture at the same time so they can be tested serially.  If, however, they do not scan one of the UUTs, it will not be tested.  Basically this is due to the fact that they may want to run only a single board.  Once all of the UUT barcode scanning has been completed, I have another button that will execute the sequence files using the 'Single Pass' execution entry point.  I agree that the 'Single Pass' and 'Test UUTs' points should be hidden from the user.  Once the execute test(s) button is pressed, it will check each UUT barcode to make sure that it is valid.  If both UUT's have valid barcodes, it will run the first UUT and then the second using the 2 sequence files that were previously loaded, otherwise, it will run only one or the other.  The UUT(s) will then be removed and the process starts over again from the UUT ID barcode scanning.  They will not have to scan the fixture barcode again since the correct sequence files have already been loaded.

Currently I have the UUT/Sequence File associations hard-coded in the UI.  I will need to put my thinking cap on so that as we increase the product lines (several are already in the pipeline) we can use the same UI without any modifications.  Scalability is King!