-
Notifications
You must be signed in to change notification settings - Fork 64
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
[cob_twist_controller] Investigate JLA constraints behavior #56
Comments
I think the main cause for this behavior is #57 |
#57 is not (necessarily) related to the observed behavior (i.e. constant offset/command). |
We have seen some "drift" on the cob4-1 torso (torso_2_joint) when doing tests related to Elmo-VelocityMode-JointLimits-Tests, i.e. rotating torso_3_joint towards its limit....
The "drift" might also be caused by the issue described in #65 |
Just for the record: Still the JLA-variants need to be investigated further...
Also, we were still running into the JointLimits in case JLA is used together with CA enabled when close to an obstacle....maybe the Priority order is not correct....I guess JLA should have higher priority than CA!
|
Needs to be investigated further, but here are some details I figured out so far:
On schunk_lwa4d with current JointState (see below), sending Zero-Twist results in a constant velocity command (see rqt_plot), TwistController conifg (see below):
joint_limits:
rviz screenshot:
rqt_plot screenshot:
From left to right, I swtched JLA_OFF, JLA_ON, JLA_MID, JLA_INEQ.
arm/twist_controller config:
@fmessmer FYI
The text was updated successfully, but these errors were encountered: