-
Notifications
You must be signed in to change notification settings - Fork 97
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
Quality of service setting missing and laser scan (/scan) on ground level #301
Comments
FIY, I just ran into the same issue, tried to work around it by changing the QoS in |
@jankolkmeier Hi, I am having the issue where there is incompatibility issue with Unity and ROS. The laser scanner driver that we are using uses BEST EFFORT, but unity apparently only supports RELIABLE. I tried looking into the subscriber.py to change the QoS, but i cant seem to find the line of code of: Do you mind double checking if that is still a valid solution? |
Change the qos_profile in Hope this helps. |
@KingKiger This is the subscriber.py script that is from Unity-Technologies/ROS-TCP-Endpoint repo, unless I am missing something or looking at the wrong place, i do not see the where is
|
Our robot uses quality of service 'RELIABILITY=VOLATILE' for the laser scan, but it needs to be changed to 'RELIABLE' to work with Unity. I couldn't find anywhere to configure it in Unity. Then, when it works, the laser scan is on ground-level. It should be a bit above it.
The global and local costmaps also don't align. This, plus the laser scan issue, makes me think it might be a problem with the /tf.
When I run the Nav2-SLAM-Example, everything is aligned and properly positioned (with the data from Unity's simulated robot).
Environment:
In the following image, pink is the floor on Y=-1, laser scan are the colored dots, white dots are the point cloud (unrelated), and the costmap is the white+black-ink square (also looks weird).
Nav2-SLAM-Example has maps and laserscan properly aligned and positioned:
The text was updated successfully, but these errors were encountered: