-
Notifications
You must be signed in to change notification settings - Fork 219
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
Does the rsi_hw_interface driver modify the target joint positions? #151
Comments
No.
Neither. This may sound pedantic, but it's important to be as precise as possible when talking about this. The Which "entity" writes into Which controller that would be is up to you. If you configure it to be a |
Closing this as it's a question and not an actionable issue or defect. |
Note:
there is no assumption about the period in the |
Thanks a lot for the extremely fast and helpful answers. That helps me a lot understanding how it all works |
Hello everyone,
we want to use the kuka_experimental package to control a KR16 R1610 using ROS. I have a question regarding the functionality of the rsi_hw_interface.
Please correct me if I am wrong: The RSI interface is quite a low level interface to the robot so the Kuka controller does not do any trajectroy planning while RSI is active and simply moves the joints to the target joint positions received every 4 ms. So the trajactory (and velocity and acceleration) planning has to be done on the ROS side. Are the trajectories planned by ROS (e.g. Moveit) parsed and streamed directly via the RSI interface to the robot or are they modified by the rsi_hw_interface driver to account for joint movements too big for the 4 ms timeframe?
Thanks a lot
The text was updated successfully, but these errors were encountered: