Skip to content
Open
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/source/_toctree.yml
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@
- local: notebooks
title: Notebooks
- local: feetech
title: Updating Feetech Firmware
title: Feetech Troubleshooting and Firmware Update
Comment on lines 136 to +137
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sidebar title (“Feetech Troubleshooting and Firmware Update”) doesn’t match the page H1 (“Feetech Troubleshooting and Motor Firmware Update”). Please make these consistent to avoid confusion/search mismatches in the rendered docs navigation.

Copilot uses AI. Check for mistakes.
- local: damiao
title: Damiao Motors and CAN Bus
title: "Resources"
Expand Down
46 changes: 36 additions & 10 deletions docs/source/feetech.mdx
Original file line number Diff line number Diff line change
@@ -1,41 +1,67 @@
# Feetech Motor Firmware Update
# Feetech Troubleshooting and Motor Firmware Update

## Troubleshooting

### Position Overflow

If during calibration you encounter an error like this:
```bash
ValueError: Magnitude 2816 exceeds 2047 (max for sign_bit_index=11)
```

The firmware may be overflowing and returning incorrect position readings.

**Quick fix:** Unplug both the AC power and USB cable, then reconnect them. This should give you correct position readings again.
Comment on lines +13 to +15
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PR description mentions a specific diagnosis (homing offset + current position overflow beyond the [0, 4095] range after consecutive calibrations), but the doc here only says the firmware “may be overflowing”. Consider documenting the actual suspected mechanism and the expected valid position range so readers can verify they’re hitting the same issue (and distinguish it from other calibration failures).

Copilot uses AI. Check for mistakes.

If the issue persists, reset the positions of the motors:
1. Complete the first 4 steps of the motor firmware update process
2. Select the *Programming* tab
3. Move all joints to the middle of their range
4. Click *Offset*
<img
src="https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/lerobot/feetech_reset_offset.png"
alt="Feetech Offset Position"
/>
Copy link

Copilot AI Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The ordered list ends immediately before the block tag without a blank line/indentation, which can break list rendering in MDX/Markdown parsers. Align this with the pattern used elsewhere in the docs (e.g., docs/source/so100.mdx inserts a blank line before images after list items) by adding a blank line and/or indenting the image block under the relevant list item.

Copilot uses AI. Check for mistakes.


## Feetech Motor Firmware Update

This tutorial guides you through updating the firmware of Feetech motors using the official Feetech software.

## Prerequisites
### Prerequisites

- Windows computer (Feetech software is only available for Windows)
- Feetech motor control board
- USB cable to connect the control board to your computer
- Feetech motors connected to the control board

## Step 1: Download Feetech Software
### Step 1: Download Feetech Software

1. Visit the official Feetech software download page: [https://www.feetechrc.com/software.html](https://www.feetechrc.com/software.html)
2. Download the latest version of the Feetech debugging software (FD)
3. Install the software on your Windows computer

## Step 2: Hardware Setup
### Step 2: Hardware Setup

1. Connect your Feetech motors to the motor control board
2. Connect the motor control board to your Windows computer via USB cable
3. Ensure power is supplied to the motors

## Step 3: Configure Connection
### Step 3: Configure Connection

1. Launch the Feetech debugging software
2. Select the correct COM port from the port dropdown menu
- If unsure which port to use, check Windows Device Manager under "Ports (COM & LPT)"
3. Set the appropriate baud rate (typically 1000000 for most Feetech motors)
4. Click "Open" to establish communication with the control board

## Step 4: Scan for Motors
### Step 4: Scan for Motors

1. Once connected, click the "Search" button to detect all connected motors
2. The software will automatically discover and list all motors on the bus
3. Each motor will appear with its ID number

## Step 5: Update Firmware
### Step 5: Update Firmware

For each motor you want to update:

Expand All @@ -46,12 +72,12 @@ For each motor you want to update:
4. **Click on Upgrade button**:
- The update progress will be displayed

## Step 6: Verify Update
### Step 6: Verify Update

1. After the update completes, the software should automatically refresh the motor information
2. Verify that the firmware version has been updated to the expected version

## Important Notes
### Important Notes

⚠️ **Warning**: Do not disconnect power or USB during firmware updates, it will potentially brick the motor.

Expand All @@ -61,7 +87,7 @@ For debugging purposes only, you can use the open-source Feetech Debug Tool:

- **Repository**: [FT_SCServo_Debug_Qt](https://github.com/CarolinePascal/FT_SCServo_Debug_Qt/tree/fix/port-search-timer)

### Installation Instructions
#### Installation Instructions

Follow the instructions in the repository to install the tool, for Ubuntu you can directly install it, for MacOS you need to build it from source.

Expand Down
Loading