Imaging (sensors)

The most viewed and commented post on the Imaging page had to do with an Init failure on the multizone part. These parts have large I2C writes at the beginning, which is downloading the Firmware (on the L5 and L7) and downloading patch updates on the L8.  The solution was: uint8_t WrMulti(VL53L8CX_Platform *p_platform, uint16_t RegisterAddress, uint8_t *p_values, uint32_t size) { uint8_t status = HAL_OK; // Initialize status as HAL_OK uint32_t remaining_size = size; // Calculate remaining size to write uint16_t current_address = RegisterAddress; // Initialize current address // Loop until all data is written while (remaining_size > 0) { // Calculate the current chunk size to write uint32_t current_chunk_size = (remaining_size > chunk_size) ? chunk_size : remaining_size; // Perform write operation for current chunk status = HAL_I2C_Mem_Write(&hi2c2, addr, current_address, I2C_MEMADD_SIZE_16BIT, p_values, current_chunk_size, 100); // Check for error if (status

Hi ST Support.I am currently working with a camera module using VB1940. I could not find a detailed pinout or pin definition in the official documentation. I would greatly appreciate it if someone could help me with that.Thank you very much for your help!

Hello, we have a system that consists of 12 VL53L7CX sensors each, on 4 different I2C busses and we are using an I2C address translators (LTC4316CDD) to address them all without needing to change their address dynamically. We are using ST's ULD (ultra-light driver) to interface with them.One challenge we are running into during application development, is that after we initialize all 12 sensors and start ranging, if we restart the microcontroller application we are sometimes unable to re-initialize the sensors - the `vl53l7cx_init()` call fails somewhere.Our current test setup makes it difficult to power cycle just the sensors because doing so also power cycles the host computer.My questions are:Is there an I2C register (or set of registers) that I can access to check if the sensor has been previously configured and if it's actively ranging? This would be helpful to avoid spending time re-initializing if we don't need to.Also, is there an I2C register that I can write to "reset" the se

Hello, I am currently trying to write code for the I2C communication with the VL53L1-SATEL board. I was trying to confirm that the I2C was working by reading some registers mentioned in the VL53L1 Datasheet, those being 0xC0, 0xC1, 0xC2, 0x51, and 0x61. I was never able to get actual data from these registers. I have since found some example code that when I run I am able to read distance but when I try to read those registers in the example code I still am unable to get any of the data that is meant to be in those registers and some I get just zero while others I get the wrong values. I am wondering if the info in the datasheet about those registers is wrong or if I am doing something wrong along the way. A important note is that I am also reading from 0x010F using the same command which outputs 234, 0xEA in hex, but I am unable to see anywhere if that info is right or wrong.  Thanks, Carson

in interrupt read program as follow 

Hi,I would like to know if the STSW-IMG041 code that is flashed into the device is available somewhere. My goal would be to use the same code but on a custom board to verify that the sensor is working properly.Thank you! 

I wrote the i2c communication code for the vl53l1x ULD API in vl53l1_platform.c and i2c32.c, and called the API in tof.c to initialize vl53l1. The VL53L1X_GetSensorId function can correctly read 0xEACC, but the VL53L1X_CheckForDataReady function always shows that the distance measurement is not completed, and at the same time, the VL53L1X_GetDistance also cannot read the distance measurement result.

Hello everyone, I would like to know if someone has ever tried to couple those two hardware components together?I am currently using the STM32C092RC board to build an FD-CAN network, and I would like to exchange some real data — or more explicitly, to simulate some real scenarios. Since the C092RC has an UNO shield connector, I thought I could easily use the VL53L8CX sensor on it.But the platform.h file, which normally communicates with the hardware, is made for the STM32F4xx family. So, is there any way to get the correct platform version for the STM32C0xx family? Has anyone ever tried this?  

Hi everyone,I’m having issues with the VL53L7CHV0GC ToF sensor drivers on Linux. The kernel module loads fine, but I can’t read any data using the userspace part. When I try to use the driver completely in userspace mode, it reports that it can’t find the device on the bus, even though the device is physically present and visible on I²C.I use official sources from STMicroelectronics website.Has anyone encountered the same issue or maybe has a newer / fixed version of these drivers that works correctly?If not, at least a detailed datasheet with the I²C register description - which also doesn’t seem to be available online - would be really helpful, so we have a chance to write our own drivers.Thanks in advance!

Hello community,I'm new to using this sensor, but based on some initial testing I'm hoping it's a good fit for my application. I was hoping to get some general opinions/guidance on the approach I'm planning, so any tips/feedback are greatly appreciated!My application:Collect some reference data for a small (~1.5x1.5m) room, with the sensor mounted fixed in the middle of the ceiling, about 2.75m from the floor, looking straight down to the room. There are some stationary objects in the room that will be part of this reference 'scene' that is being captured. It is a fully enclosed room (expected to have no sunlight when the door is closed), and we can turn the lights off, so there should be little to no ambient light.I'd like to be able to periodically rescan the room and look for any differences to the reference 'scene' -- essentially looking for unexpected objects. It is not a very time sensitive application, so any filtering etc that might be helpful in making this determination is fi

I have broken the SATEL-VL53L8 into its small PCB form and have connected it with flying wires (about a foot in length) to the NUCLEO-53L8A1A breakout board. It is wired in the I2C configuration and the J9 connector is also set to I2C.When I open up the Smart Presence Detection software, I only get a sparce reading of different array values, which I believe are coming from the ToF located on the NUCLEO board and not the SATEL. This looks to me like some sort of comms issue, but I am not sure how to tackle it.Has anyone experienced this issue and know how to rectify it?Thanks in advance! 

Hi All, I've been using the VL53L1 sensor for drone height control, and the results have been quite good- however, the environment it is used in has plastic skylights with poor IR blocking. This causes unstable readings in direct sunlight. Some of the IR is blocked, and as such this is tolerable but undesirable. Would changing to the VL53L4CX improve this? Ranging up to 3m is required. Will the L4CX broadly outperform the L1CD in most situations?   Thanks!

Hello, I am using the VD6283TX45/1 to develop a device and now have a question to consult. Due to my insufficiently careful reading of the data sheet during the initial design phase, I connected the I2C pins of this device to an I2C bus where the pull-up voltage of the bus is 3.3V. Later, when I checked the data sheet, I noticed that the reference design uses a 1.8V pull-up for the connection. However, the board with the device connected to the 3.3V pull-up has passed tests and the VD6283TX45/1 is operating normally for now. I am currently concerned about whether this connection method can ensure reliable operation in the long run. Or do I need to modify the circuit to implement level conversion for the I2C pull-up voltage?

Has anyone seen documentation or done optical power measurements for VL53L4CD? I’m trying to find the radiant energy or optical power output of this low power time-of-flight device. (I only succeed to find a graph showing the relative emitted power in their datasheet)

Hi    follow  can  make offset calibration？Place the object 14cm away .Must be in a dark environment?     follow can make Crosstalk calibration?   Place the object 60cm away. my coverglass like follow,The measured distance seems very short. How can I solve this problem? follow is my read out data          

 Hi, we would like to use the VL53L7CH on Linux 6.12.Standard kernel interfaces are required:IIO/hwmon subsystems and regmap — no proprietary ioctl/miscdevice interface.Is an IIO-based driver for the VL53L7CH already provided or planned for upstream/mainline integration?If available, the corresponding patches and Device Tree bindings would be appreciated.Best regards,Markus

Hello ST：       VL6180X has been discontinued, but our older equipment still uses it. We hope to obtain the IEC 60825-1 CB test certificate to prove its Class 1 rating. However, this certificate is not available on ST's official website, whereas it is provided on the VL53L4CD product page. Could you please provide support for this?"

Hi, We have incorporated a vl53l4cd into our product. We wish to measure 0 to 100mm with a resolution of 1mm, and an update rate of at most 1 second.We have set the vl53l4cd 19mm back from front measurement face (so we need to actually measure 19 to 119mm).We placed statically on a desk I find, the variation of the readings to be from 33 to 40mm.It does vary from reading to reading but the trend also varies so I cannot simply average it out.Is this was what I should expect?I attached a screenshot of what I find. This is against a light teak table. I would say is appears to better when against something black.Is there any recommendations for settings for getting the best performance between 19 and 59mm in terms of stability (The inaccuracies are less significant beyond that)?kind regardsLiam

Hi,        vl53l0x in continue mode ,how to read data_status and in time mode how to set time and read data and data_status?               thanks

 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 __delay_us(100); // wait for measurement to complete I2C_Master_RepeatedStart(); I2C_Master_Write(0

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 The camera is also recognized at startup (dmesg as well), as confirmed by the output of v4l2-ctl --list-devices. I have also read through several forum threads on this topic and have already tried many of the suggested troubleshooting steps, but the issue persists.Could you please help me identify what might be causing the problem and how to resolve it? Additionally, I noticed the following behavior:During setup, I only ran sudo apt update but did not perform a full upgrade.After running a full system update/upgrade later, some Ras

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 schematic, it includes a XC6206P332MR regulator that provides 3.3 V @ 200 mA.So my question is:Is this voltage drop caused by a large current consumption from the VL53L0X during ranging operations, or could there be another cause (e.g. the onboard regulator, wiring, or setup)? Thanks in advance for your help!

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