fetch_ros icon indicating copy to clipboard operation
fetch_ros copied to clipboard

Open ROS Components for Robots from Fetch Robotics

Results 19 fetch_ros issues
Sort by recently updated
recently updated
newest added

I use the fetch navigation,but it don't work well. First I build the map and send a pose to navigation.The robot's location match the map is terrible when it is...

bug

The current bag file moves the arm around a lot more than it probably needs to. Poses should flow better. At the same time, it would be worth adding some...

enhancement

**Describe the bug** I am porting the fetch URDF to bullet3. Looking through the URDF I found bellows_link and bellows_link2. They are causing the robot to every-so-often jump due to...

bug

Hi all, I would like to use moveit group to do motion planning for fetch's arm without considering the collision on its gripper. I first enable the moveit active sensing,...

Hello, I've been playing around with the local planner and Fetch. I based my code off the base_local_planner and was copying the configuration variables over, when I saw this in...

Because locks are standard now? https://github.com/fetchrobotics/fetch_ros/blob/melodic-devel/fetch_teleop/src/joystick_teleop.cpp#L153 https://en.cppreference.com/w/cpp/thread/mutex

enhancement

this PR changes `longest_valid_segment_fraction` from `0.05` to `0.005`. this changes is applied to `arm` group in #122 , but not in `arm_with_torso` group, so I made this PR.

fetch arm collides with base or torso when `path constraints` is given to `MotionPlanRequest`. This is because Moveit computes in `cartesian model state space` when `path constraints` is given, and...

This PR adds possible collision check and ignore warning. ## Add possible collision check - `base_link` and `upperarm_roll_link` can collide, but ignored in current `melodic-devel`. - [check collision between base_link...