FAQ 2017-09-22T16:50:11+00:00

FAQ

1. KNXCONTROL

At the first startup you will only see the empty Home screen of the OPTIMA interface on the device. In order to configure your project, you have to connect remotely to the KNX CONTROL device. Please start Google Chrome on your PC and access it by typing the following URL:

(default:) http://192.168.0.110

If you get a certificate warning, please confirm the certificate in order to connect to the interface!

In order to login, please use the following user/password combination:

User: admin
Password: admin

Afterwards you can access the OPTIMA Administration area. Just follow the instructions in the OPTIMA Administrator-Manual.

This problem can have a lot of causes. If you are facing the problem that you get completely no communication, please check the following points:

  • Is the connection between the KNXCONTROL device and the KNX bus OK?
  • Is the bus signal OK (bus voltage, polarity, signal strength, etc.)?
  • Is there an address conflict with the KNXCONTROL device? (Default physical address: 0.0.255)
  • Is it possible that telegrams from / to the KNXCONTROL device are blocked by a line / area coupler? In this case you have to create a dummy object for the KNXCONTROL device within your ETS project, which is consequently added to the filter tables of the line / area coupler and allows the communication.
  • Please access the „License and module management“ page through the administration menu and check if the KNX module is licensed correctly. If not, please contact our technical support.

If you are able to realize at lease a one-way communication (e.g. sending OK, receiving NO), please check the following points:

  • Is it possible that telegrams from / to the KNXCONTROL device are blocked by a line / area coupler? In this case you have to create a dummy object for the KNXCONTROL device within your ETS project, which is consequently added to the filter tables of the line / area coupler and allows the communication.
  • Please check inside your project if you have connected the feedback objects correctly to the command objects. If an object is not connected to its feedback objects, it can write on the bus, but it will not be refreshed through the bus. In the OPTIMA Administrator-Manual you find the information, how this is realised.

As last advice, please try to export your database (as backup copy), reset the database of the KNXCONTROL device to factory defaults and try to import either an older backup or retry the import the compatible ETS import file.

If none of these hints can help you to resolve your communication problems, please get in contact with our technical support.

Please not that this function is currently not supported for ETS versions newer than 4. We are working on it. If you have ETS3 or ETS4, read on:

When using this feature in the local network, it is really easy to configure the KNXCONTROL device in ETS: just create manually a new communication interface of type “KNXNet/IP” and insert the IP address of the KNXCONTROL device. In the connection the interface can be selected and used for example for the programming of KNX devices or the control of the group monitor. This feature is always active and doesn’t affect the functionality of the visualisation.

The same functionality is available also remotely; in this case the following additional steps have to be done:

  • In the administration menu of the KNXCONTROL device login credentials for the ETS gateway must be created
  • For the port 1723 a port forwarding to the KNXCONTROL device must be set up in the internet router

In the connection you can create a VPN connection from your PC to the network where the KNXCONTROL device is running and create a new interface in ETS just as described before. Further information can be found in the OPTIMA Administrator Manual.

Tools and software provided by DIVUS are available for download in the download area.

Manuals and additional information about the KNX CONTROL products are available for download in the download area.

If not explicitly specified otherwise, all files offered for download are intended to be used for the latest hardware version and software version of the respective devices.

PDK Versions:

For KNXCONTROL devices with production date:
– KNXSERVER May 2012 to March 2016
– KNXSUPERIO February 2013 to March 2016
the version 1.3.6 of the PDK can be used.
Download PDK 1.3.6

For KNX CONTROL devices with production date April 2016 or later (with Optima 2.x) you may find the PDK in the download section or directly on the PDK page.

Projects:

The projects created with the PDK may be transfered to KNX CONTROL devices with the same or newer software version.
Projects can not be transfered to KNX CONTROL devices running older versions of the software.
A project created e.g. with PDK 2.0.1 can’t be transfered to a device with Optima 1.3.6! The procedure in the opposite direction is not a problem.

Demo project for PDK 1.3.6

Database backup

Images backup

Optima 1.3.x manuals

Furthermore, you can find the manuals for your device here:
Administrator: Administrator manual
User: User manual

Intercom module manual

Data logging module manual

Scripting module manual

All other manuals may be downloaded from the download section.

Updates:

KNXCONTROL devices with production date up until March 2016 can not be updated to Optima version 2.0 or newer. Update attempts using the update files will lead to failure with an error message which will interrupt the update.

If your device was produced in the time frame shown above, you can update to the latest version of Optima 1.3. Choose the file according to the kind of device as listed here:
KNXSERVER: Update KNXSERVER (May 2012 to March 2016) 1.3.6
KNXSUPERIO: Update KNXSUPERIO (capacitive) (February 2013 to March 2016) 1.3.6
KNXSUPERIO (resistive): Update file KNXSUPERIO (resistive) 1.3.1

For KNX CONTROL devices with production date April 2016 or later you may find the update files (if available) in the download section or on the product pages directly.

*** NEW *** starting from version 2.2.0 you can use online updates to keep your device up to date. See Point 2.22 of the FAQ or directly the DIVUS OPTIMA Administration Manual.

It is generally recommended to make a complete backup of the project and a reboot before updating.

2. OPTIMA

Within the OPTIMA surface in many places you will be confronted with actions that can be realized by using „Drag & Drop“. This concept in OPTIMA is used everywhere you have to create connections between objects; no matter if you want to connect KNX objects with their feedback object (wizard menu „Connection of the KNX functions“), to connect KNX objects to a new group / page (wizard menu „Creation of the visualisation“) or to add elements to a scenario / a logic / a timer group: in each of this cases you will open the side panel by clicking on the title of the desired sections and can then select the desired object in the side panel, „drag“ it to the desired area and „drop“ it there. This technique is used in nearly all the configuration menus of the OPTIMA interface; once you understood the concept, you will be able to configure the different functions really easily and quickly.

It can be that you are currently visualising a page, whose contents are bigger than your browser window. In this case, on the right side you should see a small, grey bar, which permits to scroll through the contents of the page. Alternatively, you should also be able to scroll by using your mouse wheel.

Image files in the OPTIMA interface are partially scaled, partially kept in its original size; therefore it is important that you define the image size depending on the client devices you are planning to use. The following information should simplify your selection:

Home-screen: the image file is scaled automatically to the corresponding screen size. Nevertheless you should try to use the nearest possible resolution, since scaling actions require a lot of performance and – if the scaling grade is too high – can cause artifacts.

Background view: the image file is shown in its original resolution: if the image is smaller than the screen, the image is shown normally and the remaining space is empty; if the image is bigger than the screen, only a part of the image will be shown. Therefore, these image files should be selected depending on the resolution of the client device.

Starting from OPTIMA v.2.x you know can also use the zoom function in the single rooms’ settings. In this way the background image will be scaled (zoomed) to match the available screen size within a customizable range (default is 70% – 130% of the image’s size).

Grid view: the grid view modes are working with some fixed values:

  • Image on top: fixed height of 256 pixel
  • Image right: fixed width of 512 pixel
  • Image left: fixed width of 450 pixel

The shown image depends on one side on those fixed values, on the other side on the second value which depends on the current resolution of the client device. Let’s look at an example for the image on top: at a resolution of 1680×1050 pixels the image will be shown correctly if it has the resolution 1650×256 pixels. If we are looking at the same image on a display with resolution 1366×768, the image will be cut, since the height of 256 pixel remains the same and the available width on the second device is smaller. In the inverted case (the image file has a resolution of 1366×256) instead the image will be scaled on the screen with 1680×1050 pixels (from 1366×256 to 1680×315 pixels); since the height is fixed, only 256 of the 315 pixel will be shown, the rest will be cut.

We recommend PNG and JPG formats of the size of your biggest screen.

To  create or crop background images for DIVUS TOUCHZONEs or devices with similar resolutions, you might find this template useful:

OPTIMA applies changes immediately, but doesn’t write them to the flash storage instantly, in order to spare the storage. The long-term saving is executed every 5 minutes automatically: if in this time frame there are non-saved changes, the “Save” button in the administration menu will turn red. You can store the data also manually by simply clicking on the red button but it is an important step only before powering off or rebooting the device.

OPTIMA offers a clear and detailed technical documentation, further the system contains an information and help system. Nearly every page contains information about the available functions / options, furthermore many pages offer a help button (question mark) with even more detailed explanations and examples.

However, if it should happen that you are stuck or feel insecure with certain parameters, don’t worry: just try to realize the desired actions / functionalities and you will see that in most cases your questions will be answered automatically. And if not, you can still contact our technical support.

