<< Click to Display Table of Contents >> Navigation:  Design > Important notes

 
Please always save your projects on the local hard drive. Always open them locally, not from a cloud drive.

Automatic synchronisation can damage the project files and lead to the total loss of the project. You can save the project data in the cloud as a backup. Please ensure that the projects and the editor are completely closed when copying.

 

Project files that are copied and/or moved at file level can result in the project no longer being able to be opened.

 

Drag & Drop:

When inserting components, make sure that the new components are NOT stored on a panel or macro panel.

No more than 1024 components can be created per page.

 
Working with graphics:

The visualization allows you to use all popular pixel graphic formats. It should be noted that the graphics files are each inserted in full resolution, i. that z. For example, images created with the digital photo might have a file size of 2 MB or more. In the PC, the required memory can easily be 5 times larger. With multiple use of such graphics can quickly be needed much memory. This then causes a slowdown of the system. For this reason, please use files in the actual required size (pixels). The smaller the graphics, the faster the download of the project to the different clients will be. This is important when connecting over the Internet.

As file format we recommend * .png. With this can be, for example, Transparency and partial transparency and the file size can be reduced very well. As a processing program, we recommend the free image editing program GIMP (https://www.gimp.org). This makes it possible to create slim and fast surfaces.

 

For App / WebApp:

If plotters are created in the project, they should be on a separate project page. When the page is called up with a plotter, the information is downloaded and only displayed when all the data is available. This then also affects components that are on the same page as the plotter, for example the app list view. The amount of data that is downloaded for historical data is limited. For this reason, data may not be displayed completely. The time range to be displayed should be selected as small as possible.

 

resolution:

For projects where the title bar, the menu bar and the scaling bar are to be displayed, a gray bar is normally displayed to the right and left of the visualization. To avoid this, the resolution in the project should be adjusted.

 

Example:

Desktop resolution: 1920x1080

Project resolution: 1920x1005

 

 

Design of the EIB / KNX system

 

Note the following guidelines when configuring a KNX installation,  for the best result of your software front end:

 

•In principle, you should not work with status feedback for actuators. Active status feedback may appear to be the optimum solution at first glance, but in practice the bus is overloaded by too many status feedbacks; this results in telegram losses. The display on the visualization, the pushbuttons and the panels are then incorrect. The main load occurs with group-wise or complete control of the KNX devices, as all devices then respond AT THE SAME TIME.
The visualisation maps the state of the KNX device object in each case, i.e. even if many group addresses are assigned, the state is recorded correctly. The only application for the use of active status feedback is, for example, circuits with time functions in outputs. Since these are usually a few/individual circuits in the project, this is not critical for the telegram load on the bus.
 

•When using KNX devices with collective objects, e.g. with KNX tableaux or dummy applications, it is necessary to solve the concatenation of the addresses in the communication object. For this purpose, an additional auxiliary address, e.g. 31/7/0-x is created in the first position of the communication object. This is not used for any other function. All other addresses are automatically created in the data point list as so-called "central addresses" and can be used normally for linking.

 

•To read out the system status, i.e. when starting the visualisation software, it is necessary to set the read flag once for each group address. The address to be read out must be a sending address, since in the case of a read request to a receiving address, the response is sent by the sending group address of the device object. For this reason, it is also important to ensure that no central addresses (e.g. total lighting ON/OFF) are entered as the sending address in the device objects to be queried. First always assign the local functions as group address and assign these to the sensor and actuator objects.

 

•To avoid reactions of other KNX devices to read-response telegrams, the update flag should be removed from the device objects concerned. In this way, the KNX devices only react to switching commands.

 

•If addresses are queried which are located in several objects or KNX devices, all objects will generally interpret the response telegram as a switching command. In practice, this means that other switching circuits for lighting and/or blinds can move or be switched on and off during initialisation. For this reason, you should create a local group address for each switching function/group (usually for each output). This should then be used to query the switching status/status. With devices of new design, it is possible to delete the update flag in the objects. This completely prevents unintentional switching as a result of response telegrams.
 

•In any case, do NOT set any read flags for all relative dimming addresses and for blind addresses for up/down and stop/slat adjustment.

 

•The EisBaer visualisation can execute the initialisation of the individual group addresses with different priorities. The same priorities are used for this as in the ETS. The priority levels entered there are adopted during the import into the KNX connection. There are 4 priorities:

 

 

Within the priority levels, the group addresses are queried in ascending order.

 

Further information on filter tables can be found in the chapter Driver\KNX\KNX Dummy / Filter Tables.