Components > Comfort

The scenarios is an unVisiblee server component, with the ability to record static states of channelsn in one out of 256 possible scenes and render them back when needed. The user can so z. B. Save values of any data points and trigger them with a keystroke. The values can be changed, saved and recalled at any time. An intervention in the programming of the surface is not necessary.

The component can use up to 999 channels for storage and retrieval. Data suppliers can be arbitrary sources, whether internal signals, KNX data points or other drivers. Each channel is defined by a unique channel name. Thus, the components is a universally applicable "value memory". When saving, the channel state and use (Ignore) are always saved.

After calling up a scene, the component monitors whether the state of a channel has been changed subsequently. If the current situation differs from the values of the scene, this is signaled via the "scene changed" output with an "on signal". If the target state of the scene is restored, the output is set to "Off" again.

To use the scenarios, a scenario editor, as Visible Client component, can be connected. The use of multiple editors on different pages of the project is also possible. This allows multiple keypads to access the same scenario building blocks, and display and operate this.

Data points of the component

Name	Type	function
Dynamic	Folder Bidirectional	Folder Dynamic displays the data points for the defined channels. These must be linked here. Each channel has 3 data points available: - Channel001 - Bidirectional (blue) Input and output of the desired signal - Channel001_Input - StatusInput (green) to set the channel. e.g. for status feedback - Channel001_Ignore - Bidirectional (blue) input and output, to set channel usage. If a true signal is applied to the data point and the scene is saved again, this channel is not connected the next time it is called up. This has the same functionality as the "Selected" option in the scene editor.
1Bit	Folder	has the subfolders Recall and Save, which each contain the inputs from 000 to 255. Here the scenes can be addressed directly.
Export (XML Text) Output	Output	Output of the scene data in xml format. This data can be sent to another scene (Import (XML Text)).
Export (XML Text) Trigger	Input	Trigger input to output the scenes at the output "Export (XML text) output" in xml format .
Import (XML Text)	Input	Input for the scene data as xml text. The data can come from another scene (export(XML text) output).
Scenario Editor	Bidirectional	Connection between a scenario component and one or more scenario editors.
Scenario Name	Output	Text output of the last accessed scene.
Scenario Number	Output	Output of the number of the last called scene. The output number corresponds to the internal memory number of the scene.
Scenario Save Name	Input	If a saved scene name is transferred to this input, the scene is called up with the corresponding name and the stored values are output.
Call Scene 000	Input	If an arbitrary signal is applied to this input, the scene is called with the internal number 000 and thus the stored values are output.
Save Scene 000	Input	If any signal is applied to this input, the scene with the internal number 000 is saved with the currently applied values of the channels. ATTENTION: The selection of the channels within the scene is set according to the states at the ignore data points. If the data points are not linked, all channels are set to "Selected" when saving.
Scene was changed	Output	If the current situation differs from the values of the last called scene, this is signaled via the "Scene changed" output with On
Call Scene XXX	Input	If a NumberValue On is set for this input, the Scene is called with the corresponding internal number and the stored values are output.
Save Scene XXX	Input	If a numerical value is applied to this input, the scene is saved with the corresponding internal number with the currently applied values of the channels. ATTENTION: The selection of the channels within the scene is set according to the states at the ignore data points. If the data points are not linked, all channels are set to "Selected" when saving.

Properties

Name	Standard	function
Channels	0	Here the individual channels are defined in a list. These then appear as a channel in the data point folder Dynamic. Channels can also be read in via a CSV file. One channel and its name is added per line. No further formatting is necessary in the file.
Send delay [ms]	0	Here, the delay when calling a scene is selected. The transmission delay is the pause between the output of two values. This allows the telegram load of the downstream system to be controlled.
Export scene on change		If this option is set, an export is automatically triggered when a scene changes.

Name

Standard

function

Channels

Here the individual channels are defined in a list. These then appear as a channel in the data point folder Dynamic.

Channels can also be read in via a CSV file. One channel and its name is added per line. No further formatting is necessary in the file.

Send delay [ms]

Here, the delay when calling a scene is selected. The transmission delay is the pause between the output of two values. This allows the telegram load of the downstream system to be controlled.

Export scene on change

If this option is set, an export is automatically triggered when a scene changes.

To call a scene with a button, the button is set to "Always on" and the send value declared as 8-bit. Then the output "Value On" can be connected to the component scenario at the input "Scene XXX".

Scenarios

Scenarios