Flex II System Triggers

Triggers are a way to identify one or more Flex II Audit Trail Events and designate a resulting Inter-hub signal or an output pattern from a selected set of output lines on the local Flex II Controller hub. Each hub gets a distinct set of triggers.

Flex II Trigger Execution Logic

---

Triggers may also be set to execute only during certain time frames and if selected inputs are either in a high or low state. Delays may be added prior to evaluating the input line states and then prior to executing the trigger. The chart below illustrates the logic executing a trigger.

Flex II Triggers List

---

Each Flex II controller has a distinct list of triggers. They are viewed by selecting properties for a Flex II controller in the Flex Hub listing page then selecting from the tabs on the left.

Click the to add a new trigger.

A click menu for each trigger in the list enables editing the trigger properties or deleting it.

Triggering an Inter-hub Signal

---

To use audit trail events to trigger an inter-hub signal:

1 Assign a name to the trigger. Uniqueness is not enforced so the same name may be used for a trigger on a different controller.
2 Select the group where the events originate from. Some events have no associated group. This includes system events, events from auxiliary, UPS, and tamper inputs. In that case, select All Groups from the selector.
3 Use the item-chooser to select one or more audit-trail events.
4 The trigger may be optionally modified to only execute when input lines connected to the controller or expanders are in the desired states. The Input States Logic Editor uses boolean logic (And/Or operators) and selected inputs paired with a selected state. States on inputs are either high (default) or low. Pressing a button wired to causes a low state. A delay may be added to pause before the input line state is evaluated. This might be useful if some time is needed to ensure the state(s) have settled.
5 Choose Send this Inter-Hub Signal and select an Inter-hub signal from the drop-down selector. Inter-hub signals are created and listed on this page. Note: You may instead choose to cancel a selected Inter-hub signal.
6 The trigger may optionally be contrained to execute only during the time frames of a selected schedule. If this is required check the box and select a schedule from the selector. The schedule may further be bound by a beginning and end date.
7 Click Save.

Triggering Local Output Lines

---

To use audit trail events to trigger an output pattern on one or more lines connected to the local controller, follow these steps:

1 Assign a name to the trigger. Uniqueness is not enforced so the same name may be used for a trigger on a different controller.
2 Select the group where the events originate from. Some events have no associated group. This includes system events, events from auxiliary, UPS, and tamper inputs.In that case, select All Groups from the selector.
3 Use the item-chooser to select one or more audit-trail events.
4 The trigger may be optionally modified to only execute when input lines connected to the controller or expanders are in the desired states. The Input States Logic Editor uses boolean logic (And/Or operators) and selected inputs paired with a selected state. States on inputs are either high (default) or low. Pressing a button wired to causes a low state. A delay may be added to pause before the input line state is evaluated. This might be useful if some time is needed to ensure the state(s) have settled.
5 Choose Send Output Pattern to Selected Outputs on this Controller.
6 The trigger may optionally be contrained to execute only during the time frames of a selected schedule. If this is required check the box and select a schedule from the selector. The schedule may further be bound by a beginning and end date.
7 Use the item-chooser to select one or more output lines. Note that relay outputs with connected to a Door Controller may not be selected for triggers. Responses for Door Controllers must be created using Inter-hub signals.
8 A delay of up to 30 minutes may be added to wait before the trigger executes. If no delay is desired, select None.
9 Select an Output Pattern from the Pattern selector. Additional Output Patterns are created and listed on this page.
10 Click Save.

Additional notes about Triggers:

• Inter-hub signals have priority over triggers. An Inter-hub signal will override output behavior on any output currently executing a trigger. However if an output behavior is not specified for a given output, the output behavior specified in the trigger will continue.
• A trigger will not override output behaviors specified in an Inter-hub signal. However if an Inter-hub signal does not specify a behavior for an output, a trigger may execute an output pattern for that output.
• A trigger which toggles a relay will override a door being held closed in a Man Trap. If that door were opened, it would also generate a Flex II audit event 578 (Door Opened Without Access Permissions).
• Once created, triggers should be tested to ensure they operate as expected.
• If delays are used before evaluation of inputs or execution of output, the schedule, if used, is NOT evaluated again after those delays. It is only verified to be in-schedule immediately following the triggering event.
• unlike Inter-hub signals, triggers are not tracked by the server and not persisted in storage on the controller. If the hub is restarted during an 10 minute execution delay, it will not resume a trigger. This is unlike an Inter-hub signal which will resume upon hub startup.
*Note