mhubii

could you give me a helping hand @kweonhj and send me your script, so I can test this in simulation. Thank you :)

okay just had a look, can confirm this behavior. Will see what can be done

hi @kweonhj , here is an updated version, that computes inverse kinematics and sends a joint state next. This seems to work better. Let me know if this works for...

great! Happy to hear this worked. I do agree that this behavior is rather strange. Sometimes wonder whether there will be a replacement for Moveit at some point. There is...

hi @vazik01, will work on updating the documentation this week. There is documentation here: https://lbr-stack.readthedocs.io/en/latest/, but it is outdated. Thank you for raising the issue. Expect updated documentation this week....

I guess this depends on what is being launched. If the hardware interface is launched, then the control rate is set by the controller manager, e.g. https://github.com/KCL-BMEIS/lbr_fri_ros2_stack/blob/d1e70a7a1160ea2d3f29203b6ab83e2919292c29/lbr_bringup/config/lbr_controllers.yml#L3 Could you do...

indeed solves the issue. Reminder to update the readme https://github.com/KCL-BMEIS/lbr_fri_ros2_stack/tree/foxy/lbr_examples#admittance-control, once bringup was re-written

blocked by https://github.com/ros-controls/gz_ros2_control/issues/182

interactive marker nonreactive for moveit launches

hi @xlzhu0317. You can launch the system via: ```shell ros2 launch lbr_bringup bringup.launch.py model:=med14 sim:=false ctrl:=forward_lbr_torque_command_controller ``` You'll see a topic `/lbr/command/torque`. The corresponding message definition is here https://github.com/lbr-stack/lbr_fri_ros2_stack/blob/humble/lbr_fri_msgs/msg/LBRTorqueCommand.msg A...