Imaging (sensors)

 Hi all, I'm back with another question re: our 5-TOF setup (VL53L4CX x 5, all 'looking' out of the centre of a spherical sculpture, trying to detect and interpret people approaching and interacting with it).I posted earlier about trying to multiplex these 5 sensors to avoid crosstalk, and that sort-of-worked but introduced enough lag that it wasn't worth it -- we have carefully managed the positioning of the cones and I don't think we are getting much crosstalk, or at least, once we started throwing out rangeStatus 4, 12, and 11 we got pretty good results.  We are basically only using rangeStatus 0 readings now.Further note: we are looking for targets at about .75-2.5m, so right at the edge of where these results seem reliable.My question is:I'm seeing a bit of 'bouncing' where on one read a sensor

I'm trying to port the VL53L0X library for use with the RP Pico W for academic reasons, but I can't map the calls between the VL53L0X SDK and the RP Pico W SDK. For example, the function int32_t VL53L0X_read_multi(uint8_t address, uint8_t index, uint8_t *pdata, int32_t count) would theoretically need to be adjusted to call the function int i2c_read_blocking(i2c_inst_t *i2c, uint8_t addr, uint8_t *dst, size_t len, bool nostop) Attempt to read specified number of bytes from address, blocking. Am I right? Or should it be another way?Thanks

Hi, I have teh VD55G1 connected to UCM-IMX8m PLUS sbev from compulab Here is the links to the SBC : https://www.compulab.com/products/computer-on-modules/ucm-imx8m-plus-nxp-i-mx-8m-plus-som-system-on-module-computer/ I am compiling the driver with my kernel for that SBC and it loads and registers the device accurately. I would like to start the stream with the camera using v4l2-ctl but it give me a negotiation error. The logs attached is what i see when i try to start the video.  Is there anything that I should attempt to fix this issue?   

I use the VL53L1X TOF- Sensor on an Arduino Mega.With just the Sensors, everything works well.But when I try to read from Serial1 (and I tried Serial2 and 3 as well) I do not receive any Data from the SerialPort.Without the Sensors the SerialPorts work well.I do not undestand, where this comes from. Has anyone some advice for me?Thanks!!

Hello,We have an issue with the VL53L7CX. We are using 2.8V for both IOVDD and AVDD. We have 4x TOF sensor on the same I2C line. We set the LPn for 3x of them to low to disable the i2c comm. We are only using 1x TOF for now with it's LPn set to High for testing purpose.We are able to finish the initialization OK using the ULD API https://www.st.com/en/embedded-software/stsw-img036.html. However, when we reach the while loop (using the polling mode) to check for the : uint8_t vl53l7cx_check_data_ready(VL53L7CX_Configuration *p_dev,uint8_t *p_isReady) p_isReady is always false and We hit this particular return line:

Hi, I would like to use an external signal to trigger camera capture with the STEVAL-EVK-U0I board. I am using a promodule (CAM-56G3), and looking at the document: how-to-integrate-and-configure-the-vd56g3-vd66gy-and-vd16gz-devices  (p.g. 22 section 1.3), I know it should be possible to do this by using the gpio 0 pin, and setting the first 2 bits of the VT_CTRL  register to EXTERNAL_SYNC. However, it is unclear to me if the STEVAL-EVK-U0I board exposes the gpio pin I need or if there is another way to go about this with the STEVAL-EVK-U0I board and a promodule.Thanks

Hi Guys,I'm on windows 11, i installed all the drivers needed (STSW-IMG501_v.1.1.1) that contains InstallCx3Driver.exe and EVK GS_1.1.1_win64.exe  I have connected the steval-56g3mai module to steval-evk-u0i.I'm trying to run the script vdx6gx_example_open_cv.py from STSW-IMG507_56G3_v.2.0.2.zip What i noticed is that for some image sizes (like 600x600) the camera can acquire correctly and i see the image displayed with openCV, but if i increase the size to for example 800x800 or more i get this error from the script:c:\tmp\windows>python vdx6gx_example_open_cv.pyLoading st_brightsense_sdk_vdx6gx.dllIMG platform version 305 loaded :)Boards connected: (0,P4405C-00A#0219)No board id was specified, selecting board 0.Initiating CCI communication

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 suc

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

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 =

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

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 code

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 WriteAuto

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 c

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: 

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 impl

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()-> GetDe

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 (

    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

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.