Cycle Trigger Manager

The source of Cycle Trigger is defined by CycleTriggerSource.

When set to Immediate, the Cycle Trigger Manager is self-triggered. It generates a Cycle Trigger immediately after the start of the sequence and then repeatedly every CycleMinimumPeriod period.

When set to StartCycle or to <any I/O toolbox event source> the Cycle Trigger Manager doesn't start immediately after the start of the sequence, instead it waits for the execution of a StartCycle command or the occurrence of an event on the selected I/O toolbox event source.

A wide set of Cycle Trigger event sources is available. It includes all the I/O toolbox events, namely: LIN, QDC, MDV, DIV, DEL, EIN and User Events.

The Cycle Manager is fitted with a trigger latch mechanism capable of latching cycle triggers that cannot be served immediately. Such triggers are named ''pending triggers" since their execution is simply postponed until the corresponding CIC cycle is initiated.

The maximum number of pending triggers that can be recorded is defined by CycleMaxPendingTriggerCount. When CycleMaxPendingTriggerCount = 0, the trigger latching mechanism is disabled. This is the default value. To enable the trigger latching mechanism, set CycleMaxPendingTriggerCount to any integer value in range 1 to 7.

The number of pending triggers is reported by CyclePendingTriggerCount.

When CycleTriggerSource is set to StartCycle or to <any I/O toolbox event source>, every Cycle Trigger event is evaluated against the trigger acceptance criteria and sorted according to the result.

The rejected Cycle Trigger events increment the Cycle Lost Trigger Counter.

The accepted Cycle Trigger events increment the Cycle Pending Trigger Counter if the pending trigger cannot be served immediately.

Cycle Trigger events are accepted and executed immediately when both conditions are satisfied:

Cycle Trigger events are accepted and executed later when following conditions are satisfied: