Technische Alternative

Technische Alternative offers control of various controllers and system monitoring. A connection to IP-Symcon is established using CMI or BL-NET.

Description

IP-Symcon supports both the BL-NET (UVR1611) and the CMI variants of Technische Alternative.

CMI Installation
BL-NET Installation

CMI

The connection to IP-Symcon is established via LAN.

Integration in IP-Symcon

After a suitable CMI instance has been created, the IP address of the CMI must be entered.
The device, node number and interval must also be specified.
If authentication is required, this must be entered in the parent instance of the WWW Reader.

The connection can be tested via "Update".
Variables are automatically created on first-time queries and updated at every interval.

BL-NET

The connection to IP-Symcon is made via LAN or USB using the "BOOTLOADER" (BL-NET).
In any case, the DL (data line) must be used.

Reading out via the CAN bus is not possible.

Integration in IP-Symcon

After an instance has been created in IP-Symcon, the IP address of the BL-NET must be specified. If the USB version is to be used, a new parent instance must be created and the SerialPort must be selected when selecting it.

In order to display one or more variables in the Visualization, a profile (e.g. temperature) must be assigned to each of them in order to make it visually recognizable what type of value they are. As the UVR1611 controls and inputs are user defined, this cannot be done automatically by the system. More information about variable profiles can be found here: Variable Profiles

If two (2) UVR1611 are to be connected, two instances must be created. Once with ID = 1 and once with ID = 2. However, the timer may only be activated in one of the two instances, since a request delivers both data packets and thus updates both instances.

Tips & Tricks

Since the BL-NET is not very resilient, as few applications as possible should access the device. Otherwise failures can occur during which the BL-NET cannot be reached.

The following entries in the log file are normal and not an error:

Client Socket | Socket: Connect.... #1  
Client Socket | Socket: Connected  
Client Socket | Socket: Disconnected