Please note that OPTIMA is a browser-based software: this means that the OPTIMA interface uses the browser cache in order to store different contents. When you make changes remotely, those will only be visible locally on the panel as soon as you will make a refresh of the interface. This can easily be done by clicking on the SYNC-icon in the lower right corner of the interface (opened navigation menu). In the OPTIMA APP the refresh can be made through the APP settings.

The KNX CONTROL device during the import of the ETS project automatically checks if the project contains multiple relations (e.g. communication objects connected to more than one group address).

If for example the channel of an actuator is controlled through the group address 0/0/1, but its status is returned through group address 0/1/1, in the ETS at least one related communication object (typically the one of the device that is used as sensor / switch or input) must be connected with both group addresses, so that the KNX CONTROL device can recognize and create the relation. Otherwise, no commonality can be found and both group addresses are imported completely independently from each other. In this case, the relation must be created manually using the administration menu of the KNX CONTROL device:

  • Open the properties window of the KNX object of the COMMAND group address
  • Enable the EXPERT mode using the button in the upper right corner
  • Now an area with connected group addresses should be shown
  • Activate the search filter and use the search function (upper left corner) in order to locate the STATUS group address you want to connect; Please be sure to search for the object of type “KNX group address” (grey)
  • Once located, drag the group address into the area of the connected group addresses
  • As communication type, please set “READ ONLY”
  • Check that the “primary” group address – the COMMAND group address – is on top of the connected group addresses; if not, please drag it to the top
  • Save and test the created relation

If group addresses for the status feedback are used, please mind that the primary (command) group address is configured as “WRITE ONLY” and that the secundary (feedback) group address is configures as “READ ONLY”

OPTIMA 2.x introduces a new mechanism to automate the coupling of these addresses. Through customized rules referring to the names or to the group addresses of the objects, the system may be taught what logic to use to recognize the addresses to relate to each other. For further details, see the administration manual, chapter 5.5.

Yes. When importing the second project it is only important to disable the option “Delete existing KNX objects:” and “Remove non existing KNX objects:” (EXPERT mode) in order to keep all the objects that are not present in the new ETS project anymore. Afterwards the visualisation will contain the KNX objects of both imported projects.

Please consider one thing: if the project imported as last one contains group addresses, which were already present in one of the previous projects, they will be refreshed based on the information in the last project and therefore will not be working in the older projects anymore.

Thanks to the COMPLEX OBJECTS it is possible to combine several KNX functions in one graphical symbol and therefore keep the visualisation clean and easier to control. Find below a list of complex objects, which are already predefined in OPTIMA:

SHUTTERS: up/down, stop, value%
DIMMER: on/off, value%
RGB: control of the different color channels and the intensity
THERMOSTATS: measured temperature, different setpoints, operating mode, ventilation speed etc.
WEATHER STATIONS: brightness, temperature, wind, rainfall
EMERGENCY LAMPS: operating mode, status, alarms, function texts etc.

Furthermore also a general complex object exists, which permits to create your own complex objects without any restrictions.

In general before each update the data of your KNX CONTROL device should be saved, therefore a backup of the database, pictures, scripts and maybe also of the tracked energy data should be made.

Once you started an update procedure, please never interrupt it! Wait until you see the result page!  It may take up to 4 – 5 minutes to see the concluding message.

After the successful update of OPTIMA to the actual version and the restart of your KNX CONTROL device through the green “Restart” button, the local browser cache has to be cleared; this way the local browser cache will load all changes introduced with the new OPTIMA version.


Update OPTIMA 2.2+

If your device is on version 2.2.0 or newer, you may use the online update mechanism. Go to OPTIMA’s administration area and switch to BASE view. Then load the update page and simply push the UPDATE button. If there are newer versions available, the procedure will load and install the newest version automatically. Refer to the DIVUS OPTIMA administration manual for further details.

Update OPTIMA 2.0 and 2.1

You may find the latest update file on the download page or on your product’s page.

Update OPTIMA 1.3.x

If your device is already equipped with OPTIMA 1.3.1 then you can directly apply version 1.3.6. Please read the FAQ point 1.6 for the download link and further details.

Update OPTIMA 1.2.1 and 1.3.0

To update a KNX CONTROL-device equipped with version 1.2.1 or 1.3.0 of OPTIMA (>=1.2.1 & <1.3.1) it is needed to update OPTIMA first to version 1.3.1, before the update to a newer OPTIMA version can be done. OPTIMA 1.3.1 can be downloaded here (the usage of Google Chrome is recommended):

KNX SERVER (DIN-rail device),

KNX SUPERIO Capacitive (capacitive touchscreen),

KNX SUPERIO Resistive (resistive touchscreen) – Last update for this product

Once the update-package matching your KNX CONTROL-device is downloaded, the update can be performed as explained in the manual.

Update OPTIMA 1.1.5 and 1.1.8

To update a KNX CONTROL-device equipped with an older version of OPTIMA (>=1.1.5 & <1.2.x) it is needed to update OPTIMA first to version 1.2.1, before the update to version 1.3.1 and afterwards to the actual OPTIMA version can be done. OPTIMA 1.2.1 can be downloaded here (the usage of Google Chrome is recommended):

KNX SERVER (DIN-rail device),

KNX SUPERIO Capacitive (capacitive touchscreen),

KNX SUPERIO Resistive (resistive touchscreen)

Once the update-package matching your KNX CONTROL device is downloaded, the update can be performed as explained in the manual.

Update OPTIMA 1.1.3 and lower

If a KNX CONTROL device is equipped with OPTIMA 1.1.3 and lower, please get in contact with support@divus.eu to obtain the corresponding update instructions.

Previous OPTIMA generation can’t be updated

Devices equipped with the previous generation of OPTIMA can’t be updated to the actual version.

To identify the OPTIMA generation installed on your KNX CONTROL device check out the following screenshots:

Previous OPTIMA generation (no update possible):

optima_alt

Actual OPTIMA generation (update possible):

optima_neu

If after the successful reboot of the KNX CONTROL device after the update the web interface doesn’t show the entire menu, then the browser cache of the Google Chrome browser has to be deleted.
To delete the browser cache you have to make the following steps:

  • Open chrome://settings/clearBrowserData (Insert the URL directly into the URL field or press [Ctrl]+[Shift]+[Del] or open it over the Google Chrome menu > “Tools” > “Clear browsing data”)
  • Select the time period: “the beginning of time”
  • Select “Empty the cache”
  • Click on “Clear browsing data”

Now you can reload the web surface of your KNX CONTROL device and the entire content should be displayed correctly.

Google Chrome in version >40 is not able to interpret the HTML5 cache files correctly on access with HTTPS and continues therefore to reload them, which results in no possible access to the visualisation. This access over HTTPS should only be used for remote access and not for local access.
The solution is pretty simple:

  • Use an older version of Google Chrome, e.g. Google Chrome Portable (executable without installation)
  • Use a different Browser e.g. Mozilla Firefox.

