-
Notifications
You must be signed in to change notification settings - Fork 8
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
How to add button states? #3
Comments
Hi @CarlDegio , the cleanest and I think most efficient way of doing so is to set up a GPIO component in If you need some help to do it, juste create a PR and I can give you a hand. |
Thank you! I just know the GPIO type of ros2_control. I will try it and seek for help if there are problems。 |
I add GPIO states successfully. But I only have Omega.3 device, which only has one button, so I only add id 0 button in code. My change at: #4 |
FYI, this code has been added to the main branch (humble), see PR #15. |
I want to use Omega button states to switch movement boundary. I tried some way but still don't work. I would like to ask if you have a better method.
Attached my attempts:
Initially, I want to put button states under current ros2 control framework by treating it as fourth joint. Add a button joint in urdf, and add it in
fd_controllers.yaml
. Read hardware data infd_effort_hi.cpp
. Publish button joint position in state interface ofee_pose_broadcaster.cpp
. However, the problem occured at load joints. [ERROR] joint 'button' don't have effort command. I found changingfd.r2c_hardware.xacro
may be helpful. But this could destroy the command dimension so I decide to seek another way. But in the end this might be the way to get close to the truthI design another node to read button data. But the function dhdOpen() seems can't be executed twice.
The text was updated successfully, but these errors were encountered: