TTL serial bus
What a designer must do
- Identify the servo family before any write. Feetech memory tables are not interchangeable, and a wrong persistent write can change ID, baud rate, mode or protection [1].
- Power the motors from an external regulated supply, never from USB [2]. Share one common ground [3].
- At first power-up, connect one servo with no load [4].
- Set each ID with only that servo connected [5]. Then add servos one at a time [6].
- Size the supply for servos moving at once times peak demand, with margin [7].
- Budget bus time: frame bytes times 10, over the baud rate, summed over one control cycle [8].
- Read back after any sync or broadcast write. They return no status [9].
- Cut power before you unplug a servo or change any wiring [10].
Scope: the TTL serial-bus guidelines, for half-duplex serial-bus servos. They come from two makers: the FEETECH wiki at commit 5637b79 and the ROBOTIS e-Manual at commit 0807b1b. The SO-101 follower uses 6 STS3215 motors [11], so the Feetech rows apply to it.
A DYNAMIXEL row does not prove the same point for Feetech. Where the Feetech column says "No guideline", the database has no statement. Do not fill it from the DYNAMIXEL column.
Two protocols side by side
| Item | Feetech FT-SCS (SCS, STS, SMS, HLS) | DYNAMIXEL Protocol 2.0 |
|---|---|---|
| Serial format | 1 start, 8 data, 1 stop, no parity [12] | Half-duplex 8-bit asynchronous, 1 stop, no parity [13] |
| Bus access | No guideline on record | One device transmits, all others in input mode [14] |
| Packet header | Two 0xFF bytes [15] | 0xFF 0xFF 0xFD 0x00 [16] |
| Check field | Inverse of the low byte of ID + Length + Instruction + Parameters [17] | CRC_L, CRC_H in the packet [16]. No guideline gives the method |
| ID range | 0 to 253 [18] | 0 to 252 [19] |
| New servo ID | No guideline | 1 [20] |
| Factory baud | SCS and STS 1000000, SMS 115200 [21] | No guideline |
| Baud storage | STS register 6 holds a code 0 to 7 [22] | On models with this table, 2,000,000 / (Value + 1). Not all models [23] |
| Two-byte values | Low byte first on STS, SMS, HLS. High byte first on SCS, SCSCL [24] | No guideline |
| Broadcast reply | Normally none [9] | A write sent to the Broadcast ID returns no status packet [25] |
| Broadcast PING | Only with a single servo on the bus [26] | No guideline. The source quote for the broadcast-reply guideline sets Ping, Sync Read and Bulk Read apart from its no-status sentence [25] |
| Multi-servo write | SYNC WRITE, higher real-time performance than REG WRITE plus ACTION [27] | Sync Write: same address and length, ID 0xFE [28]. Bulk Write: each ID once [29] |
| Reply level | STS: 0 answers READ and PING, 1 answers all [30] | 0 answers PING, 1 PING and READ, 2 all [31] |
| Return delay | SMS address 7. The same STS address is reserved [32] | 2 microseconds per unit, default 250 units or 500 microseconds, maximum 508 [33] |
| Byte gap | No guideline | Under 1.5 ms, or the servo drops the packet [34] |
| Direction switch | Named only as a fault cause [35] | Check the shift register empty flag. Disable interrupts around the last byte [36], [37] |
| UART to bus | No guideline | Needs a half-duplex converter [38] |
| Logic level | No guideline | ROBOTIS circuit is for 5 V or 5 V tolerant MCUs. Otherwise use a level shifter [39] |
| USB latency | No guideline | SDK default 16 ms. Lower it for high baud rates [40], [41] |
The reply levels are a trap. Level 1 means different things across the two makers, so the host parser should match the level set on each servo [30], [31].
STS baud codes
Register 6 stores the code, not the rate. The byte time is computed: 10 bit times per byte, over the baud rate.
| Code [22] | Baud rate [22] | One byte, computed [8] |
|---|---|---|
| 0 | 1000000 | 10 microseconds |
| 1 | 500000 | 20 microseconds |
| 2 | 250000 | 40 microseconds |
| 3 | 128000 | 78.1 microseconds |
| 4 | 115200 | 86.8 microseconds |
| 5 | 76800 | 130.2 microseconds |
| 6 | 57600 | 173.6 microseconds |
| 7 | 38400 | 260.4 microseconds |
The STS3215 part page lists the rates of a driver library: seven match the codes above, 76800 is missing, and 19200 is added. Its default is 1000000. STS and SCS servos leave the factory at 1000000 baud, so ping there first [21]. All servos on one bus must share one baud rate [42].
ROBOTIS states that a baud rate error below 3 percent does not affect UART communication [43]. The database has no matching Feetech statement.
Bus time budget
Use the bus-budget formula: frame bytes times 10, divided by baud rate, summed over one control cycle [8].
Worked on the guideline's own example frame, FF FF 01 02 01 FB [17]:
- Checksum: 0x01 + 0x02 + 0x01 is 0x04, and its inverse is 0xFB.
- On the wire: 6 bytes times 10 bits [8], at 1000000 baud [21], is 60 microseconds. This is computed, for this one frame.
Add every read reply and every write in the cycle, then compare with the control period. Shipped SO-101 control rates are in RL configs that ship. The typing vision policy commands every 40 ms [44].
This book gives no full-cycle figure for the SO-101. No guideline gives a Feetech sync-write frame length, a read reply time, or USB latency on the SO-101 adapter. The 16 ms USB latency is a DYNAMIXEL SDK default, not an SO-101 value [41]. Measure the round trip on your host, and log the serial transport delay for your model [40], [45].
Power and wiring
| Level | Requirement | Check | Source |
|---|---|---|---|
| must | USB does not power the servo motors. Motor power comes from an external regulated supply | review: wiring diagram shows a separate motor supply | [2] |
| must | The debug board ground and the motor supply ground share one common ground | measure: continuity between the two grounds | [3] |
| must | Size the supply as servos moving at once times the peak demand of each, with margin | calc: supply current rating against this sum | [7] |
| should | Thin, long or poorly contacting wires cause voltage drop and communication errors | measure: voltage at the last servo under peak load | [46] |
| should | Avoid long star branches and loose connectors | review: chain topology and connector retention | [47] |
| must | Use an adapter made for the servo's own bus type. TTL, RS-485 and CAN adapters are not interchangeable, and lines of different bus types are never joined | review: adapter matches the servo interface | [48] |
| must | Cut power before unplugging servos or changing wiring | review: bring-up procedure | [10] |
| must | Do not infer signal or power pins from wire colour. Follow the drawings | measure: continuity against the pinout before power | [49] |
For the SO-101 follower on STS3215-C018 servos, the stall sum is 6 times the stall current of one servo at 12 V, from its maker sheet [11]. That counts all six moving at once at stall [7]. Add your margin, then check the supply as in step 13 of First power-on. Label the leader and follower supplies: they differ at 5 V and 12 V and must not be swapped [50]. Keep one supply per bus segment, as the STS3215 voltage-rating guideline asks [51]: a project README rates the 7.4 V STS3215 at 16.5 kg.cm stall at 6 V and the 12 V version at 30 kg.cm.
RS-485, CAN and EtherCAT have their own signal-bus guidelines in Electrical and power. No guideline carries those limits over to a TTL bus.
IDs and persistent writes
| Level | Requirement | Check | Source |
|---|---|---|---|
| must | Every servo on one bus has a unique ID, and all share one baud rate | review: scan one servo at a time and list IDs | [42] |
| must | On DYNAMIXEL, a duplicate ID causes packet collision and network problems | review: scan reports each ID once | [52] |
| must | Feetech broadcast PING works only with a single servo on the bus | review: used only on a one-servo bus | [26] |
| must | Clear the STS lock flag before changing EEPROM values, then set it back. With the lock at 1, a write works until power off, then is lost | measure: power cycle and read back | [53] |
| must | After an ID write the servo answers only on the new ID. Use it for the relock | review: procedure uses the new ID | [54] |
| must | The connection drops as soon as an STS baud write succeeds. Reconnect at the new rate before you relock | review: procedure reconnects first | [55] |
| must | Register addresses differ across Feetech families. Write return delay only on families that hold it | review: per family | [32] |
| must | SCS, SMS/STS and HLS memory tables are not interchangeable | review: addresses come from the exact model table | [1] |
The order for an STS persistent write, from those guidelines:
- Clear the lock flag [53].
- Write the value.
- If it was the ID, talk to the new ID. If it was the baud code, reconnect at the new rate [54], [55].
- Set the lock flag back [53].
- Power cycle and read back [53].
Bring-up
Do this before step 22 of First power-on, which reads all six servos.
| Step | Do | Pass when | Source |
|---|---|---|---|
| 1 | Read each servo label. Find the family | Addresses come from the exact model table | [1] |
| 2 | Match the adapter to the interface | Adapter fits TTL | [48] |
| 3 | Check pins against the drawings | Continuity matches the pinout, before power | [49] |
| 4 | Wire an external motor supply and a common ground | Continuity between grounds | [2], [3] |
| 5 | Connect one servo, no load. Power on | One servo, nothing else on the bus | [4] |
| 6 | Ping at the factory rate | The servo answers | [21] |
| 7 | Set this servo's ID, with no daisy chain | lerobot-setup-motors runs with one motor on the bus. The servo answers on the new ID | [5], [54] |
| 8 | Power cycle and read back | The ID survives | [53] |
| 9 | Repeat 5 to 8 for each servo | Each is set once. Reused motors are set again | [56] |
| 10 | Add servos one at a time | Each answers a ping after you add it | [6] |
| 11 | Scan the full chain | Each ID appears once, at one baud rate | [42] |
| 12 | Log supply voltage while torque enables on all servos | Voltage holds. Startup transients are a frequent power fault | [57] |
| 13 | Load the chain to peak | Voltage at the last servo is logged | [46] |
| 14 | Read back after a sync write | Position changed as commanded | [9] |
| 15 | Log command transport delay | Delay is recorded for the model | [45] |
| 16 | Calibrate the arm | Leader and follower read the same values in the same pose | [58], [59] |
On the SO-101
| Item | Value | Source |
|---|---|---|
| Follower | 6 STS3215 motors, 1/345 gearing | [11] |
| Leader | Mixed gearing. Shoulder pan motor is 1/191. Check the table per joint | [60], [61] |
| Encoder | 4096 ticks per turn in the Playground driver | [62] |
| One tick, computed | 0.0879 deg, or 0.00153 rad | [62] |
| Factory baud, STS | 1000000 | [21] |
| ID and baud storage | EEPROM. One setup is enough unless motors are reused | [56] |
| Finding the arm | USB serial number. It stays stable across reboots and replugs | [63] |
| Finding a camera | Linux: /dev/v4l/by-id path. macOS: an OpenCV index that can change | [64] |
| Firmware update | The official Feetech tool needs a Windows computer | [65] |
Faults
| Symptom | Suspect first | Source |
|---|---|---|
| Jitter or dropped packets | Power: a sagging supply or a missing shared ground. Wiring: long cables, poor connectors, star branches. Timing: the baud rate and the half-duplex direction switch | [35] |
| Power fault when several servos start | Startup transients | [57] |
| Communication errors under load | Thin, long or poorly contacting wire | [46] |
| No reply after a baud write | The connection dropped. Reconnect at the new rate | [55] |
| No reply on the old ID | The ID write worked. Use the new ID | [54] |
| A setting is lost after power off | The lock flag stayed at 1 during the write | [53] |
| Wrong position values | Byte order for the family. Read back a known position | [24] |
| ID, mode or protection changed unexpectedly | A write used the wrong memory table | [1] |
| A broadcast PING misbehaves | More than one servo on the bus | [26] |
| A commanded servo did not move, with no error | Sync and broadcast writes return no status. Read back | [9] |
| Corrupted status packets, DYNAMIXEL | An interrupt during the last byte | [37] |
Where the database is thin
- No guideline gives a maximum cable length or servo count for a TTL bus.
- No guideline requires or forbids termination on a TTL bus. The wiki sentence on termination is about complex RS-485 networks [47].
- No guideline gives a Feetech byte gap limit, a logic level, or a direction-switch method. The rows on these are DYNAMIXEL only.
- No guideline gives a Feetech sync-write frame length or a reply time, so this book gives no full-cycle time.
- No guideline gives USB latency or round-trip time for the SO-101 adapter.
- No guideline says what an STS3215 does at the moment torque turns on. The startup-transient guideline covers the power transient only [57].
- No guideline gives the current rating of the SO-101 kit supply.
- The Feetech rows rest on the maker's wiki, and the source licence row allows facts only.
Sources
Each guideline in this chapter with its source, the date it was read and the exact words of the source. Level: must means breaking it causes failure or harm, should is good practice, guide is a rule of thumb.
- Feetech SCS, SMS/STS and HLS memory tables are not interchangeable; a wrong persistent write can change ID, baud rate, mode or protection. Level: must. github.com 2026-11-08
- USB must not power the servo motors; motor power comes from an external regulated supply. Level: must. github.com 2026-11-08
- The debug board ground and the motor supply ground must share one common ground. Level: must. github.com 2026-11-08
- Connect only one servo and no load at first power-up. Level: must. github.com 2026-11-08
- Set each SO-101 motor ID with only that motor connected, and with no daisy chain. Level: must. raw.githubusercontent.com 2026-11-09“Make sure it's the only motor connected to the board, and that the motor itself is not yet daisy-chained to any other motor.”
- Add servos one at a time and reverify communication after each one. Level: should. github.com 2026-11-08
- Size the supply as the number of servos moving at once times the peak demand of each, with margin. Level: must. github.com 2026-11-08
- At 10 bits per byte, one Feetech byte takes 10 bit times; divide by the baud rate to size the bus budget. Level: should. github.com 2026-11-08
- Feetech broadcast and sync writes normally return no status, so they cannot confirm action by one servo. Level: must. github.com 2026-11-08
- Cut power before unplugging servos or changing wiring. Level: must. github.com 2026-11-08
- The SO-101 follower uses 6 STS3215 motors with 1/345 gearing. Level: guide. raw.githubusercontent.com 2026-11-09“The follower arm uses 6x STS3215 motors with 1/345 gearing.”
- Feetech FT-SCS uses 1 start bit, 8 data bits, 1 stop bit and no parity. Level: must. github.com 2026-11-08
- DYNAMIXEL uses half-duplex 8-bit asynchronous serial with 1 stop bit and no parity. Level: must. github.com 2026-11-08
- On a half-duplex bus only one device may transmit at a time, and all others must be in input mode. Level: must. github.com 2026-11-08
- A Feetech FT-SCS frame starts with two 0xFF bytes. Level: must. github.com 2026-11-08
- A DYNAMIXEL Protocol 2.0 packet starts with 0xFF 0xFF 0xFD 0x00. Level: must. github.com 2026-11-08
- The Feetech checksum is the bitwise inverse of the low byte of ID + Length + Instruction + Parameters. Level: must. github.com 2026-11-08
- Feetech FT-SCS IDs run 0 to 253; a separate broadcast ID sits above that range. Level: must. github.com 2026-11-08
- DYNAMIXEL Protocol 2.0 IDs run 0 to 252; a separate broadcast ID sits above that range. Level: must. github.com 2026-11-08
- A new DYNAMIXEL ships with ID 1. 1 Level: guide. github.com 2026-11-08
- Feetech SCS and STS servos leave the factory at 1000000 baud, SMS-protocol servos at 115200. Level: guide. github.com 2026-11-08
- STS register 6 stores a code 0 to 7, not the baud rate: 1000000 (0), 500000 (1), 250000 (2), 128000 (3), 115200 (4), 76800 (5), 57600 (6), 38400 (7). Level: must. github.com 2026-11-08
- On DYNAMIXEL models that use this control table, not all models, baud rate follows Baudrate = 2,000,000 / (Value + 1). Level: guide. github.com 2026-11-08
- Feetech two-byte values are low byte first on STS, SMS and HLS but high byte first on SCS and SCSCL; use the matching SDK layer. Level: must. github.com 2026-11-08
- A DYNAMIXEL instruction sent to the Broadcast ID returns no status packet, except Ping, Sync Read and Bulk Read. Level: guide. github.com 2026-11-08
- Feetech broadcast PING works only with a single servo on the bus. Level: must. github.com 2026-11-08
- Feetech SYNC WRITE updates several servos in one instruction and has higher real-time performance than REG WRITE plus ACTION. Level: should. github.com 2026-11-08
- DYNAMIXEL Sync Write needs the same address and data length for all devices and the packet ID 0xFE. Level: must. github.com 2026-11-08
- In a DYNAMIXEL Bulk Write each device ID may appear only once. Level: must. github.com 2026-11-08
- STS response status level 0 answers only READ and PING; 1 answers all instructions. Level: should. github.com 2026-11-08
- Status Return Level 0 answers only PING, 1 answers PING and READ, and 2 answers all instructions. Level: should. github.com 2026-11-08
- Register addresses differ across Feetech families: SMS address 7 is the response return delay, and the same STS address is reserved. Level: must. github.com 2026-11-08
- DYNAMIXEL return delay is 2 microseconds per unit, default 250 units (500 microseconds), maximum 508 microseconds; lower it to shorten bus time. Level: should. github.com 2026-11-08
- Keep the gap between bytes of a DYNAMIXEL instruction packet under 1.5 ms; above that the servo drops the packet and waits for a new header. 1.5 ms Level: must. github.com 2026-11-08
- For jitter or dropped packets, check supply droop, common ground, cable length, connectors, branch topology, baud rate and half-duplex direction timing. Level: should. github.com 2026-11-08
- Check the shift register empty flag, not the buffer ready flag, before switching from send to receive. Level: must. github.com 2026-11-08
- Disable interrupts around the last transmitted byte; an interrupt there can exceed the return delay and corrupt the status packet. Level: must. github.com 2026-11-08
- A UART controller needs a half-duplex converter to drive DYNAMIXEL. Level: must. github.com 2026-11-08
- The ROBOTIS TTL circuit is for 5 V or 5 V tolerant MCUs; use a level shifter on other MCUs. Level: must. github.com 2026-11-08
- For stable communication at high baud rates, lower the USB latency setting. Level: should. github.com 2026-11-08
- The DYNAMIXEL SDK default USB latency is 16 ms; it can be reduced for faster communication. 16 ms Level: guide. github.com 2026-11-08
- Every servo on one bus must have a unique ID, and all must share one baud rate. Level: must. github.com 2026-11-08
- A baud rate error below 3 percent does not affect UART communication, as ROBOTIS states. 3 % Level: guide. github.com 2026-11-08
- The vision policy in this project integrates joint-rate actions into position commands every 40 ms. Level: guide. raw.githubusercontent.com 2026-11-09“joint-position commands every 40 ms.”
- Estimate the serial command transport delay before fitting, and align command times to the measured rollout. Level: should. raw.githubusercontent.com 2026-11-09“Estimate and log the serial command transport delay ($t_1 - t_0$).”
- Thin, long or poorly contacting wires cause voltage drop and communication errors. Level: should. github.com 2026-11-08
- Avoid long star branches and loose connectors on the bus. Level: should. github.com 2026-11-08
- This guideline is held back: its source does not allow us to publish it yet.
- Do not infer signal or power pins from wire colour; follow the drawings. Level: must. github.com 2026-11-08
- Label the SO-101 leader and follower supplies, because they differ at 5 V and 12 V and must not be swapped. 5 and 12 V Level: must. docs.nvidia.com 2026-11-08
- The STS3215 7.4 V version is rated at 16.5 kg·cm stall torque at 6 V; the 12 V version is rated at 30 kg·cm. Level: guide. github.com 2026-11-08“The 12V version has a stall torque of 30kg.cm.”
- On DYNAMIXEL, a duplicate ID causes packet collision and network problems. Level: must. github.com 2026-11-08
- Clear the Feetech STS lock flag before changing EEPROM values and set it back after; with the lock at 1 a write works until power off, then is lost. Level: must. github.com 2026-11-08
- After a Feetech ID write the servo answers only on the new ID; use the new ID for the relock. Level: must. github.com 2026-11-08
- The connection drops as soon as an STS baud rate write succeeds; reconnect at the new rate before relocking. Level: must. github.com 2026-11-08
- SO-101 motor IDs and baud rate are stored in EEPROM, so one setup is enough unless motors are reused from another robot. Level: guide. raw.githubusercontent.com 2026-11-09“Since we will write these parameters in the non-volatile section of the motors' internal memory (EEPROM), we'll only need to do this once.”
- Multi-servo startup transients are a frequent power fault. Level: should. github.com 2026-11-08
- Calibrate SO-101 arms so leader and follower give the same position values in the same physical position: start with joints mid range, then move each through its full range. Level: must. raw.githubusercontent.com 2026-11-09“First you need to move the robot to the position where all joints are in the middle of their ranges. Then after pressing enter you have to move each joint through its full range of motion.”
- Calibrate each SO-101 before running a policy; another setup's released offsets do not calibrate your robot. Level: must. isaac-sim.github.io 2026-11-08“they do not calibrate another robot.”
- The SO-101 leader uses mixed gearing; its shoulder pan motor, for one, is geared 1/191, so check the table for each joint. Level: guide. raw.githubusercontent.com 2026-11-09“| Base / Shoulder Pan | 1 | 1 / 191 |”
- The SO-101 leader uses several gear ratios, while the follower uses 1/345 gearing. Level: guide. huggingface.co 2026-11-08
- The Playground SO-101 driver uses an STS3215 with 4096 ticks per turn. Level: guide. raw.githubusercontent.com 2026-11-09“MOTOR_MODEL = "sts3215" TICKS_PER_TURN = 4096”
- Identify SO-101 arms by USB serial number; it stays stable across reboots and replugs. Level: should. raw.githubusercontent.com 2026-11-09“**Arms** — identified by USB serial number, which is stable across reboots and replugs.”
- On macOS a camera is an OpenCV index that can change after a replug; on Linux use the stable /dev/v4l/by-id path. Level: should. raw.githubusercontent.com 2026-11-09“On Linux the camera value is a stable `/dev/v4l/by-id/...` path. On macOS it is an OpenCV index, which can reshuffle if you replug devices”
- Updating Feetech firmware through the official tool needs a Windows computer. Level: should. raw.githubusercontent.com 2026-11-09“Windows computer (Feetech software is only available for Windows)”