Configure errors and alarms

You can specify how the Sequencer object handles irregular configuration and values at run time. You can:

• halt program execution if a condition trigger or Alias in the output matrix has bad quality or cannot be read, or if an Output OnEntry/OnExit Alias cannot be written or if the Sequencer Object is hanging in Initializing state.

• report alarms if an output or condition has a syntax error. You can log separate alarms for On Entry output errors and On Exit output errors.

Two types of errors can occur when the Sequencer object is deployed and interacts with ArchestrA attributes:

• Condition Errors - a condition error occurs when

  • the object failed to resolve a trigger reference

  • the quality of the trigger reference is not good

  • the data type is mismatched and cannot be handled by Message Exchange

• Output Errors - an output error occurs when

  • an output reference cannot be resolved or has bad quality

  • the reference of a pass by value Alias cannot be resolved or has bad quality

    Note: This affects the attributes ConditionTriggerFailure, OnEntryOutputFailure and OnExitOutputFailure.

Examples:

• configuring a non-existent attribute as an output in a step program causes an Output Error

• configuring a non-numeric attribute as an input (trigger) in a step program causes a Condition Error

• the quality of the attribute belonging to an input (trigger) or an output is bad.