[New Product] Benewake New launched LiDAR TFmini Plus

Started by What is what, May 17, 2019, 02:37:10 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

What is what

Benewake's new launch LiDAR TFmini Plus

You might heard TFmini, and this one is an upgrade version of TFmini, here are the new upgrades:

1. frequency from 100 times/per sec to 1-1000 times/per sec, and it is adjustable now.
2. Blind Zone from 30cm to 10cm.
3. Distance Resolution from 1cm to 5mm.
4. New added IP65 protection case for dust proof and water resistance.
5. You can switch the interface between UART and I2C in one pieces of LiDAR.
6. Wider operation temperature.

Product Video:

You can check more details here at http://en.benewake.com/product/detail/5c345cd0e5b3a844c472329b.html

oximar

I am having trouble with the programming of a TFmini LIDAR/TOF sensor.  I want the program to turn on one of 2 LED's depending on the distance an obstacle is away from the sensor.  This will eventually turn into a 2-lane monitoring sensor for Soap Box Derby racing to tell me which car is in the lead at the midpoint of a race.  The idea is that I can mount the sensor unobtrusively on the side of the track and still monitor both lanes.  If the sensor sees something in the far lane first it will illuminate one light. If it sees something close than it will illuminate a different light.  I have adjusted the sample code for the TFmini found on GitHub to do this but there is a strange problem.  If something passes by the sensor, it illuminates the LED several times instead of just once.  Meanwhile on the Serial monitor it displays several distances that display in a time frame that match the delays in the program. To me it seems like the sensor is not taking a single distance measurement as the program suggests. To say it differently, when an object QUICKLY passes through the sensors field of view,  it seems like the object is passing SLOWLY and illuminates the corresponding LED several times.  This is shown in the Serial Monitor as several lower numbers that output over a span of several seconds even though the object has long since passed through the sensors field of view.

Any ideas on why this isn't working?  Thanks for your time.


regards,
work as graphic design at https://iprice.co.id/