Imaging (sensors)

The VL53L3CX API‘s example code use 12KB of RAM, which makes it impossible for me to try to use the program with a smaller RAM MPU.The example for L1X,L0 are not the same, they only use about 2KB of RAM.I would like to know if it is necessary to use such a large amount of RAM to use the VL53L3CX API or if this is a software bug.Thank you.

Hi,Are there any examples for Interrupt based people count detection?We required Interrupt method for power optimizations, longer battery life.Please help us.RegardsMariswamy

Please, do you know if there is a way to solve stability problems with the VL53L1X satel ?Thank you for your help.Best wishesAnne

Hello,we utilize both VL53L1X and VL53L1CB for our projects, but from datasheets seems that there is no "easy" way to distingish between them, for example reading registers 0x010F-0x0110 gives the same results between Vl53L1X and VL53L1CB.Is there any (maybe some undocumented register) way to distinguish between them? We need the distinction to perform different behaviours of our devices accordingly.Thank you very much,Marco

Hello, I have series of questions related to the data implementations using SPAD zone settings. After reading of manuals i made conclusions how to use this feature of the sensor, but i'm not sure if my conclusions are correct.1. I'm interested in accuracy of data returned by sensor in different zones. I tested all center zones started from 16x16 and reducing it to 4x4 size array. And each redusing gave me differense almost in 1.5cm, so the difference between value that retured in 16x16 case and 4x4 case equals 7-8cm! I had clear conditions of the experiment: sensor was fixed vertically in front of plane wall. I just wondered why the zones with the same center have such differents in output value.2. The second quastions is about if there any possobility to define geometric locations of the zones. User manuals said that 16x16 array has 27 FoV, 8x8 -20 FoV, 4x4-15 FoV. So i'm really wondered how those zones geometricly exists, because the reducing of the FoV is not uniform (if it was unif

Hi,I'm working with vl053L0x sensor in a project to liquid measuremet. First I try to measure the empty cointainer 690 mm to tall but I'm not getting the correct measurement, I'm getting out of range 8191mm, or I'm getting a measurement with an offset of +- 40mm.The measurements obtained depends of calibration. I have read the documentation but I have some questions about the calibration:1) SPAD calibration, the function VL53L0X_PerformRefSpadManagement, It is necesary to remove the coverglas and execute this funciotn in a dark environment or normal environment?*For the next points is necessary put the coverglass.2) I have a black box to 10cm tall and the box bottom is black too, Would it be good to change the bottom of the box for a white background? Would offset on a white background or a black background be a big difference? 3) Crosstalk, this point is the most problematic, I try to calibrate the crosstalk with a white paper tube with 470mm to tall and a black background. I'm using

I have the X-NUCLEO53L3A2 development kit. I'm trying to get the VL53L3CX_Gui running. It connects to the development kit via USB but will not detect any sensors. I have updated the firmware, installed the STSW-LINK007 and STSW-LINK007 drivers as instructed in the user guide. I cannot get the GUI to detect any sensors. It just continuously says "Sensor Not Detected. COM4 Connected: Please ensure sensor is connected then press black button on Nucleo". No amount of resetting, plugging, replugging, relaunching the application, reflashing the device seem to clear this up. I can get LD1 to turn solid green but cannot do anything with the kit. There are sensors left/center/and right connected to the board.

I am trying to change the lower measurement threshold of this sensor so that it will only send proximity data above a certain distance. I am quite new to using ToF sensors and am not sure where to start, I have looked over the documentation and am still quite lost, any help would be greatly appreciated!

orange -VL53L1Xblue - HCSR04

..

..

Hello all,I am using the VL53L1x ultra lite driver from ST. I have 34 VL53L1X devices currently running and two of these devices suddenly would not boot the VL53L1X sensor. Note that this device did work before.We also have a GSM modem on the board and I have noticed RF interference that affects the sensor. I have therefore opted to switch off the modem before booting the sensor. Note also the extremely long delays when toggling the XSHUT pin.Basically, the sensorState value stays zero until the watchdog times out (after about 30s). The whole device reboots and the sequence simply repeats.Why would these 2 sensors (out of 34 running the same firmware) behave like this? __HAL_IWDG_RELOAD_COUNTER(&hiwdg); modem_off_on();//modem off XSHUT_GPIO_Port->ODR &= (~XSHUT_Pin); HAL_Delay(10000); XSHUT_GPIO_Port->ODR |= XSHUT_Pin; HAL_Delay(5000);   status = VL53L1_RdByte(DEV, 0x010F, &byteData);   status = VL53L1_RdByte(DEV, 0x0110, &byteData);   statu

We are working on syringe volume sensing application with VL53L0X Our expected accuracy is +/- 2mmWe configured sensor in high accuracy mode with 900msec budget timeTo check stability performance of sensor over long period of time we captured 97000 sample at @ 1 sec periodicity over 27 hours period with object at fixed distance.Overall we found the sensor output is stable varying between 3 count for fixed object distance.Attached is the 97000 readings which we captured and our observation and queries.Please help us to provide answer to our queries..

Hi,I am running into a problem where the VL53L0x will return "0" for its SignalRateRtnMegaCps value for certain range measurements. Some sensors I have it does this an overwhelming amount of the time. Some sensors I only see this periodically.I use this SignalRtn value to gauge how strong of a reading I received. The 0's happen in situations where I would certainly expect there to be a strong value for SignalRate.Does anyone knows if this "0" means anything? Or if anyone has come across this before? Thanks

I am trying to explore X-CUBE-TOF1 and I have several VL53L3CX breakout boards. I'm using the latest CubeMX and IDE (6.3.0 and 1.7, respectively) and therefor downloaded both the 2.0.0 and 1.0.0 X-CUBE-TOF1 cube modules.I've selected the following software packs:The performed the following configurations: After generating the code, the directory is completely empty.Removing the software pack results in a properly generated project (but without the software packs, obviously) How can I generate starter code to use with the VL53L3CX breakout boards?

Hi all,I'm working on a project where I need to analyze the raw histograms from the VL53L1 sensor. For my analysis to work I need to subtract the ambient light from the histograms.I get the histogram data using VL53L1_GetAdditionalData(), and I can see that every other histogram contains four bins of ambient light measurement. The problem is that all of the histograms with ambient light measurements have consistently larger bin values than all corresponding histograms without ambient light measurements, which causes an overestimation of the ambient light.I read in other posts about normalizing by the number of active SPADs - but that doesn't help, because the number of SPADs doesn't change on consecutive measurements where the setup is the same (i.e same distance from target, same lighting conditions etc).Is there a different scaling factor or offset for ranging loops with ambient measurement than loops without?Anyone has an idea how to fix that?The image attached shows a comparison of

Well, week 28 has come and gone and the VL53L5CX-SATEL is still out of stock. Is there an updated estimate of when this part will become available?Thanks,Dave

If the VDD pin on the left (breakable) part of the breakout board actually is the input voltage, then there is a problem, for the voltage drops and it even causes a brownout.

Hello, I'm currently trying to run the VL53L0X sensor on the STM32f407VG Discovery development board. I am able to measure distance with a ready-made library I found on the internet. But these measurements are very noisy, and I get an error value of 8190 after measuring 120cm. I'm not doing any calibration because I don't know how to do it. Can you help me?If you wish, I can share the library I use and my main.c code.

I have tried to use drivers and example code which are provided by STM in website. My board is P-NUCLEOWB55, and example codes are written for STM32F401RE-Nucleo and STM32L476RG-Nucleo. When I call the HAL_I2C_IsDeviceReady() function, it returns HAL_OK. And also all driver functions which I used in below code these returns zero. But I could not get any measurement result. What is the most simple way to measure the distance by using this sensor? What is the suitable way to integrate sensor driver to the project? (When I compile it, it does not give any error but maybe I made mistake when I put driver files to the project.)/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * <h2><center>© Copyright (c) 2021 STMicroelectronics. * All rights reserved.</center&

..

Hello,I'm trying to make the linux driver for VL53L3CX work on STM32MP157C-DK2. Already fixed some problems : made it work with new kernel by correcting functions names (timeval => __kernel_old_timeval and i2c_new_device => i2c_new_client_device , that's all), made it compile with bitbake and changed used gpio pins to use it on my board instead of raspberry pi.The driver now compile. Also with i2cdetect -y 1 I verified that the VL53L3CX is connected and can be detected at adress 29.But I have that error trying to load the kernel module :modprobe stmvl53lxresult :[ 545.281289] stmvl53lx_parse_tree: Unable to find boot-reg -22 41 [ 545.281366] get_pwren: pwren gpio disable [ 545.291058] cci_read: i2c_transfer :-6, @29 index 0xe5 len 1 [ 545.299320] stmvl53lx_reset_release_i2c: boot fail with error -13 [ 545.299333] reset_release: reset release fail rc=-5 [ 545.310389] ------------[ cut here ]------------ [ 545.314976] WARNING: CPU: 0 PID: 1105 at drivers/regulator/core.c:2123 _regu

Hi ST team and community !I'm here because i have some troubles on the VL53L1X.I use the following library available on GitHub : openmv/vl53l1x.py at master · openmv/openmv · GitHub.I deployed several VL53L1Xs around the mobile robot, hoping to get the distance information of other robots with the help of vision. However, in practical tests, it is found that when VL53L1X on one robot is used to obtain the distance of another robot, The VL53L1X on the other robot will produce very large interference to the measured value. The following is my experimental data, the abscissa is the number of measurements, the ordinate is the distance .It can be seen from the figure that the interference between the sensors is very large, and the measured data cannot be used at all. After subsequent experiments, it is found that when using the drive library, the sensor has been working, that is, the launch tube has been emitting laser light, which affects the measurement of other sensors. Therefo

Will I need to use a different version of the software to use the VL53L1 as compared to the VL53L1. Right now I am using the same script that was used for the VL530X.

Is not clear how to identify (via SW reading on I2C) the version of these two PNs.From the datasheet seems that the Model ID and the Model Type are the same for both ICs. The Mask Revision could be the distinctive element but unfortunately it not reported in the VL53L1 datasheet and cannot be compared with the VL53L1X value.This is a key element to know in order to switch from VL53L1CX to VL53L1CB in a product already at production stage.Thank you for your support