Has anyone created/found a library that supports the interrupt function on this board?

Excellent sensor and, yes, the qwiic connector gets you started quickly. Unfortunately, the qwiic implementation seems to get Most of the attention. There is an API call for setting the interrupt by range - that is the great news. Unfortunately, two needed APIs are left out of the library and, unlike many other sensors, you cannot write directly to the registers on the sensor like many other devices. This leaves you with a frustratingly - almost complete - driver and a tough road to figure out how to modify Sparkfun's library to add the needed calls. Of course, I have posted about this on Sparkfun's forum - but without any response.

So, like all things qwiic, easy to get started but a tough slog to realize the full potential of this amazing device.

This sensor worked very well indoors as long as you don't have any outdoor light coming in from a window. It definitely does not work outdoors, even in shade. The wavelength of natural light triggers erratic false positives with the sensor – something I found the sensor's manufacturer noted in some obscure place that I read that I'm afraid I can't find anymore.

@sparkfun Please update the description on this page to note that this sensor does not work outdoors at all, even in shade.

Is this compatible with my arduino uno or do i need to buy that Sparkfun redboard? Im also looking to use five of these sensors, how is it possible with this shield?

Having issues getting this to work consistently with a SparkFun SAMD21 LoRa Pro RF board. Best case, it will run for several seconds, then the readings will freeze. Various settings of timing budget and intermeasurement period did not make a difference. Most of the time it doesn't make it past the first library function call in the setup function.

Hi there I was trying to narrow the FoV bei changing the RoI with your library. I don't want to go as far as calling it a bug since I have no clue what your programmers intended to achieve with the specific line of code, however I seem to have found a solution. In the library you have the following fnct:

VL53L1X_ERROR VL53L1X::VL53L1X_SetROI(uint16_t X, uint16_t Y) { uint8_t OpticalCenter; VL53L1X_ERROR status = 0;

status =VL53L1_RdByte(Device, VL53L1_ROI_CONFIG__MODE_ROI_CENTRE_SPAD, &OpticalCenter);
if (X > 16)
    X = 16;
if (Y > 16)
    Y = 16;
if (X > 10 || Y > 10){      
    OpticalCenter = 199;
}
status = VL53L1_WrByte(Device, ROI_CONFIG__USER_ROI_CENTRE_SPAD, OpticalCenter);
status = VL53L1_WrByte(Device, ROI_CONFIG__USER_ROI_REQUESTED_GLOBAL_XY_SIZE,
           (Y - 1) << 4 | (X - 1));
return status;

}

-> Changing the RoI to anything lower than 11 will result in no distance readings (-1). I changed the code from: ....if (X > 10 || Y > 10){ ....
to this: ....if (X > 0 || Y > 0){ ....
This leads to an optical center value being assigned and distance values will be returned.

This might help someone struggling with the same problem.

Today I try the software With a Arduino M0 (ATSAMD21G18) After loading the software the board was unusable. no connection possible. I have try it several times every time I had to program a new bootfile.

I don't know what I do wrong, using a other library (simple one) works fine.

best regards,

Rob

Greetings!

I am trying to create a traffic sensor / data-logger using sensors like this.

I want to place a sensor on one side of a street, and a piece of reflective metal on a fence opposite the sensor, that's about six-or-so meters away. I want to detect either an object closer than the fence, (usually by a factor of two), or an interruption of the beam, (in case the vehicle is a truck with non-reflective fabric sides - or has such a horrible paint-job that the beam doesn't reflect.)

This will be used out of doors, so ambient light is a serious concern.

I don't need millimeter accuracy. In fact, I was originally considering a simple IR emitter/detector sensor pair bouncing off a reflective surface. The easy-to-assemble Qwiic systems sound like an answer to my prayers without having to re-design the wheel.

Question: Which, of the many sensors you sell, would be a good fit? (Hopefully not the Garmin sensor for $150-or-so!)

Thanks!

Jim "JR"

The VL53L0X was quite disappointing in broad daylight, which was to be expected, but also under controlled office lighting conditions. The usable range, where no ambiguous triggers occurred was around 1 metre under office lighting and on late overcast afternoons and around 1,5 metres in near darkness. It helps putting a 2-3mm tube around the receptacle part of the sensor to prevent stray light from entering too soon. Also, distance varied by as much as +/- 20mm depending on colour, reflectance and porosity of the obstacle's material.

Is this new sensor, with its tiny lenses, noticeably better? Have you had a chance to compare it to the VL530X side-by-side?

How is the performance in strong ambient light outdoors? Is there any special housing that's necessary to improve the performance in such environments?

Can I measure the distance of a metal bob inside a metal tube of 4cm diameter with this module?....Will the laser bounce off the walls of the tube?

What I want to know is how this module runs on 3.3 volt? Everything in the STM documentation states 2.8 Volt with 1.8 volt I/O. As far as I can tell Sparkfun has the only VL53L1X module that runs on 3.3 volt with I/O on 3.3 volt.

Hi, can it be used to measure water level? I am planning for a tidal gauge, but maybe absorption of light in water gives trouble. BR