|
Now that KNX can be connected to ethernet via IP couplers i cant se no reason why to use linecouplers in projects. Networks are in all buildings and it must be better to use it instead of separate KNX cable. It is also faster. Are there some arguments against the single use of IP instead of linecouplers? |
|
When KNX(EIB) once was founded one of the maintarget was to create a modern reliable and easy method of connect installationdevices to each other. Therefore I think the founders very soon found out that certain fundamental properties to the system should be met. For example: Easy to install rather than high bandwidth, this criteria leads to a twowired network with free topology and groupadressed functions. A system without central equipment leads to decentrilized handling of data and communication. This is one of the reasons to that we don´t need to take care of such things as different protocols, ports, switches, snoop bla bla bla.... I think KNX in the future will be based on the basic properties. And therefor the 2-wired buscable still will be installed mainly together with the oldschool linecouplers, but in some context will be enhanced or supplemented with KNX/IP. One should allways be aware of that the mix of transportmedia can lead to missunderstandings and demarcation problems. |
|
Don't forget that KNX IP routers use IGMP protocol (multicast messages) to transmit telegrams to each others. Most basic Ethernet routers does not support IGMP (only unicast messages). So you probably need more expensive level 2 manageable equipments for your Ethernet network in order to use KNX IP routers. With line-couplers, you just need one KNX IP interface in order to access the KNX bus from a PC running ETS3 or other vizualisation software. In this case, the protocol used is the KNX/IP-Tunneling protocol wich is a unicast (point to point) protocol. |
|
I would like to ask the opposite, why use 8 wires when you can do it with 2? And why involve the IT-department in your project? |
