404RobotNotFound's profile - activity

@cubpaw What do you mean by "every time I reset my ros env"? Is it every time that you re-launch the launch file? If so,

@Delbina Did you end up solving your issue or are you still having problems?

Edit @Delbina Something I should have noticed the first time, your kalman filter accepts the angular Z value from both

Also, take the covariance values in display with a grain of salt. What you should care more about is the odometry arrow

Edit: @Delbina Something I should have noticed the first time, your kalman filter accepts the angular Z value from both

What you are looking to use are launch arguments (arg tags) and not parameters (param tags). Here is a link to the rosla

A few things to try: For the IMU data, you have the IMU reporting the acceleration in X and Y. While your IMU probably

I am pretty sure gazebo itself runs in ROS 1 or ROS 2, but not both at the same time. You might be able to get away wit

I would recommend going through tutorials as much as you can. I would also familiarize yourself with how your data flow

Might be something similar to this question about action clients (sorta). Might be worthwhile seeing if you can either

Might be something similar to this question about action clients (sorta). Might be worthwhile seeing if you can either

Do you get any other debug messages like: Received message that preceded the most recent pose reset. from this line. w

Do you get any other debug messages like: "Received message that preceded the most recent pose reset." from this line.

From some initial searching, I found this similar / related question about setting to use only a certain interface. It

From my initial searching, I haven't found a reliable algorithm in ROS for negative obstacles detection. Which means, yo

Remapping, see this similar question: https://answers.ros.org/question/9248/how-do-you-remap-a-topic/

Remapping, see this similar questions: https://answers.ros.org/question/9248/how-do-you-remap-a-topic/

There are a lot of complications here, but basically detecting negative obstacles is a perception problem (slam_gmapping

Then it might need to be something you create, some of the work is already done with the socketcan_interface class in th

I would guess the answer is yes, checkout these packages and see if there is anything you can use: https://wiki.ros.org/

Do you have an example of how you use LaunchConfiguration and DeclareLaunchArgument? From my understanding, looking at t

There are two issues that I can see, the first is that it looks like you only spin in the rotate function, and you use y

This is probably the more correct solution after you have dug deeper into the issue. Even the code linked in the initial

As a side note, you can highlight your text and use Ctrl + k to format it as code and make it a lot more readable and no

So in the second case you have 4 objects to know the transform between: camera 1 (c1), camera 2 (c2), fiducial 1 (f1), f

So in the second case you have 4 objects to know the transform between: camera 1 (c1), camera 2 (c2), fiducial 1 (f1), f

Ah you're right that stinks. Would be worth following the issue for it: https://github.com/ros-industrial/ros_canopen/is

Disclaimer I haven't tried it, but the ROS canopen implementations have a dashing-devel branch. https://github.com/ros-

Could be two problems coming together: Use geometry_msgs instead of Geometry_msgs (as mentioned in the comments) Make

I agree with @mike-scheutzow

It isn't said specifically in your information, but usually an include directory for a package is pkg_name/inlcude/pkg_n

First, you can try to just measure the transform manually between them or to a common point and that can get you close e