BACnet Router Troubleshooting: Why Devices Disappear

A group of BACnet devices suddenly disappears from the BAS. The MS/TP controllers may still have power. The router LEDs look normal. You can even log into the router, but discovery fails or an entire network appears offline.

A router can be powered, reachable, and still be routing incorrectly. The failure can also be below the router in the field bus.

Follow the route the BACnet message has to travel.

Quick Answer

Determine which side of the router is failing.
Verify router power and IP connectivity.
Check BACnet Network Numbers.
Verify the MS/TP side independently.
Confirm router Device Instance and local MS/TP settings.
Confirm routing is enabled and the expected route exists.
Review BBMD/Foreign Device architecture only when IP subnet boundaries make it relevant.
Use routing tables and diagnostics before rebooting or replacing the router.

First: Understand What a BACnet Router Does

A BACnet router connects BACnet networks. A gateway translates between BACnet and another protocol. In a common BAS architecture, a BACnet/IP network reaches an MS/TP field bus through a router.

BACnet/IP network → BACnet router → BACnet MS/TP network → VAVs / FCUs / equipment controllers

1. Determine Which Side Is Offline

You cannot reach the router by IP

Start with router power, Ethernet, switch port, IP address, subnet mask, VLAN/network infrastructure, and duplicate-IP conditions.

You can reach the router, but not the MS/TP devices

Move downstream to the MS/TP port, baud rate, MAC address, network number, wiring, controller power, and termination.

The router sees field devices, but the BAS does not

Now the issue may be routing, BACnet/IP configuration, network numbers, BBMD/FDR architecture, or the supervisory BACnet network configuration.

2. Separate IP Settings From BACnet Settings

A BACnet/IP router still depends on ordinary IP networking. Its IP address, subnet mask, and gateway are different from its BACnet Network Number and Device Instance.

IP Address ≠ BACnet Network Number ≠ Device Instance ≠ MS/TP MAC

Confusing these identifiers is a common source of commissioning errors.

3. Check BACnet Network Numbers

A routed BACnet network needs the correct network number, and separate BACnet networks on the same internetwork should not be assigned conflicting numbers. A replacement or factory-reset router can easily come online with an incorrect default network number.

Verify the intended BACnet design rather than copying a number from a nearby router.

4. Network Number Is Not Device Instance

The BACnet Network Number identifies a network for routing. The Device Instance identifies an individual BACnet Device object. The router itself normally has its own Device Instance, while each connected BACnet network has its own network number.

5. Verify the MS/TP Side Separately

MS/TP baud rate
Router local MS/TP MAC
Device MAC addresses
Wiring polarity
EOL termination
Controller power
Physical trunk continuity

If the IP side is healthy but the serial side is not, do not spend the entire service call changing BACnet/IP settings.

6. Confirm the Router Has the Expected Route

Different router brands expose routing diagnostics differently, but the principle is the same: the router needs to know the expected destination networks and have an active path to them.

Use known-network tables, learned routes, device counts, or similar diagnostics provided by the actual router rather than relying only on the BAS device tree.

7. Understand When BBMD Matters

BACnet/IP uses broadcast communication, and normal IP routers do not forward local broadcasts across subnets. BBMD functionality becomes relevant when BACnet/IP broadcast communication must cross IP subnet boundaries in an architecture designed to use BBMDs.

Do not enable BBMD functions simply because devices cannot be discovered. Understand the site network design first. A poorly planned BBMD configuration can create new communication problems.

What Is Foreign Device Registration?

Foreign Device Registration allows a BACnet/IP device outside the local subnet arrangement to register with a BBMD so it can participate in BACnet broadcast communication. A service laptop is a common temporary example.

If a service tool cannot discover devices across a routed environment, the problem may be how the tool is participating in BACnet/IP rather than a failure of the building router.

Use Router Diagnostics Before Rebooting

Known networks/routes
Device counts
Frame or packet statistics
MS/TP errors
Duplicate-address information
Token activity
Packet capture where supported

A reboot may restore service while erasing the condition that explains the failure. Capture diagnostics first when practical.

Router Fault or Field-Bus Fault? Use the Boundary Test

