07.11.2018, 22:04
(This post was last modified: 07.11.2018, 22:07 by Erwin van der Zwart.)
Hi,
That would require the BACnet client package. At the moment the client is script based without a GUI to map the BACnet objects to KNX. Also not all BACnet object types are supported. (like BACnet trends, BACnet schedulers and BACnet alarms or notification class) and COV is not supported in the client so you need to poll the objects for changes.
Keep in mind that you can’t use the server and client at the same time due to used ports by both.
In case of a BMS i would recommand the use of the server as it has COV and can handle a lot more objects. Bindings/mapping needs to be done in the BMS in that case.
BR,
Erwin
That would require the BACnet client package. At the moment the client is script based without a GUI to map the BACnet objects to KNX. Also not all BACnet object types are supported. (like BACnet trends, BACnet schedulers and BACnet alarms or notification class) and COV is not supported in the client so you need to poll the objects for changes.
Keep in mind that you can’t use the server and client at the same time due to used ports by both.
In case of a BMS i would recommand the use of the server as it has COV and can handle a lot more objects. Bindings/mapping needs to be done in the BMS in that case.
BR,
Erwin