Plug-in and ready: the KNX USB Interface is the easiest and very reliable way to connect a PC or laptop to a KNX network. With the KNX USB Interface 312, Weinzierl offers a KNX USB interface in a compact design for DIN rail mount:
Successor to the model KNX USB Interface 311
Support of KNX Long Frames for faster download
Width only 1 module (18mm)
LEDs for status and communication errors
High mobility enabled by the smallest KNX USB device on the market: the KNX USB Interface Stick 332 offers the functions of the Model 312 in a very handy size:
Successor to the model KNX USB Interface Stick 330
Support of KNX Long Frames for faster download
Compact USB stick design
LEDs for status and communication errors
Multiple functions in one device: the KNX PowerSupply USB 367 combines a KNX USB interface with an efficient bus power supply with comprehensive diagnostic functions:
KNX power supply with 640 mA
Integrated bus choke
Output for auxiliary voltage
High efficiency
Integrated USB Interface
Support of KNX Long Frames for faster download
Integrated KNX node with diagnostic and logic functions
OLED display with diagnostic functions
4 modules width (72 mm)
Faster downloads enabled by KNX Long Frames
Standard KNX telegrams are limited to an APDU length of 15. The APDU length indicates the number of bytes of the payload. A group telegram with a 14 byte string results in an APDU length of 15. In order to increase the efficiency of the KNX communication, especially for the download, an extended telegram format was defined. This means that longer telegrams can be sent to the bus and download times can be significantly reduced. You can find more information in the manuals of our devices.
Notes for Developers
The KNX USB communication is based on the HID / cEMI Protocol according to the KNX specification. To integrate the KNX USB interface into applications under Windows or Linux, our cross-platform SDK kDrive is available. In addition to the telegram interface, the KNX USB Interfaces 312 and 332 include a complete KNX stack with communication objects and the BAOS protocol V2. This allows the device to extend devices with a USB port (for example boards with embedded Linux) to full-fledged KNX devices, which can even be programmed by the ETS.
