Create folders (e.g. lighting, heating) for the products, as well as the internal communication objects such as the EIB objects (group addresses) that are to be controlled by the HomeServer. The internal communication objects are not transmitted by the HomeServer to the EIB and serve in the first instance as auxiliary variables for comparison in the logic or for the control system in the HomeServer, etc. The EIB objects are termed external communication objects. To simplify matters, this information is termed by the HomeServer as (internal or external) communication objects. You can create your own objects or import them from the ETS (see
Import). The number of these objects that you can create in the HomeServer depends on the amount of free memory in the HomeServer.
When required, the current values of internal communication objects remain intact after a restart of the HomeServer; there is an ID for this for each communication object -
retentive memory.
EIB can be read out via the bus on a re-start.
To create an internal or external communication object, switch to the "Communication object" window. Select the menu item "Internal" or "EIB". Press the right mouse button. A pulldown menu opens. Select "Create object". To obtain a better overview, you can also sort several communication objects belonging to one area into folders. These can be created like communication objects.
EIB objects can be imported from an ETS print file or an OPC file using
Import. To do this, press the "Import" button for EIB objects.
Yes: The communication object is
retentive.
Comments: If this ID is used, then
"Request on start" is not possible. Communication objects of type time, date or 4-bit (dim) can not be stored retentive (permanently).
List
A list of values is gathered here.
The actuator is changed by the values set in the lists. e.g. "10,28,68,95"
These constants are addressed by a command.
In the previous example, a dimmer jumps from zero per cent to 10%, to 28%, etc.
If the dimmer is at 80% and the value is decreased in accordance to the list, then it assumes the value 68%.
Group address
The group address is determined here.
Two-digit or three-digit notation can be used.
A group address can only occur in a project once.
It must be unambiguous.
To separate the numbers, any non-numeral, e.g. an empty space, can be used.
Every non-numeral is thereby automatically converted to a "/".
Examples:
1/7 or
1/0/7 Internal communication objects only have one group address when they are to be recorded in the
EIB monitor.
The address space is hereby outside of the EIB address space. In this case, the "main group" is between 100 and 199.
Watch address
Every communication object can be assigned any amount of watch objects.
If this group address is changed on the bus or in the HS, then the value of the IEB object is requested on the bus.
Dim objects and switching objects on the brightness value of a dimmer, for instance, are entered here .
Background:
The watch objects were created due to the demand that the HS should display the correct brightness value (%) (i.e. the current status).
If then in a building with a push button sensor, a 1-bit or a 4-bit telegram is transmitted, the brightness value changes.
This however, is not updated by (older) dim actuators.
Switching and dimming is therefore attached to the brightness value, which is used for the display in the HS.
If something happens there, then the communication object (brightness value) is requested on the bus.
In modern dim actuators there is another possibility, as long as there is a response object for the brightness value (dim actor) .
In this case, watch group addresses are not required and the response of the brightness value can be attached to the actual object (brightness value)
as a monitoring group address.