Carl D's profile - activity

I've been fighting to port over some plugins to ROS2, and everything builds fine, but the plugins aren't discovered at runtime. Before I dig into this further, I'm wondering if this is expected to be working, and if so, is there any description of the changes between ROS 1 and ROS2?

Also are there any command line tools under ROS 2 for debugging? For example, in ROS1 there is rospack plugins --attrib=plugin

Unfortunately, development work needs to be done to enable both your questions. For the first question, about the unreg

How do you @mention someone with a space in their name on ROS answers? If I try to @mention myself, none of these option

Unfortunately, development work needs to be done to enable both your questions. For the first question, about the unreg

Unfortunately, development work needs to be done to enable both your questions. For the first question, about the unreg

Usually, header frame id is odom and child_frame_id is base_footprint or base_link. Basically, the /odom message gives

Usually, header frame id is odom and child_frame_id is base_footprint or base_link. Basically, the /odom message gives

I think my problem is, that my path has more information in it, like velocities for example. If you are using the N

Oh. Well, that is a problem. The controller uses the /odom messages to determine the current velocity of the robot. With

Assuming you intend to use the rest of the Nav2 stack, and are just swapping out the controller ... I'd still implement

It seems that the costmaps built are "occupied". That is just the default behavior when DWB fails. We just try to c

It seems that the costmaps built are "occupied". That is just the default behavior when DWB fails. We just try to c

Yes. That is OK.

See the google calendar at the bottom of this page. https://index.ros.org/doc/ros2/Governance/ for the meeting invite.

The laser scan serves two purposes in navigation: It is used by the costmap to detect obstacles so the robot doesn't h

He's not joking. We want to make nav2 better. We'd love to hear about how you are using it, and ways that we can improve

This can happen if the velocity reported in your /odom data is greater than limits set in the DWB parameters. In your ca

That's a bug in the progress checker. Sorry about that. There is no workaround other than changing the source code like

All the examples in the nav2_bringup package show how to configure navigation2 for a Turtlebot 3 which is a differential

Thanks. I fixed the command line above. When you say "It works" do you mean your problem is solved now?

I just remembered where I'd seen this before. https://github.com/ros-planning/navigation2/issues/1366. I think your pro

This CMakeLists.txt looks OK as well. However, the files you've posted don't all match with your error messages. The pr

I just remembered where I'd seen this before. https://github.com/ros-planning/navigation2/issues/1366. I think your pro

I just remembered where I'd seen this before. https://github.com/ros-planning/navigation2/issues/1366. I think your pro

The library in the error message (libnav2_behavior_tree_nodes.so) hasn't existed for a while. It shouldn't be possible t

The package.xml looks ok as well. But I just noticed that your compile error is for fr_subscriber.cpp. That isn't in you

I don't see a problem with the CMakeLists.txt. Can you provide your package.xml as well?

That library doesn't exist anymore. It has been replaced by a number of other libraries - one per node. I expect you hav

Let me add that the "better way to get the current pose" is to use TF to transform the robot's frame into the frame you

There's no need to make a new type of display in Rviz. Instead, there are 3 simple things to do: Make sure the occupan

Hmm. It could be many things, but it sounds like a power supply problem to me. I'd make sure all the drivers on the NUC

What do you mean by "the pc crashes"? Does it reboot, does it shut off, do you get kernel error messages?

Can you describe what actually happens when you do this? Any error messages, or other visible effects?

How tight are the tolerances on deviations from the path and the timing on reaching the end of a segment?

I don't know the reason off hand. If you still see this problem, I'd recommend opening a new question on the site so it