09.11.2018, 06:51
(This post was last modified: 09.11.2018, 07:44 by Erwin van der Zwart.)
Hi,
I don't understand why you need client and server at the same time, normally you would import the device BACnet points into your BMS and bind them to you processes, with the use of COV and/or polling settings you have bi-directional communication. When changing a value in the BMS the value is send to the KNX controller and when the value changes in the KNX controller it will be picked up by the BMS by the COV or polling.
So you have 2 choices, or use the server and make the connections (bindings) inside the BMS or use the client and make the connections by script in the KNX controller, you don't need both.. My first choice would be inside the BMS as the server supports more objects then the client and it saves you a lot of scripting as the server part supports COV.
I would use the client only when there is no BMS needed, like when you need to connect to a stand alone BACnet device (like a heatpump or AHU).
In case you want to use both (server and client) at the same time in the same BACnet network (BAC0 but i don't see a use case for this) then yes you need two controllers. When you have 2 networks (BAC0 and BAC1) then you could do it with 1 controller when client is used on BAC0 and server is used on BAC1 as in that case there is no port conflict. But again i don't see a use case for that setup as it's very unusual.
Keep in mind that objects in 2 different BACnet networks can’t see each other and this will form 2 separated BACnet worlds.
BR,
Erwin
I don't understand why you need client and server at the same time, normally you would import the device BACnet points into your BMS and bind them to you processes, with the use of COV and/or polling settings you have bi-directional communication. When changing a value in the BMS the value is send to the KNX controller and when the value changes in the KNX controller it will be picked up by the BMS by the COV or polling.
So you have 2 choices, or use the server and make the connections (bindings) inside the BMS or use the client and make the connections by script in the KNX controller, you don't need both.. My first choice would be inside the BMS as the server supports more objects then the client and it saves you a lot of scripting as the server part supports COV.
I would use the client only when there is no BMS needed, like when you need to connect to a stand alone BACnet device (like a heatpump or AHU).
In case you want to use both (server and client) at the same time in the same BACnet network (BAC0 but i don't see a use case for this) then yes you need two controllers. When you have 2 networks (BAC0 and BAC1) then you could do it with 1 controller when client is used on BAC0 and server is used on BAC1 as in that case there is no port conflict. But again i don't see a use case for that setup as it's very unusual.
Keep in mind that objects in 2 different BACnet networks can’t see each other and this will form 2 separated BACnet worlds.
BR,
Erwin