Imaging (sensors)

Hi,i've been posting here a few times to get a VL53L4CX to work. I've had success so far, but the latest iteration of my little PCB is really giving me troubles.When i apply power to my board (via an esp board) it stops working (the esp32 board). It feels like i've created a short, but i can't seem to measure that on the board.I do solder this myself, so there could be a short under the sensor itself (i just use a heat gun from the bottom after tinning the pads). I've done this a few times now and i'm quite sure it's not the case... so there must be an issue with my board layout/design.It would be great if somebody could review this for me?http://cyclops.nettrends.nl/stuff/tofboard.tar.gz

I am guessing there is nothing that can be done about this, but I thought I'd post about it. I got the VL53L8CH because it has better bin resolution than the VL53L3CX, which I hoped to use to distinguish between objects at different ranges that are closer to one another. It is somewhat better at that, but not as much as I had hoped. The reason for this is the signal spread. The emitter's signal arrives as a peak that spreads over about 10 bins. At 3.75 cm per bin, that means a signal spreads over 37.5 cm. It's not actually as bad as that, since the signal follows a normal distribution, but it does mean that signals for objects close to one another will overlap and distinguishing objects separated by only one to three bin widths is quite difficult.Don't get me wrong, this chip is amazing, and the people at STMicroelectronics have done wonders in giving us 3.75 cm bin resolution when the signal is traveling at the speed of light. It just may be important for the applications of

Hello everyone, I am currently working with the VL53L8CX sensor to explore solutions for a specific use case. In particular, I am trying to detect glass material using the CNH (Compacted Normalized Histogram) data—more about this can be found under the topic: Artificial Intelligence Enabler .From my research, I understand that the sensor generates a total of 121 histogram bins. However, due to constraints such as memory limitations, only 18 or 24 bins can be accessed, depending on the configuration used.I s

Hello! I've designed a custom PCB very similar to other breakout boards on the market, because there are additional components I want to fit in a small package alongside the VL53L1X sensor. When testing my PCB, the sensor does not initialize. I've been using the same library that works with other breakout boards. The PCB is supplied with 5V from an Arduino Nano, stepped down to 2.8V with an LDO and then logic shifted with two BSS138's to the SDA and SCL pins.  At first I thought it was an I2C timing issue, so I made the pullups stronger on the bus (~3.6k) but that was unsuccessful. I've done a continuity test on all components. I'm wondering if there's anything I've missed or if there's a chance something went wrong in manufacturing. I can provide the PCB layout if needed.  Any help is appreciated, this is one of my first PCB designs! Thank you!

Hi all,I'm currently developing test code for the VL53L1 ToF sensor using STM32CubeIDE, and I'm aiming to optimize the sensor's performance for close-range measurements — specifically in the 10mm to 200mm range — with a target accuracy of around 1–2%.I'm currently using the bare driver files provided by ST, which I’ve manually integrated into my STM32 project.I'm aware of the various distance modes (Short, Medium, Long) offered by the sensor, and I plan to experiment with them. From what I understand, the Short distance mode is generally preferred for close ranges due to better ambient light immunity and reduced signal crosstalk. I'm also considering manually configuring a Region of Interest (ROI) centered around the sensor’s optical center to

HI folks.I would like to wake up my ESP8266 using an interrupt from the VL53L0X sensor.I have configured the sensor to use both threshold detection and to trigger an interrupt. I tested whether the interrupt is being triggered, and it is— the GPIO pin goes from HIGH to LOW when the threshold is reached. However, I noticed that the GPIO remains LOW until the interrupt flag is cleared. If I connect this GPIO pin directly to the RST pin of the ESP8266, the program will never run because the RST pin stays LOW.To solve this, I implemented a pulse generator that triggers on the falling edge of the GPIO signal.Here is the circuit I implemented:

Hello,I am using the VD56G3 connected to a STEVAL-CAM-M0l1.  There is a very small ribbon cable between the sensor and the connector on the CAM-M0l1 - roughly 5mm.  I am working on a mock-up of some smart glasses where I'd like to extend that cable to a considerably longer length - ideally 1 meter.  Is there a way to create an extension to this cable or a product that has a lengthened connection?I know that there is also a ribbon cable from the STEVAL-CAM-M0l1 which could easily be lengthened, unfortunately, the form factor of the STEVAL-CAM-M0l1 is not suitable for my mock-up.Any suggestions/recommendations as to how to lengthen this connection along with any pitfalls would be appreciated. Thanks,Dan Luka

