Imaging (sensors)

We are using Vl53L0x for distance measurement up to 20 cm. While testing with filter glass (recommended by ST) we observed result deteriorate by 1mm for few measurement areas against results without filter glass. Now I will work cross talk calibration, some software filter in order to overcome 1 mm deterioration of result. From ST side, if you provide some input on this deterioration and possible solution to overcome same then it will helpful to us.

I wanted to use this sensors for person detection in Washroom pipe & urinal applications. I have tried different models of housings for sensor. But so many times, the taps are automatically turned on without any persons. So can anyone suggest me recommend protection ratings, instructions, dimensions, materials to be followed for using this sensor. In this type of application.If possible send examples images & 3D model for reference

VL53L1X has VCSELs and 16x16 SPADsWhat I am curious about is the order of operation when reading 16x*16 SPADs one by one.1. VCSEL on2. Read SPAD[0,0] value3. VSCEL off4. VSCEL on5. Read SPAD[1,0]6. VSCEL offwhether or not1. VSCEL on2. Read SPAD[0,0]3. Read SPAD[1,0]....n. VSCEL offWhich of the two?

We're currently evaluating a VL53L1X sensor underwater (in a sealed housing) , but beyond 2m IR light is absorbed too much. A ToF sensor based on 532nm would achieve better results. Which options exist other than 940nm?

Hi, We have been testing the VL53L1X for a while. The primary intend is to measure the occupation a container (30cmx30cmx80cm) filled by small objects (10cmx10cm). We would like to limit the number of sensors to have a low energy consumption (system is on battery). We are seeing some issues that we cannot seem to figure out with FOV as per spec (FOV 27°). Hoping for any insights.Premise.We are using Arduino platform for testing.We have tried multiple modules & libraries (sparkfun, polulu, etc)Test involves a container filled with 2 objects (say 10cm size), and sensors are placed On top of the container at 20cm from the surface Of the object (30cm from the bottom of the container). Readings are taken every few seconds.Concerns.The object is only visible in the line of sight of site of the sensor. The FOV is not operating as expected at 27° as mentioned in the specification. The FOV (8cm circle at 3

We are using VL53L0x for measuring piston position inside syringe.We consider piston position at bottom of syringe as reference position.As we move piston to top, the difference between actual and measured reading start increasing.At bottom difference around 0 mm. As we move piston up, the difference start increasing to around 1 mm, 2 mm, 3 mm.we feel the behavior is due to piston surface facing to sensor in our application. It is not flat but cone type. Time of flight change and we observe variation is actual and measured reading.Is our understanding correct? We found VL53L0X_SetLinearityCorrectiveGain. Will this API useful for our observation? What is the purpose of this API?

We are working on an application where we are making VL6180X detect an approaching hand towards it. We would like to understand how can this application work when sensor is covered by an opaque black film. Is there a special calibration required? The hand movement is being done behind the opaque black film. Will it ever detect such movement? Would appreciate appropriate technical support.

..

Hi everyone,I tried to use the eval board nucleo 53L1A1 with nucleo F767ZI with the API STSW-IMG005.I adapted the API without the serial line, i used the HAL_I2C lib etc .I used the example single ranging in the example folder in API.the first part work fine i get the info of the device juste device ID wich not display anything.After that the function perform calibration and spad management, the sub function measurment poll for completion does not work, the get measurment data ready function does not get the information about new data ready.And i don't get ranging mesurement data.But the rest is ok as staticinit return ok.I attached some pictures for display some parts of my explaination. i can share the code if necessary, I don't know what is the problem....

Hi,Readings from my VL6180X sensor are very unstable. They vary about +-8 mm from measure to measure.I tried with Nucleo board and official api, and also with Arduino board and Sparkfun code. 2,8V power supply is from linear regulator, measured object is solid white at distance 50 mm.I tried to supply it from battery instead of usb, nothing helps.

e are operating VL53L0X in High Accuracy mode with time budget configured to 9000msec.Please help us to understand how sensor taking multiple sample and gave final stable output in high accuracy mode.We are going to use this sensor for distance measurement of piston inside syringe. For same plan is to put sensor on cap of the syringe. During initial testing with multiple sensor board, when piston is at top of syringe, we observed variation in reading. That indicate, we might need to store application specific factor with sensor. For same we might need to make provision of eeprom with Vl53L0x sensor on sensor board. We wanted to know, is there any possibility to store such "Application specific factor" on VL53L0X sensor, so we can avoid eeprom?If answer is No, then is there any alternative part available (similar in size of VL53L0X ) where we can store "Application specific factor"?

Hi!I notice that in the datasheet of both VL6180 and VL6180X, there is EXACTLY the same plot of distance measurement. So that's leaving me to the question: Who is best for short distances, VL6180 or VL6180X?Have a look at page 12/87 here:Proximity and ambient light sensing (ALS) module (st.com)And have a look at page 32/73 here:VL6180-Datasheet.book (st.com)Both same plot. Why?I assume that VL6180X is better for short distances, but I can be wrong too?

Hi all,I'v developed a board with my microcontroller and one VL53L1X-SATEL - Breakout board that came with my X-NUCLEO-53L1A1 kit. I use a 3v battery for the board without regulator and 1K pull-up for the I2C line(100khz).I use the VL53L1X ULD API files for the initialisation and the one shoot ranging measurement. After the initialisation (SetDistanceMode=short, SetTimingBudgetInMs = SetInterMeasurementInMs = 20mS) of the VL53L1X my CPU go to sleep mode and the current consumption is 6uA, every 30s my CPU wake up start measurement (StartRanging, CheckForDataReady, GetDistance, ClearInterrupt, StopRanging) consumption=14mA, the Distance value is ok and go to Sleep again.All works like I expected, BUT every time I change the battery or I do a reset to my CPU, if there is no target in front of the VL53L1X, after the initialisation phase (sleep mode) the current consumption is 3mA (expected 6uA) and every 30s the CPU wake-up send a good distance measuremen

Hi ST team and community !I'm here because i have some troubles on the processus of initialisation of multiple sensors VL53L1CB.I use the following library available on gitHub : https://github.com/stm32duino/VL53L1The processus is the following :Shut down reset pin XSHUT of each sensorThen, in a for loop (to setup my 3 sensors) :Power ON the first sensor with XSHUT pinI2C scanner to detect my only sensor ON (normally at address 0x29)Create my C++ component with the I2C link and XSHUT digital/analog PINInit sensor with the new address with InitSensor function in the class VL53L1 of C++ APII2C scanner again to check if the address has been changedThen, switch to another sensor in the for loop until initialisation of my 3 sensors.My problem is when

Hello,I'm currently working with the VL53L1X distance sensor on the nRF52. I'd like to use two of them with te same i2c busses. Therefore, I need to change the address of one of these.I have successfully used a single sensor (using the default address 0x29). Now I want to change the address of this sensor (still using a single sensor), but when I try to read the distance, I get error -13.The I2C address is correctly changed, because i do get this new address when I read the I2C address buffer (0x0001). Also, my logic analyser confirms that the new i2c address is used, but the read/write command is not acknowledged (so no distance is read of cource).I looked to the api and logic analyser results in more detail, and I added the following line in the function VL53L1_init_and_start_range() (from vl53l1_api_core.c):if (i2c_index == 0x001 && buffer[0] == 0x29 && Dev->I2cDevAddr != 0x29) { buffer[0] = Dev->I2cDev

My code and console are as presented below. Values are on the console are fixed, they don't change even if i move an object in front of the sensor. Also i dont understand what should i put in "index" byte that is shown in data sheet./* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * <h2><center>© Copyright (c) 2021 STMicroelectronics. * All rights reserved.</center></h2> * * This software component is licensed by ST under BSD 3-Clause li

Hi All,We foresee cross talk calibration ​for VL53L0X in our application as we are working on enclosure with filter glass on top of VL53L0X .To get understanding of cross talk calibration working, I tried "VL53L0X_PerformXTalkCalibration" with distance parameter as 100 (10 cm), 200 (20cm), 300 (30cm) and by keeping white and grey object at mentioned distance. I always found return value of function pXTalkCompensationRateMegaCps always zero.Why I am getting always zero? What I am missing during my testing?

Given that the VL6180-SATEL breakout board has no mounting holes, is there a preferred method to accurately and rigidly mount it in the desired position and parallel to the mounting surface?I would prefer to have it removable, so a permanent adhesive does not appear to be the best solution.Thanks

Hello everyone,I am currently trying to calibrate VL53L1X sensors which are covered by a 4mm thick glass.I am using the ULD from ST to calibrate the offset and xtalk.I achieve a better result with calibration, but I still don't get further than 70-80 cm.According to the user guide the ranging curve with calibration should look like this.But in my case it looks more like this:

My application requires scanning multiple zones (ROIs) and comparing the results. When I do this I see an offset that varies somewhat randomly based on the shape and position of the ROIs. I see in the UM2133 user manual that there is a calibration procedure to correct offset per zone:VL53L1_SetOffsetCalibrationMode(Dev, VL53L1_OFFSETCALIBRATIONMODE_MULTI_ZONE);and to apply the correction per zone:VL53L1_SetOffsetCorrectionMode(Dev, VL53L1_OFFSETCORRECTIONMODE_PERZONE);My question is: Could you explain how this multizone calibration and correction works and where the per-zone data is stored? The data structure in the following quote from the user manual is only for the overall offset calibration right? There would need to be offset data stored for each ROI right? Thanks, Martin6.3.4 Offset correction options In multizone scanning mode, the offset correction can be improved by using a per zone calibrati

We would like to know sensing distance target's size spec.Our team had tested with some small pole as 1inch diameter and 2 inch height cylinder that put on table.But from upper to bottom as in front of target VL53L0X cannot detect this cylinder distance.We have tested some another medicine bottle also, it shows similar result.My understanding of TOF is photon detect by SPAD with avalanche but it takes some level of volume reflection at surface in SPAD.If there are some spec of this issue please let me know.

I am testing the VL53L0X ability to accurately measuring the distance to objects of different materials and different sizes. The sensor is in continuous mode and I am using VL53L)X_GetRangingMeasurmentData to read the distance and reflectivity value. The parameter I am reading for distance is RangeMilliMeter and the parameter I am using for reflectivity is SignalRateRtnMegaCps. I have found that as the SignalRateRtnMegaCps value goes up the distance error increases. At 25�? the distance reading to a large sheet of brown cardboard is about 25.5�? and the reflectivity reading is 122,316. But at the same distance, the distance reading to a piece of white cardboard is about 35.3�? and the reflectivity value is 58,675. Are large distance errors to be expected as the reflectivity value goes down? Is there anything that can be done to reduce this error? Is it possible to use the Reflectivity reading to reduce this error? I see this

Hello, I have series of questions related to the data implementations using SPAD zone settings. After reading of manuals i made conclusions how to use this feature of the sensor, but i'm not sure if my conclusions are correct.1. I'm interested in accuracy of data returned by sensor in different zones. I tested all center zones started from 16x16 and reducing it to 4x4 size array. And each redusing gave me differense almost in 1.5cm, so the difference between value that retured in 16x16 case and 4x4 case equals 7-8cm! I had clear conditions of the experiment: sensor was fixed vertically in front of plane wall. I just wondered why the zones with the same center have such differents in output value.2. The second quastions is about if there any possobility to define geometric locations of the zones. User manuals said that 16x16 array has 27 FoV, 8x8 -20 FoV, 4x4-15 FoV. So i'm really wondered how those zones geometricly exists, because the reducing of the FoV

I would like to use VL6180V1 in one of my project.I am interfacing it with STM8L MCU. For the sake of simplicity, I would like to copy the settings of the arduino library of VL6180X : https://github.com/sparkfun/SparkFun_ToF_Range_Finder-VL6180_Arduino_Libraryandhttp://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/DM00122600.pdfI would like to know if it would work or not because of the difference between VL6180 and VL6180X (Presence and absence of ALS). If not, then please guide me with the register setup. The API that is available is for STM32 and not STM8. Hence I am requesting for this clarification.

..