BACnet Network Design Calculator
Network segments and routers from device count and location.
About this calculator
This calculator lays out a BACnet MS/TP field network from Total BACnet Devices, applying a per-trunk device cap and the Devices per Trunk guideline (20-25 recommended) to compute MS/TP Trunks Required as the ceiling of devices divided by the per-trunk limit. The 32-device cap on Devices per Trunk is a real, standard-referenced ceiling: ASHRAE 135 (the BACnet standard) clause 9 normatively states "the maximum number of nodes per segment shall be 32 (as specified by the EIA-485 standard)" -- a standard RS-485 transceiver presents one electrical unit load, and the bus supports 32 unit loads per segment, which is where that number comes from. It is a genuinely different number from MS/TP's own Max_Master parameter, whose declared value tops out at 127 (a MAC address) -- permitting up to 128 master devices (MAC addresses 0-127) in the token-passing ring. Max_Master governs how far a node polls for new peers, not how many physical devices a segment can carry, so the two ceilings answer different questions and neither one is simply "wrong." The 32-node ceiling can be raised on a single physical segment with lower-unit-load transceivers (1/4- or 1/8-unit-load parts stretch the raw RS-485 electrical limit toward 128-256 unit loads) or a repeater, but real MS/TP deployments still hit token-rotation performance limits and Max_Master's own 128-address ceiling well before that, so this calculator keeps Devices per Trunk capped at the standard's 32 as a conservative, code-referenced default rather than the higher electrical maximum.
Total Devices is the dominant driver of trunk and router counts because it scales that division directly, while Trunks per Router and Number of Floors only reshape how the already-determined trunk count is distributed -- more trunks per router reduces router count without changing how many trunks exist, and more floors spreads the same trunk count more thinly per floor without changing the total. The calculator also checks network responsiveness: token rotation time per device scales inversely with MS/TP Baud Rate (10ms/device at 76,800 bps, proportionally more at lower baud rates), and Max Poll Cycle -- token rotation on the fullest trunk times a 1.3 retry-overhead factor -- must stay under 2,000ms for responsive DDC control. Dropping the baud rate from 76,800 to 9,600 bps multiplies token rotation time by 8x for the same device count, which is why Within 2s Poll Limit can flip from acceptable to unacceptable purely from a baud rate change, with devices per trunk held constant.
Inputs
Results
MS/TP trunks required
2
BACnet/IP routers
1
Figures current as of 2020. Source: ANSI/ASHRAE Standard 135-2020, BACnet — A Data Communication Protocol for Building Automation and Control Networks, Clause 9 (MS/TP Data Link Layer)
How to Use This Calculator
- Enter Total BACnet devices, Devices per trunk, and Trunks per router.
- Select the MS/TP Baud Rate (9,600 / 19,200 / 38,400 / 76,800 bps) and enter the Number of floors.
- Review MS/TP trunks required and BACnet/IP routers.
- Use Max token rotation (ms) and Max poll cycle (ms), along with Within 2s poll limit, to check DDC responsiveness.
- Check Est. cable length (m), Trunks per floor, and Total MAC addresses for the network layout.
How the result changes with Total BACnet devices
| Total BACnet devices | MS/TP trunks required | BACnet/IP routers |
|---|---|---|
| 25 | 1 | 1 |
| 38 | 2 | 1 |
| 75 | 3 | 1 |
| 125 | 5 | 1 |
What each input means
- Total BACnet devices
- Total number of BACnet MS/TP field devices (controllers, sensors, actuators) on the network.
- Devices per trunk
- Max devices per MS/TP trunk segment. ASHRAE 135 clause 9 caps a segment at 32 nodes (EIA-485); 20-25 recommended for token-rotation performance. Separate from Max_Master's 128-address token-passing scope — see FAQ.
- Trunks per router
- Number of MS/TP trunks each BACnet/IP router can serve. Typical: 4-12 depending on hardware.
- MS/TP Baud Rate
- Select MS/TP baud rate. Higher baud = faster token rotation.
- Number of floors
- Building floors — used to estimate trunk distribution per floor.
What each result means
- MS/TP trunks required
- Total trunk segments needed based on device count and per-trunk limit.
- BACnet/IP routers
- Number of BACnet/IP to MS/TP routers required.
- Max token rotation (ms)
- Worst-case token passing time on the fullest trunk at the selected baud rate.
- Max poll cycle (ms)
- Estimated maximum poll cycle including retry overhead. Should be < 2000ms for responsive DDC.
- Within 2s poll limit
- 1 = yes (acceptable), 0 = no (reduce devices per trunk or increase baud rate).
- Est. cable length (m)
- Rough total cable estimate assuming 50m average between devices, max 1200m per trunk.
- Trunks per floor
- Average number of trunks per floor for balanced distribution.
- Total MAC addresses
- Total MAC addresses consumed by devices and router trunk ports.
How this is calculated
Worked example, using the default values
- Identify Input Parameters4 parametersTotal BACnet devices = 50, Devices per trunk = 25, Trunks per router = 8, MS/TP Baud Rate = 3 = 5 input(s) provided
- Calculate MS/TP trunks requiredMS/TP trunks required2 = 2
- Calculate BACnet/IP routersBACnet/IP routers1 = 1
- Calculate Max token rotationMax token rotation = devicesOnFullTrunk * tokenTimePerDeviceMs250 = 250
- Calculate Max poll cycleMax poll cycle = maxTokenRotationMs * 1.3325 = 325
Figures and sources
- BACnet MS/TP segment node limit (32 nodes, EIA-485) (2020) — ANSI/ASHRAE Standard 135-2020, BACnet — A Data Communication Protocol for Building Automation and Control Networks, Clause 9 (MS/TP Data Link Layer)
Engine last updated . Checked against 3 independently-derived tests — how we verify calculators. Built by Paul Gunder, a software engineer, not a licensed financial, medical, or legal professional.
Frequently Asked Questions
What has the biggest effect on the number of trunks and routers needed?
Total BACnet Devices. MS/TP Trunks Required is the ceiling of Total Devices divided by Devices per Trunk, so it scales directly and dominantly with device count -- Trunks per Router and Number of Floors only redistribute the resulting trunk count, they don't change how many trunks the device count itself requires.
Why would lowering the baud rate break my poll-cycle target?
Token rotation time per device is inversely proportional to MS/TP Baud Rate -- dropping from 76,800 bps to 9,600 bps (an 8x slower baud rate) multiplies the token rotation time on the fullest trunk by 8x for the same device count. Since Max Poll Cycle must stay under 2,000ms for responsive DDC control, the same trunk that was comfortably within limit at 76,800 bps can fail Within 2s Poll Limit at a slower baud rate.
Does adding more floors change the total number of trunks?
No. Number of Floors only computes Trunks per Floor by dividing the already-determined MS/TP Trunks Required across the floor count for planning purposes -- it has no effect on the trunk count itself, which is set purely by Total Devices and Devices per Trunk.
Is 32 devices per trunk a hard BACnet protocol limit?
Yes and no -- there are genuinely two different numbers here, not one that's simply wrong. ASHRAE 135 clause 9 (the BACnet standard itself) directly states "the maximum number of nodes per segment shall be 32 (as specified by the EIA-485 standard)" -- a standard RS-485 transceiver presents one electrical unit load, and the bus supports 32 unit loads, so 32 is a real, standard-referenced ceiling for a single physical segment, not a myth. Separately, MS/TP's own Max_Master parameter -- which controls how far a node searches the token-passing ring for new master peers, not physical device count -- has a declared value that tops out at 127 (a MAC address), permitting up to 128 master devices (MAC addresses 0-127). Lower-unit-load transceivers (1/4- or 1/8-unit-load parts) or a repeater can stretch the raw electrical ceiling on one segment well past 32, but real MS/TP deployments still run into token rotation performance limits and Max_Master's own 128-address ceiling first, so this calculator caps Devices per Trunk at the standard's 32 as a conservative, code-referenced default rather than the higher electrical maximum.
How does the calculator estimate cable length?
It assumes 50 meters of average cable run between devices on each trunk, capped at a maximum of 1,200 meters per trunk (a practical MS/TP segment length limit), then multiplies that per-trunk figure by MS/TP Trunks Required. It is a rough planning estimate, not a substitute for an actual cable routing study.
Related Calculators
The questions that sit next to this one — chosen by subject, including calculators filed under a different category.
More in Construction & Building Trades.