BACnet Connector Client - User Guide

The bacnetLocalAddress tag is now replaced with bacnetRoute string tag if connecting through VPN and if network number is 0. 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.

The bacnetLocalAddress tag is deprecated.

The actorTimeout (“APDU Timeout”) and bacnetRetryCount (“Retry Count”) are now set up in the BACnet Global Config tool, not in the tuning policy record(s). Both will apply to all BACnet connectors.
Query to batch remove these tags from tuning policies if applicable:
readAll(connTuning).map x => diff(x, {-actorTimeout, -bacnetRetryCount}).commit

After the updating to 5.1, this process identifier number from the BACnet device will be the same for all connectors because the instance number of the device (added in the NC object recipient list) is changed.
User needs to manually change the process identifier number in the BACnet device or the value of the bacnetAlarmPid tag in order to have specific alarms added in the Alarms app. User should not have to do anything when migrating as the connector will re-subscribe to those NCs using the new pid and the new instance number.

If there was a bacnetAlarmPid set and for some reason there is a requirement to keep all settings the same, the user would just have to make sure the the bacnetInstance is the same as on the older setup and set it in the BACnet Global Config tool.

The ACC object is configured with the kind type as number after the update. The user must manually change it to string type if used.

Some point types have changed. Here is a list of those point types.

If using a Optic zip on a Windows environment, the user needs initialize the BT BACnet Stack (BBS) configuration manually. Look at the “Setting BBS Manually” section in the BACnet Connector doc on how to do this.

New connector is not supported on MAC.

New connector 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 Optic.

For intrinsic alarms, add the corresponding Event Enrollment (EE) object 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.

For IP devices the default value of APDU Timeout is 6sec and Retry Count is 3 (recommended and default in the BACnet Global Config tool).

Support for Foreign Device registration.

Recommend Java 11 for new Optic.