Aliases

At run time, the Sequencer object interacts with attributes of other objects. These attributes can be:

• Inputs that cause the step condition or jump condition to be fulfilled. Typical inputs are sensory devices that trigger the step execution when a certain condition in a factory device is fulfilled. For example, a tank level sensor.

• Outputs are written either before or after the step or jump condition is fulfilled. Typical outputs are to device controls, such as valve controls.

• Inputs and outputs at the same time. A typical example is a condition reset.

The step program can reference the same attribute multiple times in the step program. Instead of referencing these attributes directly, the Sequencer object uses a list of Aliases to reference the attributes. Using Aliases simplifies the appearance of the step program and saves time when the referenced attribute needs to be updated.

Note: Writes are not guaranteed. Only invalid references are reported. The Sequencer Object does not request or evaluate write confirmations.

In the Sequencer object, you can configure the mapping of Aliases to attributes on the Aliases page.