Revising data communication between BACnet/SC – BACnet/IP

A building hub is required in order for a BACnet object to communicate between BACnet/SC and BACnet/IP. Cascading does not permit direct communication between floor hubs and plant hubs. Communications in this case must be routed through the building hub. Specifically, this means that a BACnet reference to the object in Floor hub, 2nd floor, must be added to the building hub. The building hub receives its own BACnet object with a BACnet reference to the BACnet object in Floor hub, 2nd floor. The new BACnet object is now a BACnet reference to the BACnet object in the plant hub. We now have a visible BACnet object in the plant hub that can be referenced by a BACnet/IP device. In the case, each object requiring communication between BACnet/SC and BACnet/IP must be reference via building hub and the plant hub. In other words, data communication is implemented using two “auxiliary BACnet references. We require three BACnet references, instead of just one, to exchange data. The workflow operates the entire BACnet/SC network purely via BACnet/SC. Neither a controller nor BACnet object (highlighted in green) is visible over BACnet/IP.

 

The BACnet/SC connection from the building hub to the floor node illustrates a visual communication path to depict functionality only. Data is always transmitted via the floor hub!