Most “the actuator won’t talk” calls on a BACnet MS/TP trunk trace back to three things: wiring, addressing, or baud rate. This field guide walks through commissioning a BACnet MS/TP damper actuator from trunk planning to first successful stroke, and lists the bus errors that cause the most callbacks. MS/TP (Master-Slave Token Passing) runs on an EIA-485 physical layer, so the fix is almost always physical, not software.
What MS/TP Is — and Why It Still Matters
BACnet MS/TP is defined by ANSI/ASHRAE Standard 135 as a twisted-pair, token-passing variant of BACnet. Devices share one EIA-485 bus and pass a “token” frame around; only the device holding the token may transmit. That design makes the bus cheap, robust, and easy to diagnose — but it also means one mis-wired or mis-addressed device can disturb the whole trunk. MS/TP remains the default field bus for damper actuators, valves, and sensors in cost-sensitive commercial projects, even while supervisory controllers move to BACnet/IP.
Before You Start: Tools and Pre-commissioning Checklist
| Item | Why you need it |
|---|---|
| Shielded twisted pair, EIA-485 rated (e.g., Belden 8718 or equivalent) | MS/TP is polarity-sensitive and noise-sensitive; telephone-style cable causes intermittent dropouts |
| Two 120 Ω resistors | Termination for both physical ends of the trunk |
| Commissioning tool (YABE, VTS, or the BMS front end) | Who-Is/I-Am discovery, object mapping, MS/TP statistics |
| Address schedule (paper or spreadsheet) | Duplicate MAC addresses are the #1 software-side fault |
| 24 V supply and meter | Verify actuator supply and check for voltage drop under load |
Step 1 — Plan the Trunk
- Daisy-chain devices; do not stub or star-branch the bus. Star wiring works until it doesn’t, then costs you a day of troubleshooting.
- Keep total trunk length under ~1,200 m (4,000 ft) and device count under ~32 without a repeater. Beyond that, plan an MS/TP repeater or a second trunk.
- Run the bus away from VFDs, large contactors, and lighting dimmer runs. If a crossing is unavoidable, cross at 90°.
- Leave the two termination points physically accessible — you will touch them again.
Step 2 — Set the MAC Address and Baud Rate
Every device needs a unique MAC address (1–127). Avoid 0 (reserved for the router in some installations) and 127 (reserved). Record every address on the schedule as you set it — an address set but not written down is a future duplicate waiting to happen.
Set the baud rate to match the rest of the trunk (typically 9,600, 19,200, 38,400, or 76,800 bps). Mismatched baud is the most common cause of “device not found.” If the system specifies max-master and max-info-frames, align them with the BMS controller defaults; most trunks run happily at max-master 32 and max-info-frames 1–5.
Step 3 — Wire the Bus Correctly
MS/TP polarity matters. Connect A to A, B to B across all devices — swapping A and B at one device makes the whole bus see constant collisions, and nothing enumerates reliably. Ground the cable shield at one end only to avoid ground loops between buildings or panels. Keep the daisy chain continuous: in at one terminal block, out to the next device, resistor only at the two physical ends.
Step 4 — Power Up and Discover the Device
Apply 24 V and run a BACnet Who-Is from your commissioning tool. A healthy actuator answers with an I-Am containing its Device Instance, object list, and vendor ID. If it answers, addressing and wiring are correct — note the Device Instance for object mapping. If it stays silent while other devices on the same trunk respond, suspect that device’s address, baud, or wiring before you blame the trunk.
Step 5 — Map Objects and Test the Stroke
Typical object map for a modulating actuator:
| Object | Type | Use |
|---|---|---|
| AO-1 | Analog Output | Command 0–100% (or 0–10 V) |
| AI-1 | Analog Input | Position feedback |
| BI-1 | Binary Input | End-switch / alarm |
Send a 0→50→100% ramp and watch three things: the blade follows the command, feedback tracks it without lag or overshoot, and the end-switch flips at the expected position. If feedback lags, check for mechanical binding or loose set screws before touching controller tuning.
Step 6 — Diagnose the Common Faults
| Symptom | Likely cause | Fix |
|---|---|---|
| No device on Who-Is | Missing termination, A/B swapped, baud mismatch, address conflict | Verify 120 Ω at both ends, check polarity, align baud, make addresses unique |
| Intermittent dropouts | Ground loop / noise pickup | Ground shield at one end only; reroute away from VFDs |
| Actuator oscillates | Aggressive loop tuning, no deadband | Add deadband or lower gain in the controller |
| Partial bus works, rest silent | Termination resistor left at a mid-bus device | Remove resistors except at the two physical ends |
| Bus slows down over time | A device holding the token and timing out repeatedly | Check MS/TP statistics per device; replace or re-address the offender |
Read the MS/TP Statistics, Not Just the Object List
Most commissioning tools and BMS controllers expose per-device MS/TP statistics. Three counters are worth checking during handover:
- Token losses / timeouts — a few per hour is normal; counts climbing every minute point at wiring noise or a failing device.
- CRC errors — almost always a physical-layer problem: shield not grounded, cable run next to a VFD, or a marginal transceiver.
- Rejected frames — often a baud or max-info-frames mismatch after a firmware change.
Recording these counters at handover gives the facilities team a baseline; without it, “the BMS has always been a bit slow” becomes undiagnosable.
Handover: What to Document
- Trunk drawing with device locations, MAC addresses, and Device Instance numbers
- Baud rate, max-master, and max-info-frames settings
- Termination locations (and a photo of both ends)
- Object map (AO/AI/BI) per actuator
- Final MS/TP statistics snapshot
Working With Routers and Multi-Trunk Layouts
Larger floors rarely fit one trunk. The standard layout is a BACnet router with one MS/TP trunk per riser or floor group, each trunk carrying its own termination and its own address space (addresses repeat across trunks — Device Instances stay unique). Two commissioning notes for this topology:
- Commission one trunk at a time. Bring the router port up, verify every device on that trunk, then move to the next — debugging two half-working trunks at once costs more time than it saves.
- Watch the router’s per-port statistics during the final walk-test. A port with climbing timeouts after handover usually means a device was re-addressed or re-wired after your visit.
FAQ
Can I mix baud rates on one trunk?
No. All devices on an MS/TP trunk must run the same baud rate. Some devices auto-negotiate down to the slowest peer; do not rely on it — set every device explicitly.
How many actuators can share one MS/TP trunk?
Up to 32 addresses per segment is the practical rule of thumb without a repeater, and total length under ~1,200 m. For larger floors, use a repeater or split into multiple trunks on a BACnet router.
Can MS/TP and BACnet/IP coexist?
Yes — a BACnet router bridges the two. MS/TP typically serves the field level (actuators, valves, sensors) while BACnet/IP handles the supervisory network.
Why does my actuator drop off the bus only in summer?
Intermittent faults that track temperature usually mean a marginal transceiver, a loose terminal, or cable run near equipment that switches seasonally (chillers, VFDs). Re-torque terminals and inspect the shield ground before replacing hardware.
Choosing hardware that makes this process simple helps: DANRENS modulating damper actuators ship with clearly labeled A/B terminals, and our damper actuator range covers on/off, floating, and modulating variants for MS/TP-ready BMS projects. For sizing before you order, use the damper actuator torque calculator, and see Damper Actuators 101 for the selection basics.
Sources
Primary documents behind the standards, regulations and figures in this article. Links open in a new tab.
Need Help Specifying or Sourcing?
Tell us your system type, required quantity and target market — our engineers reply within 24 hours with matched models and a quotation.
Back to Blog
