Imaging (sensors)

I am using multiple VL53L5CX sensors to measure distances around a robot using the 4x4 resolution, target order closest and ranging in countinuous mode. When I'm measuring a distance close to the sensor ~500mm and then the object is suddenly removed so the distance becomes very far +3500mm, I get strange readings. The distance measured just freezes at the last measured distance, for example ~500mm and I get no weird target status exept for maybe a 10 in a few zones. Is there a way to detect this 'out of bounds' so I know to ignore the last reading and just set my measured distance to a certain out of bounds value?

Hi friends,  currently Iam working for the project (water level monitor with time of flight sensor).  For my application it should sense  around 4 meters.  I have selected the sensor (vl53l5cx) which is 2.7 meters sensing range which black reflective surface with 8*8, Is there any posibilities to do the same with 4*4 ?  If we do so what will be my range of the sensor while sensing water level.  2.  Can vl53l8cx is used to sense the water level.  Is it so what will be my range of the sensor when it has black reflective surface.  can anyone help to identify this issue

Hello,I am developing a system using VL53L1X.I have read UM2510 (A guide to using the VL53L1X ultra lite driver).This library implements the function called "StartTemperatureUpdate".The description for this function states, "This function performs the temperature calibration."The function declaration is written as:  VL53L1X_ERROR VL53L1X_StartTemperatureUpdate(uint16_t dev);  I'm curious as to why this function doesn't require the actual temperature as an input.The mechanism of temperature calibration, please let me know.It would be helpful if you could introduce related documents and URLs for reference.Best Regards. 

Hi, I'm testing some VL53L4CX for about 10 months with nrf52832 using I2C. It's used in very dark conditions and within 3m and I take 15 measures 24 times a day.Between periods of measures I completely power off the sensor with an LDO.It works fine for long period (1 month or more) and sometimes it starts a long period of consecutive bad measures.(15 measures with status <> 0). It can last more than one week and it comes back to normal for several weeks...I used the example of SimpleRanging code in app_tof.c only adapted for nrf52:- power on + I2C_Init + MX_TOF_Init + MX_TOF_Process + MX_TOF_DeInit + I2C_DeInit + power offMore than once, I just put the device in ambient light and it resumed the correct measurements...Questions:- How is it possible that it seems to stay in bad configuration despite of powering off the sensor?- Is it a way to reset to factory values when I have bad measurement?

Hello all,I need some help with a project I'm working on trying to help a disabled elderly family member. basically he have a 600L aquarium that stands on a cabinet, inside the cabinet are all of the aquarium support systems and one of them is small rectangular 10-15L that holds clean water with some nutrient/fertilizers mixed in ( can't remember exactly the name of this tank ) and every once in a while a small amount of water 100/300ml from this tank gets pumped up to the aquarium. its challenging for him to get up every time to check how full or empty the smaller tank is since he needs to squat/bend over to open the cabinet doors which he really having hard time to do. so I suggested that maybe I can help and put some kind of a sensor that will measure the water level ( in % ) in the tank and show it on a small tft display that I can mount on the outside of the cabinet door. that way he doesn't need to unnecessarily go to the cabinet and check, only when actually that tank

Dear Sir,There is a question about argument  VL53L1X_CalibrateXtalk().For cross talk calibration, we will use  VL53L1X_CalibrateXtalk()  with argument of uint16_t TargetDistInMm,we should give Xtalk calibration distance to  the argument. But, we wonder  which value should be used for this argument? The one we obtained from VL53L1X_Getdistance(), or the actual distance measured with a ruler?best regardsDai Sai 

Hi ,we are looking for a distance sensor that meets the below requirements1.Working distance 5mm to 200mm2. Resolution steps: 0.01mm steps what is the minimum resolution steps your sensor can provide. Let me know if you need anything else. 

Hello everyone,I am trying to read the distance data from a VL53L7CX ToF sensor with a Teensy 4.1 board. I am using the SATEL-VL53L7CX breakout board. The sensor is detected by the Teensy, however I when I try to check if the new data are ready to be read, it is never the case. I looked closely and found out that the I2C address detected by the Teensy (0x29) was different than the one used by the sensor (0x52, default address). Do you have any idea how to solve that please? Beside that, my sensor is correctly wired to the Teensy :IC2_RST on pin 22 of the TeensySDA on pin 18SCL on pin 19LPn on pin 23PWREN on pin 15AVDD on 5V

Hello,Been thru all the specs I can find on the VL53L5CX but I can't find how the Zones numbers map to array of distance_mm in the VL53L5CX_ResultsData  struct.Is Zone 0,0  distance_mm[0] please?Or can someone point me to the spec/page please?Many thanks IMK

The position return aperture of VL6180X is extremely sensible to light at 630 nm (red). I would know the sensistivity spectrum of the position return of the proximity sensor on the chip VL6180X in order to use a filter to cut not too much the red light and do not alter the distance measurement. At 630 nm very weak red light blinds the proximity sensor and we need to use the ALS to monitor the red light.If we know the sensitivity spectrum, and since need to use proximity sensor with the red light on, we can choice a filter with a cut-off that do not blindes the proximity sensor and can detect the red light with the ALSRegardsDomenico   

I read in other posts that it is not possible to read out the VL53L5CX histogram data because there is just too much of it. But I was wondering if it is possible to read it out if we do not care about real-time operation and are okay reading out the data at a slower frame rate (e.g., 0.5Hz).Thanks!

Hi there,   We are testing the VD6283 sensor so as to detect a set of colours a card might adquire (specifically, blue, green and yellow), but we do not understand what units / kind of values all its channels return, so:   Is there any way to convert those to something like Red-Green-Blue? If that is true, which formula could we use? Do you have any documentation related to this topic?   Thanks beforehand, sorry for the inconveniences, and looking forward to hearing from you soon.   Kind regards. Daniel.

I'm performing some experiments with VD6283 breakout board in controlled conditions, and when it got first energized and initialized it presents an overshoot and a huge settling time (around 3 minutes) which is not reproduced in subsequent illuminance condition changes. Is this behavior expected for some particular reason? Or there is an way to overcome this situation?BR,Gabriel.

Hi everybody, I'm trying to interface vd6283 (I own vd6283-satel breakout board) with other non-stm32 microcontrollers (esp32, samd21, ecc) .stm's library (x-cube-als) claims that "should" be easy porting on another hw but...it's not that easy....Did someone try to do that (even on a simple arduino r3) ?Thanks!

Having been using ST sensors for decades, this is the first time I stumble onto this perplexing problem: there is no datasheet available!There is a .pdf called 'datasheet', but it only documents half the registers and them very superficially. There is no example of setting up the device and reading the results. There are only hints here and there to forget about it and just use the 'driver'.The open source driver is clearly not written with porting or reverse engineering in mind. Comments are minimal and function names like 'cook_values()' do not help. The structure of the driver is scattered among several almost identically named source files and when finally the bare metal is reached, the registers that are used are not documented (but THEY do have more sensible names).All in all most of the functionality is still cryptic to me. I can read and write the registers and even measure the light... but only if I wait long enough (200 ms) before

I have been using VD6283 with STM32 and have found that they work well in detecting flicker when the light source is near the sensor. However, I have encountered an issue where the flicker is not detected when I move away from the light source.Additionally, the sensor does not detect flicker from room lighting.I have another question: can this sensor detect a mixture of lights? For instance, if there are four lights in the room, will the sensor be able to detect all of them simultaneously? and what will be the flickering frequency whether it's a mix of frequencies?

I purchased a  P-NUCLEO-53L5A1 kit and successfully used it to collect data for depth estimation with the help of Quick start guide. But I have noticed that if I used STSW-IMG024, GUI for L5, to get collected data, I would receive a .csv document and it is shown like this:As I know, from some papers that describe principle of TOF sensors, raw data collected by L5 can be arranged as a HISTOGRAM with 100 bins. So how can I get this HISTOGRAM data (or depth data of each bin) but not just a sigma and median from a fitted normal distribution? 

I am using the VL53L4CD for my current project and I would like to add acrylic glas cover to it. I am actually using 4 of the ToF Sensors and would like to cover all of them with one glas.What type of glas can be used here, are there any known limits? Somehow I found a little glas which was provided by you but I can not find it anymore. It was black and I would like to know the specifications of it so I can also use a black cover glas but as a hole and not one by one.Thanks

Hello everyone,I have designed a custom PCB with STM32WB15CC. I am using two sensors (VL53L1X and MPU6050). I am using CR2032 coin cell as a supply and I have big problems with the battery management. The project example is using sequencer and what I want to do is to take a single shot measurement with the VL53L1X sensor and then put the device to sleep until a wakeup command is received via bluetooth characteristics. What is the best way to implement this behavior when using sequencer? The program behaves as expected when testing on NUCLEO-WB15CC. I first initialize the sensors and then use timer to trigger a function which returns accelerometer values. Then I check if I receive desired threshold values to call VL53L1X measurement. This is implemented in p2p_server_app.c. I would like to call the most convenient function to save power while keeping bluetooth connection alive since I want to wake up the device and do the same steps again when I send a command.&nbs

Hi,I purchased the P-NULCEO-53L4A1 package and am testing it to use Liquid Level Monitoring.I have downloaded STSW-IMG039 and am referencing AN5851 and STSW-IMG039-L4CD.pdf.I used the provided GUI Tool (GUILiquidLevel.exe) for Nonliearity correction. The test container and environment are shown below. (I placed a black object on the bottom of the container to lower the floor reflectivity)

Hello,I am a committed STM32 addict and currently using the STM32F411 with nine VL53L0X's on a wheel robot project, which is working pretty well. However sometimes due to poll rate and beam angle/distance/speed small (narrow) objects are not seen until almost too late.So I thought I would try the VL53L5CX which seems to have a great spec and has some really nice features, like sharpness/target order. Which I have not explored as yet as I am still trying to get multiple VL53L5CX's running again after a STM32F411 NRST/program update. Problem I am having I think is due to the VL53L5CX  tiny breakout boards I am using as they only have 6 pins:3.3v, gnd, scl,sda, int, LPn but no i2c reset pin out.Basically when my (STM32F411) app starts up it initializes

I'm looking into using the VL53L7CX on a board designed for the VL53L5CX. I expected it to be a drop-in replacement on the hardware side with only a change in software needed (using the L7CX API instead of the L5CX API), but when I compared the two APIs (current versions L5CX 1.3.9 and L7CX 1.2.8), ignoring all the instances of "VL53L5CX" changing to "VL53L7CX", I can find no substantial differences at all, and in fact the L7CX seems to work just fine with the L5CX API. Can an ST engineer confirm that the two APIs are functionally identical and interchangeable at this point?Also, is there a way to tell the two sensors apart via I2C? As far as I can tell, they share the same I2C address and the contents of their identification registers are the same; is there something else that can be used to distinguish them other than visual inspection of the IC?

..

I see that the VL53L5CX sensor has two voltage supply alternatives, both for the digital part (IOVDD) and the analog part (AVDD). I am also observing that starting from version 1.3.3 of the ULD driver, we have a function called vl53l5cx_disable_internal_cp(). In my tests, calling this function resulted in a decrease in current consumption via AVDD by approximately 40%, for both 2.8V and 3.3V supply voltages. Additionally, it is worth noting that the silicon temperature also decreases significantly when this function is invoked. What are the effects of this function and in what cases should it be called? Does its usage degrade the sensor's performance in any way?Thank you!Alex

Hello all,I am confused on some test results that we performed while gauging the VL6180X's performance and am seeking some advice. We are testing various materials with the intention of using the best performing one for the target object in our application. Our application requires very precise measurements within a 30-65mm range.So in our setup, we are using 2 ToF sensors with a custom made cover glass design which separates the TX and RX side of the sensor, idea being it will minimize crosstalk. Offset and Cross-talk compensation were also performed. We took 6 measurements between 29mm and 61mm and recorded the distance and mcps.So in this case, we used a white, shiny, high reflectance material as the target object. Results were great, distance reported was within 3mm of the target distance, and the return rate was high. It looked very similar to an experiment ST performed; a distance vs return rate graph in the app notes of the VL6180X.