-
Notifications
You must be signed in to change notification settings - Fork 69
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
Solution to "Wait for device to boot" with kinco motors, not with zeroerr motors. #334
Comments
Also, I use with the ros2 differential drive controller, but it is not stable. I am confused and do not know how to solve it. |
Streamline your eRob integration with our latest open-source software, drivers, and examples now available on GitHub: github.com/ZeroErrControl |
Thanks for the quick reply, but I haven't seen the exact code related to ros2_canopen, I've tried many times before with ros2_canopen, but it didn't work. Could you please help give a few examples based on ros2_control? Thanks so much! |
Due to the instability of the official ROS2_CANopen open-source code, related examples are still under development and testing. Thank you for your response! Please follow our GitHub account for updates, and we’ll notify you as soon as there’s progress. |
Describe the bug
I get the above error when I use a motor from kinco. With the help of friends, I learnt that this was due to an eds file issue. I need to modify the eds file so that the value in the file is just the same as the value returned by the kinco motor.
But with zeroerr motor, the above methods do not solve the problem. Motor not enabled. Maybe there's a problem with the motor's registers.
Do you have the same problem? Could you please help me?
Setup:
The text was updated successfully, but these errors were encountered: