-
Notifications
You must be signed in to change notification settings - Fork 50
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
⚠️ Compliant control modes feedback cycle #236
Comments
What likely happens is the following:
This issue also relates to #226. Further details (edit): If any of the
When no one sends commands yet, the commands remain lbr_fri_ros2_stack/lbr_ros2_control/src/controllers/lbr_wrench_command_controller.cpp Line 52 in 58ff69a
Hi @Hydran00, @anselmo-parnada. The issue is explained above. Thank you again for reporting. Until this is fixed, I would recommend not to use compliant control modes in combination with this stack. |
(cherry picked from commit 779817b)
Still not fully fixed as control mode not always detected correctly (somehow the correct control mode only becomes available in
As indicated also in their default demos: $ ./LBRJointSineOverlayApp
LBRJointSineOverlayClient initialized:
joint mask: 0x8
frequency (Hz): 0.250000
amplitude (rad): 0.040000
filterCoeff: 0.990000
LBRiiwaClient state changed from 0 to 1
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 1 to 2
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 2 to 3
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 3 to 4
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 4 to 2
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 2 to 0
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
martin@rvim-sie-stack:/tmp/fri/build$ ^C
$ ./LBRWrenchSineOverlayApp
Enter LBRWrenchSineOverlay Client Application
LBRWrenchSineOverlayClient initialized:
frequency (Hz): X = 0.250000, Y = 0.250000
amplitude (N): X = 5.000000, Y = 5.000000
LBRiiwaClient state changed from 0 to 1
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 1 to 2
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 2 to 3
control mode: 0 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2
LBRiiwaClient state changed from 3 to 4
control mode: 1 reminder: POSITION_CONTROL_MODE = 0, CART_IMP_CONTROL_MODE = 1, JOINT_IMP_CONTROL_MODE = 2 |
(cherry picked from commit 0e6f076)
control mode only available in commanding active (#236)
this issue is now fixed on the |
As reported in #232, the robot drifts / executes strange motions / disconnects. The source for this error is currently unclear. This behavior can be observed in
humble-2.1.2
andhumble-2.2.0
.To replicate:
CARTESIAN_IMPEDANCE_CONTOL
modeWRENCH
ros2 launch lbr_bringup hardware.launch.py model:=med7 ctrl:=lbr_wrench_command_controller
open_loop: false
The text was updated successfully, but these errors were encountered: