Bus-powered KNX TP device. No USB — firmware is installed from the device itself.
The TULX has no USB port. It carries a recovery system that installs firmware over your network, so this page only publishes the images.
.bin below and
upload it under Install from a file.| File | Application | Version | Size | MD5 |
|---|---|---|---|---|
firmware_tulx32_esp32c6.bin | ip4knx KNX/IP Gateway KNXnet/IP tunnelling and routing. | 1.4.144 | 1497 KiB | 255f2ae58d8e9a6287e408f2252f8b1b |
firmware_cdc2net_tulx32.bin | CDC2NET - KNX TP to raw TCP Transparent TP-UART bridge on port 2329, for knxd and FHEM. | 0.2.292 | 1367 KiB | 76c80f93305aec1e22d63a0d2aff0ea4 |
firmware_mcp4knx_tulx32.bin | MCP4KNX - KNX commissioning over MCP Needs the start pass fitted at the factory; a device without one will not start. | 0.25.1 | 1612 KiB | bf5f8639fc9d27ed16be0f3063a723e6 |
These are raw application images, not full flash images. The recovery verifies the MD5 before it starts what it wrote.
Any ESP32-C6 application installs the same way. The recovery asks for confirmation because such an image carries no busware marker, and it stays reachable afterwards. Two things to know before you build one:
Machine-readable index: manifest.json