An other solution to solve the problem is to deactivate the HTML5 cache, but this results in a slower operating of he visualisation, because the different information isn’t stored and has to be loaded on each change of the visualisation page.
To deactivate the cache complete the following steps:

  • Access the administration area of the KNX CONTROL device (e.g. http://192.168.0.110/?context=configuration)
  • Navigate to “Customization” > “Options” > “Advanced”.
  • Disable the checkbox “Enable cache HTML client” and click on save.

Now the access over HTTPS with Google Chrome in version >40 should be working fine without problems, maybe it is needed to delete the browser cache first

On mobile devices it is possible that the same behavior is shown on access over HTTPS. In this case we recommend to use the DIVUS OPTIMA APP, which can be downloaded and installed over the corresponding APP store.

Uploaded symbols are filtered by OPTIMA depending on their name. This makes the compliance of certain rules regarding the naming of the symbols necessary, otherwise the symbols (icons) are not always shown in the selector.

Category Prefix for the filename Example
Rooms ico_environment_ ico_environment_fitness_room.png
Cameras ico_camera_ ico_camera_odcam1.png
Other categorie ico_ ico_special_device.png

To ensure an uniform representation and integration of the uploaded symbols into the design of OPTIMA the corresponding chapter in the administration manual should be taken as a guide.

To display 14-Byte string values correctly in OPTIMA the correct “ETS encoding” (visible only in EXPERT mode) has to be selected for the corresponding “KNX object”.
For 14 byte values the following 2 options are possible:

  • Character string: This ETS encoding transforms the value internally from a hexadecimal string into a character string which is handled in all sections of OPTIMA as a textual string.
  • Character string (RAW): This encoding doesn’t transform the value internally. The value is handled as a hexadecimal string in OPTIMA. Only inside the visualisation in the object used to display the text the hex value will be transformed into a textual string. In each other section the hexadecimal value is shown e.g. in the display area of a complex object, … .

To use features like the remote connection to the server and the voice control it is needed to access the visualisation of OPTIMA over HTTPS. On each access a security information is displayed, which has to be confirmed before the visualisation can be accessed. To get rid of this confirmation on each access the certificates have to be install once on the client device and afterwards these step will be left out.

Starting from version 1.3.2 OPTIMA is able to generate SSL certificates for a saver access. To use this new function it is needed to make a short operation on each client device which should access the visualisation of OPTIMA.

The operation is pretty simple but it differs slightly depending on the used operating system. The operation will simply insert DIVUS as a trusty source for SSL certificates for the browser and Java.

This operation has to be done only once for the device which should access a DIVUS product.

If a client is not configured to accept certificates created by DIVUS as trustful, on an access to OPTIMA over HTTPS a red crossed padlock is displayed in the URL field and there will be shown different warnings on each access.

If the client is configured to accept DIVUS as a trusty source a green confirmed padlock is displayed.

To configure DIVUS as a trusted source, the CA certificate has to be installed on the client device.
To install the CA certificate the following must be done:

Windows 7 & 8 – Google Chrome

  • Login to windows as an administrator.
  • Download the CA certificate.
  • Double click on the downloaded certificate (rootCA.DIVUS.crt).
  • If a dialog is shown click on “Open”.
  • Click on “Install Certificate…”.
  • During the import process select “Place all certificates in the following store” and click on browse.
  • Select “Trusted Root Certification Authorities” and click on “OK”.
  • Click on “Next” and confirm the shown security message with “Yes” to complete the import and close the window.
  • Afterwards a small message appears that the import process had been completed.

Windows XP and 2000 – Google Chrome

Apple MAC

  • Download the CA certificate.
  • Double click on the downloaded certificate (rootCA.DIVUS.crt).
  • Add the certificate to the keychain of “System” (if keychain of login is used, other users won’t recognize DIVUS as a trusted source of certificates).

Apple iPhone/iPad

  • Open Safari on the desired device
  • Open the URL of the CA certificate.
  • The setup for the installation of the certificate will open automatically.
  • Click on “Install”.
  • Click again on “Install”.
  • Finish the setup by clicking on “Done”.

Android
Each android version can handle the installation of certificates in a different way, therefore there is no one way solution for it.

  • Open the Browser on the desired device.
  • Open the URL of the CA certificate.
  • Confirm the installation of the certificate and follow the given instruction on the device.

Java
This operation has only to be done if the integrated WEB phone of OPTIMA should be used and to prevent warnings regarding Java.

  • Download the CA certificate.
  • Open the control panel of Java and go to the flag “Security” and press “Manage Certificates…”.
  • Open the flag “User” and click on “Import”.
  • Select the previously downloaded CA certificate (rootCA.DIVUS.crt).
  • If needed repeat this operation for other users which should access OPTIMA

The certificates had been installed but the green HTTPS padlock is not displayed
Some antivirus programs are interrupting the normal certificate handling and refusing the certificates even if they had been installed correctly.
In this case the settings of the antivirus program must be changed.

In combination with the CA certificate on the client device the web certificate will enable a secure connection between the client and the server.
The KNX CONTROL devices are regenerating the web certificates for the HTTPS access automatically.

The regeneration of the web certificates is only working if there is an internet connection, otherwise the original certificates remain untouched.

The regeneration of the web certificates is triggered in the following situations:

  • The firmware version is updated.
  • The IP address had been changed.
  • The domain for the remote access had been changed.
  • The button “REBUILD” for “Regenerate web certificates “in the maintenance page is clicked; In this case the “REBOOT” button of “Restart web services” has to be triggered manually after the regeneration of the certificates.

The remote access domain is needed to create correctly working web certificates for the remote access to the server over HTTPS.

If the remote connection is not used it is not needed to define a remote access domain. Otherwise, insert it in the section “SSL certificates – Remote access” in the field “Domain or public IP” in the network settings page of the KNX CONTROL device.

If the address for the access is for example “https://example.dyndns.org:8443” the resulting domain is “example.dyndns.org” or if it is “https://123.213.132.231:8443” the resulting domain is “123.213.132.231”.

To get an API Key/ID, you must register here www.worldweatheronline.com. or here openweathermap.org

Afterwards you have to open the link from the mail that had been send to you to verify your registration.
The next step is already the creation of your free API key.

The key is a string of multiple hexadecimal signs
e.g. “8cd2c37658fabd6adbb9b64656d69”

You can copy your key and paste it into the corresponding field in the administration of OPTIMA.

The API key version to insert for a new openweathermap key is 2.5 and 2 for a new worldweatheronline key.

Please note that worldweatheronline.com ceased all its free accounts and now only offers accounts for a monthly fee.

In the following article, we will show you how a Daikin AC system can be managed through a Divus KNXCONTROL device.

Requisites:
– DIVUS KNX Server, KNX Superio or PDK (the latter for planning/testing only)
– Daikin AC device
– man-in-the-middle device translating between KNX and Daikin’s internal language: we’ll use a Zennio KLIC-DI, but you may also use other devices with a similar set of functions.

The Zennio KLIC-DI gives access to all of the functions of a Daikin AC device from the KNX bus. To do this, it has a wide range of functions. You may need to study it and choose which ones make sense for your specific case: what product is installed exactly? Two or three steps fan speed? Simplified mode? How is the device used by the user? Is heating used? More freedom or more ease of use? These questions will help in defining the final set of functions which should be offered to the user through Optima’s visualisation.

Optima has a set of built-in complex objects. These objects are used whenever a device has more than 2 or 3 functions and its management would not be possible through the usual graphical representation. There is also an object for classical thermostats, but that does not fit all our needs in this case, so we will use another approach. We will use the Generic complex object instead, a very flexible template capable of holding a huge number of functions inside a nice GUI.

To help you get started, I created a virtual thermostat which you may download here.

[download:db_en.dpadDB]

Warning: loading the file through the backup/restore page will overwrite your previous project in Optima! Make sure to save it first and rename it so that you can easily find it later.

It uses a set of KNX objects. These objects are used to show how the functions of a Daikin AC device can be mapped and shown to the user using the “Generic complex object”. Please note that the purpose of this objects is showing how to assemble a complex object for a special purpose; it is not working and can not be used as it is. For a production system, you would have to
– choose a subset of the shown functions – some of them are redundant, others are seldom used…
– substitute every single KNX object with a KNX Object from your ETS project inside Optima, possibly maintaining the same icon and graphical representation.

pg1en pg2de

As you can see from the screenshots, the Generic complex object has
– a display area
– a main area for placing functions
– an area for up to three tabs, each with its own set of sub-functions

This complex object shows that all the functions of a Daikin AC device can be mapped to functions inside Optima.
You are free to test it and change it to anything you want or need.

I later went on and took a second step: I tried to optimize both the graphical and the functional aspects and came up with a second version of the Generic complex object for Daikin devices (over Zennio KLIC-DI, as always).

pg1ben pg2ben

pg3ben

So…now it’s your turn! We might add a second part of this tutorial showing the details of the latter version, if there’s enough interest. In any case, you are free to build your own, custom complex object for your project, starting from these examples, or from scratch if you prefer.

You may find general information about Optima in the administration manual
KNX CONTROL OPTIMA MANUAL ADMIN

If you want to access OPTIMA also from the internet (wherever you are) you need to add some special settings to your network’s router. Have a look here and also above at 2.16 and 2.17.

Starting from version 2.2.0, OPTIMA has a new online update mechanism! To use it to update to version 2.2.1 or newer

  1. switch to base mode in administration (menu bar, upper right) and
  2. go to the update page – a message will appear with further instructions
  3. then just push the UPDATE button.

If a newer version is found online, the update procedure is started automatically. Please do not interrupt this procedure!

If your device has no available internet connection, you may use the manual update procedure. The update file for your device may be obtained on request (specifying the device’s serial number) from our support.

3. KNX SERVER

KNX SERVER can be supplied with DC voltage from 11 to 30 V; it is recommended to use only power supplies with stabilized voltage, in combination with short cables, in order to prevent disturbs on the supply voltage.

4. KNX SUPERIO

The expression standalone device means that KNX SUPERIO contains everything in order to be able to create and use a KNX visualisation. All necessary software and hardware interfaces make part of the product, no additional components are required.

On the other side this also means that KNX SUPERIO is a „finalized“ system: the visualisation can only be shown on the device itself and on devices that use the DIVUS OPTIMA APP; It is not possible to install additional software.

The visualisation of KNX SUPERIO can only be created remotely. Locally on the device only a few settings, that are accessible from the visualisation can be changed (time scheduling and favorites).

Furthermore to enable access from other devices (DIVUS TOUCHZONE or mobile devices), you have to align the network settings with the one of your network (take care, beneath the standard parameters like IP address, subnet mask and gateway you also have to set up correctly the DNS address; normally you can insert the IP address of your router as DNS address).

KNX SUPERIO is delivered with the default IP address 192.168.0.110, just like KNX SERVER.

If you do not want to connect KNXSUPERIO to your network, you can also ignore the network settings and use a cross-over cable in order to connect to KNX SUPERIO. In this case all online services will be disabled.

5. OPENDOOR

Yes,it is possible. In some cases the activation of the AC door opener can cause the reset of the OD SIP module. To prevent this a spark extinguishing capacitor (THT 2n2 – 2kV) should be connected in parallel to the relay on the screw terminal of the OD SIP module.

In general all audio settings are depending on the installation way, the environment and the used internal devices. Corresponding to the different conditions the audio levels must be adjusted to match the different terms.
According to this we can not grantee that the following settings will produce the best audio quality.

According to our experience the following setting should lead to a good audio quality.

OPENDOOR-SIP PLUS:

(The settings are applied under “Advanced settings” > “Communication”)

    • Microphone level: +18dB
    • Speaker level: -6dB
    • Microphone attenuation (local mic): -24dB
    • Apply attenuation when: Remote peer is speaking
    • Switching threshold (PCD-off): 12%
    • Delay between PCD-off and PCD-on: 100ms

Not specified settings can be freely adapted.

OPENDOOR-SIP PLUS:

(The settings are applied under “Settings Hardware” > “Audio”)

    • Precedence switching threshold for “Remote station speaking”: 20%
    • Procedence switching time for “Remote station speaking”: 60*10ms
    • Remote station speaking: Microphone level: 0%
    • Remote station speaking: Speaker level: 50%
    • Remote station listening: Microphone level: 50%
    • Remote station listening: Speaker level: 0%

Not specified settings can be freely adapted.

The intercom system of DIVUS used the codecs PCMU and PCMA. If used with not DIVUS products other codecs may be required.

We recommend to use the following codec settings:

    1. PCMU2 Audio frames per Tx
    2. PCMA2 Audio frames per Tx

All other codecs should be disabled (“None”)

OD-SIP PLUS: The settings are applied under “Advanced Settings” > “Communication”

OD-SIP MAXI: The settings are applied under “Settings VoIP” > “Codec settings”

6. VIDEOPHONE

If not explicitly specified otherwise, all files offered for download are intended to be used for the latest version of DIVUS Videophone app. If you are using an older version of the app you can find the corresponding information here.

DIVUS Videophone 1.0.1

The app DIVUS VIDEOPHONE completes the DIVUS intercom portfolio and makes video communication possible also on DIVUS TZ and other supported devices with Android operating system. The app follows the Windows version of the Videophone-Software as well in functional as in design terms and permits as well to communicate with a connected IP intercom (like e.g. DIVUS OPENDOOR) as also to show the video signal of the external unit.

Requirements
For a correct usage of the app, beneath a compatible IP intercom unit also a VoIP server with SIP support is required, on which the app can be registered. Please note that only the use of VoIP servers sold or recommended by DIVUS can guarantee the full functionality of the app.

Additional information
If the app is started for the first time, a welcome screen with some useful information will be shown. Before you can use the app correctly, the connection to the VoIP server has to be configured and at least one external intercom unit has to be set up.

Functions:
• Video and audio communication to the external unit
• DTMF tone support (e.g. for door opener function)
• Direct in-app volume control
• Up to 10 compatible external units configurable
• Selectable ringtone
• Interphone function (communication between several
• mobile devices with installed app running in the same Wi-Fi network)
• Door spy function

Changelog 1.0.1 rev49 :
• Fixed a bug causing crashes if either the caller ID or the caller name starts with an empty character (space).
• Integration of different trim functions eliminating empty spaces in various code positions.
• Correction of a bug avoiding the correct visualisation of the secondary RTSP stream.

Download of the app: Google play In alternative, here the direct download of the DIVUS Videophone app!

Documentation: Manual Videophone App for Android 1.0.1

If you acquired a DIVUS Videophone Box between 2009 and 2015, you can download the manual for it here. For newer devices the manual can be found on the downloads page.

Find out how to set up your VIDEOPHONE 4 app for remote access here. For details about setting up DIVUS OPTIMA for this purpose, refer to the DIVUS OPTIMA intercom manual.

Merken