Overview of the timer programs
Up to 100 timer programs can be defined per (eBus master) location. Each timer program can include 25 actions. The following actions are possible:
| Aktion | ab Version |
|---|---|
| Switch switch group | 4.5 R3 |
| Activate target value | |
| Activate tariff |
Note:
These timer programs do not control energy data updates, structural data calculation, energy data monitoring, etc. These are individual processes in visual energy 4.
Name:
You can enter any designation you want for identification purposes.
Validity period:
You can define timer programs in advance by setting a starting and ending time. However, the individual timers, for example for daily switching, are only executed within the validity period of the timer program.
Type:
There are two types of timer programs: 'daily' or 'weekly'. Daily programs start and end on the same day. You also have to define on which week days the program is executed (Mo, Tu, ... Su). A weekly timer program can include several days. Here, the pattern for the starting and ending time is expected to be a day and time (Fr 18:00 to Mo 06:30).
Priorities (version 4.6 and higher):
If two time programs are set for the same action, the time program with the higher priority (smaller number) "wins".
Please note:
You can activate/deactivate any timer program with the 
or 
buttons. A deactivated timer program is never executed, not even within its validity range!
Creating/editing timer programs
In the eBus master configuration, switch to the location you want. Select the 'Timer program' page. A list of the timer programs that have already been defined appears. Click on the 
button to create a new timer program. Enter the name, type and validity period.
With the priority setting, you can define which timer program is more important. This means that the timer program with priority 1 can override the actions of a priority 2 program, which may be the same.
Define actions
You can define up to 25 actions within a timer program. To add an action, click on the 
button. To edit one, click on 
.
Zustände:
| Status | If this status occurs, the following command is issued: |
|---|---|
| Waiting (not activated) | No command |
| Wating Auto | Activate the 'Auto' status if the meter point is not executed. |
| Wating Off | Activate the 'Off' status if the meter point is not executed. |
| Wating On | Activate the 'On' status if the meter point is not executed. |
| Active (not activated) | No command is issued if the meter point is executed. |
| Active Auto | Activate the 'Auto' status if the meter point is executed. |
| Active Off | Activate the 'Off' status if the meter point is executed. |
| Active On | Activate the 'On' status if the meter point is executed. |
Example 1:
An independent switch group (no load management or reactive current compensation) should be defined as ON during operation. Otherwise, it should be defined as OFF. Set the configuration to 'Waiting Off' and 'Active On'.
Example 2:
A switch group that is also used for load control in connection with a multimax D6 should be defined as OFF during operation and assume the respective optimization state in all other cases. Set the configuration to 'Waiting Auto' and 'Active Off'.
Example 3:
An independent switch group (no load management or reactive current compensation) should be defined as OFF during operation. Otherwise, any state can be permissible, e.g. by manual switching. Set the configuration to 'Active Off' and remove the check mark for Waiting (not activated).