Product overview
Reads and controls lighting and other KNX TP bus devices, with built-in web HMI functions and data interfaces for BACnet, Modbus, OPC UA and MQTT systems.
Selection and reading guide
- Acquisition covers more than 500 protocols; check the driver against each connected device. This model supports Type-C power.
- Check the acquisition direction against: KNX TP. Similar names do not imply the same client/server role or serial transport.
- For supervisory integration, first check the forwarding interfaces—Modbus, BACnet, MQTT, OPC UA—then check this model’s communication roles and configuration steps.
- Check the field point list against the communication capacity of 512 points and 64 devices; count physical terminals separately from communication points.
Model document guide
- File unavailable in this language; purpose and functions: page 3; specification references: pages 2, 4
Native bus ports and wiring
1 Ethernet port; COM1 is 1 RS485 serial port and COM2 is 1 native KNX TP bus port. The ordinary serial-port count is 1; the KNX TP bus is counted separately. KNX IP protocol support is not a substitute for a physical KNX TP interface.
Wiring references (Chinese PDFs): File unavailable in this language (pp. 4)
Current product specifications
Specifications are sourced from the supplied 2026 product catalog. Unspecified values remain unconfirmed.
| Parameter | Specification |
|---|---|
| Total serial ports | 1 |
| RS485 ports | 1 |
| Ethernet ports | 1 |
| Point capacity | 512 |
| Device capacity | 64 |
| Acquisition protocols | KNX TP |
| Forwarding protocols | Modbus / BACnet / MQTT / Database / OPC UA |
| Physical interfaces | Ethernet / RS485 / KNX TP |
| Type-C power | Supported |
| HMI visualization | Supported |
Model notes: COM1: supports more than 500 protocols. COM2: supports connection to the KNX-TP bus.
Model datasheets
- File unavailable in this language