Hi!I have a question about calibrating vl53L4CD and using a coverglass. I am doing experiments with a sample flat panel from Gilysmo, and I have noticed that if the panel is 2-3mm from the sensor, the calibration doesn't compensate for it. It looks like it just ranges to the glass and that's it. Is that normal? What is the maximum distance the glass should be from the sensor? Or perhaps I am doing something wrong?Thanks!

Hello Team,                I am finding the sensor which have the up to 15 meter range.                                i am using this sensor in my water level detection project so according to suggest me the sensor.  Thanks and regard'sASHISH K.

Hello everyone,We recently tested the VL53L7CX and ran across an issue with very high reflective fabrics. Here are two images of such fabric. The first is a picture taken with flash light off, second picture is taken with flash light on. From the moment I wear this and come in front of the sensor I "disappear", the sensor also outputs status 255. Is there a way to handle this? Is there past experience with such items?  

Hi, i am trying to connect the nrf54L15 with the VL53L4CD sensor. I am having trouble with library and the code. Struggling with connecting the nrf54L15 to the sensor in the different libraries. Are you able to share the different register adresses for the VL53L4CD sensor? Do you have an examples using the nrf54L15 and or device tree with the VL53L4CD?

Hello,I am using a VL53L0X sensor with a NUCLEO-64 F411 board, and I am trying to achieve accurate measurements and low power consumption for the development of a LiDAR system.I have one problem and one question: Problem:The measurements are a bit inaccurate. For example, when I measure an object at a real distance of 5 cm, the sensor detects it at around 7 cm. Also, for some objects beyond 20–25 cm, the readings become irregular. Question:I would like to use the sensor with interrupts, but the User Manual for the API is not very clear on how to implement the interrupt feature.I am attaching my main.c file and the library I am using, which includes the API and its .h file. Thank you very much for your help! //This is the main.c /* USER CODE BEGIN Header */ /** *********************

I know the VD55H1 is in preview phase and might be difficult to get it from ST. Although from the you tube videos it seems it is ready to be requested. Do you know what is the status to get one sensor? And if maybe is there any design house offering a module for testing it?

Hello,I am currently working on integrating the Smart Presence Detection (SPD) library on a Raspberry Pi Pico.Using the programming guide, I have managed to run the SPD algorithm, but I cannot get the “Approach” state to be detected correctly— it switches to “Presence” almost immediately.I believe the key is to tune the parameters contained in the Params_t structure, but I have not been able to find detailed explanations for each field.Could you please let me know where I can find a complete description of every parameter in Params_t, or any document that explains their effect on the algorithm?Thank you for your support.

Hi Team,We have the two boards as mentioned below.                      The Code generated in Cube MX is for the F401RETX(which configures the MCU inside VL53L8CX)

Hello Everyone, I am currently using the vl53lmz_uld_api  tto process data measured by the VL53L8CX sensor. I have also used the "example_12_cnh_data" to retrieve data from my sensor. However, the incoming data seems completely incorrect, and I don't know where the issue lies. When I hold my sensor 20-25 cm in front of an obstacle, I receive highly unreasonable data: Zone : 40, Status : 0, Distance : 1383 mm Zone : 41, Status : 13, Distance : 1892 mm Zone : 42, Status : 5, Distance : 1371 mm Zone : 43, Status : 5, Distance : 1367 mm Zone : 44, Status : 5, Distance : 1347 mm Zone : 45, Status : 5, Distance : 1370 mm Zone : 46, Status : 5, Distance : 2448 mm Zone : 47, Status : 9, Distance : 2262 mm Zone : 48, Status : 4, Distance : 2977 mm Zone : 49, Status : 0, Distance : 1398 mm Zone : 50, Status : 5,

Hello  everyone,  I started learning programming on the STM32 ecosystem a few weeks ago, and I'm currently trying to get data from the VL53L8CX sensor using the NUCLEO-F401RE expansion boards and the vl53l8cx_api. I wrote a small program based on what I have seen in other projects, but my code doesn't work at all. While debugging, I discovered that the program jumps to the HardFault_Handler() function at this line in vl53l8cx_init().   status |= VL53L8CX_WrByte(&(p_dev->platform), 0x7fff, 0x00); Here is the essential part of my code maybe someone have any solution: #include "vl53l8cx_api.h" #include "main.h" #include "stm32f4xx_hal.h" #include <stdio.h> // Private variables --------------------------------------------------------- static VL53L8CX_Configuration tof_dev; // Sensor-Konfiguration static VL53L8CX_ResultsData r

Hello Everyone,I am currently working on a project to determine if it is possible to differentiate between a glass cup and other types of cups using VL53L8CX sensor data histograms, and also to detect the fill level. I have already collected data from the sensor using Example 12 provided in the Ultra Lite Driver, and I have written a small Python script to visualize my data.My first challenge is switching between the 4x4 histogram data format and the 8x8 format. The second challenge is interpreting the incoming bins_data to understand the differences between, for example, a ceramic cup (which is already possible using just the distance data) and an empty glass cup (using the histogram data to make a distinction, detect the edge, and determine the fill level).  Here below is my code stmIDE  Code//__________MY CODE ___________ p_dev.platform.address = 0x52; Reset_Sensor(); if (status != VL53LMZ_STATUS_OK)

I'm using the VL53L1X in the Arduino environment. During the initialization phase, I can read the device address as 0x29, and the device ID is EACC — so there's no issue with that.However, when I try to read the register VL53L1_FIRMWARE__SYSTEM_STATUS, a problem occurs — its value is not 0x01 as expected.I printed out the register value and it shows 2.Here's that section of the code: uint8_t system_status = readReg(VL53L1_FIRMWARE__SYSTEM_STATUS);SerialUSB.print("System Status: ");SerialUSB.println(system_status, HEX);  while

I am putting together a water level sensor based on the vl53l4ed. The device will be in an outdoors setting with wild swings in environmental conditions. I am having hard time to design a cover / cover glass system for the TOF sensor. I have now concluded that it would be best to purchase a pre-made cover glass assembly for this sensor.  I expect accumulation of dust and other contaminants on the cover glass over time so I would prefer a zero calibration option with individual emitter and receiver covers separated by a divider. Are there commercial cover glass options available for the vl53l4ed model? I found a few options on the ST website but none for the vl53l4ed. Also, are there vendors in the USA who carry these cover glasses? If available, the vendor has to be NDAA-compliant. Thanks

HI,Could somebody tell me how to configure and access VL53L1 histogram data in detail.Thank you

Hello, Apologies in advance for the length of this post. I am looking for some advice as I am working on getting a cpp based callback for the VL53L4CD sensor, to do this I have written a file which should perform all the same setup as the driver provided however I am encountering a strange error that I cannot understand.Link to Github with Code, please see: real_time_drivers/VL53L4CD/VL53L4CD_LinuxDriver_V2.3.2/user/uld-driver for all relevant codeWhen I run my own file first, it sets the sensor to always return a status of two even if I then run the example executable (menu) provided as part of the the driver example this also returns a status of two.  HOWEVER, if I run these in the other order the sensor range is printed perfectly by my own program. This status will remain the same for any executable ran after

I recently purchased a VL53L7CX and VL53L8CX, so I wanted to test the Motion Indicator functionality for each zone to show if the targets moved and how they moved via SPD of the software by STM except that there, when two people present themselves in front of the sensor, we only see one personHow to do it?

Hi Team,  Could you please share the detailed function of INT and SYNC in VL53L8CXV0GC/1?  We would probably use one sensor or two. If case of one sensor SYNC input doesn't add any value to the design. If two sensor used they'll probably share the proximity data(Just confirms if the object present or not) will it a have significance there.    Regards,  Mukesh

Maybe someone can help me. I bought five TOF050C-VL6180X time-of-flight (TOF) sensors, which also work with the Adafruit_VL6180X library, but they behave completely differently:Two:At a distance of 30 mm, the script shows: 0 mmAt a distance of less than 30 mm, the script shows: VL6180X_ERROR_RAWUFLOW "Raw reading underflow"One:At a distance of 20 mm, the script shows: 0 mmAt a distance of less than 20 mm, the script shows: VL6180X_ERROR_RAWUFLOW "Raw reading underflow"The other two: The script shows approximately the correct distance, and you can also Get unlimited close without triggering the "raw reading underflow."However, for my project, I need four sensors that are calibrated approximately the same. What can I do? Does anyone have any ideas?