If you are using Events2HVAC with the BACnet Device Interface driver or you are using the stand-alone BACnet Explorer tool for troubleshooting, you want to make sure your PC or server is not blocking BACnet traffic. BACnet/IP communicates over UDP port 47808 (0xBAC0). Windows firewall will block this traffic if it is enabled.
Verify that the firewall is blocking the connection (SQL
Server 2008)
Open the
firewall dialog, then right-click, and select Properties.
Turn off the firewall and hit Apply. Test the BACnet Explorer again (rescan devices) to see if other network devices show up.
If the connection was successful and you want the firewall enabled (recommended), you'll need to add a firewall rule on inbound connections.
Allow remote Events2HVAC Connection Rule in Windows Firewall
Type: Inbound
Rule
Name: BACnet (UDP Ports 47808)
Protocol:
UDP
Port: 47808
(Note: default BACnet port is UDP 47808, but you may want to verify if this is the case for your network)
Open the Windows Firewall dialog again, and add a new inbound rule. In the pop-up dialog, select “Port” as the type.
Select “UDP” as the protocol and indicate the port number to which the rule will apply, port 47808 in this example. Your system may use a different port; confirm the port number in Events2HVAC.
Select “Allow the connection”.
Select the appropriate profile for your organization
Provide a sufficiently-detailed name and description, as below:
Finally, turn the firewall back on using the stesp at the beginning of this article, then test the BACnet Explorer again (rescan devices) to verify that all remote devices appear.