Imaging (sensors)

Hello,We are investigating the VL53L7CX presence detection ToF sensor. In the datasheet its mentioned it needs to be mounted in a clean environment "The customer is advised to use a clean assembly process until aprotective cover glass is mounted." and the application note TN1532 "Recommendations for assembling dToF sensors without liners in an environmentally clean place" - states that the sensors should be mounted in a clean environment grade 1000.  Our manufacturer dose not have a 1000 grade clean room but he has 10000 grade. What would be the consequences of mounting the sensor in an 10000 grade environment ? Thank you very much!  

Hi all, I'm using pololu VL53L7CX sensor carrier board interfaced with Nucleo-L552zeq EVK for ranging application. For first level, iam using the Simple ranging application that comes with software package. Sensor api calls till getting the data seems working fine. But when viewing the result, the status is always 0. For first frame its 6, but i understood it will be 6 for the first frame. The expected status should be 5 (or 9), but for me its always 0. For now i have set the resolution as VL53L7CX_RESOLUTION_4X4 with ranging mode as VL53L7CX_RANGING_MODE_CONTINUOUS. Additionally, am not using INT pin or LPn pin. Is there anything i need to take care in the hardware side?Or is there anything to be handled in the sensor configuration in the app side?Below is the some zone result i got from a single frame:Details:{NumberOfTargets = 1, Distance = {53}, Status = {0}, Ambient = {0}, Signal = {0}}Details:{N

Hello Guys,  currently, im trying to get the VL53L0X to work with my MSP430 Controller but my biggest problem is the communication with the Device. Ive copied the Software from Artful Bytes and changed it to match my board. Here is the Link: https://www.artfulbytes.com/mcu-i2c-driver   Ive tried to write a simple byte to the Sensor but all it does is pulling SCL and SDA down right after transmitting the last digit (write). It doesnt even give an ACK and it willbe pulled down until i cut the power supply.

Hello, I am having trouble with the VL53L4CX Sensor for my Capstone Design Project. My group created our own breakout board for the sensor, and I was able to get it up and running with the VL53L4CX_SimpleRanging project provided by ST.However, I am having trouble figuring out the setup for our own project. Here's my steps to get to my problem:I create a new project with Board Selector, NUCLEO-U575ZI-Q.I click Software Packs, and Select the dropdown for X-CUBE-TOF1.I select VL53L4CX under the Board Part Ranging dropdown.I setup a GPIO pin on the Nucleo for XSHUT, see below. 

I want to download other versions of STSW-IMG019 software, how can I download it?At present, the official website can only download the final version

Hi, I'm trying to get the VL6180 Time-of-Flight (ToF) proximity sensor working with the SAM E54 Xplained Pro evaluation kit. Hardware Setup: Board: SAM E54 Xplained Pro Sensor: ST VL6180 ToF Module IDE: MPLAB X v6.10 (Linux x64) Connection: I2C + GPIO Current Status: SERCOM3 is connected to SDA on PA2 and SDL on PA23 The external interrupt (GPIO 1) is connected on PB08 GPIO 0 is connected on PB09 Using the VL6180X API (v2.3.1)

I am working with the ST VL53L8CH sensor for research purposes. To generate a point cloud from depth measurements, I am trying to get the directional ray to each zone. I am wondering if there is a more detailed explanation of the configuration for SPAD maps in this diagram:For example, in a similar sensor, the AMS TMF882X sensor datasheet has the following information for how SPADS map to each zone:

Hi, I am looking for a ToF sensor using VL53L1X.We are currently developing a ToF sensor using VL53L1X.I have a question about the sample API VL53L1X_UltraLowPower you are using.Whenever I execute VL53L1X_ULP_CheckForDataReady within VL53L1X_ULP_SensorInit(), it always TimeOut.After examining the contents a little more, it seems that the problem is caused by the difference between the values of &temp and int_pol obtained by the VL53L1X_ULP_GPIO__TIO__HV_STATUS command. (This is the location in the picture).In other words.・What does it mean to do this setting・What does the value of temp mean?・What does &temp return?I need answers to these three questions. The microcontroller in use is EFR32MG22Also, if I use VL53L1X_ULP_GPIO_HV_MUX__CTRL, 0x11 is returned and int_pol is set to 1. Please let me know if this is even the correct behavior. I would be glad to answer your questions!Best Regards.

We are moving to VL53L4CD.Have it all coded but having a strange experience.  Simplistically we use the sensor continuously and only use GetResult to retrieve the sensor readings (e.g. not CheckforDataReady).So,  simplistically looks sorta like this using the ULD:....VL53L4CD_SensorInitVL53L4CD_SensorStartRanging()while Forever             VL53L4CD_ResultsData_t result;             VL53L4CD_Error VL53L4CD_GetResult(&result);.... This worked fine for the VL53L1X but for the VL53L4CD while all Init, StartRanging and GetResult are returning a status of 0 the reading never changes.  It gets a reasonable reading first but then just never changes.Any idea?Thanks,Will   

