Yes I agree, actually I was diverging a little, but that could be an interesting use case for the Pocket because of the PRU and the QEP can act as an accurate motor control with encoder feedback … so many projects, so little time
Keep on the good work
Oh sure, it can be a useful application for the Pocketbeagle, I’ll try to evaluate the update rate limit of this sensor first because I quite doubt about its accuracy at 1.5kHz. Actually I really appreciate your effort on the PocketPilot project, and I want to add my small contribution to it too. Thank you.
@ppoirier
has lidar lite v3hp been added to the plane library as well, or is this going to come out in the next release for both copter and plane?
Interestingly I tested a LidarLitev3HP yesterday with the regular driver and found that it’s update rate was very slow. I’ll try again with this PR from @nghiajenius
@rmackay9 I’m also getting the slow update rate issue, see this post. What can I do to help resolve it?
Thanks for the report. So it is most likely an issue with the driver. There have been some changes made in the sensor so we need to test and then merge the PR from @nghiajenius.
I’ve got a couple of events happening next week so I don’t think this fix will get into 3.6.0 but hopefully we can get it into a “point release” … i.e. Copter-3.6.1…
Hi @anon94298870, @pumesies, @ppoirier, @rmackay9,
As far as I know, the current library only supports LidarLite V3, not V3HP. The V3HP requires us to send a measure command periodically to obtain new values, and it doesn’t have continuous mode as V3.
Therefore, if you want to use LidarLite V3HP, you can either use PWM connection or modify the source code as my PR here (it hasn’t been merged yet): https://github.com/ArduPilot/ardupilot/pull/9169. The library is shared between platforms, so I think you can use it on plane as well.
Thanks Randy so much for helping me test this driver, although I have carefully tested it myself and it could reach 50Hz update rate, more evaluation is very helpful for a stable driver. Hope to see my PR merged soon!
Thanks for the driver update! Unfortunately I’m already using all my pwm outputs, so I need to get it working on I2C. I’ll try to bench test it on Plane today and let you know how it goes.
Ok, so after spending all day on it, I could not get my build environment set up to work correctly yet. I’ll continue next week.
Hi, can you tell me more about your hardware setup?
I’ve bench tested the updated lidar drivers, and it works very well!
I fly a electric plane, with flaps etc (hence so many pwn outputs), gps, airspeed sensor, and lidar to help with landing. I used to use a TFMini, but its range was so limited that it hardly helped at all. I’m hoping the LidarLite will help me get a more accurate flare and softer landing.
Hi @pumesies,
I’m very happy to know that the driver works well on plane too. Thanks for daring to test my code! 
I have tested it in my quadcopter but I have no experience in plane. Did you use the Cube as your flight controller?
Yes I use a Cube. I’m not sure when I’ll be able to fly, maybe next week, but I’ll let you know how it went.
Thanks. A small note is that the lidar is very noisy when the range is below 30cm.
Thanks for the heads up, I have set the parameters to ignore the Lidar below 0.5m since it’s committed to the landing by that stage anyway.
So we flew the new Lidar last week, it worked a treat! The lidar activated nice and early in the glide slope, which means the flare was accurate to ensure a gentle landing. Much much better than with the TFMini.
@rmackay9 What needs to happen before this PR can be merged into the master firmware?
Hi @pumesies,
I’m so happy to know that you had a successful flight! I have followed up with reviewers and fulfilled all change requests to match Ardupilot standard, so I also hope that it will be eventually merged soon! 
Great, thanks for testing.
It’s all on us merge team members to get it in. I’ve added it as a DevCall topic so it will be discussed in next week’s developer meeting. Discussing it on the call tends to push up it’s priority in the review queue.
txs again!
Let me know if there’s anything I can do to help.
