Below are some other details about the BACnet client connector.
When discovering devices, the returned devices behind a router will not display their exact IP. This is a limitation with the BT BACnet Stack (BBS). However, they will still function.
If connecting to devices over VPN and if the network number is 0 of the network being connected to over VPN, the bacnetRoute tag will need to be added to the BACnet connector in order for it to communicate and for the connector to know where the device lives. The reason is because VPN doesn’t support broadcast messages such as ‘who-is’ and ‘i-am’. The bacnetRoute tag is a string type and it’s value is the router IP address.
It supports communication with multiple IP’s (network cards) when local bind address is set to 0.0.0.0 and standard port of 47808. If local bind address is configured to some specific IP and port other than 47808, then it can only communicate on that IP network card and port.
All projects on the same instance will share the same local bind address IP and Port.
Read Property Multiple (RPM) supports all/optional/required properties also.
Write Property Multiple (WPM) with specific Index of Array support added.
Proprietary Data types will be displayed as Raw data in FIN.
For intrinsic alarms, the corresponding Event Enrollment (EE) and/or point object must exist under the Equip Tree in the database. The EE would be mapped as a point under an equip just like all the other BACnet objects, which then allows the connector to subscribe to those notification events.
BACnet Client and Server must have different instance number if in the same instance of FIN.
BACnet Client and Server cannot communicate with each other on the same PC.