Imaging (sensors)

The tool is working (somehow) with a VL6180 soldered to the "Bottom" connector. I want to have a measurement every 2.5s, so I select Device "Bottom, tick "Continual" and enter "2500" for "Inter-Meas Period(ms). When I start the Ranging, the "Inter-Meas Period(ms) is immediately reset to 50 or 500. It drives me nuts. What am I doing wrong?

Hey, For a project I am using multiple Vl53L1X sensors from ST and the driver I used is https://github.com/rneurink/VL53L1X_ULD/tree/94b88bc06ef44950ec3a5fd50b2f0287c23c5ad7It worked perfectly and am not having any issues.But am planning to use multiple VL53L1X sensor from Pololu.Can you tell me some of the difference between them (i.e.) Should I add external resistors for the Xshut pin and If I can use the same driver for both the sensorsThank you so much

Hi,I read License Agreement for STSW-IMG005(VL53L0X API) and I have question about license because I don't find information important for me.I start develop open source project and I would like public complete source code of my project. Can I public ST c and h file included in VL53L0X API on github?

We are working on syringe piston measurement application using VL53L0X for required accuracy of +/- 2mm.Overall we are getting required accuracy of +/-2mm. Sometimes we used to miss required accuracy.While analysis we came across one behavior of sensor.We configured sensor to High Accuracy mode with Budget Time as 900msec.We kept object at fix position inside syringe and keep on recording data.We observed sensor reading start at value 148-149 and stabilize to 146-147 after 2 min.If we stop logging and start again then similar behavior observed.Please see attached log as reference.What are the reasons for this observation. How we can overcome same to get 146-147 reading right from start.

Original product brief showed both I2C and SPI peripheral communication available for the VL53L5 but the data sheet now focuses exclusively on I2C. Is SPI then no longer supported or can both/either be used with the appropriate user-provided platform functions?

From what I've read, I get that during a ranging sequence VL53L1CX performs two separate ranging operations and since we have also ambient data I think the sensor listens to the environment without sending any pulses. What I am curious about how they are sequenced? and how the timing works? For example, if I use short-distance mode and set the timing budget to 15ms in ULD API, is it like the sensor first performs an ambient reading 5ms then ranging A 5ms and ranging B 5ms?

I have exposed both GPIO1 and GPIO2 pulled up to VDDIO with a 47 K resistor on my VL53L5 breakout. GPIO1 is used as the interrupt. What can I use GPIO2 for, another interrupt? It would be very convenient to have a date ready interrupt on GPIO1 and a threshold interrupt on GPIO2, for example...Is there an AN describing use of these GPIOs?

 90% more or less of IR is absorbed per meter, whereas only 29% is absorbed for 500nm (https://www.britannica.com/science/seawater/Acoustic-properties). For underwater automation, it would be useful to have a TOF sensor that works at a different frequency.

Interference between VL53L1X on mobile object.We use VL53L1X on mobile objects, and when these objects intersect we have interference between VL53L1X, we have incorrect measurementsIs it possible ? is a misuse of VL53L1XDo you have any examples, solutions, to eliminate these interferences ?

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.

..

Hi,i am trying to get STM32F301K8 to communicate with VL6180V1 ToF sensor on my custom board., via I2C (at 20kHz) I had problem getting the API to work so i tried low level I2C access by just sending 0x01 with basic HAL_I2C_Master_Transmit. I noticed that i can not get ToF sensor to respond with ACK. I checked rise times of the I2C, it is 66ns, due to my long traces, but still well under maximum of 120ns, according to datasheet. I am using default ToF 7bit address of 0x29 (and left shifting it << 1) and on scope it is clearly visible, along with RW bit. Also start and stop conditions are looking as they should, so only problem is the missing ACK. I also tried on 2 different PCBs with fresh out of reel ToFs. Pullup resistors are 4.7k (also tried with 1k) and Vcc is 2.82V.Could it be that ToFs are faulty or i destroyed them when soldering?Scope picture of rise time measurement and the I2C master transmit signal are below: Below are readings from X-Nucleo-6180A1 development kit

Hello. I'm using a VL53L0X sensor with cover glass from www.gilisymo.com, so I need to do crosstalk calibration to get an accurate measurement. The problem is that the correction is too big. The process is as follows: 1) SPAD calibration (ok)2) Ref calibration (ok)3) Offset calibration. I use a white card located at 100mm from the sensor. Distance measured is accurate.4) Crosstalk calibration. As UM2039 says: "The starting point of the valid distance to perform cross-talk calibration is when the actual signal starts to deviate from the ideal curve". In my case that distance is 150 mm, so I place a grey card at that distance from the sensor and call "VL53L0X_PerformXTalkCalibration()". The sensor returns a value of approximately 26000 MegaCps. 5) Ranging. When an object is located at a distance of: 50 mm --> Sensor measures 55 mm80 mm --> Sensor measures 100 mm110 mm --> Sensor measures 210 mm150 mm --> Sensor measures 8191mm (0x1FFF, no object detected)I think the correctio

NCao Writes:"We have a cover window that is a few cms away from the sensor. What kind of calibration would make the sensor ignore it?"

Hello,We ordered some VL53L1X and put them on our PCB. We ran into a problem at the moment of changing the address: we can give these sensors only two address options 0x52 (default) and 0x53 so that they work correctly, but at other addresses the sensor initialization procedure looks correct, and the sensor can be seen, but during the measurement it returns only 0 mm.We are wondering if there is a possibility of defective modules that we ordered? Or do we need to find the problem somewhere else? (we do not think this is a code, because on one module of the Pololu board, changing the address works fine) .Best regards,Aliaksandra

We are using the VL53L1X with the ULD API in our products. During the production process, we perform the offset calibration process as described in UM2510. Our cover glass (Luxycryl red 1600) is actually separated with a light blocker to prevent crosstalk and therefore we do not need to perform the crosstalk calibration.After the offset calibration, the measured distance values are as expected. But for some strange reason, when detaching the cover glass the measurement values drop and we get an offset again. After restoring the original state by re-attaching the cover glass, the offset is gone.Is there any potential explanation for this behaviour ?

Hello community,I am trying to implement a simple people counter using a VL53L1X-SATEL on a breadboard with esp32. My problem is that I am confused about the wiring. I've read the data brief but as I am not an expert in electronics I cannot figure it out. Has someone done it? Can you post a picture of your circuit so I can understand the wiring?Thank you in advance

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 30cm distance) is confirmed by an infrared camera not being a 27° FOV. Différ

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.

..