Bus Servos

A Bus Servo is a smart servo that talks to your microcontroller over a serial bus instead of a PWM pulse. You can daisy chain many of them on a single data wire, address each one by ID, and ask it to report back on its own position, load, voltage and temperature. The Feetech STS3215 is one of the most popular examples — and a brilliant way to understand how the whole category works.

• Why Bus Servos Exist
• Inside a Bus Servo
• Serial, Not PWM
• The Packet Format
• The Control Table
• Daisy Chaining
• Half-Duplex and Bus Contention
• Position Resolution
• Closed-Loop Feedback
• Powering a Bus Servo
• Compared to Other Servo Types
• Where Bus Servos Shine
• Where a PWM Servo is Still the Right Choice
• Related Reading

Why Bus Servos Exist

If you’ve ever built a robot arm with classic PWM servos you’ll know the pain:

• Every servo needs its own signal wire back to the microcontroller — six joints = six GPIO pins.
• The servo is a one-way actuator. You tell it where to go, but it can’t tell you where it actually is.
• Any mechanical load on the output shaft can deflect it from the commanded angle with no way for you to detect it.

Bus servos were designed to fix all three of those problems in one go — and the trick they use is to put a tiny microcontroller inside the servo itself.

Inside a Bus Servo

A bus servo contains everything a regular hobby servo has — DC motor, gearbox, potentiometer or magnetic encoder, control circuit — plus a small onboard microcontroller that handles serial communications and closes a position-control loop in firmware.

That extra intelligence is what makes all the new behaviours possible:

• It can listen to commands on the serial bus and only respond to its own ID.
• It can read its internal position sensor and stream that data back.
• It can monitor motor current, voltage and temperature.
• It can enforce its own position limits, store calibration data, and remember them across power cycles.

Serial, Not PWM

Instead of a 50 Hz pulse-width signal, bus servos speak a serial protocol over UART (Universal Asynchronous Receiver/Transmitter).

Most hobby-grade bus servos use half-duplex UART: a single data wire carries traffic in both directions, taking turns. At any given moment, one end of the bus is transmitting and every other device is listening.

The Feetech STS3215 runs at 1 Mbaud by default — roughly a thousand times faster than I²C’s standard 100 kHz bus — so commands and replies are effectively instant from a robotics point of view.

The Packet Format

Every command on the STS3215 bus is a small binary packet. It follows a structure you’ll also recognise from Dynamixel servos and many other serial buses:

So to ping servo ID 1, the master sends just six bytes:

0xFF 0xFF 0x01 0x02 0x01 0xFB

The servo replies with a similar packet containing an error byte (0x00 if no error) and a matching checksum, proving it heard the request and is alive.

The Control Table

Inside every STS3215 is a little memory map called the control table — a set of numbered registers you can read and write across the bus. Some registers live in EEPROM (persistent across power cycles), others in RAM (reset on power-up).

A few of the most useful registers on the STS3215:

Control = write to registers. Feedback = read from registers. That’s the entire mental model.

Daisy Chaining

Each STS3215 has two identical ports — one in, one out. Both carry power, ground, and the data line on the same connector, which means the entire arm can be wired with a single continuous chain.

Driver board ──► Servo 1 ──► Servo 2 ──► Servo 3 ──► …

Because every servo is listening to the same bus, each one needs a unique ID. Out of the factory, every STS3215 ships with ID = 1. Before you daisy chain them together, connect them one at a time and write a new ID into register 5.

Send a packet with ID 254 and every servo on the bus responds — that’s the broadcast address, useful for sync-writes that drive multiple joints in the same instant.

Half-Duplex and Bus Contention

Because the bus is half-duplex, only one device can transmit at a time. The master microcontroller enforces this with a simple rule:

1. Transmit a command.
2. Switch the line around (either electronically via a direction pin, or by relying on an open-drain buffer).
3. Listen for the reply, timing out after a millisecond or two if nothing comes back.

On a driver board like the Waveshare Bus Servo Adapter, this direction switching is handled in hardware — you just connect the microcontroller’s TX and RX pins and the board takes care of the rest.

Position Resolution

The STS3215 reports position as a 12-bit value — that’s 4096 steps spanning the full 360° range of the output shaft. Each step therefore represents about 0.088°, which is well beyond what a typical 3D-printed mechanism can hold anyway.

You can drive the servo past the normal 0–4095 range in continuous-rotation mode, making it behave like a geared DC motor with feedback — handy for wheels and turrets.

Closed-Loop Feedback

This is the feature that genuinely changes what you can build. After commanding a position, you can immediately read Present position, Present speed, Present load, Present voltage and Present temperature back from the servo.

Some things this unlocks:

• Motion sequencing — wait until the servo has actually arrived before sending the next command.
• Load detection — notice when an arm has picked something up (or bumped into something).
• Teach-by-demonstration — disable torque, move the arm by hand, record the positions and play them back later.
• Thermal protection — back off before the servo overheats.

None of this is possible with a PWM servo, because a PWM servo has no way to talk back.

Powering a Bus Servo

The STS3215 is rated for 6–8.4 V (the “7.4 V class”), so the natural power source is a 2S LiPo or a 7.4 V bench supply. Higher voltages within the rated band generally give higher torque and speed.

A few important rules:

• Never power the servo from a microcontroller’s 5 V or 3.3 V rail. Stall currents can run into several amps and will instantly destroy the regulator.
• Share a common ground between the microcontroller and the servo’s power supply, otherwise the UART signals have no reference voltage.
• For multi-servo arms, size the supply for the sum of stall currents, not the idle draw — multiple servos stalling at once is a very real scenario during a collision.

Compared to Other Servo Types

The STS3215 effectively sits in the sweet spot: Dynamixel-grade features at hobby-grade prices.

Where Bus Servos Shine

• Robot arms — especially anything with more than three joints, where PWM wiring becomes a mess.
• Hexapods and quadrupeds — 12+ servos wired on a single data line rather than 12+ GPIOs.
• Animatronics — smooth coordinated motion with position feedback for safety.
• Teaching rigs — torque-off + read-position makes teach-by-demonstration almost free.

Where a PWM Servo is Still the Right Choice

Bus servos aren’t always the answer:

• Single-servo projects where the cost premium isn’t justified.
• Very small spaces where a micro servo like the SG90 is the only thing that fits.
• Ultra-fast RC applications where hobby servos are optimised for minimum latency from dedicated receivers.

Related Reading

• Servos — How they work
• I²C — another embedded bus protocol
• Shift Registers — multiplexing GPIO with serial data