In an IP based topology, must the bus also be IP based - i.e CAT5 cable - or could it also be TP? Can we also use combination? For instance TP for lines and IP for the area backbones? Or am I misunderstanding the whole concept?
I'd argue that's less of a choice and more of a consequence of the devices that you choose to use. From that perspective, if you choose to use a KNX-IP router, then you have no choice but to connect multiple lines (or multiple areas, but not both) through your Ethernet infrastructure. At the same time, each line/area uses KNX TP to connect all the KNX devices of that line/area, including the router. If you choose to use a line coupler, then you have to use KNX TP for both the interconnection of your KNX devices, and the interconnection of your lines/areas. FInally, note that KNX-IP Router is a misnomer. It should be called Gateway or Bridge. Therefore, you need a KNX-IP router at every point where your transmission medium goes from one type to another (KNX TP Ethernet).
gracias bro
In an IP based topology, must the bus also be IP based - i.e CAT5 cable - or could it also be TP? Can we also use combination? For instance TP for lines and IP for the area backbones? Or am I misunderstanding the whole concept?
I'd argue that's less of a choice and more of a consequence of the devices that you choose to use.
From that perspective, if you choose to use a KNX-IP router, then you have no choice but to connect multiple lines (or multiple areas, but not both) through your Ethernet infrastructure. At the same time, each line/area uses KNX TP to connect all the KNX devices of that line/area, including the router.
If you choose to use a line coupler, then you have to use KNX TP for both the interconnection of your KNX devices, and the interconnection of your lines/areas.
FInally, note that KNX-IP Router is a misnomer. It should be called Gateway or Bridge. Therefore, you need a KNX-IP router at every point where your transmission medium goes from one type to another (KNX TP Ethernet).