You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 8, 2024. It is now read-only.
When selecting the topic for LaserScan it only prompts for Laser1 or Laser2 respectively, even though the original param for the rviz config is the cob_scan_unifier, nevertheless, this value doesn't show the laser scans in rviz, while the other scans separately do.
All of this is done in Ubuntu 20.04, ROS Noetic, neo_simulation for MPO_700, with gmapping true, moving_base true, others args to false. Executing the main simulation.launch file.
Am I missing something? Thanks ;)
The text was updated successfully, but these errors were encountered:
Thanks for the report. We do not actually use the cob_scan_unifer anymore. We had few months back removed it. You have to use either laser 1 or laser 2. We will update the RViz configs soon.
All of this is done in Ubuntu 20.04, ROS Noetic, neo_simulation for MPO_700, with gmapping true, moving_base true, others args to false. Executing the main simulation.launch file.
Is there any specific reason you wanted to run gmapping and move_base together? Technically it is possible to run both move_base and gmapping at the same time. But, that is not advised, since you will have localization running from both the packages, because of which you can evidently see the robot jumping on RViz.
When selecting the topic for LaserScan it only prompts for Laser1 or Laser2 respectively, even though the original param for the rviz config is the cob_scan_unifier, nevertheless, this value doesn't show the laser scans in rviz, while the other scans separately do.
All of this is done in Ubuntu 20.04, ROS Noetic, neo_simulation for MPO_700, with gmapping true, moving_base true, others args to false. Executing the main simulation.launch file.
Am I missing something? Thanks ;)
The text was updated successfully, but these errors were encountered: