Skip to content

Commit 08a06b4

Browse files
jcoleharrisonpre-commit-ci[bot]aliberts
authored
add docs details for resolving firmware update issues (huggingface#627)
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: Simon Alibert <[email protected]>
1 parent 01a5cd6 commit 08a06b4

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

examples/7_get_started_with_real_robot.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -292,6 +292,11 @@ Steps:
292292
- Scan for devices. All 12 motors should appear.
293293
- Select the motors one by one and move the arm. Check that the graphical indicator near the top right shows the movement.
294294

295+
** There is a common issue with the Dynamixel XL430-W250 motors where the motors become undiscoverable after upgrading their firmware from Mac and Windows Dynamixel Wizard2 applications. When this occurs, it is required to do a firmware recovery (Select `DYNAMIXEL Firmware Recovery` and follow the prompts). There are two known workarounds to conduct this firmware reset:
296+
1) Install the Dynamixel Wizard on a linux machine and complete the firmware recovery
297+
2) Use the Dynamixel U2D2 in order to perform the reset with Windows or Mac. This U2D2 can be purchased [here](https://www.robotis.us/u2d2/).
298+
For either solution, open DYNAMIXEL Wizard 2.0 and select the appropriate port. You will likely be unable to see the motor in the GUI at this time. Select `Firmware Recovery`, carefully choose the correct model, and wait for the process to complete. Finally, re-scan to confirm the firmware recovery was successful.
299+
295300
**Read and Write with DynamixelMotorsBus**
296301

297302
To get familiar with how `DynamixelMotorsBus` communicates with the motors, you can start by reading data from them. Copy past this code in the same interactive python session:

0 commit comments

Comments
 (0)