ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2023-05-08 01:44:03 -0500 | marked best answer | Check if target joint position is valid Hi, I was wondering if there is a way to check if a goal pose of a planned path (planned in moveit with OMPL) is a valid pose, meaning that joint position constraints, collision, etc. are taken into consideration. A Python function like
would be great. Thanks for your answers |
2022-09-07 22:10:52 -0500 | received badge | ● Famous Question (source) |
2020-07-19 16:10:39 -0500 | received badge | ● Famous Question (source) |
2020-06-19 14:40:12 -0500 | received badge | ● Good Question (source) |
2020-05-22 07:31:36 -0500 | received badge | ● Popular Question (source) |
2020-05-22 07:31:36 -0500 | received badge | ● Notable Question (source) |
2020-04-09 01:04:25 -0500 | received badge | ● Famous Question (source) |
2020-03-02 09:57:24 -0500 | received badge | ● Notable Question (source) |
2020-03-02 09:57:24 -0500 | received badge | ● Famous Question (source) |
2020-03-02 09:57:14 -0500 | commented question | Which hand eye calibration method is the most popular? Well, but what kind of algorithm do they use? |
2020-02-21 03:36:35 -0500 | received badge | ● Famous Question (source) |
2019-12-10 08:17:29 -0500 | received badge | ● Notable Question (source) |
2019-11-20 12:10:22 -0500 | commented question | Which hand eye calibration method is the most popular? A few centimeters is a pretty big difference. Your camera calibration could be the cause of this deviation. |
2019-11-20 10:17:17 -0500 | received badge | ● Nice Question (source) |
2019-11-13 08:55:09 -0500 | asked a question | No return from arduino service server No return from arduino service server Hello, I just ran in a similar isse like this one. I configured a service server |
2019-10-28 07:39:26 -0500 | received badge | ● Notable Question (source) |
2019-08-10 23:37:14 -0500 | received badge | ● Famous Question (source) |
2019-08-06 16:58:04 -0500 | received badge | ● Popular Question (source) |
2019-07-16 23:44:54 -0500 | received badge | ● Notable Question (source) |
2019-07-16 23:44:54 -0500 | received badge | ● Famous Question (source) |
2019-07-01 23:43:53 -0500 | received badge | ● Popular Question (source) |
2019-06-22 12:42:19 -0500 | received badge | ● Famous Question (source) |
2019-06-17 14:53:00 -0500 | marked best answer | How to handle multiple URDF files in a single moveit package Hello, I am trying to test several robot-tool configurations. Doing that, I combined the tool urdfs (as discussed here) with the urdf of my robot. To me it seems the only way to test that configuration with my robot is to create a moveit package for every single robot-tool configuration. I was wondering if there is a convinient way to switch beetween urdf or xacro files to be able to switch between robot models and still use only a single movit package. Any ideas? Thanks a lot. |
2019-06-06 09:21:17 -0500 | commented question | Which hand eye calibration method is the most popular? Apparently the handeye_calib_camodocal package is base on this paper leads to the most robust results. I would love to |
2019-05-19 05:02:17 -0500 | received badge | ● Notable Question (source) |
2019-05-19 05:02:17 -0500 | received badge | ● Popular Question (source) |
2019-05-05 08:04:40 -0500 | received badge | ● Popular Question (source) |
2019-05-05 08:04:40 -0500 | received badge | ● Notable Question (source) |
2019-05-05 08:04:40 -0500 | received badge | ● Famous Question (source) |
2019-05-05 07:36:42 -0500 | marked best answer | How to use MoveIt without a real or simulated robot Hello, is there a way to simply do the path planning of a robot with moveit with a given URDF without the execution part of the robot? I dont want to supply any Thanks for the answers |
2019-05-05 06:20:27 -0500 | received badge | ● Famous Question (source) |
2019-04-25 01:52:29 -0500 | asked a question | Which hand eye calibration method is the most popular? Which hand eye calibration method is the most popular? Hello, I spent some time looking for Implementations, that solve |
2019-03-28 03:08:11 -0500 | marked best answer | Failed to initialize joint_names. Aborting Hello, i am using the staubli industrial robot driver. In the past it was working perfectly fine but this morning I got the following error message, when I tried launching the driver: I have not really changed any kind of settings nor have I changed the content of the package itself. Any idea, where this error comes from? |
2019-03-28 03:08:08 -0500 | answered a question | Failed to initialize joint_names. Aborting I really do not know why, but it works again. Really have no explenation for that error. Will close this now. |
2019-03-28 02:29:20 -0500 | edited question | Failed to initialize joint_names. Aborting Failed to initialize joint_names. Aborting Hello, i am using the staubli industrial robot driver. In the past it was w |
2019-03-28 02:27:49 -0500 | asked a question | Failed to initialize joint_names. Aborting Failed to initialize joint_names. Aborting Hello, i am using the staubli industrial robot driver. In the past it was w |
2019-02-25 18:59:16 -0500 | received badge | ● Famous Question (source) |
2019-02-21 02:07:05 -0500 | commented answer | Attempt to spin a callback queue from two spinners, one of them being single-threaded You might have to adjust the thread count depending on your needs. |
2019-02-21 02:06:48 -0500 | commented answer | Attempt to spin a callback queue from two spinners, one of them being single-threaded Hi, this is, what worked for me: ros::init(argc, argv, "urs100_hardware_interface"); ros::NodeHandle nh; ros::AsyncSpin |
2019-02-21 02:06:07 -0500 | commented answer | Attempt to spin a callback queue from two spinners, one of them being single-threaded Hi, this is, what worked for me: ros::init(argc, argv, "urs100_hardware_interface"); ros::NodeHandle nh; ros::AsyncSpin |
2019-02-21 02:03:09 -0500 | commented answer | Attempt to spin a callback queue from two spinners, one of them being single-threaded Hi, this is, what worked for me: ros::init(argc, argv, "urs100_hardware_interface"); ros::NodeHandle nh; ros::AsyncSpin |
2019-02-21 02:03:00 -0500 | commented answer | Attempt to spin a callback queue from two spinners, one of them being single-threaded Hi, this is, what worked for me: ros::init(argc, argv, "urs100_hardware_interface"); ros::NodeHandle nh; ros::A |
2019-02-20 23:21:17 -0500 | marked best answer | Attempt to spin a callback queue from two spinners, one of them being single-threaded Hello, I followed this guide to implement a controller for my rotary stage. Everything works just fine, but when I launch my controller, I get the following error (which does not impair the functionality of my controller btw.): The error is probably caused, when executing my controller executable of my hardware interface. The code, where I create my hardware interface looks like this: Does anyone know how I can get rid of that error? I already tried to get rid of the ros::spin() and put the spinner.start() right before the return. Would really like to know how to implement this spinning functionality properly. |
2019-02-14 16:42:54 -0500 | received badge | ● Notable Question (source) |
2019-02-12 12:08:47 -0500 | received badge | ● Famous Question (source) |