-
Notifications
You must be signed in to change notification settings - Fork 267
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
Switching between JTC and JGVC fails #34
Comments
log for Elmo: [ INFO] [1416563035.743507660]: Successfully switched to velocity_controllers abort6060#0, reason: General error [ERROR] [1416563037.757638778]: /u/fmw/git/care-o-bot/src/ros_canopen/ipa_canopen_master/src/pdo.cpp(270): Throw in function void ipa_canopen::PDOMapper::RPDO::sync() |
solved with blocking switch. see floweisshardt@7b0b44a |
* Add check if remote object already exists to avoid multiple objects with same target. * Renaming and changes to MasterNode * restrucutring for lifecycle support * changes to build * Add lifecycle to drivers, masters and add device manager * Add lifecycled operation canopen_core * Added non lifecycle stuff to canopen_core * Add lifecyle to canopen_base_driver * Add lifecycle to canopen_proxy_driver * restructured canopen_core for lifecycle support * restructured canopen_base_driver for lifecycle support * Restrucutured canopen_proxy_driver for lifecycle support * Restructured canopen_402_driver for lifecycle support * Add canopen_mock_slave add cia402 slave * add canopen_tests package for testing canopen stack * Disable linting for the moment and some foxy compat changes * Further changes for foxy compatability
Error description:
Switching from JTC to JGVC works, I can move sending velocities. Swithcing back to JTC does not work. controller manager says switching ok (JGVC stoppend and JTC running) but no movement is possible.
The state topic reports that the actual pos is static while the JTC tried to move setting the desired pos.
Occurance(s) (when? Which hardware? How often?):
always
cob4-2 arms
How to reproduce the error:
multiple calls to recover solve the error --> can move JTC again
The text was updated successfully, but these errors were encountered: