This function is used by the HS/FS to record KNX telegrams (events) with a value over a time period. The telegrams can be sent after recording on the KNX (play and simultaneous recording options).
Occupancy simulations can be imported and exported via the Global Library.
Only telegrams of defined KNX devices are recorded. The respective value of the telegram is recorded. In addition to the time period, the number of KNX telegrams to be recorded can also be limited.
Occupancy simulations can be imported and exported via the Global Library.
Only telegrams of defined KNX devices are recorded. The respective value of the telegram is recorded. In addition to the time period, the number of KNX telegrams to be recorded can also be limited.
Important
If the HS/FS date is changed, the content of the occupancy simulation can be deleted!
1.States
The occupancy simulation has 2 states:
- Recording or
- play and simultaneous recording
Recording runs continuously if the HS/FS is switched on and is connected to the KNX.
Occupancy simulation records all the changes to the assigned group addresses. Group addresses with central objects are also recorded accordingly in the event of changes to the central object. Entering the central addresses in occupancy simulation is not advisable.
Occupancy simulation records all the changes to the assigned group addresses. Group addresses with central objects are also recorded accordingly in the event of changes to the central object. Entering the central addresses in occupancy simulation is not advisable.
2.Example
Recording duration 1 week (MON to SUN), 5 group addresses.
The HS/FS must first record a week, occupancy simulation can then be executed after this. If occupancy simulation is now started (play) after 9 days (TU) at 15:00, the HS/FS sends the telegrams of 7 days previously (TU) to the KNX at 15:00.
The HS/FS must first record a week, occupancy simulation can then be executed after this. If occupancy simulation is now started (play) after 9 days (TU) at 15:00, the HS/FS sends the telegrams of 7 days previously (TU) to the KNX at 15:00.
Max. actions
This number indicates the maximum number of events (KNX telegrams) that can be saved. Maximum is 30,000.
The data is saved retentively.
The memory is designed as a ring memory, if more telegrams are created in the set time period, the oldest telegrams will be automatically deleted.
The data is saved retentively.
The memory is designed as a ring memory, if more telegrams are created in the set time period, the oldest telegrams will be automatically deleted.
Time period
This sets the time period (hours, days, weeks) over which the telegrams are recorded. The data will be overwritten when this time period has elapsed.
Control
A communication object is assigned here.
This communication object controls the behaviour of the occupancy simulation.
If this communication object has the value 0, the data is recorded for the occupancy simulation.
If this communication object has the value 1, the occupancy simulation is active, i.e. the saved telegrams are sent to KNX.
At the same time, these telegrams are recorded again for the occupancy simulation. Additional telegrams from the KNX are not taken into account for the occupancy simulation, i.e. the number of saved actions remains constant! After processing of the ring memory the process starts again from the beginning.
This communication object controls the behaviour of the occupancy simulation.
If this communication object has the value 0, the data is recorded for the occupancy simulation.
If this communication object has the value 1, the occupancy simulation is active, i.e. the saved telegrams are sent to KNX.
At the same time, these telegrams are recorded again for the occupancy simulation. Additional telegrams from the KNX are not taken into account for the occupancy simulation, i.e. the number of saved actions remains constant! After processing of the ring memory the process starts again from the beginning.
Saved actions
A communication object can be assigned here.
This communication object contains the number of events currently saved in the occupancy simulation.
The number of processes should be monitored at the beginning, so that, if required, the "time period" or "Max. actions"" can be modified.
This communication object contains the number of events currently saved in the occupancy simulation.
The number of processes should be monitored at the beginning, so that, if required, the "time period" or "Max. actions"" can be modified.
Communication objects
The list shows the communication objects which can be saved and retrieved in the occupancy simulation. The operating buttons for editing the list are located to the right of the list.