Imaging (sensors)

I am using the VL53L4CD sensor with a nucleo board by using the API provided by ST.By using the xshut pin and the API, I can change the device address.But as soon as I shut down the power or reset the sensor through xshut, its address comes back to the default one.Am I doing something wrong?If not, is there any way to save the new address in non-volatile way?   

Hi, I am using the VD66GY image sensor on the STEVAL-56G3MAI board. It is connected to an Allwinner S3 with an ISP. This is my v4l2 pipeline:media-ctl --set-v4l2 '"vd56g3 0-0010":0[fmt:SGRBG10_1X10/1120x1360]' media-ctl --set-v4l2 '"sun6i-mipi-csi2":0[fmt:SGRBG10_1X10/1120x1360]' media-ctl --set-v4l2 '"sun6i-csi-bridge":0[fmt:SGRBG10_1X10/1120x1360]' media-ctl --set-v4l2 '"sun6i-isp-proc":0[fmt:SGRBG10_1X10/1120x1360]' v4l2-ctl -d /dev/video1 --set-fmt-video=width=1120,height=1360,pixelformat=NV12 v4l2-ctl -d /dev/v4l-subdev3 -c vertical_blanking=2977 # set 30 Hz update rate The image I receive is too green. When I use the colorbar test pattern (v4l2-ctl -d /dev/v4l-subdev3 -c test_pattern=2) I see all colors correctly indicating that the issue is not originating from the ISP. When I set horizontal or vertical flip, the image changes to pink, if both are active it is too green again. When I change the format to 480x640, which uses binning, the image is pink. W

Hi guys!From the last week I am trying to connect my TOF sensor with the STM32, but the I2C Communication has not been started. I have tried to use I2C Scanner to scan the address of the   VL53L7CX SATEL breakout board but was not even able to gets its address back. I also tried changing the VL53L7CX SATEL breakout board but it was also not very useful.  I have tried using both the STM32 Cube Ide software package that they provide for the TOF Sensosrs and the STM32duino VL53L7CX Library but was unsuccessful in making them work.Can anyone let me know if I am making any mistakes or if my approach is wrong in any way!Thank you in advance!

Dear STMicroelectronics team,I would like to suggest including references in your documentation—such as datasheets, application notes, or user manuals—for the VL53L family of time-of-flight range sensors regarding the use of retroreflective surfaces as a technique to enhance signal return levels in feasible applications.In my experience across multiple VL53L-series devices, even small retroreflective tapes can greatly improve signal strength and extend the usable range, often surpassing performance obtained with standard Lambertian white targets. These retroreflectors significantly improve accuracy and reduce noise, especially at longer distances, where standard targets often yield weaker and noisier returns.Unfortunately, many users and reviewers are unaware of this option, possibly due to the current documentation emphasizing only white diffuse targets as the ideal case. This can lead to underestimating the sensor’s true potential and, in some cases, favoring less suitable alternativ

I'm having an issue with a breakout board housing a VL53L1X sensor where, between the breakout board and MCU, the only connections are power, gnd, sda and scl through a PCA9617ADPJ I2C buffer. I've set it up for continuous ranging at about 200ms timing budget and is usually accurate for my purpose of just detecting if something is within about 1-2 meters. I have my codes set up so if the sensor status returns 255 VL53L1_RANGESTATUS_NONE, the code will attempt to reinitialize the sensor for re-connection.  However, sometimes it will randomly enter this state when plugged in normally. While I'm still yet to figure out WHY it enters this state, my big issue is that once it reports VL53L1_RANGESTATUS_NONE and reinitializes, the ranging accuracy is hopelessly screwed up, where hovering a target about 4cm in front of the sensor reports a maxed out distance value of 8043mm, and linearly scales from there as an object gets closer. The absolute worst part about this is that a physical rese

