Imaging (sensors)

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 reading the results. Any attempt to read the

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. Please see atta

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)config.txt is shown below.--------------------------firmware=VL53L4CDOCalgorithm=0totalheight=200offsetcalibration=100indicators=10characterization=2turbu_det_std=20--------------------------Referring to page 3 of STSW-IMG039-L4CD.pdf, when the indicators was set to 5, 4 measurement levels (10, 20, 30, 40%) were created, but the distance values of the characterization plot did not match. Therefore, the indicator of config.txt was set to 10 and proceeded. (ex, if the total height is 200, the distance of 10% should be 180) During non-linear correction, the Characterzation button changed from Le

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 and set new i2c address in the two VL53L5CX's, I then set the 8x8 resolution, ranging speed and Start Ranging, all of this works just fine.Problem is after the STM32F411 app/code has been updated I ca

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. We then performed the same experiment wit

When executing "vl53l0x_SingleRanging_Example" or "vl53l0x_SingleRanging_High_Accuracy_Example", the distance can be measured correctly, but when executing "vl53l0x_ContinuousRanging_Example", it cannot be measured.Is there somewhere I can check?Below is the log when running "vl53l0x_ContinuousRanging_Example".VL53L0X PAL Continuous Ranging exampleCall of VL53L0X_DataInitAPI Status: 0 : No ErrorVL53L0X_GetDeviceInfo:Device Name : VL53L0X ES1 or laterDevice Type : VL53L0XDevice ID : VL53L0CXV0DH/1$CProductRevisionMajor : 1ProductRevisionMinor : 1Call of VL53L0X_StaticInitAPI Status: 0 : No ErrorCall of VL53L0X_PerformRefCalibrationAPI Status: 0 : No ErrorCall of VL53L0X_PerformRefSpadManagementAPI Status: 0 : No ErrorCall of VL53L0X_SetDeviceModeAPI Status: 0 : No ErrorCall of VL53L0X_StartMeasurementAPI Status: 0 : No ErrorIn loop measurement 0: 0In loop measurement 1: 0In loop measurement 2: 0In loop measurement 3: 0In loop measurement 4: 0In loop measurement 5: 0In loop measurement 6

I have a very simple question concerning the size of the zones and the field of view for (for example) the VL53L8CX sensor. which has a diagonal FoV of 65 degrees. Can anyone provide a simple answer to this question:If the sensor is 1 meter from the target, what size is each (8 x 8) zone at the target?I have tried to follow the app note and calculated 0.37 x 0.37 meter - but I have little faith in my calculation. Thanks

HI, i am studying how to controll vl6180 with a custom board which MCU is STM32L452CCU6. At the beginning , i tried to avoid implementing the api by changing register directly using i2c, however,0x018 is set to 0x2 or 0x0 both did not generate the raw value in 0x064. Therefore, i think there are more config i need to be made before the sensor start reading and an API is required . During searching in the internet, i only found STSW-IMG003 for VL6180X, can i use it for VL6180?Which example could i use just for 1 sensor read range?

Hey, I am using a customize board (MCU:STM32L452CCU6) to develop a gate checker with vl6180/V1 and cover glass with IR filter. Implemented a default value and setting ,the sensor and code works fine indoor. But in the outdoor condition under the sunlight, the sensor only shows 255. I read the datasheet, some setting could help me to overcome this situation, but I don't know which steps should i go first( crosstalk,threshold , convergence time or SNR?). So, which parameter should i deal with it first in order to solve this problem?

Hi, I would like to download older versions of the VL53L5CX gesture library (to be exact the 1.7 and 1.8 versions for cortex M4), but I'm only allowed to download the latest one (1.9). Is there any possibility to download these two versions?Regards.Stepan

Dear ST Engineers,I am planning to port this device driver to another 8 bit MCU:https://www.st.com/en/embedded-software/stsw-img023.htmlMy 8 bit MCU has I2C slave address range from 0x00 to 0x7F.However, hint of that ST driver code insists on using uint16_t as I2C address, for example, typedef struct { /* To be filled with customer's platform. At least an I2C address/descriptor * needs to be added */ /* Example for most standard platform : I2C address of sensor */ uint16_t address; } VL53L5CX_Platform; How do I reconcile this conflict?  Or do I misunderstand something about ARM 32 bit architect?Please give your valuable opinions.  :cowboy_hat_face:

Hello,I am developing a system using VL53L1X.I have read UM2356 (VL53L1X API user manual).I would like to know the background of the recommended conditions for the offset calibration procedure Chart distance: 140mm.Is it a peculiar point that Chart distance: 140mm is characteristic of the sensor?If anyone knows the effects of calibrating at other than 140mm, it would be helpful if you could let me know. Best regards.

In my product I use the VL53L1X sensor for more than 2 years. But the last 50 sensors I bought had a problem. The measurement is too incorrect and the peak_signal_count_rate_MCPS and ambient_count_rate_MCPS parameters are too low. I purchased sensors from two different vendors and both had the same problem. The image below shows my test device. The first two lines of the display show data from the new sensor with a problem. And the last two lines show data from a sensor that is working correctly, used as a reference. My doubts are:Have there been any firmware updates recently?As I import this component, could the customs X-ray have damaged the sensor?Is there anything else I can check to try to resolve the issue?