Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sim time stops when echo laserscan/data #18

Open
ronnic4280 opened this issue May 9, 2022 · 15 comments
Open

sim time stops when echo laserscan/data #18

ronnic4280 opened this issue May 9, 2022 · 15 comments
Labels
question Further information is requested

Comments

@ronnic4280
Copy link

Hi, we are using the Robtnik Summit XL for the competition. While testing in the virtual maize field an trying to subscribe to rostopic echo /robot/front_laser/scan , we'll get the message: "WARNING: no messages received and simulated time is active. Is /clock being published?" and the simulation time in Gazebo pauses. I won't get the issue while testing on plain ground or in different worlds.
I don't know where to seach for a solution, it seems like this is a issue relating to the virtual maize field.
Has anybody an idea how to solve ist?

I'm using ros melodic on ubuntu 18.04

@Rick-v-E
Copy link
Member

Hi, the topic for the laser scanner is different. You can try rostopic list to see which topics are available. I think the correct topic is something like /front_laser/scan instead of /robot/front_laser/scan.

@ronnic4280
Copy link
Author

Hi, I'm subscribing to the right topic for the Summit-XL and it is working in different worlds, but not in the virtual maize field.

@Rick-v-E
Copy link
Member

A few ideas:

  • Did you start Gazebo in the paused mode? Because that results in the described error and can be solved by pressing the play button in Gazebo.
  • Can you see the lidar data in RVIZ?
  • Is the robot spawned correctly in Gazebo? And is there no error in the terminal that you used to start the Gazebo (roslaunch virtual_maize_field simulation.launch)?

@ronnic4280
Copy link
Author

  • Gazebo starts un-paused and the Button won't change to pause when trying to subscribe to the laserscan topic, but the time is stopping.
  • I can't see the lidar data in Rviz. When trying to show them in Rviz, same thing happens and sim_time stops.
  • while launching the maize field, I get following errors:
    Bildschirmfoto vom 2022-05-14 10-03-23

@Rick-v-E
Copy link
Member

Rick-v-E commented May 14, 2022 via email

@ronnic4280
Copy link
Author

The dandelions are at the right folder as suggested and the package is up to date.
grafik
grafik

@Rick-v-E
Copy link
Member

Rick-v-E commented May 14, 2022 via email

@ronnic4280
Copy link
Author

I fixed it and the Error for the dandelion won't occur anymore, but the sim time problem is still the same.

@Rick-v-E
Copy link
Member

Rick-v-E commented May 14, 2022 via email

@ronnic4280
Copy link
Author

Yes, its working and I’m able to echo the /front/scan while driving.

@Rick-v-E
Copy link
Member

What happens if you use your URDF files (and meshes) in the example robot workspace?

@Rick-v-E
Copy link
Member

@ronnic4280, were you able to solve this problem?

@ronnic4280
Copy link
Author

Unfortunally not, but we decided to not use the laserscan anyway. I might try to solve this problem later.

@g-pranav
Copy link

Unfortunally not, but we decided to not use the laserscan anyway. I might try to solve this problem later.

I am having the same issue, Lidar is not publishing anything when I use virtual_maize_field world but it works with other worlds.

@Darkproduct
Copy link
Collaborator

If you don't get laserscan data, this could be due to the type of ray plugin used in Gazebo. Altough, I would suspect, that there should be at least some data with the normal plugin as long as the scanner has something in its few.

It is however recommended to use the GPU ray plugin from Gazebo, because this plugin intersects with the mesh and not with the collision box of the plants. If you don't have a GPU available you can try to set ths environment variable export LIBGL_ALWAYS_SOFTWARE=1 to enable rendering on the CPU. But this will slow down the fps of Gazebo as well.

Rick-v-E pushed a commit that referenced this issue Mar 21, 2023
Checkstyle Action + Small improvements and fixes
@Rick-v-E Rick-v-E added the question Further information is requested label Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants