Modules for KNX
The ability to connect to the KNX bus is increasingly becoming a key feature and quality indicator for building automation devices.
Due to the complexity of the KNX protocol, integration can be very complicated. Especially with existing devices, upgrading the software is often difficult to implement. For small and medium production runs, this is generally not economically viable.
Our KNX BAOS solutions (BAOS: “Bus Access and ObjectServer”) offer a cost-effective way to connect devices to KNX—a universal architecture that enables KNX connectivity for a wide range of applications and products. It provides interfaces to KNX at both the telegram level and the data point level (KNX Application Layer).
In addition to a KNX transceiver, the modules and devices in the Weinzierl BAOS series include a microcontroller with a certified KNX stack. Communication with the module takes place via UART, USB, or IP. Furthermore, depending on the model, the modules offer galvanic isolation from the bus.
While the modules can be integrated into devices as components, the BAOS devices serve as external interfaces for integrating applications into a KNX network.
All variants are suitable for developing certifiable KNX devices with integration into the ETS® software, the standard commissioning software for KNX. Support of KNX Security is available for various types.
The world of BAOS
KNX BAOS solutions with serial interface
KNX connectivity on a small footprint. Our KNX BAOS modules with a serial interface integrate a complete KNX node consisting of a KNX transceiver and a microcontroller running Weinzierl’s certified KNX stack. Possible applications for the modules include integration into sensors, actuators, communication devices, and even visualization devices. Communication with the modules takes place via the serial BAOS protocol, which is embedded in an FT1.2 telegram frame. Alternatively, the solution also offers a telegram interface to KNX. In this case, the telegrams in cEMI format are embedded in FT1.2 frames in link layer mode.
The core component of the KNX BAOS modules, the pre-programmed microcontroller with KNX stack, can also be ordered separately as a chip. Integrating the chip into custom hardware allows for optimization of space requirements and component costs.
Without security
With KNX Security
KNX BAOS solutions with USB interface
KNX with an OS-friendly interface. Our KNX BAOS modules with a USB interface are functionally comparable to the serial BAOS modules. The interface to the host is implemented via a USB connection. The BAOS protocol is embedded as a telegram frame within USB HID reports, in accordance with the KNX USB specification.
Alternatively, the solution also offers a telegram interface to KNX, which can also be used as a programming interface for the ETS. In link layer mode, the telegrams in cEMI format are embedded in FT1.2 frames.
The BAOS modules with USB are particularly suitable for devices running a powerful operating system such as Linux or Windows. The BAOS solution with USB is available both as a module (PCB with pin header) and as a complete device (stick) with a housing.
This makes the KNX BAOS USB stick perfect for making complex devices KNX-compatible via an external expansion. Of course, it includes an ETS® entry and is certifiable.
Without security
KNX BAOS solutions with IP interface
KNX with Network Interface. Our KNX BAOS devices with IP interfaces are independent devices designed for mounting on a DIN rail. Communication between the host and the BAOS server takes place over the network. To achieve this, the BAOS protocol is integrated into TCP/IP frames, based on the KNXnet/IP protocol.
The BAOS IP devices are especially suitable as a KNX extension for complex devices that have a network connection. Of course, they are ETS®-registered and certifiable.
In addition, the devices in the KNX IP BAOS series offer a KNXnet/IP tunneling server, which provides a telegram interface or programming interface for the ETS.
