Update acceleration limits for robot configs

[pac48]

See #194 for more detail. I think some discussion on how to manage different sets of joint_limits.yaml could be beneficial.

[sjahr]

Do you mind adding a comment why has_jerk_limits: false for all joints in a file called joint_limits_jerk_limited? I think that might be confusing otherwise

[pac48]

@sjahr That is a good point. The problem is that joint_limits.yaml was created before MoveIt supported jerk limits. So the acceleration limits were intentionally low to implicitly enforce jerk constraints. Now that there is some support for jerk constraints, it is reasonable to remove the artificially low acceleration limits in some configurations. The idea was to make a new config with the actual hardware acceleration values. I guess the name is not very clear. Do you have any suggestions? There is some discussion in this issue: #194

[pac48]

Do you mind adding a comment why has_jerk_limits: false for all joints in a file called joint_limits_jerk_limited? I think that might be confusing otherwise

@sjahr What if we call it hard_joint_limits.yaml It looks like this is already a convention in here

[sjahr]

👍 Yes, I like that. Let's do it

[sea-bass]

Looks good.

So the plan is to use this new file for our servo examples going forward, then?

[pac48]

Looks good.

So the plan is to use this new file for our servo examples going forward, then?

Yes, we can use these limits in servo for better control.