ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
2023-07-21 07:04:49 -0500 | received badge | ● Good Answer (source) |
2023-02-07 06:57:31 -0500 | received badge | ● Nice Answer (source) |
2022-11-02 13:54:01 -0500 | received badge | ● Nice Answer (source) |
2022-09-25 22:32:35 -0500 | received badge | ● Nice Answer (source) |
2022-05-21 14:09:38 -0500 | commented answer | Understanding Pointcloud2 data @petros ADLATUS This should really be a separate question, but the short answer is: it depends... REP-117 says it shoul |
2022-05-21 14:09:04 -0500 | commented answer | Understanding Pointcloud2 data @petros-adlatus This should really be a separate question, but the short answer is: it depends... REP-117 says it shoul |
2022-03-13 15:49:24 -0500 | commented question | parameter passed to xacro not changing the default one It shouldn't matter where the master is running. I see that your xacro file defaults to "other," and that is also the d |
2022-03-12 21:29:26 -0500 | edited question | Timed out waiting for transform from robot1/base_footprint to map ... tf error: canTransform: target_frame map does not exist Timed out waiting for transform from robot1/base_footprint to map ... tf error: canTransform: target_frame map does not |
2022-03-11 18:29:56 -0500 | commented answer | parameter passed to xacro not changing the default one He is using melodic. I don't understand the implication. Could you expand? |
2022-03-11 18:29:36 -0500 | answered a question | parameter passed to xacro not changing the default one He is using melodic. I don't understand the implication. Could you expand? |
2022-03-11 18:29:36 -0500 | received badge | ● Rapid Responder (source) |
2022-03-11 10:01:41 -0500 | commented question | parameter passed to xacro not changing the default one What command are you using to run setup.launch? |
2022-03-11 10:01:31 -0500 | commented question | parameter passed to xacro not changing the default one What command are you using run setup.launch? |
2022-03-11 09:55:38 -0500 | commented answer | parameter passed to xacro not changing the default one Command line arguments are supported (xacro wiki): Xacro currently supports most of the rospack commands that roslau |
2022-03-10 08:40:01 -0500 | commented question | configuring DWA navigation correctly That does sound like the source of the map->odom transform issue, and making it a separate question seems appropriate |
2022-03-07 14:05:56 -0500 | commented question | configuring DWA navigation correctly Yes, move_base should be the only node publishing to /cmd_vel. The alternating speeds may be a result of tuning, but it |
2022-03-05 11:27:06 -0500 | commented question | configuring DWA navigation correctly You now have your local planner parameters in the right namespace (DWAPlannerROS), where move_base can find them. The a |
2022-03-04 19:06:50 -0500 | commented question | configuring DWA navigation correctly In my_base_local_planner_params.yaml try changing the first line to DWAPlannerROS instead of TrajectoryPlannerROS. |
2022-02-18 13:21:50 -0500 | commented question | Error with intializing controllers Your arm transmission macro contains typos ("(" vs. "{"). It's worth going over your file carefully to make sure there |
2022-02-17 11:56:33 -0500 | commented question | ROS can't read json file I already configurated it properly Please provide your configuration file. |
2022-02-16 19:17:30 -0500 | commented answer | Failure to load controllers Are you running any other launch files? |
2022-02-13 14:45:40 -0500 | edited answer | Failure to load controllers The problem appears to be in your launch file based on the error: Could not find parameter robot_description on paramete |
2022-02-13 14:43:09 -0500 | answered a question | Failure to load controllers The problem appears to be in your launch file based on the error: Could not find parameter robot_description on paramete |
2022-02-13 14:43:09 -0500 | received badge | ● Rapid Responder (source) |
2022-02-03 22:44:28 -0500 | commented question | AMCL not publishing map->odom What is publishing the map -> base_footprint transform? Also, is something publishing odometry data? AMCL requires o |
2022-02-03 22:40:21 -0500 | commented question | AMCL not publishing map->odom What is publishing the map -> base_footprint transform? Also, is something publishing odometry data? |
2022-02-03 11:18:19 -0500 | received badge | ● Nice Answer (source) |
2022-02-02 22:02:45 -0500 | received badge | ● Rapid Responder (source) |
2022-02-02 22:02:45 -0500 | answered a question | Seeking clarity regarding frame of reference in which robot velocities are provided From what you describe, the short answer is that your Twist message is probably applied in the "'instantaneous' body fra |
2022-01-31 20:08:57 -0500 | commented question | How the lua configuration file should be set in cartographer ros? Sorry for taking so long to reply. That does sound odd, and I have not had that happen. Can you post the picture of yo |
2022-01-31 20:00:11 -0500 | commented question | Turtlebot3 LiDAR laser_filter package error "Reason: new node registered with same name" The launch files, indeed, look fine. This may have been implicit in your reply, but are you starting a fresh session ea |
2022-01-31 19:59:51 -0500 | commented question | Turtlebot3 LiDAR laser_filter package error "Reason: new node registered with same name" The launch files, indeed, look fine. This may have been implicit in your answer, but are you starting a fresh session e |
2022-01-29 14:55:52 -0500 | commented question | Turtlebot3 LiDAR laser_filter package error "Reason: new node registered with same name" robot_state_publisher is the name of the duplicate node--not topic. Your included launch file (turtlebaot3_remote.launc |
2022-01-29 14:45:07 -0500 | edited question | Turtlebot3 LiDAR laser_filter package error "Reason: new node registered with same name" Turtlebot3 LiDAR laser_filter package error "Reason: new node registered with same name" i'm trying to use a laser_filt |
2022-01-25 09:21:36 -0500 | commented question | How the lua configuration file should be set in cartographer ros? Have you read the cartographer_ros documentation? As mentioned there: If you can’t get Cartographer to work reliabl |
2021-12-16 16:46:24 -0500 | commented answer | Dynamic reconfigure vs Rosparam get. Yes, one node (with the server) is configured, but any node with a client will receive notice of the changes. Perhaps " |
2021-11-01 13:39:55 -0500 | commented question | difference in the out of /rtabmap/localization_pose AND tf_echo base_link map Does localization_pose match the /map -> /odom transform? |
2021-11-01 12:47:01 -0500 | commented question | difference in the out of /rtabmap/localization_pose AND tf_echo base_link map I'm not very familiar with rtabmap, but looking at your timestamps, it seems the outputs are about 90 seconds apart. A |
2021-10-29 14:11:34 -0500 | commented question | Can we disable the local planner from move_base ? Why do you say the local planner will affect the global planner's performance? I don't see a need to disable the local |
2021-10-14 09:35:01 -0500 | answered a question | How to use Quaternion from IMU to get the transformation to inertial reference frame? Have you looked through the tf2 tutorials? I highly recommend them. Specifically, Writing a tf2 listener (C++) and Usi |
2021-10-14 09:35:01 -0500 | received badge | ● Rapid Responder (source) |
2021-10-14 08:53:37 -0500 | answered a question | rospy.Time.now() sometimes returns 0. prevTime may sometimes initialize before the first /clock message, so it defaults to 0. If you use a non-deterministic |
2021-10-14 08:53:37 -0500 | received badge | ● Rapid Responder (source) |
2021-10-14 08:29:00 -0500 | commented question | rospy.Time.now() sometimes returns 0. Are you using simulated time? |
2021-10-11 13:54:26 -0500 | commented answer | No world frame in tf tree I'm glad it's working! static_transform_publisher can take the transform as 6 numbers (x y z yaw pitch roll) or 7 numbe |
2021-10-11 12:48:45 -0500 | commented answer | No world frame in tf tree They appear unrelated to the static_transform_publisher nodes as the warnings reference gazebo and base_footprint transf |
2021-10-11 12:48:29 -0500 | commented answer | No world frame in tf tree They appear unrelated to the static_transform_publisher nodes as the warnings reference gazebo and base_footprint transf |
2021-10-11 10:41:10 -0500 | edited answer | No world frame in tf tree You can publish a static transform for each robot relative to an arbitrary world frame like so: rosrun tf2_ros static_t |
2021-10-11 10:39:48 -0500 | received badge | ● Rapid Responder (source) |
2021-10-11 10:39:48 -0500 | answered a question | No world frame in tf tree You can publish a static transform for each relative to an arbitrary world frame like so: rosrun tf2_ros static_transfo |