Control the program flow at run time

You can control step program flow by telling Sequencer to

• start or stop program execution

• resetting program execution

• hold or resume program execution

• advance a step

• run in Single Step mode

• confirm a step transition when running in Single Step mode

• jump to a specific step

  Note: This is done by writing execution commands to the attribute ExecutionStateCmd. You can query the current state of execution by reading the value of the attribute ExecutionState.

The following terminology used in the tables of this section:

• Current State - the current execution of the step program. You can find out the current state by reading the attribute ExecutionState. Only certain combinations of current state and execution commands produce a meaningful result.

• Target State - the state of the step program execution after you have written the execution command to the attribute ExecutionStateCmd. This is your desired execution state.

• Target State Timer - after you write the execution command to the attribute ExecutionStateCmd, the timers act accordingly. They may restart, continue, or stop.

• Target Step - the step that becomes active after you write the execution command to the attribute ExecutionStateCmd.

• Write OnExit - informs you whether Sequencer writes values to the On Exit outputs, if configured, of the currently active step after you write the execution command.

• Write OnEntry - informs you whether Sequencer writes values to the On Entry outputs of the step that is active after the currently active step.