Imaging (sensors)

I was trying to implement VL53L1 TOF sensor on VL53L1-SATEL breakout board with STM Nucleo C071RB development board using STSW IMG009 VL53L1X Ultra Lite Driver.By following the example after init, boot, setup and startRanging I called VL53L1X_CheckForDataReady(), which always returned error -13 - VL53L1_ERROR_CONTROL_INTERFACE . After extensive checking of I2C interface I figured out that this error occurs when VL53L1X_GetInterruptPolarity() is called (within checkForDataReady or independently) when ranging is active. If ranging is stopped, GetInterruptPolarity() works just fine.My solution was to write my own library of required functions that further rely on VL53L1X_api. Before start ranging, I read the Interrupt Polarity, store it locally and then use modified checkForDataReady() function, which uses stored InterruptPolarity to check if new data is available.Has anyone else noticed such behaviour?This also connects to topics:https://community.st.com/t5/

Hi, I am having trouble with the interrupt. I manange to coummunicate via I2C and read Model ID and Type. But my problem is that i can't initiate the sensor via the VL53L1X_SensorInit() function in the Ultra Lite Driver I'm using. When I debug I see that the program gets stuck in the wait for new data from the sensor in VL53L1X_CheckForDataReady(). In this function the polarity of the interrupt is read as 0x00 and the GPIO__TIO_HV_STATUS as 0x03. Bit 0 in GPIO__TIO_HV_STATUS and the interrupt polarity must be equal for the program to interpret this as data is ready (i.e. a measurement has been made and can be read). A strange thing is that the interrupt polarity is 0x00 (active low) by default even if the manual says active high. And if I try to set the polarity to active high using the dedicated function it will still be active low. If I plug in a logic analyzer I can see that the GPIO1 (Interrupt output) from the sensor is high all the time. I then tested the sensor wi

Hello Developers, Hello ST-Team,unfortunately we are stuck in implementing VL53L5CX on our PIC18. We see a strange clock stretching behaviour of the sensor and problem downloading the firmware.We implemented Ultra Lite Driver 2.0.0 in an application on a Microchip PIC18F57Q43 (CURIOSITY NANO Evaluation Kit) using Example_1_ranging_basic.c from the examples folder.After the adjustments of platform.c and modification of the download routine to download the 86 KB firmware in chunks, we got the following odd behaviour:- The function  vl53l5cx_is_alive(&Dev, &isAlive); returns SUCCESS = No error!- The function vl53l5cx_init(&Dev); fails.Sending the first package of data seem to be successfull. When trying to start sending the second chunk of data the sensor refuses to communicate with the MCU by returning NACK for any further byte.Has anybody an idea why the sensor behaves like that and why the sensor stretches the clock line?Even while stretchin SCL for each byte

Hi there!I'd like to use the STEVAL-CAM-M01 P-board to evaluate the VD55G0 BrightSense image sensor with the Discovery kit for the STM32N6 MCU (STM32N6570-DK). The discovery kit does have a camera connector, however, looking at the schematics it seems that the polarity of the CSI data and clock lines is swapped compared to the P-board. Everything else looks fine.Is it possible to use the P-Board with the Discovery kit without destroying either of the two? ST's marketing material (slide 33) seems to suggest it is possible but the schematics are unclear. Note that a similar question has been asked in the MCU forum, but it was suggested to ask in this forum to be sure. Also note that I'm not asking about software driver support here, only hardware compatibility.Camera connector on STM32N6 discovery kit: Connector on P-board:Thanks a lot!Michael

Hi, I'm currently facing a challenge with the VD55G1 driver. I've designed my own minimal system board for the N6 and VD55G1, using MIPI CSI for communication. When attempting to drive the VD55G1, I can enter the stream mode but no data is being transmitted (the N6 interrupt is not triggered). Upon reading the stream_fsm register of the VD55G1, I noticed it remains stuck in the dark task, with the REPEAT_COUNT, CURRENT_CONTEXT, and NEXT_CONTEXT values consistently showing 0 0 1.Here is my codetestfsm means getting the value of the stream_fsm register.I would greatly appreciate your prompt assistance in resolving this issue. Thank you.

I am using the STSW-IMG501 software v1.1.1 with the STEVAL-EVK-U0I connected to a STEVAL-56G3MAI (the S-board evaluation module for the VD56G3).  In the EVK software, I am using the built-in script generation tool to upload different register configuration sets and test them.  However, I find that uploading the following script will cause the SW to fail to read a frame sequence:$SCRIPT SetBank(0x20); WriteAutoIncrement(0x0220, 0x00, 0x1b, 0xb7, 0x00); //SENSOR_SETTINGS.EXT_CLOCK = 12000000 WriteAutoIncrement(0x0224, 0x02); //SENSOR_SETTINGS.CLK_PLL_PREDIV = 2 WriteAutoIncrement(0x0226, 0x86); //SENSOR_SETTINGS.CLK_SYS_PLL_MULT = 134 WriteAutoIncrement(0x0227, 0x05); //SENSOR_SETTINGS.VT_CLK_DIV = 5 WriteAutoIncrement(0x0300, 0xd4, 0x04); //STREAM_STATICS.LINE_LENGTH = 1236 WriteAutoIncrement(0x0304, 0x00, 0x00); //STREAM_STATICS.X_START = 0 WriteAutoIncrement(0x0306, 0x63, 0x04); //STREAM_STATICS.X_END = 1124 WriteAutoIncrement(0x030a, 0x08); //STREAM_STATICS.FORMAT_CTRL

Hello ST team,Thank you very much for your previous help with debugging TOF. We have now selected the TOFL1CX and TOFL1CB as our distance measurement sensors. However, we have encountered a problem: both TOF models have already been soldered onto the PCB, and we cannot tell which one is TOFL1CX and which one is TOFL1CB. We would like to distinguish the two TOFs by reading their IDs, but for some reason, the IDs read out are identical. Is there any way to distinguish between these two TOF models? Their appearance also seems identical.At the same time, I am a bit confused: are these two TOFs considered as high-end and low-end versions? According to the datasheet, the main difference is the measurement range, and TOFL1CX does not support multi-target detection (but I found that running TOFL1CB’s code on the TOFL1CX also works and provides multi-target output), whereas TOFL1CB officially supports multi-target.Thank you in advance for your reply.Below is the code segment I used to get the I

Hi @John E KVAM ... I have seen several discussions about best way to use multiple VL53L4CX sensors, and I've appreciated your responses.  ("Every reboot is its own adventure!").  I'm currently implementing an unusual setup that has 5 of these sensors that could conceivably interfere with one another - we are trying to get our mounting and the view-cones to be as independent as possible, but it can't be guaranteed.   We are using the bare STM32duino library on an ESP32 (Arduino/C++) micro, which is also doing many other things.Given the physical setup of our system, it is difficult to run single lines to all the chips for XSHUT.  We would very much like to work only with the simple STEMMA/QT-style 4-conductor I2C cabling.   For this reason, we've opted to use an I2C multiplexer, rather than changing the addresses of the chips.So my questions are: 1. Is there an I2C command to tell the chip to reset itself?   In our projec

Dear ST Support Team,I hope this message finds you well.I am currently working on a project where I aim to implement gesture recognition using the VL53L5CX sensor. However, I noticed in the official documentation that the supported cores for gesture recognition do not include the M55 (which is the core of my STM32N657 microcontroller).Could you please advise if there are alternative methods to achieve gesture recognition with the VL53L5CX on this platform? For example:Are there any software libraries or algorithms compatible with the STM32N657 that I could utilize?Would it be possible to port the existing gesture recognition functionality to the M55 core?Are there other recommended approaches or workarounds to accomplish this?I would greatly appreciate any guidance or resources you could provide to help me proceed with this implementation.Thank you in advance for your time and support.Best regards,dw1

Hello Everyone,We have a custom board that utilizes 10 x VL53L4CX sensors, length of board is about 66cm. For context I am using an NRF54L15 with Zephyr. On bootup they are all configured with a different address and an attempt is made to calibrate the sensors as well. I am using the I have been testing for a few weeks now and I am constantly running into initialization issues, all revolving around communication to sensors, especially when I am trying to run through a calibration on the sensor. I have tried different calibration methods, but all result in errors. And if I comment out the calibration I would get a Hardware Failure error after a few reads from the sensor. My initialization code flow is as follows: Shutdown all sensors -> Boot sensor N -> change I2C address -> Wait Device Booted-> DataInit -> PerformRefSpadManagement-> SetOffsetCorrectionMode(STANDARD)->PerformOffsetZeroDistanceCalibration()-> GetDeviceInfo()->SetTuningParame

Hi, I'm experimenting with VL53L4ED. it suits by requirements except that is has only 18° FoV. Is there any way to increase the FoV (upto120°) using a lens may be without hampering the laser class?

Hi everyone, I have been struggling to work with VL53L5CX on my NRF board using Zephyr. I used the VL53L5CX_ULD_driver_2.0.1 API and changed the platform.cpp. So far, what my problem is as follows:Failed on the vl53l5cx_init, because after the firmware is successfully flashed the  _vl53l5cx_poll_for_answer always gets the wrong value as attached image Since _vl53l5cx_poll_for_answer calls VL53L5CX_RdMulti, I check whether my function is working correctly with this (https://community.st.com/t5/imaging-sensors/vl53l5cx-init-fails-in-vl53l5cx-poll-for-mcu-boot/m-p/614318/highlight/true#M3328 ). The results are that the data did not match the desired value, but it works for several reasons.My code is as follows:uint8_t VL53L5CX_WrMulti(VL53L5CX_Platform *sensor, uint16_t reg, uint8_t *p_values, uint32_t size) { uint8_t status = VL53L5CX_STATUS_OK; uint16_t current_address = reg; // Initialize current address uint32_t remaining_size

    Since we require long-distance detection, we have employed both Ranging Mode and Long Distance Mode. Additionally, due to the use of battery power, power saving is essential. Consequently, we acquire the distance reading after just two sampling cycles.    When the distance is less than 3 meters, we can successfully obtain readings without issue. However, when the distance exceeds 3 meters, acquiring a reading with only two sampling cycles becomes impossible. Instead, it requires 10 sampling cycles, or even several dozen cycles, to obtain a distance measurement. This significantly increases power consumption.    Why are multiple measurements required to detect objects beyond 3 meters? Can this be improved?    The software version we are using is STSW-IMG019: VL53L1CB_BareDriver_6.6.18.2652.    Thank you for your help.

Hi everyone,I am currently working with the STM32N6570-DK board and would like to integrate the STEVAL-56G3MAI camera module with it. The camera's overview page mentions that it supports the STM32N6 series. However, I have been unable to locate any STM32N6 header files to facilitate this integration.I did come across the STSW-IMG502 software package, which also lists STM32N6 compatibility, but it only includes drivers for Raspberry Pi and Linux platforms.I would greatly appreciate any guidance or resources (e.g., example projects, driver libraries) that could help me successfully interface this camera with the STM32N6570-DK board.Thank you in advance for your support.

We have designed and shipped a water level sensor based on the VL53L1X. It works well in most situations, but we have one issue in a particularly large tank (3m tall, 2m diameter). I believe this is due to reflections in the tank. It is a black tank, but the surface is glossy.I thought reducing the FoV might help with reflections, but the datasheet states this reduces range, but I can't really understand why. If the laser is pulsing light at the same power, and that light falls back on the SPAD, why does only looking at the center diodes affect range?I think I'm misunderstanding how it works so I thought I would ask. I'm not sure there is much I can do in this situation and it may just be unsuitable for this particular tank.Thanks

I am currently using a VL53L1X Sensor to read a distance in the range of 40cm to 130cm. I initialized the Sensor to work in the short distance mode, so the range should not be a problem. I used the VL53L1X_calibration library to get the values for offset and xtalk. In the Datasheet i read that with the function VL53L1X_GetDistance() the distance should be returned in mm. The value i get returned from that function does change when i change the physically measured distance, but it is not the expected value. For example when i want to measure a distance of 1m i get a value of about 55500. Also the measurement change on the same height in a range of 1000. For the offset and xtalk calibration i set the physical distance to 1m and gave that as a parameter in the function as 1000(mm). I copied the values i got from the function to the function setoffset and setxtalk. To calibrate i used the following diagramm:And my init in my software looks like

Hi,I was wondering if there were plans to make drivers for the ST BrightSense image sensors available for the ST STM32N6 Series μCs (these could be bare metal, FreeRTOS, ThreadX or Zephyr drivers) or for ST STM32MP2 Series SoMs (in the form of libcamera drivers)?I heard that drivers for the VD66GY image sensor are planned for the STM32N6 Series μCs but I wasn't sure about the other BrightSense image sensors.Providing drivers for the ST BrightSense image sensors for the STM32N6 Series μCs and STM32MP2 Series SoCs would allow ST customers to fully leverage the enormous power of both ST image sensors and the leading ISP and AI capabilities of STM32N6 and STM32MP2 while developing a solution entirely within the ST ecosystem. Having drivers provided by ST instead of coding our own drivers would enormously speed route to market and reduce risk.Thank you very much for your help.Will

Does ST supports multiple slave devices for single spi, I want to use mutiple VL53l8cx sensors on single spi bus using multiple chip select. I am facing challenge to run more than two slave devices (VL53l8cx sensors). I am getting failure in vl53l8cx_init() call, means failing to upload firmware in VL53l8cx sensors.

What are the best practices for controlling the exposure time of the VD55G1 in Linux?

There are three types of sensor in vl53l8 family, VL53L8CA, VL53L8CH and VL53L8CX. It seems like sensor in X-NCULEO-53L8A1 is VL53L8CA, but the relevant documents and resources are very few. so what should i read as a reference? what is the diffrence among the three sensors?

Dear all,I'm trying to reproduce the steps of STSW-IMG051 smart cup detection Example. Running the CupDetectEVK.exe, I get the errors you see on the screenshots. I tried to check whether the sensor itself is working by running the STSW-IMG043 example, and I succeeded. I'm sure the hardware is working fine, but from the errors I see, the .bin supplied in the IMG051 example and the EVK software that comes with it don't seem to be compatible.There are no source files available for either, so I can't dig into debugging it on my own, hence I'm turning to this portal for help. Thanks! 

Hello everybody!I would really appreciate if you find some time to help me with my project. I want to take distance data from VL53L5CX module, which I have connected with Nucleo L476RG board exactly as in the picture uploaded. I just want this data to be printed in serial port, 4x4, 8x8 matrix would be great. Need some real help step by step, also with the scripts in CubeIDE as I am a new enthusiast in this whole thing.Thanks in advance,EriolThese are the exact pin connections(L476RG board)

I am trying to build the libcamera from the source files provided in "en.STSW-IMG502_RPI.zip" and I am getting the following error. I have cloned https://github.com/raspberrypi/libcamera.git and confirmed I can successfully build it to verify I have installed all the necessary tools.Here is the output from the meson setup command:$ sudo meson setup build --buildtype=release -Dpipelines=rpi/vc4,rpi/pisp -Dipas=rpi/vc4,rpi/ pisp -Dv4l2=enabled -Dgstreamer=disabled -Dtest=false -Dlc-compliance=disabled -Dcam=disabled -Dqcam=disabled -Ddocumentation=disabled -Dpycamera=enabled The Meson build system Version: 1.5.1 Source dir: /home/chad/stcam/STSW-IMG502_RPI/STSW-IMG502_RPI_v.0.5.0/libcamera0.5_0.5.0+rpt20250429+st20250606/src Build dir: /home/chad/stcam/STSW-IMG502_RPI/STSW-IMG502_RPI_v.0.5.0/libcamera0.5_0.5.0+rpt20250429+st20250606/src/build Build type: native build Project name: libcamera Project version: 0.5.0 C compiler for the host machine: cc (gcc 12.2.0 "cc (Debian 12.2.0-14+

Hello everyone,I am currently working with the VL53L4CD sensor using the ULP (Ultra Low Power) driver. My goal is to use it for presence detection and distance measurement while keeping power consumption as low as possible.I understand that using very low power settings will naturally reduce performance. However, with a configuration of macro period = 1 and ROI = 4x4, the results are extremely inaccurate, as shown in the attached image (distance_plot_macro_1_ROI_4.png).To give a specific example:An object placed at 50mm is detected at a distance ranging from 90mm to 230mm. The readings are very inconsistent with each measurement.Conversely, when the sensor reports a distance of 100mm, the object's true position could be anywhere between 10mm and 80mm. This makes the data unreliable for our application.I am aware that increasing the settings improves performance significantly. As you can see from the other attachments (distance_plot_macro_10_ROI_16.png and distance_plot_macro_100_ROI_16

Hardware environment: STM32F405 chip and VL53L5CX-SATEL module;Software environment: Based on the STSW-IMG023 sample code, the code is ported to KEIL5 for use;Problem description: After completing the sensor initialization (ranging frequency 10hz, ranging continuous mode), use polling to read data, call the vl53l5cx_check_data_ready function to read the sensor data: 0x00, 0x03, 0x01, 0x0D, these four values ​​are considered data not ready after judgment.I want to know what these four values ​​mean? I checked the documents I know (DS13754, um2884, etc.) and did not find the relevant register description.Why does this happen, and how should I debug?Thank you!