Hi everyone,So I'm trying to get the VL53L8CX ToF lidar working in ZephyrRTOS running on a NRF9151 chip. I'm using the VL53L8CX ULD driver version 2.0.1. The VL53L8CX is connected to the NRF9151 using i2c with the address 0x52, however when I call the vl53l8cx_is_alive() function from the driver i only see the messages being sent over i2c and getting a NAK. The i2c setup itself is confirmed to be working given that other devices use the same bus and are working as intended (we have tested with just the VL53L8CX connected as well with no difference in behaviour). We are using a custom pcb and the lpn pin is connected to 1.8v IOVDD with a 47k resistor and the system is powered with 3v AVDD. The VL53L8CX relevant circuitry for our custom pcb looks like this:With pull-up resistors for the i2c lines.The vl53l8cx_is_alive() function is called right at the beginning of main, but we have tried to add a delay before calling to give the system time to get fully powered up without effect.As

I discovered a strange phenomenon:After I powered on the VL53L4CD, I called the interfaces:The interfaces such as VL53L4CD_SensorInit, VL53L4CD_SetRangeTiming, VL53L4CD_SetDetectionThresholds, and VL53L4CD_SetSignalThreshold complete the initialization operation.Then call the VL53L4CD_ClearInterrupt and VL53L4CD_StartRanging interfaces to start the measurement. At this time, interrupts can be received normally, and the interrupt pin can rise and fall normally.At this point, I call the VL53L4CD_StopRanging interface to stop the measurement. At this time, tthe interrupt pin is at a high level.At this point, I put the device aside without operating it for about two or three days.I recalled VL53L4CD_ClearInterrupt and VL53L4CD_StartRanging, and immediately received an interrupt. At this time, I called the VL53L4CD_GetResult and VL53L4CD_ClearInterrupt  interface to read the result and found that the value of range_status was 2.Subsequently, the interrupt pin remained at a low level. I

Hello everyone,I am currently working with the VL53L8CH sensor, and it's impressive what can be achieved with it. However, I would like to know if there is any way to reduce, modify, or adjust the sensor's field of view while maintaining its resolution (8x8).Then, in certain specific use cases, I would like to increase the resolution, though I believe 64 (8x8) is the maximum. If increasing the resolution isn't possible, is there perhaps another way to reduce the field of view to focus on a smaller area while preserving accuracy?

I use some VL53L3CX with Arduino (in C++) with PWFusion_VL53L3C.h library.In some situation I need to disable multi-target detection.How can I do this ?ANDWhere I can find a detailed documentation about VL53L3CX api ?ANDCan I use a different library on Arduino ?Thank youMax   

For a medical device that use NIR light we are using the VL53L4CX as range detector. We found that the TOF sensor light interfere with our NIR lighting system. In order to perform some simulations we would like to have some more details about the light irradiance from the sensor VCSEL. From datasheet we found only few data related to the wavelength. Is it possible to have some more detailed applicaiton notes and/or datasheet related to the VCSEL of the TOF. BR  

We found a problem with VL53L1CB, After VL53L1_GetMeasurementDataReady returns 0, VL53L1_GetMultiRangingData returns VL53L1_ERROR_ZONE_GPH_ID_CHECK_FAIL. What causes this problem?Thank anyone for a little help

