Automatic Mode

In automatic mode, the test cycles are automatically driven by the system either until the test run is finished or until it is interrupted. You can also pause and resume the test run.

There are different ways to execute an automatic test run in PAtools:

  • Sequence tables: Flexible parameterization of steady state or dynamic work points in different control modes. Sequence tables can continue an interrupted sequence at so-called recovery points.
  • Step tables: Tracing time-based or path-based cycles in one control mode from a step table.
  • Tracing files: Tracing time- or path- based cycles in one control mode from a file.

If some of the setpoints of a sequence table or a step table are changed, it is possible to edit the according groups in PAconfigurator and reload the table while the test is running.

Sequence Tables in Automatic Mode

Main Sequence

Each application has a main sequence that is the entry point for all detail sequences. The main sequence calls the application-specific sequence tables.

When automatic mode is activated, initially only the main sequence can be started.

Sub-Sequences

One sequence table can call another sequence tables up to a level depth of 5. The sub-sequence tables that are started by the main sequence usually have a set of columns that are used to define setpoint values. These setpoint values are approached using a configurable ramp. Afterward, the setpoint values are stabilized and then the measurement time starts. The measured values can be stored only during the measurement time or continuously.

There are three phases for each step:

  • Ramp: The new setpoint settings are reached from the current setpoints using a linear ramp.
  • Steady state: This time is used to establish the conditions of the new setpoints, so that the actual values are steady.
  • Measure: This time is used to record values for the actual combination of setpoints.

Definition of the Ramp

The ramp for reaching the new setpoint settings can be implemented either by defining a total ramp time or by specifying a gradient.

When reaching the setpoint by defining a ramp time, the values entered in the sequence table define the absolute time that is spent for changing the setpoint value. The gradient that is needed to reach the setpoint within that time is calculated by the system.

Figure 24. Definition of the Ramp by Specifying the Ramp Time
1378

When reaching the setpoint by specifying a gradient, the values entered in the sequence table define a gradient that is used for changing the setpoint value. The absolute time that is needed to reach the setpoint with that gradient is calculated by the system.

Figure 25. Definition of the Ramp by Specifying a Gradient
1378

These methods are implemented depending on the choice of the table type for the sequence table:

  • PTXYEM_Gradient.ABT: Contains columns for reaching the setpoint settings using a gradient.
  • PTXYEM_Time.ABT: Offers columns for entering a total ramp time.

Stability Check Measured Values

You can define a tolerance for the measured values related to the setpoint values. Additionally, you can define a minimum stable time that all measured values must be within the defined tolerance. If one of the measured values exceeds the tolerance, the stable time is reset to 0. If the minimum stable time is reached at the end of the steady state phase, the measurement phase starts.

If the minimum stable time is not reached at the end of the steady state phase, a soft stop is triggered and the following actions are executed:

  • Automatic mode is left.
  • A message displays which setpoint(s) could not be stabilized.
  • The system is switched off regularly (no safety-related shut down).

Sequence Tables: Selection of the Start or Recovery

If a sequence takes a long time for execution, do not start this sequence from the very beginning if it was not finished. Possible reasons for this type of interruption may be either a violation of a limit value or an abort by the test bench driver.

You can start a sequence table from a selectable point in the sequence instead of the beginning of the sequence.

With the recovery function, it is possible to continue a test sequence if the execution is not finished. You can define recovery points in the sequence table for this purpose. Start or continue the test sequence wherever a recovery point exists. In a PAtools sequence table, a recovery point is identified by the entry Recovery Point in the first column of the sequence table, and the second column defines the name of the recovery point.

If more than one recovery point is passed by the last execution of the sequence table, you can choose at which point the execution of the sequence to resume.

Step Tables in Automatic Mode

Step tables differ from sequence tables as follows:

  • There is no choice of the control mode (the control mode is parameterized in the sequence table that calls up).
  • Setpoints have a fixed column assignment (according selected control mode).
  • First column: Monotonously rising time or path track.
  • No option to select actions.
  • No option to parameterize loops, queries, recovery points, etc.

The processing of a step table starts in a sequence table. The sequence table thus specifies the control mode. You can call several step tables consecutively in a sequence table.

Files in Automatic Mode

Rather than processing time- or path-based cycles based on a step table, the setpoint source can also be a file. Tracing a file is also started from a sequence table. Again, the sequence table specifies the control mode. Several files can be called one after the other in a sequence table.

Options for Customizing Automatic Mode

PAtools provides the following options to customize the automatic mode:

  • Editing the contents of the sequence and step tables.
    • You may change setpoint settings. In case of sequence tables, additionally ramp or measurement times, specifics actions, etc. may be adapted. This editing can occur before the test was loaded and in a special way also during the runtime of the test.
  • Adding new step- or sequence tables that are called by the main sequence.
    • There is no limit for adding custom sequence tables to the main sequence. Adding new tables to the test can only be made before the test is generated—this is not possible at runtime.

Reloading

The PAtools reloading mechanism allows the exchange of parts of the test during runtime. It applies to several group types that are described in the PAtools User Manual.

The basic work flow for reloading is:

  • Opening the table directly from the running test in PAconfigurator.
  • Changing and saving the according values.
  • Generating only this specific reloadable object to the PCU.
  • Exchange of the old and the new object during the runtime of the test at specific test states.

Reloading is not possible for objects that are not part of the running test. Therefore, you cannot reload new step or sequence tables that are added to the test.