-
Notifications
You must be signed in to change notification settings - Fork 16.8k
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
AP_RangeFinder: investigate and resolve RPLidar startup issue #13611
Comments
I have checked the code and I would like to make this suggestion to modify the initialise function.
And also the corresponding changes to the header file. |
Can you please raise a github PR with that ? |
Yes, but I am very bussy at work, so it won't be possible before weekend. |
What is the status on this? I am having troubles even running the pixhawk on a separate circuit and plugging power into the pixhawk after the lidar has spun up. |
Hello all, |
This reports comes from this discussion in the Rover-4.0 category: https://discuss.ardupilot.org/t/bad-lidar-health-message-with-rplidar-a2m8/52350
At least 3 users have reported that the RPLidar must be powered up before the flight controller or "Bad Lidar Health" messages appear on the HUD.
We should investigate and then try to resolve this issue. Perhaps there are some startup messages sent by the driver that we should keep resending until we start receiving distances
The text was updated successfully, but these errors were encountered: