bribri123's profile - activity

map_server Caught exception in callback for transition 10 I have a launch file that uses the bringup_launch.py from the

map_server Caught exception in callback for transition 10 I have a launch file that uses the bringup_launch.py from the

map_server: Original error: parameter 'yaml_filename' is not initialized I have a launch file that uses the bringup_laun

Original error: Could not load library: libnav2_change_goal_node_bt_node.so: cannot open shared object file: No such fil

You can do this by calculating your robots odometry, the measure of where your robot is in space based on sensors like a

A RPlidar A1M8 is a 2D lidar, meaning that it can only get data about its surroundings from a 2D perspective. 3D lidars

This may not help but try using the robot_pose_ekf package it transforms odom->base_footprint. and maybe try setting

This is most likely because you have not sourced your environment try running source /opt/ros/humble/setup.bash if this

There is no reason for this, that is just how it is named, and you can probably just change odom_gmapping to odom in the

I was able to run hector slam on a Rpi 4 4gb model

my resource folder was already there i just needed to rename the file inside

Have you had luck using DWA local plannner?

Can you show the configuration for the TEB local planner

errors running robot_state_publisher When I run ros2 run robot_state_publisher robot_state_publisher neato.urdf.xacro I

errors running robot_state_publisher When I run ros2 run robot_state_publisher robot_state_publisher neato.urdf.xacro I

errors running robot_state_publisher When I run ros2 run robot_state_publisher robot_state_publisher neato.urdf.xacro I

errors running robot_state_publisher When I run ros2 run robot_state_publisher robot_state_publisher neato.urdf.xacro I

Hopefully this is the answer you are looking for. AMCL and rtabmap are only to correct for errors in wheel odometry and

Hopefully this is the answer you are looking for. AMCL and rtabmap are only to correct for errors in wheel odometry and

Hopefully this is the answer you are looking for. AMCL and rtabmap are only to correct for errors in wheel odometry and

This is probably because you do not have the map_server node running. see http://wiki.ros.org/map_server. It publishes o

robot only executes velocity set in escape_vel paremeter and in-place rotations I have a robot running the navigation st

robot only executes velocity set in escape_vel paremeter and in-place rotations I have a robot running the navigation st

robot only executes velocity set in escape_vel paremeter and in-place rotations I have a robot running the navigation st

(it is not a command) there is a file called 56-orbbec-usb.rules inside ros-astra-orbec package delete everything in the

(it is not a command) there is a file called 56-orbbec-usb.rules inside ros-astra-orbec package delete everything in it

maybe this is because your laserscan is not aligned with your costmaps correctly, can you send a photo of your costmap a

well its rotating because it is stuck and is performing a recovery behavior