Imaging (sensors)

Issue with VL6180X returning incorrect value when reading the RESULT__RANGE_RETURN_CONV_TIME register.

So from my understanding, after polling the sensor we can read directly from the RESULT__*** registers to reveal things such as distance, return rate, error code and such to view the results from the sensor range measurements. However, I've seen that...

Using DMA for communication with ToF sensor VL53L7CX

Hello,Standard library for ToF sensors, as far as i know, works in blocking mode and it needs few seconds to initialize sensor and later on to gather all of 64 results. In my project I need to handle other process during this time and using DMA seams...

VL6180 proximity detection logic output mode

Hi, I would like to know if we can configure GPIO0 or GPIO1 as a logic output mode. In datasheet, we can configure in INT mode. But we need to clear the flag each time we have a value. So we have a wrong value during the clearing. I would like to con...

VL53L4CD getting "stuck" returning the same value

When I run the program, the sensor starts up and is working as expected. Occasionally, the sensor gets "stuck" and just sends the same ranging results. I read that the xshut pin is sensitive and can cause a partial reset of the sensor, putting it in ...

LoRaWAN-End-Node + VL53L4CD, Sleep issue

Hello, I'm using the LoRaWAN-End-Node example on an STM32WL55JC MCU to drive the VL53L4CD sensor.  I would like to use the interrupt pin to get the data from the sensor.what is happening is that once __WFI() in the getting data subroutine is executed...

Does the cross-talk calibration on a VL6180X sensor always need to be performed?

The calibration procedure for a VL6180X sensor states that the offset calibration does not need to be done if the sensor is within +/- 3mm for a specified target. Is there every a situation in which the cross-talk calibration procedure doesn't need t...

I did the calibration on offset on VL53L1X. Then get the offset value by calling getOffset() which is 1336. Use that in setOffset() in subsequent measurement. xTalk gives 15912. Cal distance used is 0.97m. But normal ranging at 2m is all wrong. Why?