I am trying to run a VL53L8CX sensor at the maximum advertized speed. Originally, following the marketing for this chip, I had thought that this was possible at the full 8x8 sensor resolution, but later learned that that has a maximum speed of 15 Hz (strangely, an associate of mine was able to get it to work closer to 20 Hz, but no faster). We need to have the sensor running at 60 Hz, even if at a reduced resolution, but all examples we can find online are below that 20 Hz threshold. Does anyone have any advice for settings and configurations to bring this sensor to maximum speed? For example, beyond cutting the resolution down by 75%, do we also have to use SPI? Are there any important clock speed values that have to be set to some specific maximums?For reference, I am running the board with an ESP32 S2 Dev Module board.

static const uint8_t VL53L4CD_DEFAULT_CONFIGURATION[] = {#ifdef VL53L4CD_I2C_FAST_MODE_PLUS0x12, /* 0x2d : set bit 2 and 5 to 1 for fast plus mode (1MHz I2C),else don't touch */#else0x00, /* 0x2d : set bit 2 and 5 to 1 for fast plus mode (1MHz I2C),else don't touch */#endif0x00, /* 0x2e : bit 0 if I2C pulled up at 1.8V, else set bit 0 to 1(pull up at AVDD) */0x00, /* 0x2f : bit 0 if GPIO pulled up at 1.8V, else set bit 0 to 1(pull up at AVDD) */0x11, /* 0x30 : set bit 4 to 0 for active high interrupt and 1 for active low(bits 3:0 must be 0x1), use SetInterruptPolarity() */ Above is the default configuration for the VL53L4CD (the beginning part anyway). When I first started testing with the VL53L4CD readings were static.  Meaning,  they never changed.  The first reading was the only reading it would ever give out. However,  comparing the Configuration I had for the VL5

Hi All,we tried to migrate from VL53L1CX to VL53L4CD for better precision in short range.both use ULD driver, we expect they work in similar way however it seems not.we set both to TB20 and compare power consumption in single shot case. It seems VL53L4CD takes much long time and power than VL53L1CX ev

(I deleted the content by accident) I'm working on a project that uses Smart Presence Detection to control a LED strip using the X-NUCLEO-53L8A1 board. I started a blank project in STM32CubeIDE and included the X-CUBE-TOF1 bundle. I have added several other features to control the LEDs (SPI, DMA, timers, etc). I am able to get ranging data from the ToF sensor.I would like to add the Smart Presence Detection from STSW-IMG048 but I'm having a great deal of difficulty integrating the SPD code with the existing code that talks to the VL53L8. It seems that the SPD code makes extensive use of function calls to control the sensor using the VL53LMZ_ULD_API but these calls do not work in the context of my existing project - perhaps it some incompatibility in the GPIO or I2C setup but I cannot be sure. I would prefer to be able to use calls to the sensor-control functions in the X-CUBE-TOF1 package to satisfy the requirements of the SPD but it does not look possible - the T

Hi, We use the calibration ST APIs.  The procedure we follow is run calibration and then reboot with the new offset. However,  is there anyway to avoid having to reboot? We would like to auto calibrate in real time without a reboot if this is at all possible with this sensor.  Additionally,  we are moving to the CD sensor and would like to know if it is perhaps also possible with the CD. Thanks, Will  

Hi team,I am new to the STM32 Cube IDE environment and would like to interface and control the VL53L4CX Time-of-Flight sensor using an STM32F030 DEMO Board. I kindly seek your guidance and support in achieving this.Here are the details of the hardware I am working with:MCU Board: STM32F030 DEMO BOARD V1.1TOF Sensor Module: VL53L4CXI would greatly appreciate any resources, sample code, or advice you can provide to help me get started.Looking forward to your support.Thanks and regards,Anirudh

Hello,I am using the VL53L8CX sensor on an I2C bus, and it operates normally until I run the i2cdetect command. After running i2cdetect, the sensor stops working properly, and calling vl53l8cx_check_data_ready() returns a GO2 error status.Interestingly, if I have another sensor (e.g., a temperature sensor) enabled on the same I2C bus, the VL53L8CX recovers and continues working after i2cdetect. The temperature sensor is at a different address and only performs normal read operations.Why does i2cdetect disrupt VL53L8CX?Why does another sensor’s read operations seem to "fix" the issue?How can I debug and prevent this problem without adding a secondary sensor?Any insights or debugging tips would be greatly appreciated!Thanks!

Hi,I am using VL53L8CX sensor from Pololu and connected it with Nucleo-F411RE board. I am using Arduino IDE 2.3 where I have downloaded STM32duino VL53L8CX library. When I run HelloWorld_I2C example with the wire  connections as mentioned with (SPI/I2c-->GND, Lpn-->A3), I am getting the distance result. But when I do the same with the HelloWorld_SPI example with mentioned connection (SPI/I2c-->3v3, Lpn-->3v3), I am getting nothing. When I put the breaker in between, the initialization itself fails saying sensor initialization status 1. I would be a great relief if you could help me with this.Thank you

I’m using the VL53L8CH sensor with an ESP32 and developing a program in Arduino language based on Example_10_motion_indicator.c provided by ST. I successfully obtained the motion indicator output using a 4x4 map.Next, I tried switching to an 8x8 map by applying the following settings: VL53L8CH sensor(&Wire, LPn_PIN); sensor.set_resolution(VL53LMZ_RESOLUTION_8X8);sensor.motion_indicator_init(&motion_config, VL53LMZ_RESOLUTION_8X8);  However, when I checked the output, I noticed that the 1st and 2nd values, as well as the 9th and 10th values, are identical, resulting in behavior similar to a 4x4 map.Could you please advise if there are any additional settings required or if this might be related

Hi, I am following the linux-startguide-stbrightsense for the Raspberry Pi 5 (with a clean build of RPi OS Lite, where I only had to install the i2c regmap), and I have come across some problems in the tutorial. I am using two VD66GY cameras, with the entire S-board kit. Hardware connection is OK, as I get I2C communication and I can detect them both via the i2cdetect on i2c4 and i2c6.I have put both dtoverlays together, as I have both cameras plugged in (basically the same thing except changing some names for conflict reasons):  // SPDX-License-Identifier: GPL-2.0-only /dts-v1/; /plugin/; /{ compatible = "brcm,bcm2835"; fragment@0 { target-path="/"; __overlay__ { camera_clk_12M: camera_clk_12M { #clock-cells = <0>; compatible = "fixed-clock"; clock-frequency = <12000000>; }; v1v2: v1v2 { compatible = "regulator-fixed"; regulator-na

  Hello ST Team, We have integrated the TOF sensor into our hardware, and we would like to clarify the following: How can we calibrate the TOF sensor? When does the calibration occur—during device power-on or reboot? What are the results of the TOF sensor calibration? Thank you for your assistance!

I am trying to use Satel -Vl53L8 after breaking it .  I am unable to operate it , I also tried to use the same method as used by brekout board but failed . Here is the circuit I usedIs there a way I can use the brakout board , What circuit do I need to use.

Hello, I am wondering if there is any software reset for the VL53L8CX when using the ST provided API. When I reprogram my micro using ST-LINK but do not do a hard power reset on my device the VL53L8CX init fails. I have attached an image below showing soft reset ST-LINK operation and hard reset. In UM3183 I see that a power cycling of the device is recommended for reset. Is there any ability to do this through the API?    Point in which the VL53L8CX init fails:vl53l8cx_api.c  --> _vl53l

Hello,I am trying to get my STM32WB5MM module to talk to VL53L7CH. I have working BLE project (compiles no warnings, no error and works-advertises as beacon). Now I added files from STSW-IMG043, according to doc file in the package.I also modified the platform.c file, with I2C functions (used the ones from F401 example, just changed the I2C handle to the one I use "hi2c3").After trying to compile, I receive some weird errors in log that I haven't dealt with before, so some help would be appreciated. From what I could extract, there are some "wrong" definitions in file "vl53lmz_buffers.h" (haven't modified that file at all). Log output:   11:14:34 **** Incremental Build of configuration Debug for project XXXXX **** make -j16 all arm-none-eabi-gcc -o "FPulse.elf" @"objects.list" -mcpu=cortex-m4 -T"C:\Users\klemen.skorjanc\Doc

We are developing product with VL53L8CH integrated. Now I have to developed simple firmware that will extract data and control it and for that I need datasheet with registers description. After searching for over an hour, I cant find any datasheet, user manual or application note on this topic.

Hello,in one of our new devices, we are using the VL53L3CX as a distance sensor, mainly for its small size and I2C connectivity. But we found out that even if we compensate the distance offset, after turning the device off and on again, the compensation is not valid anymore. The variance is in order of millimeters, but sometimes we can get up to 10 mm of difference. The API offset functions just add/subtract value internally. We tested it with the small daughter boards of the X-NUCLEO-53L3A2 and later with own PCBs. Is there a way how to get the distance consistent across power cycles?