I’ve been experimenting with the Garmin Lite-V4 distance sensor. See below for a plot of measured vs. true distance. It is (maybe?) expected that there’s an offset, but the ‘dead zone’ puzzles me. In other words, the output from the sensor never gives out values between 55-61cm, i.e. skips the range [56,60] cm altogether.
In other words, if one moves the target away at a steady pace, the output doesn’t change after it passes 55cm -until it gets far enough to output 61cm. Notice that there’s also a ‘droop’ starting around 40cm (true distance) before hitting the dead zone.
I’ve purchased two units from different vendors, and they both have the same problem. I’ve tried the following tweaks:
-Different target colors and finishes
-Trigger measurement by writing 0x03 instead of 0x04 (disable/enable receiver bias correction)
-Adjusting Max Acquisition Count and Quick Acquisition Termination (Garmin’s sample code LIDARLite_v4LED.cpp tunes these two parameters to go between different ‘operation modes’)
Has anyone else noticed a similar problem? If you have a functioning Lite-V4, I’d be interested to see if you can replicate the problem.
