This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

Bacnet for dummies
#6
(09.11.2018, 06:51)Erwin van der Zwart Wrote: 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
Thanks for a great answer, Erwin..


I want to do to simple things actually.

I  want to send values from knx to bacnet side and handle them in BMS system. This is done via the export function on bacnet server. This i got working. Found it using Yabe. And is working fine in the BMS.

Then i want to write to for example a setpoint from bacnet to knx. Thermostat setpoint etc.
Is this as simple as exporting the SP knx object and connect it on the bacnet side. Then it will write the other way, or is this too simple  Smile ..

So i really dont have any real value of using the Client.? The server will work fine for me for this work.

Then i cases where i want to integrate for example a complete AHU with the most commen values i would need to use the Client. 

Sorry for the low knowledge, but aswell you dont get aswears if i dont ask.
Thanks again for the help..
Reply


Messages In This Thread
Bacnet for dummies - by Tokatubs - 07.11.2018, 21:28
RE: Bacnet for dummies - by Tokatubs - 07.11.2018, 23:13
RE: Bacnet for dummies - by Tokatubs - 09.11.2018, 08:28
RE: Bacnet for dummies - by Daniel - 08.11.2018, 09:09

Forum Jump: