If using more than one Bacnet Comm network port, and “Routing Enabled” is true in the parent Bacnet Comm, Network slot, corresponding router table entries automatically populate under this container. Router entries are listed by “dnet” (destination network). See Figure 4.

After device discovery from the Bacnet Device Manager, where the “All Networks” option was chosen, additional router table entries may exist. These reflect other discovered remote BACnet routers. Such entries may populate following an “All Networks” discovery even if “Routing Enabled” is false. Entries like this may also appear resulting from unsolicited messages received from remote networks.

After 24 hours of no traffic directed to a network, router table entries are cleared, to prevent the table from being cluttered with old entries. As needed, router table entries are discovered again.

If the station detects a BACnet “router loop”, the BacnetComm, Network’s “Routing Enabled” may be automatically set to false. If this case, the station stops acting as a BACnet router for its enabled network ports. Corresponding entries are generated in the stations’s LogHistory, noting detected misconfiguration and disabled BACnet router functionality.

If needed, you can override this behavior by setting the “Maintain Routing Enabled” property to true, and then resetting “Routing Enabled” back to true.