ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2021-04-09 02:33:58 -0500 | received badge | ● Famous Question (source) |
2021-03-08 16:12:26 -0500 | received badge | ● Famous Question (source) |
2021-03-08 16:12:26 -0500 | received badge | ● Notable Question (source) |
2021-02-14 09:52:45 -0500 | received badge | ● Famous Question (source) |
2020-10-18 21:00:24 -0500 | received badge | ● Notable Question (source) |
2020-08-23 05:01:22 -0500 | received badge | ● Notable Question (source) |
2020-08-13 14:06:21 -0500 | received badge | ● Popular Question (source) |
2020-08-12 15:03:21 -0500 | asked a question | Implementing CUDA with ROS/Gazebo Implementing CUDA with ROS/Gazebo Hi! I'm currently trying to configure CUDA with ROS/Gazebo because it looks like when |
2020-08-10 08:07:11 -0500 | received badge | ● Enthusiast |
2020-08-08 04:39:11 -0500 | received badge | ● Popular Question (source) |
2020-08-07 16:54:03 -0500 | commented answer | Simulation deteriorates over time, robot arms do not go to the same position Thanks! You've given me a lot to think about in terms of improving my simulation. One last question-- do you know where |
2020-08-07 12:10:06 -0500 | received badge | ● Supporter (source) |
2020-08-07 12:10:03 -0500 | marked best answer | Simulation deteriorates over time, robot arms do not go to the same position Hi! I'm currently running a ROS network (ROS Melodic, Ubuntu 18.04) using the ARIAC 2019 simulation interface. I have the competition going on a loop, and two UR10 arms that run on independent threads. In the beginning of the Gazebo simulation, the robot arms pick up the parts on the conveyor belt just fine, but over time, they don't seem to go back to the same position. In fact, three minutes into the simulation, the robot arm hardly ever picks up parts even though it's the same code, just running on a loop. After checking the topic that contains the arms' joint states, I've come to the conclusion that the arm doesn't reach the same position as I'm specifying when publishing to the topic. Has anyone else experienced something similar? (i.e. after running a simulation on Gazebo where the robot actions are all looped/the same, the behavior is not consistent/deviates more and more away from expected/preferred behavior) |
2020-08-07 12:10:03 -0500 | received badge | ● Scholar (source) |
2020-08-07 10:52:25 -0500 | commented answer | Simulation deteriorates over time, robot arms do not go to the same position Thank you for your response! That definitely makes sense, and is really unfortunate. I'm looking into the physics engine |
2020-08-06 03:44:42 -0500 | received badge | ● Popular Question (source) |
2020-08-05 18:02:50 -0500 | commented question | Running ROS Network on Non-Loopback Network Interface Thank you for your response! In terms of clarifying my question, I want to run the ROS network on a non-loopback inter |
2020-08-05 18:02:50 -0500 | asked a question | Simulation deteriorates over time, robot arms do not go to the same position Simulation deteriorates over time, robot arms do not go to the same position Hi! I'm currently running a ROS network (RO |
2020-08-03 16:47:12 -0500 | asked a question | Running ROS Network on Non-Loopback Network Interface Running ROS Network on Non-Loopback Network Interface Hello! I'm currently running a very simple ROS network based on th |