Browse Prior Art Database

Method for Control of Multiple Independent Cyclic Test Processes

IP.com Disclosure Number: IPCOM000115832D
Original Publication Date: 1995-Jun-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 42K

Publishing Venue

IBM

Related People

McKay, J: AUTHOR

Abstract

Cyclic testing is a very common requirement in manufacturing and development. The disclosed method is novel in that it allows one simple control loop to control multiple cyclic processes while allowing unique timing parameters for each process and the ability to modify, initiate or terminate individual tests without terminating other tests.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 96% of the total text.

Method for Control of Multiple Independent Cyclic Test Processes

      Cyclic testing is a very common requirement in manufacturing
and development.  The disclosed method is novel in that it allows one
simple control loop to control multiple cyclic processes while
allowing unique timing parameters for each process and the ability to
modify, initiate or terminate individual tests without terminating
other tests.

      The method begins with a Setup screen in which the user may
enter desired test parameters such as cycle time.  When the Setup
screen is closed the testing is initiated.  This begins with a
comparison of a clock to the time at which the first tester is to
cycle.  If the comparison yields true, then the tester cycles and
data collection and processing occur.  The process is repeated for
the second tester and so on.  If an operator interrupt is sensed,
(for instance a key is pressed) then the computer returns to the
Setup screen.

The steps are ordered as follows:
  1.  Setup Menu in which the user enters test parameters such as
       cycle time.
  2.  Compare the computer's clock time to the time or interval at
       which a tester should cycle.
  3.  If the time comparison yields true then begin the start or stop
       cycle for that tester with associated data collection and
       analysis.
  4.  Repeat steps 2 and 3 for the next tester, unless a key has been
       pressed in which case return to step 1.

...