An event links one or more triggers to actions. This allows you to combine multiple, indivial measurement values to a status.
Each trigger as well as each action must be assigned to at least one event in order to be initialized.
Each event has the following base parameters:
|Description||Name / description of the event|
|Force Actions||If enabled, each trigger update invokes the actions associated with this event - even if the event status remains the same|
|Troubleshooter||Enable the troubleshooter feature|
|Enabled||If disabled, the event won't be initialized|
|Pause until||When an event is paused, actions associated with that event are no longer executed during the specified time period.|
The boolean operator affects the event logic. If you choose
AND, all triggers linked with this event need to be active for the event to switch to
On, whereas only one of the triggers needs to be active when you select
You can add as many triggers to one event as you like. They are logically combined by the boolean operator set in the event settings. There must be at least one trigger per event.
When adding a trigger to an event, you can configure the following parameters:
- Status: Current trigger status
- Status Code: Trigger status code (can be left empty)
negate negates the trigger (XOR):
|Trigger Status||Negated||Status in Event|
The trigger states are as follows:
|No State||Trigger status is unknown|
|Off||Trigger is off (condition not matched)|
|On||Trigger is on (condition matched)|
|Failed||Trigger has failed (e.g. lost connection, internal error)|
|Initialized||Trigger has been initialized by Broadcast Suite Core, but no data has been received so far|
|Initialization failed||Trigger initialization has failed (e.g. due to missing parameters, invalid configuration)|
|Disabled||Trigger has been disabled by user|
Whenever the status of an event changes, a set of actions can be executed. You can define the execution point of each action with the
Action State parameter:
|low to high||Execute action when the event changes from |
|high to low||Execute action when the event changes from |
|both||Execute action on every status change|
Actions can be sorted with drag and drop and are executed sequentially. The top-most action (first entry in the action list) is executed first.