-
Notifications
You must be signed in to change notification settings - Fork 217
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
Added calculation of joint velocities. #95
base: melodic-devel
Are you sure you want to change the base?
Conversation
Thanks for the PR. Can you say anything about the (perceived) 'quality' of the velocities that come out of this? In my experience dx/dt is really not a very good way to derive joint velocities and can result in noisy data. I'm not opposed in general to adding this, but I think we need to be very careful with adding derived data to |
There is of course some noise but I assume velocities directly from robots which have that capability would have some noise as well. It was usefull for debugging for me. |
You could accomplish the same with a separate debugging node outside of the hardware interface and then you could choose the derivative approximation that best suits your needs/application. I agree with @gavanderhoorn that this could easily cause confusion if published directly. |
To add my two cents: |
I agree. We could make this configurable by the user, with a default |
The actual joint velocities are available within the KRC via a combination of |
It would indeed make sense to use values calculated/derived by the controller if possible. That would be preferable over |
@hartmanndennis: would you be interested in making the changes to read the joint velocity from the RSI datastream? |
These are KRL variables and not RSI elements like DEF_RIst. I don't know if it's easily or at all possible to send KRL variables with RSI while doing motion with RSI_MOVECORR. But I'm not an RSI expert. |
I seem to remember joint velocities being available through the RSI function blocks as well. But I'm not sure, would have to check the manual again. |
Hm, no: Thought: what about making RSI do the |
The differentiation object should work here |
Is this with the |
Sorry for being unclear, this is using this PR, so calculated on ROS side by simple dx/dt. |
Ok. would you be up for trying the |
I'm not currently interested to dive into RSI stuff, which seems to be not that trivial. |
Ok, fair enough. It would be good if we could use We'd just have to be careful with |
Btw: I believe what you're seeing in those plots is exactly why using a real-time OS with deterministic scheduling is so important for RSI (and a host of other tasks). |
Hello @hartmanndennis and @gavanderhoorn. I am reading this chat of the Pull Request. I want to ask if it is possible to appy velocity control commands with KR C4, KSS v8.3.43 and RSI v3.2.0. I am controlling this robot and i am asking what are the possible commands that the RSI can receive? Velocity Control, position Control, Cartesian velocity Control? Thanks in Advance |
With this PR computed joint velocities are published by JointStatePublisher and can be viewed with rqt plot for example.