Component guide · Intermediate · 3 min read
Serial Bus Servos
Smart Servos for Robot Arms and Legs
By Geekobot Learning Team · Updated 24 Oct 2026
On this page
A serial bus servo, or smart servo, takes position commands over a shared serial line instead of a PWM pulse. Each servo has an ID, so you can daisy-chain many on one cable, and most report back position, temperature, voltage and load. That makes them ideal for robot arms, hexapods and humanoids. They need a controller or adapter board for the half-duplex bus, and a power supply strong enough for every servo moving at once.
Key specs at a glance
- Bus
- Half-duplex UART (TTL) or RS-485 on some models
- Wiring
- Three-wire daisy chain: power, ground, data
- Feedback
- Position, speed, load, temperature, voltage (model dependent)
- Supply
- About 6 to 12 V depending on model
- Range
- Often 240 or 360 degrees, or continuous rotation mode
- Setup
- Set a unique ID for each servo before chaining
Bus servos vs PWM servos
A normal hobby servo needs one PWM pin each and gives no feedback. Bus servos share one data line and answer questions, so your code knows where each joint is and whether it is overloaded. You can also turn torque off, move the arm by hand, read back the positions and replay them, which is a quick way to teach a robot a motion.
The trade-offs are cost, the need for a bus adapter and slower update rates when many servos share one line.
Wiring and IDs
All servos come with the same default ID, so connect them one at a time first and give each a unique ID with the maker's software or library. Then daisy-chain them.
The data line is half duplex: the controller sends and listens on the same wire. Use the maker's debug or adapter board, or a microcontroller with a tri-state buffer circuit. ESP32 boards with a dedicated servo driver are common for these servos.
Size the power supply for the worst case of several servos stalled at once; a 6-servo arm can draw well over 5 A. Use thick power wires and inject power at more than one point on long chains.
Using them in robots
- Robot arms: read positions back for smooth, coordinated motion and collision detection by load. See robotic arms.
- Legged robots: hexapods and quadrupeds need 12 to 18 servos with high torque and feedback; see legged robots.
- Wheels: many bus servos switch to continuous rotation (motor) mode.
- Watch temperature readings and pause motion when servos get hot; constant load at a stall burns them out.
Try it: Motor power torque calculator
Change the values and the diagram and results update as you type.
Common mistakes to avoid
- Connecting several new servos together before setting IDs.
- Wiring the half-duplex bus straight to a UART without the right adapter.
- An undersized power supply.
- Mixing servo brands with different protocols on one bus.
- Holding a stalled load until the servo overheats.
Frequently asked questions
Are serial bus servos better than normal servos?
For multi-joint robots, yes: fewer wires, feedback and better control. For one simple movement, a PWM servo is cheaper.
Can I control bus servos with Arduino?
Yes, with the right adapter board and library, using a hardware serial port.
Why do all my servos move together?
They share the same default ID. Set each one separately.
Can bus servos rotate continuously?
Many have a motor mode for continuous rotation.
Do they need a separate supply?
Yes. Power them from a supply or battery sized for all servos, not from the board.
Parts for this guide
Calculators
Terms in this guide
Projects that use it
Put this into practice: 1 step-by-step build in our project library uses parts from this guide.
Keep learning
Sources
- Hiwonder LX-16A bus servo communication protocol
- Feetech STS/SCS series servo manual
- ROBOTIS Dynamixel protocol documentation
Written by the Geekobot team from manufacturer datasheets. Always check the datasheet for the exact part and variant you buy.




