2018-08-28 07:32:41 -0600 | received badge | ● Taxonomist |
2016-05-26 07:22:23 -0600 | received badge | ● Famous Question (source) |
2015-08-28 03:57:59 -0600 | received badge | ● Notable Question (source) |
2015-08-24 18:55:17 -0600 | received badge | ● Popular Question (source) |
2015-08-21 11:58:39 -0600 | received badge | ● Scholar (source) |
2015-08-20 19:55:26 -0600 | asked a question | How can I activate/deactivate sensors in Gazebo? Is it possible, from ROS, to send a message to Gazebo to turn on/off a sensor by name? Peeking at the source code, I see the sensors themselves have a |
2015-03-17 20:24:59 -0600 | received badge | ● Supporter (source) |
2014-07-24 17:40:18 -0600 | answered a question | launching gazebo fails with ros-groovy-pr2-interactive-manipulation If you were working on a 32-bit OS, then I believe that is your issue. I have the same issue on all the 32-bit machines in my lab, but not the 64-bit ones. It is also not a problem in later versions of Gazebo; only the one needed by Groovy (1.5). |
2014-07-24 17:39:02 -0600 | commented question | Gazebo 1.5 ros::InvalidNameException Are you saying here that it worked when you switched to Gazebo 1.3 instead of 1.5? I don't understand what you mean by "changing the resource path". |
2014-07-24 17:31:46 -0600 | commented answer | After updating to Gazebo 1.3 under ROS Groovy I get a .launch file error Yeah that's referring to a graphics resource name, not a node name. But I think I've recently discovered the source of that error: it's a bug in Gazebo 1.5 on 32-bit machines. |
2014-07-24 17:28:13 -0600 | received badge | ● Editor (source) |
2014-07-24 17:27:20 -0600 | answered a question | Gazebo 1.5 crash on startup, InvalidNameException If you were working on a 32-bit OS, then I believe that is your issue. I have the same issue on all the 32-bit machines in my lab, but not the 64-bit ones. It is also not a problem in later versions of Gazebo; only the one needed by Groovy (1.5). |
2014-07-09 20:49:40 -0600 | commented question | launching gazebo fails with ros-groovy-pr2-interactive-manipulation Did you ever find a solution to this? I've reproduced this issue on 4 machines, while other machines just work, with no explanation at all. Mine also uses the 0018 character code, but it's gazebobo# instead of gazeboeb. It obviously doesn't exist anywhere; my thought is that it's somehow reading the launch files in a corrupted way? But this is only a problem for the gazebo launch files. |
2014-07-09 20:10:32 -0600 | commented question | Gazebo 1.5 ros::InvalidNameException Did you ever find a solution to this? |
2014-07-09 20:00:16 -0600 | commented answer | After updating to Gazebo 1.3 under ROS Groovy I get a .launch file error I'm almost positive that's not true. |
2014-07-09 19:13:49 -0600 | commented question | Gazebo 1.5 crash on startup, InvalidNameException Hi, did you ever find a solution? I have the same |