Hello All,
I am in the process of designing an Test System and would like to have some input from the experts here.
We have a proposed Operator interface where the operator selects a unit under test and its corresponding test sequence is loaded from a database. The operator should then be presented with the following options (these options could change) to run.
production (this would also include some flash programming subsequences) - Fixed number of tests, operator cannot change the test selection
repair - initial (where the units flash is read and saved to analyses any fault codes) - Fixed number of tests, operator cannot change the test selection
repair - intermediate (where the operator can chose a particular test/s to run - Operator is allowed to chose the tests
repair - final (final test before the unit is sent back to the customer) - Fixed number of tests, operator cannot change the test selection
This is the same across many UUT's and I would like to standardise this without hardcoding the OPTIONS in to my Operator Interface. As the options above can change.
My thoughts were as follows:
1. Modify process model to add extra Execution Entry Points, but this seems ugly to me and is not very flexible.
2. Overriding the MAIN SEQUENCE by passing corresponding subsequence names to the Process model using Parameters.Sequence
3. Have these options as sequence call steps in the MainSequence and each of these are acually calls to subsequences which lists the tests in the sequence.
What would be nice is to read the OPTIONS from the selected sequence file and to display it on the Operator Interface and then based on operator selection execute a corresponding subsequence. We are not allowed to have multiple sequences for the same UUT unfortunately.