Design of (TS + LV + SQL inputs)

Question

Hi,
I have a big project to manage which includes :
-TestStand + LabVIEW
-SQL Database for test inputs (UUT characteristics, sequences parameters,...)
-HTML Reports
-almost 10000 different part numbers (that's THE point) with common characteristics (almost 3000 families) + specific characteristics
Everything has to be imaginated.
The SQL inputs tables have to be created.
The number of sequences to code has to be reduced to the minimum because, of course, it's impossible to code 8000 sequences differents files...
The final solution must be as simple as possible.
Possible ways of reflexion :
-XML and Xpath for families and their children
-Intermediate LabVIEW OOP layer for families and their children
-Dynamically created sequences + variables (TS scripting)
-Dynamically created sequences (concatenating a bunch of generic sequences to build a specific sequence)
There is a lot of documentation about TestStand and SQL, but only for results (outputs), not really about inputs.
Does anybody manage this kind of project ? In which way ?
What would be your advices ?
Thanks,
Sébastien
CLA

Answer 1

Hi
I used to work on a big project in the process model group ( modifying the process model) so that same process is used across all testing station globally.
Few inputs which may help you :
1)Storing of the test files:
Create a good folder system in the version management system.
Ex :
Family1 Folder
                Model 1 Folder
                       TestSequence
                        Limits file
                        Specific Support files,etc
                 Model 2 Folder .....
This is probably a must when you are thinking of automatically creating test sequences.
2) Creating sequences
Create feature specific sequences.( sub sequences equivalent of a function in C)
Your main sequence can call only the required feature specific sequences.
You can write a program to do create the main sequences based on some text file input.
This can be done in LV or any other language using TS APIs.Probably thats what you meant by Dynamically created sequences (concatenating a bunch of generic sequences to build a specific sequence).
3)Property loader step type
The step test limits and values of variables for a given sequence can be loaded dynamically from a file or DB using this feature.Please explore this.You can run the examples to understand more.
SQL Database for test inputs (UUT characteristics, sequences parameters,...)
Not sure what you exactly mean by this.I think property loader feature should take care of this.It inputs data from an external DB\File into the sequence at run time.
4) Modifying process model ;
You can modify the existing process model to suit your process requirement.
Ex : Checking for test sequence checksum before running.
Checking if the correct sequence is running on the correct machine and for the correct product.
5) Reports
Deciding the best report format for your application.
TestStand supports HTML,ATML,TXT report.The default ones can be modified as per your needs.
Storing of the reports in database should be considered.
6)Storing of results.
What data to store in DB?
Is the default tables given by TestStand suits your requirement.Any modifications required ? Modifications can be done to suit your requirements.You can refer help or search in forums.
Also how much data will be stored.Backup required at what intervals?
Is the sequences run at only one locations ( multiple servers needed?)
7) Who will run this sequences?
If its an operator then you can use the default user interface or think of modifying it as per your requirements.
8) Failures and error handling during testing.
Ex - print a fail ticket if a product failed.
No error pops up during testing if an operator is testing a product.
Hope it helps.
Ravi