-
Notifications
You must be signed in to change notification settings - Fork 21
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
Strange accel override #3
Comments
Unfortunately I wouldn't know why it's set to The driver was written by @muhrix and colleagues during his time at Ocado and he no longer works there. He currently works for a company that either doens't let him work on OSS or makes it (very) difficult to do so. If |
@simonschmeisser: have you had any further feedback from your customer? |
I heard no further complaints but I'll ask them and report back here |
Thanks. Performance of |
@simonschmeisser thanks for the hint; I will give it a try on our setup. I also noticed the motions were rather un-smooth as you mention, but never put in the time to check why, and this could be it. |
I can confirm that accel is expressed as a percentage and has a default value of 100. There is essentially no upper limit on accel (up to 99999%) and putting in a value higher than 100% will cause the arm to attempt that acceleration. |
Ok. If we can come up with a better default, we could change the current value. |
staubli_val3_driver/staubli_val3_driver/val3/ros_server/pushMotion.pgx
Line 77 in 55b4fe6
sets the acceleration (deceleration) to 9999 if velocity override is activated. This is motivated by a reference to the manual and Val3's default value. However in said manual the acceleration is specified to be in percent, ie in the range of 100 to 0. 9999 is the default value for tcp velocity.
Our customer set this to 60 and obtained good results, 9999 was apparently very un-smooth and not visually pleasing
The text was updated successfully, but these errors were encountered: