Microduck Robot●microduck-robot.com
Tools

Bus servo tool

Build, check and understand Feetech bus packets.

Configure a command

254 broadcasts to all servos. Ordinary broadcast commands do not reply; Sync read is the exception.
Enter 0–359.9° for a single turn. For signed or multi-turn targets, edit the register value instead.

Packet

Format and checksum valid

Protocol responses only. No real hardware is connected.

Python / Arduino code

            
Virtual bus and replies
    Received an unexpected reply?

    Build and inspect Feetech bus transactions

    Use the packet builder and virtual bus to understand requests and replies before working with a real serial connection. No physical servo is connected by this page.

    Models in the virtual bus

    • Feetech STS3215
    • Feetech STS3250
    • Feetech HD1910M

    Rules version: 2026-11-12.2

    Choose a model and packet direction

    Select the servo model, instruction, target ID and register. Values follow the register size and signed representation. A command instruction and a status error share packet positions, so choose the correct direction when decoding pasted hexadecimal bytes.

    Follow a transaction

    1. Build a request and inspect its header, ID, length, parameters and checksum.
    2. Send it to the virtual bus or paste a request with its matching replies into the transaction recorder.
    3. Review checksum, response IDs, data length and servo status before interpreting register values.

    Code and local records

    Copy packet bytes or Python/Arduino examples. Export request/reply records as JSON or CSV and import them for another inspection. Voltage, temperature and encoder-position conversions use the register context; other values remain raw.

    Use simulation results in context

    Virtual acknowledgements do not prove that a real servo answered or accepted a write. Match supply levels, half-duplex TTL wiring, baud rate and model documentation separately. The browser does not execute the exported hardware commands or upload packet records.

    Complete request-and-reply cases

    Inspect fixed SDK-shaped requests and explicitly virtual replies. Download the supported bus-log JSON or CSV to check them again; these are not hardware captures and nothing is transmitted.

    Offline configuration checks do not verify physical hardware or safety. These synthetic reference cases are separate from the settings above. Import an example to check its inputs again; a saved verdict is not trusted.

    Decode values in the matching READ context

    What do 00 08, 4A and 1F mean in these replies?

    Version baseline: Microduck bus rules 2026-11-12.2 · Feetech SDK 64922cda46e56b21b8c1d9e830d936a1941645ae · Register-table baseline LeRobot 0.6.1, as recorded by src/servo-tool/data.json

    Inputs and steps

    Virtual STS3215 ID 1 replies match READ requests for registers 56, 62 and 63. Payloads are 00 08, 4A and 1F; log times are 0, 10 and 20 ms.

    1. Pair each reply with its request, ID, byte count and checksum.
    2. Read position little-endian: 00 08 is 2048; convert 2048 / 4096 × 360.
    3. Use the register units for 74 / 10 V and 31 °C.

    Reference check result

    No known configuration conflict

    The offline report finds no known conflict and displays 180°, 7.4 V and 31 °C for these virtual data.

    Inspect inputs and reference JSON
    {
      "inputs": {
        "records": [
          {
            "request": "FF FF 01 04 02 38 02 BE",
            "responses": [
              "FF FF 01 04 00 00 08 F2"
            ],
            "timeMs": 0,
            "origin": "virtual",
            "model": "sts3215"
          },
          {
            "request": "FF FF 01 04 02 3E 01 B9",
            "responses": [
              "FF FF 01 03 00 4A B1"
            ],
            "timeMs": 10,
            "origin": "virtual",
            "model": "sts3215"
          },
          {
            "request": "FF FF 01 04 02 3F 01 B8",
            "responses": [
              "FF FF 01 03 00 1F DC"
            ],
            "timeMs": 20,
            "origin": "virtual",
            "model": "sts3215"
          }
        ]
      },
      "status": "no_known_conflict",
      "findings": [],
      "outputs": {
        "pairs": [
          {
            "index": 0,
            "timeMs": 0,
            "model": "sts3215",
            "id": 1,
            "error": 0,
            "request": "FF FF 01 04 02 38 02 BE",
            "response": "FF FF 01 04 00 00 08 F2",
            "address": 56,
            "values": [
              {
                "address": 56,
                "name": "Present_Position",
                "raw": 2048,
                "value": 180,
                "unit": "°"
              }
            ]
          },
          {
            "index": 1,
            "timeMs": 10,
            "model": "sts3215",
            "id": 1,
            "error": 0,
            "request": "FF FF 01 04 02 3E 01 B9",
            "response": "FF FF 01 03 00 4A B1",
            "address": 62,
            "values": [
              {
                "address": 62,
                "name": "Present_Voltage",
                "raw": 74,
                "value": 7.4,
                "unit": "V"
              }
            ]
          },
          {
            "index": 2,
            "timeMs": 20,
            "model": "sts3215",
            "id": 1,
            "error": 0,
            "request": "FF FF 01 04 02 3F 01 B8",
            "response": "FF FF 01 03 00 1F DC",
            "address": 63,
            "values": [
              {
                "address": 63,
                "name": "Present_Temperature",
                "raw": 31,
                "value": 31,
                "unit": "°C"
              }
            ]
          }
        ],
        "pairing": "declared-request-response",
        "units": "Only voltage, temperature and encoder-position conversions are established here; other registers remain raw."
      }
    }
    

    What this case does not establish

    • 180° is an encoder-angle conversion, not a calibrated SO-101 joint angle or verified physical pose.
    • This STS3215 example does not establish other model/firmware behavior, broadcast PING support or conversions for raw-only registers.

    Reference prepared:

    Specification sources

    The links below retain the technical sources’ original titles. Read each version and review date with the case assumptions.

    Reject a reply with a bad checksum

    Can a plausible payload still be rejected?

    Version baseline: Microduck bus rules 2026-11-12.2 · Feetech SDK 64922cda46e56b21b8c1d9e830d936a1941645ae · Register-table baseline LeRobot 0.6.1, as recorded by src/servo-tool/data.json

    Inputs and steps

    The virtual READ-position reply ends in F3 instead of the known reference checksum F2; its payload still reads 00 08.

    1. Keep the request and reply directions separate.
    2. Check the complete reply before converting its payload.
    3. Replace it with the separately authored valid reference reply and check again.

    Reference check result

    Cannot use this configuration

    The report is blocked: the reply is invalid and no valid reply remains for ID 1. No position value is produced.

    Inspect inputs and reference JSON
    {
      "inputs": {
        "records": [
          {
            "request": "FF FF 01 04 02 38 02 BE",
            "responses": [
              "FF FF 01 04 00 00 08 F3"
            ],
            "timeMs": 0,
            "origin": "virtual",
            "model": "sts3215"
          }
        ]
      },
      "status": "blocked",
      "findings": [
        {
          "code": "bad_reply",
          "severity": "blocked",
          "fieldPath": "records",
          "messageKey": "rxBad",
          "details": {
            "index": 1
          },
          "sourceRef": null
        },
        {
          "code": "missing_reply",
          "severity": "needs_review",
          "fieldPath": "records",
          "messageKey": "missingReply",
          "details": {
            "index": 1
          },
          "sourceRef": null
        }
      ],
      "outputs": {
        "pairs": [],
        "pairing": "declared-request-response",
        "units": "Only voltage, temperature and encoder-position conversions are established here; other registers remain raw."
      }
    }
    

    Adjust and check again

    The known virtual reference ends in F2 and decodes to 180°. This demonstrates parsing, not a repaired wire or a recovered servo.

    No known configuration conflict

    Inspect the adjusted reference JSON
    {
      "inputs": {
        "records": [
          {
            "request": "FF FF 01 04 02 38 02 BE",
            "responses": [
              "FF FF 01 04 00 00 08 F2"
            ],
            "timeMs": 0,
            "origin": "virtual",
            "model": "sts3215"
          }
        ]
      },
      "status": "no_known_conflict",
      "findings": [],
      "outputs": {
        "pairs": [
          {
            "index": 0,
            "timeMs": 0,
            "model": "sts3215",
            "id": 1,
            "error": 0,
            "request": "FF FF 01 04 02 38 02 BE",
            "response": "FF FF 01 04 00 00 08 F2",
            "address": 56,
            "values": [
              {
                "address": 56,
                "name": "Present_Position",
                "raw": 2048,
                "value": 180,
                "unit": "°"
              }
            ]
          }
        ],
        "pairing": "declared-request-response",
        "units": "Only voltage, temperature and encoder-position conversions are established here; other registers remain raw."
      }
    }
    

    What this case does not establish

    • For real traffic, capture a fresh reply and diagnose integrity; do not bless unknown bytes by merely recalculating their checksum.
    • The downloadable bad log is valid as a log file; its packet remains invalid.

    Reference prepared:

    Specification sources

    The links below retain the technical sources’ original titles. Read each version and review date with the case assumptions.

    A status error suppresses physical-unit output

    Does a valid checksum make a status-error reply usable?

    Version baseline: Microduck bus rules 2026-11-12.2 · Feetech SDK 64922cda46e56b21b8c1d9e830d936a1941645ae · Register-table baseline LeRobot 0.6.1, as recorded by src/servo-tool/data.json

    Inputs and steps

    A virtual register-63 reply has error byte 0x04 and payload 1F, with a valid checksum.

    1. Validate the frame, then inspect its status-error byte.
    2. Keep the error visible; do not turn payload 1F into an accepted temperature.
    3. Compare with a separate status-0 reference reply.

    Reference check result

    Needs review

    The report needs review and produces no converted temperature while the error byte is 0x04.

    Inspect inputs and reference JSON
    {
      "inputs": {
        "records": [
          {
            "request": "FF FF 01 04 02 3F 01 B8",
            "responses": [
              "FF FF 01 03 04 1F D8"
            ],
            "timeMs": 0,
            "origin": "virtual",
            "model": "sts3215"
          }
        ]
      },
      "status": "needs_review",
      "findings": [
        {
          "code": "servo_status",
          "severity": "needs_review",
          "fieldPath": "records",
          "messageKey": "servoError",
          "details": {
            "id": 1,
            "code": "0x4"
          },
          "sourceRef": null
        }
      ],
      "outputs": {
        "pairs": [
          {
            "index": 0,
            "timeMs": 0,
            "model": "sts3215",
            "id": 1,
            "error": 4,
            "request": "FF FF 01 04 02 3F 01 B8",
            "response": "FF FF 01 03 04 1F D8",
            "address": 63,
            "values": []
          }
        ],
        "pairing": "declared-request-response",
        "units": "Only voltage, temperature and encoder-position conversions are established here; other registers remain raw."
      }
    }
    

    Adjust and check again

    The synthetic status-0 packet yields 31 °C and no known packet conflict. Only the reference bytes changed; no motor was reset or tested.

    No known configuration conflict

    Inspect the adjusted reference JSON
    {
      "inputs": {
        "records": [
          {
            "request": "FF FF 01 04 02 3F 01 B8",
            "responses": [
              "FF FF 01 03 00 1F DC"
            ],
            "timeMs": 0,
            "origin": "virtual",
            "model": "sts3215"
          }
        ]
      },
      "status": "no_known_conflict",
      "findings": [],
      "outputs": {
        "pairs": [
          {
            "index": 0,
            "timeMs": 0,
            "model": "sts3215",
            "id": 1,
            "error": 0,
            "request": "FF FF 01 04 02 3F 01 B8",
            "response": "FF FF 01 03 00 1F DC",
            "address": 63,
            "values": [
              {
                "address": 63,
                "name": "Present_Temperature",
                "raw": 31,
                "value": 31,
                "unit": "°C"
              }
            ]
          }
        ],
        "pairing": "declared-request-response",
        "units": "Only voltage, temperature and encoder-position conversions are established here; other registers remain raw."
      }
    }
    

    What this case does not establish

    • 0x04 is the overheat flag in this STS profile; this virtual packet is not evidence that a real servo overheated.
    • A status-0 reference does not prove physical recovery or resolve model-specific broadcast behavior.

    Reference prepared:

    Specification sources

    The links below retain the technical sources’ original titles. Read each version and review date with the case assumptions.

    Contact us