3D Robotics

Lidar Lite back with V3 after Garmin aquisition

3689700337?profile=original[Updated with more info] Glad to see that the Pulsed Light team, which joined Garmin earlier this year, are back with a new version of the Lidar Light range finder. Not many details yet, but it's now listed for $150 at Sparkfun:

  • Description: It’s back! This is the LIDAR-Lite v3, a compact, high-performance optical distance measurement sensor from Garmin™. When space and weight requirements are tight, the LIDAR-Lite v3 soars. The LIDAR-Lite v3 is the ideal solution for drone, robot or unmanned vehicle applications.

    This easy-to-use 40-meter laser-based optical ranging sensor has all the core features that made the LIDAR-Lite v2 so popular. Small in form and light in weight with low power consumption of less than 130mA during an acquisition. And it’s user-configurable so you can adjust between accuracy, operating range and measurement time.

    Each LIDAR-Lite v3 features an edge-emitting, 905nm (1.3 watts), single-stripe laser transmitter, 4m Radian x 2m Radian beam divergence, and an optical aperture of 12.5mm. The third version of the LIDAR-Lite still operates at 5V DC with a current consumption rate of <100mA at continuous operation. On top of everything else, the LIDAR-Lite is user-configurable, allowing adjustment between accuracy, operating range and measurement time. It can be interfaced via I2C or PWM.

    Note: The LIDAR-Lite v3 is available for pre-order. We expect to have these in stock and shipping by early to mid-October. Adding a pre-order product to an order may cause a delay. Be sure to uncheck “ship complete order” in your cart to avoid delays in shipping in-stock items.

    Dimensions: 20 x 48 x 40 mm (0.8 x 1.9 x 1.6 inches)

    Features:

    • Range: 0-40m Laser Emitter
    • Accuracy: +/- 2.5cm at distances greater than 1m
    • Power: 4.75–5V DC; 6V Max
    • Current Consumption: 105ma idle; 130ma continuous
    • Rep Rate: 1–500Hz
    • Laser Wave Length/Peak Power: 905nm/1.3 watts
    • Beam Divergence: 4m Radian x 2m Radian
    • Optical Aperture: 12.5mm
    • Interface: I2C or PWM

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • @Andrew , thanks! i believe there is something wrong with the HW (lidar). I don't have an arduino board around to check the original driver from Garmin. I will try it tomorrow to see if it is something in .NET or in the HW.

    @Dale , ok, that what i wanted to know , that V3 works , now it is either a broken unit or some issue in .NET for netduino board

  • I am using V3 on a pixfalcon I2c with no problems I just setup via mission planner nothing special.

    I can't check versions now, but I believe it is the latest APM copter.

  • Developer

    @Alex I'd be happy to fix the I2C driver if someone wants to send me a V3 unit. I wrote the drivers for V1 and V2.

  • Thanks for the answers  and sorry for the multiple posts, the server probably a little bit slow, hit add multiple times :(

    Yes, i'm using 0x62, the writes work, but the reads always return zeros. BTW, the V1 was also using 0x62 . I'm using netduino plus2, to get thru c# , i probably have to dig in to the firmware 

  • Got a V3 version unit a week ago. PWM works fine, but couldn't get I2C to work, looks like the read commands don't work. The same SW/HW works fine with V1 , Anybody has a luck to bring a V3 up ? 

  • The Lidar Lite driver files contain the 0x62 address . See line 58 in https://github.com/ArduPilot/PX4Firmware/blob/3e947ccf02c66b77f6d1c... 

    ArduPilot/PX4Firmware
    PX4 Firmware for PX4FMU autopilot and PX4IO servo / failsafe board - ArduPilot/PX4Firmware
  • Developer
    I see that v3 uses i2c address 0x62, I can't check what v1/v2 uses right now though, is it set for that address now?
  • Got a V3 version unit a week ago. PWM works fine, but couldn't get I2C to work, looks like the read commands don't work. The same SW/HW works fine with V1 , Anybody has a luck to bring a V3 up ? 

  • Got a V3 version unit a week ago. PWM works fine, but couldn't get I2C to work, looks like the read commands don't work. The same SW/HW works fine with V1 , Anybody has a luck to bring a V3 up ? 

  • Thank's Tom

This reply was deleted.