Treat the router as a boundary between two networks. Test each side independently before replacing hardware:

Confirm the IP side can reach the router and that the expected BACnet/IP interface is active.
Check whether router diagnostics show the expected downstream network, MS/TP token activity, device count, and error trend.
Connect an approved field tool on the downstream segment, when site procedure allows, and determine whether devices are visible locally.
Compare scope: one device, one MS/TP segment, one router port, one routed network, or the entire BACnet/IP side.
Determine whether the failure follows the router port or remains with the same field segment after a controlled test.
Review routing tables and duplicate BACnet Network Numbers before factory-resetting the router.

If the router is reachable, its IP settings look correct, and no downstream token or device activity appears, continue on the serial side with the BACnet MS/TP troubleshooting guide. If devices are visible locally but not across the router, focus on routing, network-number, BBMD, and interface configuration.

Real-World Field Case: The Router Was Not the Only Problem

Investigation

At one anonymized commercial building, BACnet communication problems led to investigation of the router and its associated VAV network. The router was rebooted during the initial response, but two VAV controllers still remained offline.

Findings

The remaining failure did not match a complete router outage: other devices behind the same boundary were communicating. A field check at the two affected VAV controllers found their power terminals unplugged.

Corrective Action and Verification

The terminals were reconnected using the site’s approved electrical procedure. Both controllers powered up, rejoined the network, and returned to the BAS device view. Their live values and communication status were then checked rather than treating a visible device name alone as proof of recovery.

The practical lesson is simple: “offline behind a router” does not automatically mean “failed router.” Preserve the topology and test the smallest affected boundary.

Do Not Factory-Reset the Router Too Early

A factory reset can erase the IP address, BACnet Network Numbers, Device Instance, MS/TP baud rate, router MAC, BBMD table, Foreign Device settings, and routing configuration.

Before resetting or replacing a router, save or document the configuration and understand which networks it connects.

Replacement Decision: Router or Supervisory Controller?

At another anonymized site, a failed legacy Niagara AX JACE raised the question of whether a simpler BACnet router could replace it. The answer depended on the role, not the enclosure: a router can connect BACnet networks, but a supervisory controller may also host schedules, control logic, alarms, histories, graphics, integrations, and remote access.

Use a router as the replacement only when routing is the complete required function and all other dependencies have been accounted for. Before removing a failed supervisory controller, document its services and follow the BAS controller replacement checklist.

A Practical Router Troubleshooting Order

Power – Is the router actually running?
Ethernet/IP – Can you reach the router?
BACnet/IP – Can BACnet communication reach the router?
Routing table – Does it know the expected networks?
Network numbers – Are they correct and unique for the design?
MS/TP port – Is the serial side configured correctly?
Field network – Are controllers powered and communicating?
BBMD/FDR – If multiple IP subnets are involved, is the broadcast architecture correct?

Key Takeaways

A reachable router can still have a routing problem.
Verify both sides of the router.
Keep IP settings and BACnet identifiers conceptually separate.
Check Network Numbers carefully after replacement or factory reset.
Verify the serial trunk independently.
Use routing diagnostics before rebooting.
Understand BBMD architecture before modifying it.
Check the field devices before condemning the router.

FAQ

What is the difference between a BACnet router and a gateway?

A BACnet router moves BACnet messages between BACnet networks. A gateway translates between BACnet and another protocol.

Can two routed BACnet networks use the same Network Number?

Separate networks within the same BACnet internetwork should use unique network numbers so routers can identify the correct path.

Is BACnet Network Number the same as Device Instance?

No. The Network Number identifies a BACnet network; the Device Instance identifies an individual BACnet Device object.

Why can I log into my BACnet router but not see controllers?

The IP side may be working while routing, the MS/TP port, network number, baud rate, wiring, or field-controller power is wrong.

Do I need a BBMD every time BACnet/IP crosses an IP router?

Not automatically. Use BBMD functionality only when it matches the designed BACnet/IP architecture.

Sources & Further Reading

Disclaimer: This article provides general commercial building-automation information. Always follow manufacturer documentation, approved site procedures, cybersecurity requirements, and applicable electrical or life-safety practices.

BACnet Router Problems: Why Devices Disappear and What to Check First