Note: Manual address binding is not the recommended method for connecting to your BACnet network. Connection as a foreign device to a BBMD is recommended unless all BACnet devices are on the same subnet as Events2VAC.
The Address Bindings tab allows you to manually perform address binding to known BACnet/IP devices that can’t be discovered on the network with a BACnet WhoIs command. As an example, if the BACnet server is located on subnet 192.168.1.0 and there are 2 more devices located on different subnets and these subnets do not have any BBMD’s defined, you must manually add the devices to this list as shown.
For assistance in determining the address binding information, you can check the Device Properties of a device discovered in the BACnet Explorer.
There are 3 different entry options when adding a manual device:
• BACnet/IP Device – BACnet/IP device that is not routed.
• MSTP Device (or Virtual Device) – Device that is routed by a BACnet/IP router device
• Router Device – BACnet/IP device that routes traffic to a different network number usually for MSTP devices.
If you enter a MSTP device, you must have one entry for the router device that routes to that network number.
Field Name |
Description |
Range |
Name |
A friendly name for the device mapping. |
|
Device ID |
The BACnet device ID |
0 <= deviceID <= 4194303 |
IP Address |
The IP address assigned to the device |
xxx.xxx.xxx.xxx |
UDP Port |
BACnet UDP port that the device is operating on. |
Default = 47808 |
MAC |
If device is a MSTP device, MAC address is shown |
List shows HEX value of MAC address. The add/edit entry shows the decimal value of MAC address. |
Network |
The network number of the device. |
If the device is a MSTP device, a matching router to the network must be defined. |
Is Router |
Device is a router to a network number |
Any MSTP devices must have a router defined for its network number. |
Any device that is added to this list will not get a WhoIs if the device times out during a BACnet option on that device.
Note: After any updates to the manual bindings list, you must restart the Events2HVAC Windows service on the server for the changes to be seen.