-
Notifications
You must be signed in to change notification settings - Fork 52
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
Having problems with humble no plan execution #4
Comments
Hi @FrGe2016, Unfortunately, this ros2_RobotSimulation repository works with ROS2 Foxy, and not for ROS2 Humble (the ros2_control and ros2_controllers of both versions are different, and that is the main reason why it won't work). As an example of components that change from one version to the other, ROS2 Humble Gazebo + MoveIt!2 simulations require the {use_sim_time:= True} parameter to be assigned, and the joint_state_publisher in Foxy is converted to joint_state_broadcaster in Humble. However, I am planning to upload the ROS2 Humble packages soon. Best regards, |
Thanks for the reply. I lost many hours trying to make many exemples found
on the internet work with humble + gazebo + moveit2. Please let me know
when your new package will be uploaded. By then, i will work on other parts
of my custom made robot.
Regards Francois
Le mar. 28 févr. 2023, à 04 h 29, Mikel Bueno Viso ***@***.***>
a écrit :
… Hi @FrGe2016 <https://github.com/FrGe2016>,
Unfortunately, this ros2_RobotSimulation repository works with ROS2 Foxy,
and not for ROS2 Humble (the ros2_control and ros2_controllers of both
versions are different, and that is the main reason why it won't work).
As an example of components that change from one version to the other,
ROS2 Humble Gazebo + MoveIt!2 simulations require the {use_sim_time:= True}
parameter to be assigned, and the joint_state_publisher in Foxy is
converted to joint_state_broadcaster in Humble.
However, I am planning to upload the ROS2 Humble packages soon.
Best regards,
Mikel
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEARAMJVNOIJUCYQCLQBV73WZXAOXANCNFSM6AAAAAAVBKLWTQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@MikelBueno Thanks for your work and effort! An example with moveit2 and gazebo would also help me a lot! Can you tell me why you chose Gazebo over the new Ignition simulation package? |
I have always worked with gazebo classic ( gazebo 11 actualy) and most of
the ROS2 tutorial use gazebo .
I dont remember how i finished with the gazebo version that i have.
I explain. I upgrades from Ubuntu 22 to Ubuntu 20
I first installed and verified a few personal very specific ROS 1
packages in a Neotic Docker.
I then had to remove all previous visions of ROS1 and ROS2. I
never namely removed gazebo in the process. ( but i could have been done
somehow)
I then installed ROS2 humble desktop from apt.
It took me quite a while to convince my self to switch ROS2 with a
significant learning curve.
I have been waiting for enough packges and tutorials to be available and
bug free.
I just learned that a new gazebo existed quit recently.
To tell the truth, I did not came in my mind to change to the new gazebo
"garden".
Is there any recommendation in this way.
What is the futur of gazebo classic ? ( any phase out planned ? )
What is the impact of the transition to the new version
- stability of the product
- availlibility of tutorials and support
- retrocompatibility with old models
- importance of the learning
Any advantages ?
- performances
- new functions ?
Le ven. 3 mars 2023, à 04 h 30, Johannes Biermann ***@***.***>
a écrit :
… @MikelBueno <https://github.com/MikelBueno> Thanks for your work and
effort! An example with moveit2 and gazebo would also help me a lot!
Can you tell me why you chose Gazebo over the new Ignition simulation
package?
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEARAMMCBUQBQ54J7UJTIKLW2G22DANCNFSM6AAAAAAVBKLWTQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for your comments :). First of all, I am happy to share that I have just uploaded the ROS2 Humble repository for ros2_RobotSimulation. @FrGe2016 I would really appreciate it if you could test some of the packages and confirm they are working on your PC (I have uploaded the simplest set-up instructions to the README.md file as well). That would help me a lot to find some bugs in the code or documentation. With regard to your question @bi3ri, I come from ROS1 and I have always used Gazebo, and that is the main reason why I still work with it. When something works, that's a good reason to continue using it :). But yes, you're right, it seems that Ignition will replace Gazebo in the future, therefore I might start testing some stuff with it (I still feel there is a lack of ROS2-Ignition documentation)... But for the moment, I will stick to Gazebo for ros2_RobotSimulation. Best regards, |
Hi Mikel I will try the package (starting today but not necessarily ending) I will simply document the problems that apear ( not trying to solve them unless a solution is obvious and do not involve C++programming) First the package build ros2_action fails |
Very interesting results of my first tests ( i will need the ros2_action to go further ) ros2 launch cr35ia_ros2_moveit2 cr35ia.launch.py
ros2 launch panda_ros2_moveit2 panda.launch.py
ros2 launch irb1200_ros2_moveit2 irb1200.launch.py ok for the execution |
Hello, @MikelBueno, |
Fixed!
Le ven. 9 juin 2023, à 16 h 11, Sungsoo Park ***@***.***> a
écrit :
… Hello, @MikelBueno <https://github.com/MikelBueno>,
Sorry for interruption. I also got stuck on ROS 2 Humble with issue #11
<#11> .
Could you confirm it and what's the problem on it? Thanks.
—
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEARAMOBR4Z3HTIGFUEHRJTXKN7OZANCNFSM6AAAAAAVBKLWTQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi
I have installed the pakages using the various humble branches for all of them.
Unfortunately after the plan has been made nothing is happening when i try to execute. I have the following messages. with
ros2 launch panda_ros2_moveit2 original.panda.launch.py
[move_group-11] [INFO] [1676858740.016299549] [moveit_move_group_default_capabilities.move_action_capability]: Motion plan was computed successfully.
[rviz2-12] [INFO] [1676858740.016713319] [move_group_interface]: Planning request complete!
[rviz2-12] [INFO] [1676858740.052927755] [move_group_interface]: time taken to generate plan: 0.0168374 seconds
[move_group-11] [INFO] [1676858742.558244929] [moveit_move_group_default_capabilities.execute_trajectory_action_capability]: Received goal request
[move_group-11] [INFO] [1676858742.558383129] [moveit_move_group_default_capabilities.execute_trajectory_action_capability]: Execution request received
[move_group-11] [INFO] [1676858742.558423099] [moveit.plugins.moveit_simple_controller_manager]: Returned 3 controllers in list
[move_group-11] [INFO] [1676858742.558447790] [moveit.plugins.moveit_simple_controller_manager]: Returned 3 controllers in list
[move_group-11] [INFO] [1676858742.558531070] [moveit_ros.trajectory_execution_manager]: Validating trajectory with allowed_start_tolerance 0.01
[rviz2-12] [INFO] [1676858742.558380164] [move_group_interface]: Execute request accepted
[move_group-11] [INFO] [1676858743.558678868] [moveit_ros.current_state_monitor]: Didn't received robot state (joint angles) with recent timestamp within 1.000000 seconds.
[move_group-11] Check clock synchronization if your are running ROS across multiple machines!
[move_group-11] [WARN] [1676858743.558720377] [moveit_ros.trajectory_execution_manager]: Failed to validate trajectory: couldn't receive full current joint state within 1s
[move_group-11] [INFO] [1676858743.558759820] [moveit_move_group_default_capabilities.execute_trajectory_action_capability]: Execution completed: ABORTED
[rviz2-12] [INFO] [1676858743.559199775] [move_group_interface]: Execute request aborted
[rviz2-12] [ERROR] [1676858743.659235852] [move_group_interface]: MoveGroupInterface::execute() failed or timeout reached
I have made the changes proposed in that post moveit/moveit2#1480
but the i get a new problem
[rviz2-12] [INFO] [1676859524.497266606] [move_group_interface]: Planning request accepted
[move_group-11] [INFO] [1676859524.497296263] [moveit_move_group_default_capabilities.move_action_capability]: executing..
[move_group-11] [WARN] [1676859525.598361714] [moveit_ros.current_state_monitor]: No state update received within 100ms of system clock
[move_group-11] [WARN] [1676859526.599494855] [moveit_ros.current_state_monitor]: No state update received within 100ms of system clock
with every possible launch that i have tried
ros2 launch panda_ros2_moveit2 panda.launch.py
ros2 launch panda_ros2_moveit2 modified.panda.launch.py
or simply
ros2 launch panda_ros2_gazebo panda.launch.py
I never have/ joint_states published when i am tryng to echo them
ros2 topic echo /joint_states
The text was updated successfully, but these errors were encountered: