BACnet routing between different BACnet data links

BACnet/SC is simply another BACnet data link layer option (like BACnet/IP and BACnet MS/TP) but with added security. BACnet/SC brings cybersecurity and IT-friendliness to the BACnet protocol, but it maintains the interoperability, scalability, flexibility, and compatibility to any existing or future versions of BACnet that the BACnet protocol is known for. BACnet routing functionality in the PXC4/5/7 can be leveraged in projects to route between BACnet/SC, BACnet/IP, and BACnet MS/TP data links.

BACnet/SC still uses the same method of device/object identification (the device instance and object instance numbers). There is no need to rediscover devices and their objects or recreate trends, schedules, and graphics when switching network driver configuration from BACnet/IP to BACnet/SC or when routing from existing data links to BACnet/SC. This saves time on projects and allows for easier transition to the new secure data link option.

BACnet/IP to BACnet/SC routing in the PXC4/5/7 is activated by default to allow the communication between the BACnet/SC network and other BACnet/IP networks. In addition, if BACnet MS/TP devices are connected to the PXC4/5/7, they are also routed to BACnet/SC. This allows the communication with BACnet/IP and BACnet MS/TP devices that do not support BACnet/SC. The workstation configured as a BACnet/SC node connected to the PXC4/5/7 hub will only see BACnet/SC traffic.

By leveraging BACnet routing, existing building automation systems can be designed with both, new BACnet/SC devices and currently available BACnet devices with future upgrades in mind, as more BACnet/SC devices become available.

BACnet routing is configured in ABT Site and DT+. To disable BACnet routing, uncheck the Routing check mark in tool configuration.