Skip to content
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

Moveit2 doesnt work with simulation time #1811

Closed
TheConstructAi opened this issue Dec 15, 2022 · 6 comments
Closed

Moveit2 doesnt work with simulation time #1811

TheConstructAi opened this issue Dec 15, 2022 · 6 comments
Labels
bug Something isn't working E-medium Medium Effort stale Inactive issues and PRs are marked as stale and may be closed automatically.

Comments

@TheConstructAi
Copy link

Description

We had to set the use_sim_time hardcoded her MOD to launches.py
To avoid failing the execution of trajectories.

The question is how is it supposed to be set using the new system of :

def generate_launch_description(): moveit_config = MoveItConfigsBuilder("panda", package_name="my_panda_moveit_config").to_moveit_configs() return generate_move_group_launch(moveit_config)

We imagine that this has to be done somehow, but what is the way the moveit2 developers consider that it should be set? Because the setup assistant doesn't seem to consider that possibility in the config files anywhere when it generates the config files.

Your environment

  • ROS Distro: HUMBLE
  • OS Version: Ubuntu 22.04
  • Source or Binary build? SOurce
  • If source, which branch? Humble, forked here: moveit2

Steps to reproduce

Launch a simulation with a movitconfig generated with wizard.
You can try it using this ROSject: https://app.theconstructsim.com/l/537b5a08/

Expected behaviour

It should work with simulations by being able to set somewhere easy the use_sim_time, or detect that the clock topic is there.

Actual behaviour

Unless you hardcode to use the ' use_sim_time' the trajectories in moveitr are planned but not executed

@henningkayser
Copy link
Member

The config builder is just producing a dict in the end, so adding or overriding values after returning the config would be the way to go, currently. In this particular case it's debatable if adding support for a MoveGroup config file would be more adequate, though.

@github-actions
Copy link

github-actions bot commented Sep 6, 2023

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Sep 6, 2023
@jeans-s12
Copy link

I have the same problem, I need to transfer "use_sim_time: true", how can I do this?

@github-actions github-actions bot removed the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Sep 14, 2023
@DiegoCarvajal98
Copy link

I have the same problem, I need to transfer "use_sim_time: true", how can I do this?

I just set the use_sim_time parameter to true after starting everything and is working, the command I used is this one:

ros2 param set /move_group use_sim_time true

Copy link

github-actions bot commented Jan 5, 2024

This issue is being labeled as stale because it has been open 45 days with no activity. It will be automatically closed after another 45 days without follow-ups.

@github-actions github-actions bot added the stale Inactive issues and PRs are marked as stale and may be closed automatically. label Jan 5, 2024
Copy link

This issue was closed because it has been stalled for 45 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
@github-project-automation github-project-automation bot moved this to ✅ Done in MoveIt Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working E-medium Medium Effort stale Inactive issues and PRs are marked as stale and may be closed automatically.
Projects
None yet
Development

No branches or pull requests

5 participants