-
The MoveGroup interface uses the default (empty) namespace, and so it won't work with a robot that is using a non-empty namespace.
-
Hi !
I am Aaditya Saraiya and I am currently working on a GSoC 2018 project with @Levi-Armstrong on a project titled [Robot Work Cell Discovery](https://github.com/ros-industrial/workcell_explorer…
-
This is a continuation of #661. Here a quick summary:
With more planners tested with MoveIt in general usage, we noticed a minor interface issue for `MotionPlanRequest`:
With the current semantics…
-
Hi,
I'm trying to use xarm_planner to plan around a couple of obstacles.
However the planner finds paths that are highly suboptimal and take very large detours, as shown in the picture below:
!…
-
Support navigation in multi-story buildings. This involves:
- [ ] Making a planner work across multiple maps
- [ ] Breaking the navigate mission into multiple sub-navigations. ie. nav to elevator,…
-
### Description
Overview of your issue here.
### Your environment
* ROS Distro: [Indigo|Jade|Kinetic]
* OS Version: e.g. Ubuntu 16.04
* Source or Binary build?
* If binary, which release ver…
-
Detecting collisions between arbitrary robot meshes and obstacles is hard. I think we would have more success with our motion planning scene's collision detection if we replaced the `.obj` collision g…
-
### Description
I'm testing moveit servo with the actual Ur5e robot. The robot moves smooth when providing continuous constant velocity using the original URDF provided by Universal Robots (Velocit…
-
## Description
Ball sensors in the form of break beams in the mouths of our robots detect if the ball is in position to be kicked. This hardware often has issues from damage or misalignment and so …
-
Define the movement limits of the robot and make a document description about it, for mechanical design to be able to dimension and design the interaction between the storage and cobots.