hello, you should try to start manually in mavlink console “ll40ls start i2c”. If it is still not available, try again !!. I think it is a bug on lidar lite driver
Hello, I have also have a similar issue. I have two different Lidarlite v3s (both have 2019 label as shown in picture above) and two different pixhawk 4s (tested firmware 1.8 and 1.9) and have tested them both similarly in the console. If I repeatedly do a “ll40ls start i2c” over and over again I can eventually get the ll40ls driver to start. Sometimes it takes 10 times or more. (I figured this out by accident as it just started for me once randomly, and after repetitive testing it started again…
opened 09:25PM - 14 Jun 19 UTC
closed 02:57PM - 30 Jan 20 UTC
stale
The Lidar Lite V3 rangefinder is an optional rangefinder to be used with the Pix… hawk 2.1. It can be enabled by the parameter EKF2_RNG_AID=1 and the Lidar Lite V3 can be initialized by the parameter SENS_EN_LL40LS. I use the I2C protocol.
I currently have 3-4 Lidar Lite V3's that are dated 2016 on the label. These Lidars work every time. The tests I have ran:
- Visual: Noticing the craft holds altitude
- The Analyze tab in QGroundControl: In QGroundControl, look in the top left corner, click widgets, then analyze. Type distance_sensor_current in the filter box. If the Lidar is working it will display a parameter that can be clicked and data can be viewed. (Note: the Lidar must be connected to the Pixhawk correctly, and both the Pixhawk and the Lidar have to be powered. I will add links to the correct way to wire this at the end)
- Arduino test: Connected the Lidar to the arduino using the provided documentation. https://learn.sparkfun.com/tutorials/lidar-lite-v3-hookup-guide/all
The 2016 Lidars will pass all of the tests described above. The 2018-2019 Lidars will only pass the arduino test.
I decided to go straight to the source by contacting Garmin. Garmin's response was, "The newer units use a newer hardware design that uses a faster FPGA. The intent was for it to function as a drop-in replacement for the original, but there are some differences. We have made updates to the https://github.com/garmin/LIDARLite_Arduino_Library that are intended to account for the differences."
Also I have attached what Garmin sent me about the change.
[LLv3-I2C-Guidelines.pdf](https://github.com/PX4/Firmware/files/3292284/LLv3-I2C-Guidelines.pdf)
Do you guys plan to support this new change? When could I expect the change to be implemented if so? Is there anything I can do in the meantime to fix this? Any and all help is appreciated.
1 Like
