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

issue in the source for gazebo simulation in melodic ver. #46

Closed
LeonJung opened this issue Feb 6, 2020 · 2 comments
Closed

issue in the source for gazebo simulation in melodic ver. #46

LeonJung opened this issue Feb 6, 2020 · 2 comments

Comments

@LeonJung
Copy link

LeonJung commented Feb 6, 2020

Hi,

I found that current melodic source base - gazebo simulation doesn't work (by following the commands described in README) with navigation stack,
since the gazebo xacro file for sick_s300 urdf doesn't have (I guess) correct frameName for libgazebo_ros_gpu_laser.so.

And also is there anything to merge two sick lidar datas (front / back) together to output /scan?
since the navigation stack wants /scan topic, not /b_scan and /f_scan.

I modified those two things like,
putting ${prefix} in front of ${link},
and changed topicName from ${topic} to scan (I know that this will make /b_scan data and /f_scan data be mixed and published, so it may cause some trouble on localization)
and now the simulation works perfect with navigation stack.

or if there is other solutions that I couldn't catch, please suggest that.

Cheers.

@mintar
Copy link
Member

mintar commented Feb 19, 2020

I found that current melodic source base - gazebo simulation doesn't work (by following the commands described in README) with navigation stack,
since the gazebo xacro file for sick_s300 urdf doesn't have (I guess) correct frameName for libgazebo_ros_gpu_laser.so.

I have just tested it, and it all works correctly. If it doesn't work on your machine, you probably don't have a graphics card that works with Gazebo. Please try again on a PC with a different GPU.

And also is there anything to merge two sick lidar datas (front / back) together to output /scan?
since the navigation stack wants /scan topic, not /b_scan and /f_scan.

Yes, that's already included and running:

https://github.com/dfki-ric/mir_robot/blob/bc6c4ff4f9a980ec25f2159af72295411b7d09f2/mir_gazebo/launch/mir_gazebo_common.launch#L38-L40

I modified those two things like,
putting ${prefix} in front of ${link},
and changed topicName from ${topic} to scan (I know that this will make /b_scan data and /f_scan data be mixed and published, so it may cause some trouble on localization)
and now the simulation works perfect with navigation stack.

There is no need to modify anything. It already works the way you want it. :)

mintar added a commit that referenced this issue May 1, 2020
The GPU laser plugin has caused multiple people problems before, because
it is not compatible with all GPUS: #1 #32 #46 #52

The normal laser plugin directly uses the physics engine, so it doesn't
depend on any specific GPU. Also, it doesn't slow down the simulation
noticeably (maybe 1-2%).
@mintar
Copy link
Member

mintar commented May 1, 2020

I've committed a fix for this problem!

@mintar mintar closed this as completed May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants