ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2023-07-14 09:16:56 -0500 | received badge | ● Enlightened (source) |
2023-07-14 09:16:56 -0500 | received badge | ● Good Answer (source) |
2023-07-12 12:04:06 -0500 | edited answer | Where are ros2 message ostream operators for c++ logging? UPDATE: It seems the original method below is now deprecated in Humble. You should now use geometry_msgs::msg::to_yaml() |
2023-07-12 12:03:52 -0500 | edited answer | Where are ros2 message ostream operators for c++ logging? UPDATE: It seems the original method below is now deprecated in Humble. You should now use geometry_msgs::msg::to_yaml() |
2023-07-12 12:03:52 -0500 | received badge | ● Editor (source) |
2023-07-12 12:00:18 -0500 | edited answer | Where are ros2 message ostream operators for c++ logging? I had the same issue... here's how to fix it: use rosidl_generator_traits::to_yaml(poseMsg) instead of just poseMsg #i |
2022-04-05 02:05:06 -0500 | received badge | ● Nice Answer (source) |
2022-02-23 07:49:15 -0500 | received badge | ● Enthusiast |
2022-02-17 22:42:32 -0500 | received badge | ● Necromancer (source) |
2022-02-17 18:45:58 -0500 | answered a question | Where are ros2 message ostream operators for c++ logging? I had the same issue... here's how to fix it: use rosidl_generator_traits::to_yaml(poseMsg) instead of just poseMsg #i |
2022-02-17 17:51:28 -0500 | received badge | ● Famous Question (source) |
2021-05-11 06:22:41 -0500 | received badge | ● Taxonomist |
2016-11-16 23:20:28 -0500 | received badge | ● Famous Question (source) |
2016-07-21 06:06:26 -0500 | received badge | ● Self-Learner (source) |
2016-07-21 06:06:26 -0500 | received badge | ● Teacher (source) |
2016-07-21 06:06:09 -0500 | received badge | ● Notable Question (source) |
2016-06-27 17:37:39 -0500 | received badge | ● Popular Question (source) |
2016-06-23 14:15:58 -0500 | received badge | ● Scholar (source) |
2016-06-23 14:15:13 -0500 | answered a question | "startGrabbing: Node is not writable." in pylon_camera package I reported the problem as suggested by @gvdhoorn They promptly committed a bugfix: https://github.com/magazino/pylon_cam... All is well now after an update! |
2016-06-20 19:28:33 -0500 | asked a question | "startGrabbing: Node is not writable." in pylon_camera package Hi, When I try to launch the pylon_camera node, I receive the following error:
I traced through the code and found that an exception is thrown when the node is trying to set the PixelFormat to Mono8 using the setValue function in pylon_camera_base.hpp in the startGrabbing function. I'm using the basler ace acA4600-7gc GigE camera with pylon 5 sdk. I can view the camera images and set camera parameters just fine using the PylonViewerApp. Any advice? Thanks, Michael |
2015-12-11 08:27:18 -0500 | received badge | ● Notable Question (source) |
2015-02-09 13:55:55 -0500 | received badge | ● Popular Question (source) |
2013-03-13 13:34:01 -0500 | asked a question | stomp_motion_planner Hi, I recently cloned the STOMP git repo, and the code doesn't compile. I'm running Fuerte on 12.04. The issues I'm having are when I try to compile stomp_motion_planner:
Any help would be appreciated. Thanks, Michael |
2013-03-13 13:19:27 -0500 | received badge | ● Famous Question (source) |
2013-01-10 08:20:08 -0500 | answered a question | Run Graspit! with plugin Hey, I couldn't get this working either. I looked through the source and it seems that there is a bug in the graspitGUI.cpp code for loading plugins on the command line. The problem is here starting at line 155 in graspitGUI.cpp: This shows that "if (arg.section(',',0,0)=="plugin")" and "QString libName = arg.section(',',1,1);" are actually looking for an argument of the form "plugin,name" versus "plugin:name" So, just change your argument to "plugin,name" to get it to run for now I guess... Or, recompile with the commas replaced with colons. -Michael |
2013-01-10 08:07:27 -0500 | received badge | ● Supporter (source) |
2012-10-21 16:16:51 -0500 | received badge | ● Student (source) |
2012-10-16 20:37:19 -0500 | received badge | ● Popular Question (source) |
2012-10-16 20:37:19 -0500 | received badge | ● Notable Question (source) |
2012-10-16 20:37:19 -0500 | received badge | ● Famous Question (source) |
2012-10-01 04:41:27 -0500 | received badge | ● Notable Question (source) |
2012-09-08 08:15:58 -0500 | received badge | ● Popular Question (source) |
2012-07-12 05:24:51 -0500 | asked a question | how to use interpolated_ik_motion_planner Hi, Does anyone have any examples or know of any documentation on using the interpolated_ik_motion_planner with the planning_scene_warehouse_viewer? Thanks! |
2012-06-24 04:32:15 -0500 | commented question | planning_scene_warehouse_viewer crashes when using secondary IK It looks like it may be possible just to use the pr2_arm_kinematics_node. I haven't tried it yet but it looks generic enough. |
2012-06-21 16:28:17 -0500 | commented question | planning_scene_warehouse_viewer crashes when using secondary IK Electric branch |
2012-06-21 14:12:24 -0500 | asked a question | planning_scene_warehouse_viewer crashes when using secondary IK Hi, I'm using ROS Industrial on Electric. Everything works except when I try to plan a new trajectory using the secondary planner (interpolated IK), planning_scene_warehouse_viewer crashes: [planning_scene_warehouse_viewer-10] process has died [pid 3263, exit code -11]. I have tried it with the stock code from the repository with the sia10d: $ roslaunch sia10d_mesh_arm_navigation planning_scene_warehouse_viewer_sia10d_mesh.launch Any ideas? Thanks, Michael |