-
Notifications
You must be signed in to change notification settings - Fork 21
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
Using both sonars and lidar at the same time for collision detection #86
Comments
Both the sonar and LiDAR data should be published at the same time. I guess the frequency of the sonar data is to low or something since: move_basic/src/obstacle_points.cpp Line 204 in 7c277c3
I will test this and post results here. |
I've tested on Magni and points (detections) from both are used. I think this might be more of a Polaris problem. |
I've tested it myself a while back and yes it should be working in theory, but polaris doesn't really stop using sonars in gazebo either. Right now I'm thinking of doing a separate node that blocks movement once only the front sonar gets blocked for a specified time, so I can tweak it specifically for these trash sensors. Gonna be a bit hard to do without the actual hardware but I think mark has a few he could potentially test with. |
I think this should be easily feasible after #90 closes. |
Confirmed working using both Sensor and LiDAR. #90 is a separate long-term issue. |
In cases where the lidar is mounted super high or low on the robot we can't detect all obstacles and must also look at the sonars and not just the laserscan despite it being available.
The text was updated successfully, but these errors were encountered: