At Pharos, we focus on seamless integration with industry-standard protocols, including KNXnet/IP. This is a key part of our dynamic lighting controls system. Building-wide automation often sees lighting as just one part of a wider network of systems. That’s where an IP KNX router becomes the bridge between intelligent lighting control and holistic building management systems.
This section will examine the interaction between Pharos Designer and KNXnet/IP. We will also discuss adding a KNX router to your project. This will help to create a reliable and unified control system.
What is KNXnet/IP?
KNXnet/IP is a communication protocol for KNX systems. It uses Ethernet to send KNX messages over IP networks. This is a smart way to connect lighting, HVAC, blinds, security, and other building systems. It works well when these systems are already part of a building automation plan.
However, to communicate in KNX, Pharos Designer controllers require a translator: the IP KNX router.
How does Pharos support KNXnet/IP?
Pharos Designer controllers support the KNXnet/IP protocol natively using an IO Module. An IO Module is similar to a plug-in but they’re free of charge. Pharos Designer controllers with the KNXnet/IP IO Module installed can send and receive KNX group messages over Ethernet. A KNXnet/IP routing device can then transfer these messages to the KNX TP (Twisted Pair) bus.
You set up everything in the Pharos Designer software. Just assign KNX group addresses to specific triggers and actions. From there, the IP KNX router relays the communication between your Designer controller and the KNX world.
Getting Started: Key Requirements
To integrate KNX with Pharos Designer, make sure you have:
- A supported KNX router (also known as a KNXnet/IP interface)
- The KNX ETS software to configure the KNX router
- A Pharos Designer project with the Pharos KNXnet/IP IO module installed
- A KNX installation with assigned group addresses
- A networked connection between your KNX router and the Pharos controller
The IP KNX router acts as a gateway, enabling Pharos Designer controllers to read and write KNX group objects. You can set these to start lighting scenes, change dimming levels, or respond to changes in the room, like occupancy or temperature.
Practical Use Case
Imagine a lobby scenario where your KNX system handles blinds and HVAC, while Pharos controls the lighting ambiance. You can connect the two systems using an IP KNX router. This allows you to program the lights to dim when the blinds close. You can also set up welcome lighting scenes for when people enter the building.
This kind of cross-system synergy adds value to projects by improving both energy efficiency and user experience.
Technical Considerations
Pharos Designer communicates over multicast UDP on port 3671, following the KNXnet/IP standard. Make sure:
- The Router Port in the module configuration matches the port of the KNX router
- Your KNX router supports routing mode (not just tunneling)
- You have a network that allows multicast traffic
- You have configured the KNX group addresses used in Pharos in the ETS software
All devices conduct KNX communications via the IP backbone. Therefore, having a dependable and properly configured network and IP KNX router is crucial for achieving success.
Summary: Why use an IP KNX Router?
Integrating a router into your Pharos setup allows for:
- Seamless two-way communication with KNX TP networks
- Integration of dynamic lighting control with wider BMS functions
- Reduced wiring complexity by utilising existing Ethernet infrastructure
An IP KNX router connects KNX with Pharos seamlessly. It provides reliable control for smart offices, luxury homes, and public spaces.
For full integration details, explore our KNXnet/IP documentation. KNXnet/IP – Version 2.5.1 – IO Modules
