Function block | |||
  |   |
,-------------, | .'11 12 1'. |------ Output | :10 \ 2: | | :9 @-> 3: |------ Scene On | :8 4; |------ Scene Off | '..7 6 5..' | | Mo,Di,...Su |------ Logic (Gates an Time-Delays) '-------------' |
|
Configuration | |||
  | Active |
You can use this circuit to switch a timer on and off. |
|
  | Name |
Give the timer a name. The name improves the clarity and enables you to reference this timer using the name in another place, for example in the operations or time-delays. |
|
  | Settings |
You can use the |
|
  | Delete |
By pushing the delete button, you launch the relevant time switch with standard values. |
|
  | Time |
The time switching points are entered here using the 24-hour clock. |
|
  | Value |
There are three options to choose from for the value. "-" for do nothing, "on" for switch on and "off" for switch off. |
|
  | Weekly profile |
You can use this button to determine the individual days on which the time switch is to function. |
|
  | Trigger |
The trigger decides whether the time switch takes on its status immediately
after the launch or reconfiguration of the system, or only after the configured
time switching points |
|
  | Output |
Here, you can specify that the time switch has a direct effect on output, as defined, for example, in the technologies KNX, EnOcean etc. |
|
  | Scenes |
Here, you can specify that the time switch on a scene is forwarded. If an "on" signal is generated, the "on" scene is carried out. If an "off" signal is generated, the "off" scene is carried out accordingly |
|
  | used by |
If the time switch is used as an input by one or more instance(s), such as an operation or a time-delay, a corresponding list of these instances is shown here. |
|
FAQs | |||
  |
Do outputs and scenes have to be entered in the configuration fields? |
||
  |
What status does a connected operation provide on days that are not marked
in the weekly profile? |
||
  | |||
  | |||
  |