Summary
Problem: Room functions are to be transferred to other rooms. Several rooms are separated by sliding walls. Depending on whether walls are open or closed, the commands of each sensor within the open rooms should be forwarded to all actuators that perform functions in these rooms.
The number of rooms and partitions should not be limited.
The number of functions per room (switching, setting, dimming, regulating… of arbitrary actuators of any trades) should not be limited.
Solution: In the global script of the process server, changes to an actual value of a space function are registered. If the change originates from a room with movable walls, all connected rooms will receive this value for this room function as a target value.
The names of the data points for room functions and walls must be specially constructed for this purpose.
The special feature of this solution: It does not require any further calculations of data point properties. The global script does not need to be changed.
Attention: Only from version 2.1.1.185 it is possible to search in the data points at runtime. Therefore, this version, or a higher, is essential for this solution.
Details
The name of a data point that is to belong to the MRC as a spatial function must be structured as follows:
MRC_ROOM_space_designation_space_function
e.g.: MRC_ROOM_Wohnzimmer_Dounlight or MRC_ROOM_Halle_Jalousie
Each ROOM data point must have the user-defined property MRC_dirty. Their type is Boolean. So that the calculation does not abort with “Type mismatch”, the dirty flag must be set once manually (data point properties).
The name of a data point that is to belong to the MRC as a wall (room divider) must be structured like this: MRC_WALL_first room_second room_ e.g. MRC_WALL_Wohnzimmer_Halle_ or MRC_WALL_Tagungsraum12A_Tagungsraum12B_ Note the underscores! The ActualValues of the WALL data points should be persistent!
The global script of the MRC solution as a text file (4.5 KB).
The sample project: mrc.db (1100 KB) mrc.iep (40 KB).
