Imaging (sensors)

 Hi， the rear background exceeds 2 meters, and there are no obstacles in front of the sensor. The measurement data is unstable, and the reading sometimes reaches 0 and sometimes reaches 115.      

STMicroelectronics support,I am testing a VL6180X laser sensor device for use in autonomous robotics.I currently get good distance measurements using an Arduino sketch but can't use that platform in my final product.Instead I'm using a pic18f46k22 microcontroller but the measured value of the distance at register 0X62 always reads zero.The device is configured exactly as shown in the Arduino_VL6180X.cpp file and I can successfully read the VL6180X slave address at register 0x212. All voltages for the sensor are 3.3.I have used a pic and I2C with other devices and I'm getting all the acknowledgements with the VL6180X.My code for reading the measurement is:int readDistance(void) { int distance = 0; I2C_Master_Start(); I2C_Master_Write(0x29 << 1); // TOF050C I²C address write I2C_Master_Write(0x18); // VL6180X_REG_SYSRANGE_START I2C_Master_Write(0x01); // start a distance measurement __dela

Hello, I have a problem when I try to run the SPD code under STM32cube IDE, I have this under the serial monitor which remains stuck like this: SPD ULD SW Kit version 1.0.0Module type = VL53L8CXModule ID : 0000000000000000_VL53L8CBV0GC/1$2FW Version : 1.7.0.0ULD Driver VL53LMZ_2.0.10SPD Initialize SPD  

I am using a pcb4188_vd66g1 camera module with a Raspberry Pi 5.The system has been freshly set up with Raspberry Pi OS 64-bit, and I followed the official setup guide step by step.After completing the setup:The camera is detected correctly when running rpi-hello --list-cameras. However, when I run rpi-hello, no image is displayed (black screen), and an error message appears (see attached screenshot). Modified versions of the command do not work either

Hi everyone,I’m working with the VL53L0X sensor and I noticed that when it starts ranging, the supply voltage (of my board with the VL53L0X, the Vcc pin) drops from 3.389 V down to 2.544 V.In this setup, the VL53L0X is powered from the 3.3 V pin of a NodeMCU V2 board (powered via USB from my computer). The 3.3 V rail on that board comes from an NCP1117ST33T3G regulator, which is rated for 1 A output current. I also tried powering the NodeMCU using a 5 V / 2 A phone charger instead of USB, but the voltage drop still occurs.The sensor is mounted on an Adafruit VL53L0X breakout board, similar to this one .According to its 

Hi,Currently, we are testing vl53l8cxv0gc/1 by placing an object in front and moving it and reading the values. Is there a way to test the functionality of vl53l8cxv0gc/1 in a production environment? Is there a self test mechanism for this sensor?Thanks,Jagan 

Hi, I'm trying the VL53L7CX sensor for a prototype and I'm trying the example codes provided within  this page https://www.st.com/en/embedded-software/stsw-img036.html I'm experimenting the Example_10_motion_indicator and I'm able to display the "motion power" of the 16 zones within a 10-iteration loop. I just can't figure out what the results mean ! Even when the sensor is totally masked (I mean, physically), the Motion powers seem to start at 0 for all zones (which looks relevant) and increase to apprently random values up to 50-something. Lacking information from the datasheet, I wonder how to use this data and what is its signification. Thanks for your help!

Hi everyone,I’m currently using the VL53L0X sensor to measure the liquid level inside a container, and I have a question regarding the offset calibration procedure described in the documentation.Is it really necessary to perform the offset calibration in this type of application, considering that I later apply a custom correction algorithm to compensate for systematic errors? I’d like to know if the calibration provides any meaningful improvement in accuracy when working with liquid surfaces, or if it would be redundant in my case.Additionally, if the offset calibration is required, should it be performed with respect to the liquid surface itself, or should I follow the recommended method using a white target as described in the official documentation?I’d appreciate any insights or experiences from anyone who has w

Hello,I have been using the this ToF sensor along an ESP32-WROOM MCU for a while without major issues. My impementation of the i2c interface seems to be working well since in most simple ranging cases everything works well.However, recently, i have been playing around with detection thresholds. I discovered that when I enable detection thresholds while in autonomous mode, I am unable to start ranging. In fact, the sensor gets properly configured (resolution, ranging mode, integration time, frequency and detection thresholds) but when it starts ranging (function vl53l8_start_ranging), error VL53L8_STATUS_ERROR occurs. The error gets raised in this part of the function  /* Read ui range data content and compare if data size is the correct one */ status |= l8_dci_read_data(p_dev, (uint8_t*)p_dev->temp_buffer, 0x5440, 12); (void)memcpy(&tmp, &(p_dev->temp_buffer

On page 9 of https://www.st.com/resource/en/datasheet/vl53l1x.pdf, it is written:"Ranging is continuous, with a programmable delay between two ranging operations (called anintermeasurement period)"This is wrong. It should be:"Ranging is continuous, with a programmable delay between two ranging operations (called anintermeasurement, see Figure 9)"The "intermeasurement" and the "intermeasurement period" are two very different things, as shown in Figure 9 page 12. The "intermeasurement" goes from the END of a measurement to the start of the next one, whereas the "intermeasurement period" goes from the START of a measurement to the start of the next one.

Hello ST Brightsense Team,Would like to know if the VD66GY Linux driver (STSW-IMG503_V4L2) will work on an NXP IMX8M Mini (no hardware ISP) ?  If not will it work with the IMX8M Mini Plus (with Hardware ISP).Currently using the STEVAL-66GYMAI.In the STSW-IMG503_V4L2 package, the provided driver / device tree seems for the Raspberry PI, what would be the required changes for that to work on NXP IMX8 platform ? Is the vd56g3.json ISP tuning file required ( no libcamera installed, only using Gstreamer)... Thank you.

Hello,   I am having a hard time finding which software pack this file vl53l8cx_def.h is in? I think once I get that I should be get the zones if Im understanding the error correctly. Please advise.  If it helps with the solution I am trying to use the P-NUCLEO-53L8A1 and VL53L8CHV0GC to generate 3D point clouds.            

I need to cut off all the power supplys of VL53L8 to save power. Does the firmware need to be re-downloaded every time the device is powered on? loading firmware is in the function uint8_t vl53lmz_init( VL53LMZ_Configuration *p_dev)​

Hi everyone,I'm working with the VL53L0X sensor and have a couple of questions:Does noise affect the sensor's measurements? Does the sensor include a checksum or mechanism to verify the integrity of I2C messages? Can adding capacitors to the I2C bus help reduce noise interference?Thanks in advance for your help!

Good morning.I am trying to evaluate a P-NUCLEO-53L8A1 evaluation kit. I downloaded the software example from your website and am trying to carry out some tests with water and cofffee.I am wondering whether I could ask you another question to the GUI for the cup and liquid detection software. I seem to be able to detect the cup ok. Also the cup height and diameter measurements are ok. However, I struggle with the liquid level detection, using water or coffee (two liquids I got readily available) in a coffee mug. The issues I see are:- The measured liquid level is often too low in comparison to the actual fill level.- Often the measured fill level increases initially but then decreases even though the actual fill level increases monotonically. - Often, when the liquid level reaches the top of the cup, several of the pixels in the 8x8 ranging image are black without any value, while others show very large distance values (i.e. severa

I'm using several VL53L7CX sensors in a robotics application.  They work well except for when a retroreflective surface is present, which blinds the entire sensor, including SPADs not pointed at the retroreflective surface.  A large retroreflective area is not needed, only a few cm^2 patch.This is a big problem for us since industrial environments are full of retroreflective surfaces (e.g. safety vests, markings on the ground, etc.).I'm currently using the default values for sensitivity, sharpener, etc.  Any parameters you recommend tuning/adjusting to make this sensor more robust?

Hi ST Support. The VB1940 camera has IR smart upscale.I think IR smart upscale separates only the IR data from RGBNIR and compensates for any missing data.Is there a way to send IR data without interpolating this missing data (without changing the image size)?If possible, please tell me how to set it up. Best, regards.

Hello everyone,I’m evaluating ST ToF sensors (VL53L5CX / VL53L8CX) for an outdoor motion-tracking use case and would like to understand the general feasibility before investing in prototypes. Setup:A ToF sensor would be placed approximately at ankle height behind a moving person, facing upwards. The goal is to detect center-of-mass shifts and general arm/torso positioning while the person moves — not detailed skeletal joints, just coarse body-position indicators. Environment:Potentially strong sunlight and ambient IR exposurePossible water droplets, spray, and wet surfaces near the sensor (but not submerged)Target surfaces are typically dark fabrics or wetsuit-like materials at a distance of 0.5–2 m QuestionsGeneral feasibility – Can VL53L5CX or VL53L8CX reliably detect human body shape or coarse motion under these li

I was looking to wire these 2 items together to acquire a LiDAR 3d point cloud data set for a research project im working. I wanted to get some input, feedback and guidance on utilizing this hardware for LiDAR 3d point clouds? VL53L8CHV0GCP-NUCLEO-53L8A1

Hi, I asked for help because my measurements took >> 15 seconds (up to 30s) in:https://community.st.com/t5/imaging-sensors/vl53l1-measurement-takes-up-to-30-seconds/td-p/843640Now after hours of debugging i found a bug in the API at least for platforms where an Integer is not 32 bit, in:vl53l1_core_support.c:114 the code is:pll_period_us = (0x01 << 30) / fast_osc_frequency; but on AVR uC like atmega644 0x01 is 16 bit wide. Which leads to pll_period_us = 0.The wrong value messes up all tim_cfg and gen_cfg, and introduces weird behavior.Fix:pll_period_us = (0x01UL << 30) / fast_osc_frequency;Telling the compiler to use unsigned long fixe

Heya,  Is it possible to see the background light (intensity/histogram) without actually transmitting, using a VL53L8 or VL53L9?We don't want to measure the distance to objects. We just want to be able to use the SPAD array to get histogram for each zone. Its a high volume use-case, so would be great if we can achieve this. regardsShjayago

What's the difference between the following sensor variants:VL53L7CHVL53L7CXFrom what I've seen from going through the available product documents, they are all the same, performance-wise (range, frequency, FoV etc).Difference between the CH and CX seems to only be the firmware with the CH being able to output histogram data?Is this correct?Can the CH still output the normal processed data? 

The Ultra Light Driver (STSW-IMG023) init function vl53l5cx_init() fails in this section :/* Get offset NVM data and store them into the offset buffer */   status |= WrMulti(&(p_dev->platform), 0x2fd8,   (uint8_t*)VL53L5CX_GET_NVM_CMD, sizeof(VL53L5CX_GET_NVM_CMD));   status |= _vl53l5cx_poll_for_answer(p_dev, 4, 0,   VL53L5CX_UI_CMD_STATUS, 0xff, 2);The sensor does not answer with '2' as expected by _vl53l5cx_poll_for_answer. (The senosr answers '0')This results in a failed initialization.How can this be fixed?

Hi ST Support,A few datasheets for the BrightSense series, eg. um3224, show an option under CFG: Streaming readout mode control which is not precisely described in the documentation."-0x06: = XY binning x2"How does this differ from "-0x01: = digital binning x2"?The documentation says that digital binning is vertical+horizontal."Digital binning digitally combines every two pixels in horizontal and vertical directions to create the pixel output.This solution averages the pixel photoshot noise and improves the SNR without impacting the frame rate."Thank you!

Hello, I am working on a project using an AVR64DB32 MCU and the VL53L1 time-of-flight sensor over I2C.I downloaded the official API from ST (STSW-IMG007) and adapted vl53l1_platform.c to my environment.Since my I2C communication library is written in C++, I converted it into vl53l1_platform.cpp. I also wrote a simple distance measurement test program (main.cpp).My custom I2C driver (I2cDriver.cpp) is already used in other projects and seems reliable, so I assume the issue is not primarily there. I have attached these files for reference. The issue: Inside the while loop, I repeatedly call VL53L1_WaitMeasurementDataReady. If successful, I call VL53L1_GetRangingMeasurementData and then VL53L1_ClearInterruptAndStartMeasurement. In this