This guide walks through commissioning a BACnet MS/TP damper actuator in the field — from trunk planning to first successful stroke — and lists the bus errors that cause most “it won’t talk” calls. MS/TP (Master-Slave Token Passing) runs on an EIA-485 physical layer, so almost every problem is either wiring, addressing, or baud rate.
Step 1 — Plan the trunk
- Daisy-chain devices; do not stub or star-branch the bus.
- Use shielded twisted-pair (Belden 8718 or equivalent), EIA-485 rated.
- Terminate both ends with a 120 Ω resistor; leave mid-bus devices unterminated.
- Keep total length under ~1,200 m and devices under ~32 without a repeater.
Step 2 — Set address and baud
Every device needs a unique MAC address (1–127). Avoid 0 (reserved) and 127 (broadcast). Set baud rate (typically 9,600, 19,200, 38,400, or 76,800 bps) and the max-master / max-info-frames to match the rest of the trunk. Mismatched baud is the #1 cause of “device not found.”
Step 3 — Wire A/B correctly
MS/TP polarity matters. Connect A to A, B to B across all devices. The shield should be grounded at one end only to avoid ground loops. A common mistake is swapping A and B at one device — the bus then sees a constant collision and nothing enumerates.
Step 4 — Power up and discover
Apply 24 V and run a BACnet Who-Is from your commissioning tool (e.g., YABE, VTS, or the BMS browser). If the actuator answers with an I-Am, addressing and wiring are correct. Note its Device Instance for object mapping.
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 confirm the physical blade follows and feedback tracks. If feedback lags or overshoots, check damping/PID in the controller.
Step 6 — Fix the common errors
| 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 | Ground shield at one end only; keep away from VFDs |
| Actuator oscillates | Improper PID / no damping | Add deadband or lower gain in the controller |
| Partial bus works, others silent | Mid-bus termination resistor left in | Remove resistors except at the two ends |
Most commissioning failures are solved at Steps 1–3. Get the trunk, address, and polarity right and the software side is routine. DNARENS BACnet/Modbus actuators ship with DIP or software addressing and a clearly labeled A/B terminal block to keep this process simple.
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
