Discovering BACnet devices from a BACnet interface
Unable to discover BACnet devices after changing IP Address on AS or ES
Discover Devices and Broadcast Address
Bacnet devices are offline after a power cycle or loss of IP connection at the AS or ES
StruxureWare Building Operations site using devices configured with BACnet
Broadcasting on wrong network from either the Automation Server or the Enterprise Server can be a problem. In the example below an AS is broadcasting for a BACnet device (in this case a MNB Controller). In the IP Network for the BACnet Interface, check your settings for Broadcast Address. The key is to ensure your BACnet broadcast address is in the correct range.
In this first screen capture, we have a BACnet network interface using the IP Network with a red failure to communicate indicator on the MNB.
In this example, the broadcast is on 192.168.1.255
The computer being used as well as the BACnet devices we want to discover and use are in the following IP network and settings:
Changing the broadcast address to match what the BACnet network is using resolves the issue(since we are not using a BBMD)
Lastly, choose to discover devices
When the IP Network broadcast address is set incorrectly, a Wireshark capture may reveal that no WHO-IS message is sent out from the SmartStruxure server when a device discovery is attempted.
When in doubt as to whether the 'IP Broadcast Address' is correct, a simple test is to set the IP Broadcast address to 255.255.255.255, doing so will instruct the SmartStruxure server to broadcast on ALL subnets, if the problem was caused by an incorrect broadcast address it will be resolved but care must be taken not to leave the default address set to 255.255.255.255 as this will cause unnecessary traffic on all sub-nets, instead, review your calculations for what the appropriate broadcast address should be and set it appropriately.
Key Concept: The AS will retain the Broadcast address, and if moved to a new Subnet, the old Broadcast address must be updated. One can do either of the following:
- Edit the IP Broadcast Address Setting
- Delete the BACnet Interface and recreate in the new Subnet