这是我的代码，我之前以前改地址成功了的，这里就开始测量数据while (1) {        // 获取当前时间作为起始时间        clock_gettime(CLOCK_MONOTONIC, &start_time);  // 获取起始时间                for (i = 0; i < 2; i++) {  // 轮询两个传感器            Timeout = 0;            dataReady = 0;            // 检查数据是否准备好            error = VL53L1X_CheckForDataReady(Devs[i], &dataReady);            if (error != 0) {                printf("Error checking data readiness for sensor %d\n", i);                continue;  // 如果检查失败，跳过这个传感器            }            // 等待数据准备就绪或超时            while (dataReady == 0 && Timeout == 0) { 

Hi,Im currently testing the Smart Presence Detection Firmware for the VL53L8X and have some questions:- When I start the ranging, the firmware triggers false positives (detecting someone when there isn't anyone) and after some seconds it stabilizes thus not detecting anyone unless a person approaches the sensor. Is this the normal behavior ?- I would also like to know how direct sunlight affects the sensor. It makes more difficult to detect someone ? Trigger more false positive, however I believe it is only during few times along the day that we can "observe" 940 nm.Thank you! 

Hi All,we are currently working with both the VL53L5CX and L7CX ToF-Sensors.In EMC testing, there are sometimes occurences of the statuses TIMEOUT_ERROR and CORRUPTED_FRAME during the acquisitons (via the Vl53lxcx_get_ranging_data uld function).If these statuses occur, the only thing that gets the sensor back to measuring correctly seems to be a full power-on reset. Otherwise, all uld functions like get_ranging_data or get/set anything keep returning the same error code. Just resetting the i2c by toggling I2C_RST does not seem to do the trick.My question is now: is there another way to recover from these error state of the sensor? Especially one that does not require downloading the sensor firmware again?Thanks in Advance!    

Hi all,I'm trying to setup the SPI communication with a VL53L8CX which is connected to a STM32F401RE-Nucleo. I took some code snippets from the STSW-IMG040 package and I wonder why the bytes to be send in VL53L8CX_WrMulti and VL53L8CX_RdMulti are treated with a special mask instead of just separating the bytes like shown below:#define SPI_WRITE_MASK(x) (uint16_t)(x | 0x8000) // 1 #define SPI_READ_MASK(x) (uint16_t)(x & ~0x8000) data_write[0] = SPI_WRITE_MASK(temp) >> 8; data_write[1] = SPI_WRITE_MASK(temp) & 0xFF; respectively data_write[0] = SPI_READ_MASK(temp) >> 8; data_write[1] = SPI_READ_MASK(temp) & 0xFF; instead of just data_write[0] = (temp >> 8) & 0xFF; data_write[1] = temp & 0xFF; Is there a special reason for doing this?RegardsBastian

Hi,I want to create a reflectometer to measure samples targets reflectivity in %. The samples are 10x15cm and the distance will be fixed: samples can be between 15cm to 1m. The measurement will happen in the dark in a controlled environment.I found the ST reflectometer demo page so I thought it may be viable to use a VL53 ToF sensor. However, there is not much technical explanations : https://www.st.com/en/embedded-software/stsw-img018.htmlSo, I am currently investigating the idea of using a VL53 sensor. My first question is : is it a good idea ? If any, what would be the best VL53xx device for this purpose. If it is not a good idea do you have any suggestion or something to look for ?I think reflectivity should be proportional to the signal rate in kcps multiplied by the number of active SPADs. I guess I can ignore the distance because it is fixed.I have a VL53L1 and a board, so I made a basic test with reference materials placed at 20cm in a closed box. But for some reason the signal

Subject: Request for Technical Information and Quotation – Sensor Testing for Precision Seeding Applications Dear Mr , My name is Giovanni Ziliani, and I am an expert in industrial automation and sensor technologies. I currently provide specialized consulting services to several companies operating in the field of precision agriculture. In particular, I collaborate with leading Italian manufacturers of precision seeding machinery, including: Maschio Gaspardo MaterMacc S.p.A. Bassi Seminatrici S.r.l. Mascar S.p.A. In recent months, I have received multiple consultancy requests related to the integration of advanced sensors into precision seeding equipment. I am very interested in testing your [sensor model VL53L1X] for real-time measurement of: Seeding depth I would kindly ask if it is possible to test 1 or 2 units of your sensor on seeding machines currently under development. Could you please send me: A detailed technical manual of the sensor A quotation for the purchase of 1 or

Hello, I have two expansion boards: X-NUCLEO-53L8A1 with VL53L8 and X-NUCLEO-53L7A1 with VL53L7CX. I used a gesture recognition example project for NUCLEO-F401RE board I found on this page: https://www.st.com/en/embedded-software/stsw-img035.html?icmp=tt26851_gl_lnkon_may2022#get-software The example project works fine for X-NUCLEO-53L8A1. However, when I tried to use X-NUCLEO-53L7A1, which is stated to be compatible in the manual, the vl53lmz_init function gets the "VL53LMZ_STATUS_UNKNOWN_DEVICE" error code (4) and exits here:     /* method below copied from vl52l5cx_is_alive() */ status |= WrByte(&(p_dev->platform), 0x7fff, 0x00); status |= RdByte(&(p_dev->platform), 0, &(p_dev->device_id)); status |= RdByte(&(p_dev->platform), 1, &(p_dev->revision_id)); status |= WrByte(&(p_dev->platform), 0x7fff, 0x02); if((p_dev->device_id!=(uint8_t)0xF0) || ((p_dev->revision_id!=(uint8_t)REVISION_CUT11) && (p_dev->revisi

I am exploring STM image sensors for a new project and am evaluating different options. To make an informed decision, I would like to refer to EMVA1288 datasheets, especially for details on read noise and dark current performance. Could you please let me know if such datasheets are available for STM image sensors, or how I might obtain this information?For reference, the EMVA1288 standard is freely available, and here is an example of a datasheet template:https://www.emva.org/wp-content/uploads/EMVA1288-3.1_datasheet_template.pdf

Hi, I am testing the SATEL VL53L7CX board, but the SDA on this board is stuck at zero. I have checked that there are no short cuts and that the pull up is there. Any ideas how to solve this?

I found a problem while using the VL53L4CD. My usual practice is to initialize the VL53L4CD after the terminal is turned on. During subsequent use, I only use Start and Stop to control whether to start ranging.Now it is found that when I stop, the terminal enters a low-power state. When this state persists for a period of time, when operating VL53L4CD again and sending the start instruction, no interrupt signal can be received. Moreover, after I send VL53L4CD_ClearInterrupt, the interrupt signal remains at a low level all the time.When I start, I first call VL53L4CD_ClearInterrupt, and then call VL53L4CD_StartRanging. At this time, there is no occlusion before VL53L4CD, and the register value printed out is after the VL53L4CD_StartRanging interface is called.Tof reg [0], value [1]Tof reg [1], value [29]Tof reg [2], value [2]Tof reg [3], value [10]Tof reg [4], value [0]Tof reg [5], value [2f]Tof reg [6], value [bc]Tof reg [7], value [cc]Tof reg [8], value [9]Tof reg [9], value [80]Tof r

Hi, I have downloaded the STSW-IMG302_LNX which has this description "Linux driver for VD6283 6-channel ambient light sensor, with flicker extraction expansion application programming interface (API)", I want to compile this driver for my embedded linux for arm64 platform, I don't know how can I compile it as there are number of files and folders as shown below.The read me doesn't help me either. Do I need to make a module out of it and load that in my embedded linux ? if so then how ? I tried following,I used aarch64-linux-gcc compiler. What I did was I executed make all which produced the build folder with a number of .o files, then I created an .a archive file out of it using command ar r mylib.a build/*.o and now I am not sure if I am suppose to make a main.c file and use this library when compiling my main.c file. I didn't find any good documentation and README file for the procedure. Following is where my sensor is connected on my embedded linux.  #

I am having trouble with the VL53L7CX recording incorrect measurements after being powered on. Often times the distance if off consistently until I unplug it and plug it back in (The raspberry pi). Sometimes even that will not solve the problem. I have looked at the calibration function but it seems that it is only for cover glass and I use none. Has anyone had this issue and know how to solve it?

Hello community,I just downloaded ULD driver for vl53l8ch. However it looks only i2c interface is implemented in the driver, no SPI interface related is present. Is there a SPI version of the driver available? or I missed something? Thank you./Roland 

Hi,I have installed the v4l2 driver for the STEVAL-56G3MAI1 camera module on ubuntu 22.04.05 LTS on a RPI CM4. But I am unable to access the module through /dev/video0.I have followed the instructions in the linux start guide fro ST BrightSense but I cannot get it to work.I am not sure if I need to do something in addition to these instructions:cd en.vd56g3_1.0.3/srcmakesudo cp *.ko /lib/modules/$(uname -r)sudo depmod -asudo rebootsudo apt updatesudo apt install device-tree-compilercd en.vd56g3_1.0.3/dts/rpi1_to_4/sudo dtc pcb4188_vd56g3.dts -o /boot/firmware/overlays/pcb4188_vd56g3.dtbosudo sh -c "echo 'dtoverlay=pcb4188_vd56g3' >> /boot/firmware/config.txt"sudo reboot v4l2-ctl --list-devices gives:unicam (platform:fe801000.csi):/dev/media3 Cannot open device /dev/video0, exiting. Is there something I am missing in the setup? Should the driver be placed in a different folder?Thanks for any assistance!