Low-Voltage Field Reference • Technical term
BACnet MS/TP Explained: Trunks, Addresses, Bias and Commissioning
BACnet MS/TP carries BACnet communications over an EIA-485-style multi-drop trunk. Reliable operation depends on a disciplined trunk topology, unique addresses, correct baud rate, compatible bias and termination, cable practices and measured commissioning evidence.
Direct answer
what is BACnet MS TP: the practical answer
BACnet MS/TP carries BACnet communications over an EIA-485-style multi-drop trunk. Reliable operation depends on a disciplined trunk topology, unique addresses, correct baud rate, compatible bias and termination, cable practices and measured commissioning evidence.
For a working contractor, the value of this definition is its ability to translate field language into a verifiable design decision. Use the sequence meaning → project consequence → evidence → acceptance. The label alone never proves compatibility, compliance or performance.
What this changes in the design package
BACnet MS/TP Explained: Trunks, Addresses, Bias and Commissioning should change at least one controlled project record. On a floor plan, identify the physical location or route affected by controller and device manuals and trunk length and cable type. On the riser or signal-flow drawing, show how the selected equipment, pathway, power and communications relationships support the intended outcome. In the schedule, preserve the exact data needed to buy, configure, install and test the system.
Plan
Show the device, route, zone or interface in context. Use stable IDs rather than relying on a symbol alone, and flag any assumption that can change quantity or performance.
Riser or schematic
Show origin, destination, intervening equipment, shared infrastructure and interface responsibility. A diagram should expose relationships the floor plan cannot show clearly.
Schedule
Record device count and MAC plan, baud-rate policy, bias and termination ownership and shield and grounding method where they can be reviewed and revised without redrawing the entire plan.
Proposal
State the verified design basis, named allowances, exclusions, owner/IT/electrical dependencies, testing method and the event that triggers a change order.
Field method
A repeatable definition workflow
Start by deciding what the term must communicate on this project. Then connect the definition to a selected device, a measurable setting, a drawing note and an acceptance result.
- 1. walk the physical trunk in order.
- 2. verify unique MAC addresses and instance numbers.
- 3. measure polarity and idle conditions with suitable tools.
- 4. capture token, error and retry evidence.
After the final step, repeat the original operating scenario. A correction is not complete until the system passes the required function, the drawing and schedule match the installed condition, and the handoff record identifies what changed.
Decision and evidence table
| Question | Evidence to collect | Where to record it | Acceptance signal |
|---|---|---|---|
| What controls controller and device manuals? | walk the physical trunk in order; use exact model, reading, setting, photo or log evidence. | BACnet riser, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls trunk length and cable type? | verify unique MAC addresses and instance numbers; use exact model, reading, setting, photo or log evidence. | trunk and address schedule, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls device count and MAC plan? | measure polarity and idle conditions with suitable tools; use exact model, reading, setting, photo or log evidence. | commissioning capture, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
| What controls baud-rate policy? | capture token, error and retry evidence; use exact model, reading, setting, photo or log evidence. | as-built device order, keyed to the same device/cable/door/zone ID. | The reviewed record and field condition agree, with no unresolved assumption hidden as fact. |
Keep evidence close to the decision it supports. A screenshot without an equipment ID, a cable test without the cable identifier, or a code note without edition and jurisdiction is difficult to audit later.
Technical deep dive
Six controls that make BACnet MS/TP defensible
1. controller and device manuals
preserve controller and device manuals before the team commits BACnet trunk to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to walk the physical trunk in order. Compare the evidence with the intended building automation outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for star branches and undocumented taps, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the BACnet riser. Tie it to BACnet MS/TP and BACnet trunk with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
2. trunk length and cable type
establish trunk length and cable type before the team commits MAC address to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to verify unique MAC addresses and instance numbers. Compare the evidence with the intended building automation outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for duplicate MAC addresses, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the trunk and address schedule. Tie it to BACnet MS/TP and MAC address with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
3. device count and MAC plan
measure device count and MAC plan before the team commits RS-485 termination to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to measure polarity and idle conditions with suitable tools. Compare the evidence with the intended building automation outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for termination at every device, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the commissioning capture. Tie it to BACnet MS/TP and RS-485 termination with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
4. baud-rate policy
trace baud-rate policy before the team commits building automation network to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to capture token, error and retry evidence. Compare the evidence with the intended building automation outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for changing baud rates without a controlled record, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the as-built device order. Tie it to BACnet MS/TP and building automation network with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
5. bias and termination ownership
reconcile bias and termination ownership before the team commits token passing to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to walk the physical trunk in order. Compare the evidence with the intended building automation outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for star branches and undocumented taps, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the BACnet riser. Tie it to BACnet MS/TP and token passing with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
6. shield and grounding method
challenge shield and grounding method before the team commits BACnet MS/TP to the drawing. Identify who supplied the value, how current it is, which exact device, cable, interface, door, zone or route it controls, and what would invalidate it. If the answer comes from a product sheet, retain the model and revision. If it comes from a field observation, retain the location, timestamp, instrument or screen, and technician. If it comes from a requirement, retain jurisdiction, edition and reviewer.
Use this checkpoint to verify unique MAC addresses and instance numbers. Compare the evidence with the intended building automation outcome and the accepted project baseline. A discrepancy should become a named issue with an owner and due date; it should not be buried in a markup. Watch specifically for duplicate MAC addresses, because that failure can create a plausible-looking plan while breaking the installation, test or commercial handoff.
Close the checkpoint in the trunk and address schedule. Tie it to BACnet MS/TP and BACnet MS/TP with the same stable identifier used on the plan and schedule. The reviewer should be able to see the source, selected value, status, exception and acceptance result without reconstructing the designer’s assumptions from email.
Field-capture worksheet
Before leaving the site, collect enough evidence that another qualified person can reconstruct the decision. Start with the site, floor, room and stable asset ID. Record the date, technician and current drawing revision. Photograph the overall context before taking close-ups, and place a readable label or reference in the image when practical.
- Identity
- Exact manufacturer, model, firmware or listing, terminal names, cable ID, panel/port/zone/door address, and the related plan symbol.
- Observed state
- What the user reported, what the technician reproduced, timestamps, LEDs or messages, logs, settings and whether the condition is continuous or intermittent.
- Measured state
- Applicable voltage, current, resistance, optical level, cable result, protocol status, signal format or environmental condition, including the instrument and test boundary.
- Change control
- The one change made, authorization, before/after evidence, temporary workaround, regression checks and any effect on other devices or shared infrastructure.
For this topic, call out controller and device manuals, device count and MAC plan and bias and termination ownership. Use the vocabulary BACnet MS/TP, BACnet trunk, MAC address consistently so the field note, drawing, schedule and proposal can be found together.
Worked field example
From an uncertain condition to a controlled record
A project manager receives a report involving BACnet MS/TP. The available plan shows a symbol, but it does not identify controller and device manuals, trunk length and cable type or device count and MAC plan. Instead of pricing or repairing from the incomplete symbol, the team opens a single issue record and assigns the affected equipment, cable or location a stable ID.
The technician collects the current settings, model information, photos and measured state. The designer compares that evidence with the selected equipment documentation and the current authoritative sources listed below. The estimator separates verified scope from allowances. The project manager records who owns any external dependency, such as an electrical circuit, network policy, door hardware condition, AHJ decision or owner-furnished device.
The corrected package includes the BACnet riser, trunk and address schedule and commissioning capture. The team then repeats the operating test under the same conditions that produced the original question. That closed loop turns BACnet trunk and MAC address from search terms into traceable project decisions instead of isolated notes.
Common failure modes—and why they happen
Failure 01
star branches and undocumented taps
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 02
duplicate MAC addresses
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 03
termination at every device
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
Failure 04
changing baud rates without a controlled record
This shortcut removes context from the decision. Correct it by returning to the project-specific input, documenting the selected basis, and repeating the affected acceptance test.
When a failure involves regulated life safety, egress, listing, energized work, public-safety radio, or code interpretation, stop at the boundary of your authorization. Escalate to the responsible qualified party and preserve the condition and evidence.
Minimum contractor deliverables
A useful answer survives the handoff from design to estimating, proposal, installation and closeout. At minimum, create the following:
- BACnet riser.
- trunk and address schedule.
- commissioning capture.
- as-built device order.
Each deliverable should show the project, revision, author, review status and the identity of the system element it controls. If a value is not verified, label it as an assumption, allowance, pending submittal or owner/AHJ decision. Do not let a blank field become an accidental commitment.
How to carry the answer into scope and proposal language
Describe the outcome first: what the customer will receive, where it applies and how it will be tested. Then name the basis used for BACnet MS/TP, including the controlling drawing revision and selected equipment data. Include the labor and documentation needed to produce BACnet riser and trunk and address schedule.
Separate dependencies explicitly. Examples include usable owner drawings, accessible ceilings, working branch power, network addressing and policy, compatible owner equipment, door hardware readiness, permits, shutdown windows, AHJ review and access to occupied areas. If one of those facts is unknown, write an allowance or qualification and define how the price changes when the fact is confirmed.
Finish with acceptance: identify who witnesses the test, what evidence is retained and which result constitutes completion. This makes the page commercially useful without turning it into a product pitch.
Commissioning, handoff and future service
Commissioning should prove the designed function, not simply show that equipment turns on. Run the accepted scenario, an expected failure or trouble state, recovery, and any interface that crosses to network, electrical, fire alarm, door hardware, controls or owner systems. Save results against stable IDs and the approved revision.
At handoff, give the owner the BACnet riser, trunk and address schedule, final configuration, approved substitutions, warranties and the contact path for unresolved external responsibilities. Remove default credentials and temporary access where applicable. Explain which changes can invalidate the result—for example a new firmware release, equipment replacement, changed speaker tap, moved camera, added cable, revised AHJ direction or modified switch policy.
Future service begins by comparing the current condition with this accepted baseline. If the record is missing, recreate it before making broad changes. That discipline reduces repeated troubleshooting, protects proposal scope, and lets the next technician distinguish a design issue from a later operational change.
Frequently asked questions
What should I verify first?
Start with controller and device manuals and trunk length and cable type. Establish the exact product, project location and current system state before applying a diagram or changing configuration.
Can I use this page as a construction detail?
Use it as an editorial planning and verification aid. Convert it into a project detail only after reconciling the manufacturer instructions, adopted requirements, approved submittals and responsible professional or AHJ direction.
What belongs in the closeout package?
Include BACnet riser, trunk and address schedule, commissioning capture, as-built device order, plus test evidence, deviations, final settings and the identity of the person or authority that accepted the result.
What should I read next?
Continue with DORI Distance for Security Cameras: Detect, Observe, Recognize, Identify, Security Camera WDR Explained: When Wide Dynamic Range Helps, ONVIF Profile S vs Profile T: What Security Designers Should Specify, OSDP Access Control Explained: Wiring, Supervision and Secure Channel and the Building Automation design software resource.
Authoritative references and how to use them
These links are starting points for current primary-source information. Confirm the current edition, product revision, publication status, jurisdiction and applicability. Accessed for this release on 2026-08-08.
- BACnet International MS/TP glossary — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- CISA Secure by Design — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.
- TIA Standards and Technology — use the source to verify terminology, conformance, published requirements or manufacturer-specific behavior; do not substitute this summary for the controlling document.