47
Aktionen
10. Actions
The Action principle allows the Web-IO to issue individual alarms and messages
– but also to switch the outputs. This is done based on defined IO states or other
events.
Up to 12 actions can be created and managed, whereby an individual name can be
defined for each action.
Trigger
Inputs
Any input can be defined as an initiator. For the input you can specify whether a
change from OFF to ON, a change from ON to OFF, or any state change should initi-
ate an action.
Outputs
Any output can be specified as an initiator. For the output you can specify whether a
change from OFF to ON, a change from ON to OFF, or any state change should initi-
ate an action.
Counter
Any counter can be specified as the initiator. For the counter you must specify for
which count value an action should be initiated. You also need to determine whether
the counter is reset to zero after the action is initiated.
I/O combination
A combination of inputs and outputs can also initiate an action. Here you can speci-
fy whether the individual states should have an AND or OR operation performed.
Interval Timer
The Web-IO can be configured to perform actions at specified times. The times are
entered in
Cron
format.
