Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable the rising attribute in urdf calibration tag #93

Open
Tacha-S opened this issue Dec 6, 2024 · 2 comments · May be fixed by #96
Open

Enable the rising attribute in urdf calibration tag #93

Tacha-S opened this issue Dec 6, 2024 · 2 comments · May be fixed by #96

Comments

@Tacha-S
Copy link

Tacha-S commented Dec 6, 2024

URDF includes an attribute called rising,
which allows specifying the offset between the joint position in the URDF and the motor position.
I want to enable this functionality to be reflected in Dynamixel as well.

@Tacha-S Tacha-S linked a pull request Dec 10, 2024 that will close this issue
@ijnek
Copy link
Member

ijnek commented Jan 15, 2025

I have never used the tag in URDF, but my understanding from reading up is that it is not a way to specify an offset for joint values to account, but rather seems like the rising and falling attributes mark specific sensor-triggered positions to aid in the calibration process.

One way to modify this is directly on the motor, by using dynamixel wizard 2.0 and modifying the Homing Offset per motor. Have you tried that?

@Tacha-S
Copy link
Author

Tacha-S commented Jan 15, 2025

I believe using the Dynamixel Wizard for setup is very convenient when dealing with individual motors.
However, performing setup with the Dynamixel Wizard for a system or robot composed of multiple components is not ideal. This is because it requires a GUI to be prepared, and the calibration results must be reflected manually.

In the robot_calibration package, if the calibration only involves the joint's rotation direction, the calibration results can be applied by modifying the rising in the calibration tag without changing the origin in the URDF.
Based on this approach, I introduced offsets using rising.

Considering that an offset is applied to the trigger point (where the Dynamixel encoder reads 0), using rising does not seem unreasonable to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants