-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Refactor the ll40ls namespace driver methods to more closely match other distance sensor driver implementations #12695
Conversation
3c610b7
to
cc14586
Compare
@cmic0 , I put in place in this PR your I've simplified and standardized this driver's namespace methods against the other i2c distance sensor drivers' methods and although the diff isn't beautiful, once all of the distance sensor drivers are aligned it will be worth it. (Back in March I mentioned in a dev call that I thought this would be a 6 month process... it's getting close now.) @ar1040, would you mind giving this one a go? (Ensure your have |
f2911eb
to
a9c4eed
Compare
@mcsauder , sorry for the late reply, have been caught up at work. So i put the latest master on my flight controller and tried again. Still no distance sensor on boot, until I run the ll40ls start command in the mavlink console. This is the output I get: |
Hi @ar1040, the current master branch does not contain these changes yet. You will need to check out this branch and build/flash to see if these changes fix the issue for you. (Also, just double checking to make sure you set the parameter to start the driver on boot.) Feel free to find me on px4 slack if you could use a hand testing this, I am glad to give you a hand to help test this! |
@mcsauder, is there any documentation on checking out and building this branch? I'm mainly a hardware engineer but i'm always willing to learn! |
@ar1040 On a separate dir: |
Hi @HenryHuYu , are you able to test this PR to see if it fixes the issue for you? You will need to checkout this PR's branch, (see comments above), and build then flash to your hardware. If you run into any issues testing this just let me know on PX4 slack. Thanks! |
2aaca76
to
f31e842
Compare
0b06d47
to
156f45b
Compare
156f45b
to
422134f
Compare
Rebased with current master and changes from #12934 pulled into this PR. Bench tests look as they should: |
7d8c107
to
86332c4
Compare
86332c4
to
43ff332
Compare
02b7e80
to
4eddecb
Compare
Merged current master and rebased, no code changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice cleanup!
…e cm8jl65, mappydot, leddar_one, and other distance sensor driver implementations.
…s of OK to PX4_OK.
f321883
to
2d1ba62
Compare
…e docs link in ll40ls.cpp, and shortened comments to allow uniform indentation in LidarLiteI2C.h.
2d1ba62
to
2e40501
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks @TSC21 ! I appreciate your review! |
Describe problem solved by the proposed pull request
The LidarLite driver is somewhat non-standard at the moment. This PR aligns the driver with other distance sensor drive implementations.
Additional context
Please see #12278 and #12690