Imaging (sensors)

With the following code the VL53L5CX should get it's firmware uploaded. "   /* Download FW into VL53L5 */   status |= WrByte(&(p_dev->platform), 0x7fff, 0x09);   status |= WrMulti(&(p_dev->platform),0,           (uint8_t*)&VL53L5CX_FIRMWARE[0],0x8000);   status |= WrByte(&(p_dev->platform), 0x7fff, 0x0a);   status |= WrMulti(&(p_dev->platform),0,           (uint8_t*)&VL53L5CX_FIRMWARE[0x8000],0x8000);   status |= WrByte(&(p_dev->platform), 0x7fff, 0x0b);   status |= WrMulti(&(p_dev->platform),0,           (uint8_t*)&VL53L5CX_FIRMWARE[0x10000],0x5000);   status |= WrByte(&(p_dev->platform), 0x7fff, 0x01);" (code is from https://github.com/sim

I use cube ide when i add the function Status = VL53L0X_StaticInit(pfab);on main.c ,how build it i have this error :arm-none-eabi-gcc "../Core/Src/main.c" -mcpu=cortex-m0plus -std=gnu11 -g3 -DUSE_HAL_DRIVER -DSTM32G030xx -DDEBUG -c -I../Drivers/CMSIS/Include -I../Core/Inc -I../Drivers/CMSIS/Device/ST/STM32G0xx/Include -I../Drivers/STM32G0xx_HAL_Driver/Inc -I../Drivers/STM32G0xx_HAL_Driver/Inc/Legacy -O0 -ffunction-sections -fdata-sections -Wall -fstack-usage -MMD -MP -MF"Core/Src/main.d" -MT"Core/Src/main.o" --specs=nano.specs -mfloat-abi=soft -mthumb -o "Core/Src/main.o"arm-none-eabi-gcc -o "TOF_0.elf" @"objects.list"  -mcpu=cortex-m0plus -T"C:\Users\f.scurti\STM32CubeIDE\workspace_1.3.0\TOF_0\STM32G030F6PX_FLASH.ld" --specs=nosys.specs -Wl,-Map="TOF_0.map" -Wl,--gc-sections -static --specs=nano.specs -mfloat-abi=soft -mthumb -Wl,--start-group -lc -lm -Wl,--end-groupc:\st\stm32cubeide_1.3.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.7-201

Hello, is there a way (after applying a calibration such as offset calibration or crosstalk calibration) to return the sensor back to the default calibration that was performed at ST? If so, which I2C commands would perform this job?

..

We checked the status of each step and the status for VL53L1_WaitDeviceBooted = -13

A couple of questions.First there seems to be some conflicting comments. In the vl53l5cx_plugin_detection_thresholds.h file there is the following statement in regard to the mathematical operators for multiple checkers. "Please note that the first checker MUST always be a OR operation." Then in the file Example_9_detection_thresholds.c there is the statement " Please note that the first one must always be set with a mathematic_operation VL53L5CX_OPERATION_NONE." I've tried the example with both OR and NONE and it works either way.The seconds question is I can't seem to get the AND operation to work. I want it trigger when the distance is between 200 and 400 mm AND the SIGNAL_PER_SPAD_KCPS > 10. When I use the VL53L5CX_OPERATION_AND operator it never triggers. If I change it to look for VL53L5CX_TARGET_STATUS == 5 instead of VL53L5CX_SIGNAL_PER_SPAD_KCPS > 10 then it triggers, but none of the zones have a distance between 200 and 400 mm. Looks like it is triggering when the d

Hello all.I'm looking for any serious software documentation for LV5x sensors and... I cant't find any?!?For serious software documentation I understand precision description of all registers and macro procedures i.e. calibration, data collection etc.I'm using a lot of different peripherals from different producers, processors etc. To this time I never meet situation, that telatively complicated component have really no any documentation except for simplified (unusable) description and ready complicated API 100% wrote in C.I want to try to use LV53L3CX in industrial robust and micropower sensor and I must have full control in this project. I do'nt want to use ST microprocessor, because I'm using others. And I don't wat to use (I can't use) any processor with RAM and ROM big enough for needs of original API. No any LV5x sensor don't need so peripheral hungry control. But for making project like this, good documentation is necessary.Is it possible to get LOW LEVEL software documentation

I want to use the TOF unit to detect when a physical object is passing. The Threshold detection shall rise an interrupt signal which I use to initiate a function. As I understand the mentioned VL6180X, the interrupt must be cleared each time via an I2C command. In my application I want the interrupt to reset itself when the object has passed and the value is within the threshold limit. As an object is passing each second, I do not have time to reset the interrupt by the I2C bus. Is there another TOF where this can be done, or does anybody have a solution for this? Thanks in advance /Poul

Hello, I'm Jee Kyungsub, a student studying at RISE Lab at Sungkyunkwan University.​We are conducting study on mapping using VL53L0X proximity sensor to your company. But we met some problems while we were researching.​To proceed with the mapping, we need to know exactly what the value returned by the sensor means. So it's important to know what values this sensor gets and how it calculates the distance.​For example, only complete FOV covered experimental data exists in your data sheet. However, we should be able to predict how the data will come out if there are two or more objects in the sensor range, if one object is partially FOV covered, and if the sensor detects a tilted object.​So, I send email because we can't know this information just by the data sheet provided on the website. Would you be able to help me.

Greetings - within the "Example_9_detection_thresholds.c" , there a comment (line 164) stating: "... Please note that the first one must always be set with a mathematic_operation VL53L5CX_OPERATION_NONE...."Yet, within "vl53l5cx_plugin_detection_thresholds.h" it states (line 120):"...Please note that the first checker MUST always be a ORoperation...."Base on the example code is working, I assume the first is correct?Q2 - Single 4x4 threshold: To validate what I'm testing is correct, for single a 4x4 threshold would look something like this: for (uint8_t i = 0; i < 16; i++) {    thresholds[i].zone_num = i;    thresholds[i].measurement = VL53L5CX_DISTANCE_MM;    thresholds[i].type = VL53L5CX_IN_WINDOW;    thresholds[i].mathematic_operation = VL53L5CX_OPERATION_NONE;    thresholds[i].param_low_thresh = 400;    thresholds[i].param_high_thresh = 800; } th

I am using the VL53L1 Nucleo Pac with the Flight Sense GUI supplied by ST. I am trying to evaluate different ROI settings but everytime I change the ROI, all the calibration settings seem to be cleared. Can one change the ROI in the GUI without resetting all the calibration values?

Hi, I plan to use the VL53L3:The goal is to power it with 1300mah battery, 200ms measurement refresh rate, 2 years life expectancy. The product could reach <100µA in this conditions ?Thanks

Hi, I'm trying to get the bare driver running in user mode to work on the Pi, because I just need the easiest way to use the VL53L3CX module, and I think the Linux driver is not necessary. I'm not sure how exactly to get the ULD working on a Pi however, any guidance/example code for RPi is appreciated. Thanks!

It displays the error message "Failed to open /dev/stvmvl53l5"If I run the test program in user mode it works fine.

Unfortunately, I couldn't find any documentation relating all tuning parameters. Comments are also missing. Any ressources available?

HiI've downloaded the latest version of STSW-IMG007 (V2.4.5).I'm facing a portability issues with a previous version (2.3.3).As the X-CUBE-53L1A1's software examples are outdated, how can I use it?/What should I do?Thanks,Hamza

The first pixel of each of eight rows seems to provide a good range estimate in mm but the rest of the data is either zero or some huge number that doesn't respond to changes in the field of view. I assumed I would get 64 range estimates as output of Results.distance_mm[VL53L5CX_NB_TARGET_PER_ZONE*i] but that is not what I see. What am I doing wrong? Can you post a working example of 64 zone output please?

Is there any documentation how to setup the various threshold parameters? These are the macros defined in the vl53l5cx_plugin_detection_thresholds.h#define VL53L5CX_DISTANCE_MM            ((uint8_t)1U)#define VL53L5CX_SIGNAL_PER_SPAD_KCPS      ((uint8_t)2U)#define VL53L5CX_RANGE_SIGMA_MM            ((uint8_t)4U)#define VL53L5CX_AMBIENT_PER_SPAD_KCPS      ((uint8_t)8U)#define VL53L5CX_NB_TARGET_DETECTED         ((uint8_t)9U)#define VL53L5CX_TARGET_STATUS            ((uint8_t)12U)#define VL53L5CX_NB_SPADS_ENABLED         ((uint8_t)13U)#define VL53L5CX_MOTION_INDICATOR  Some examples or documentation on setting these up would be helpful.Thanks,Barry

Could someone please shed some light on the algorithm the VL53L0X and VL53L1X use to calculate the distance from the returned photons for each laser pulse? @John E KVAM​  you’ve mentioned in other blogs that photons seen are “averaged�? – is the logic something like “during the return period there were X number of photons counted, photon number X/2 was counted in bin #11, therefore use the time of this bin for this pulse�??I’m really interested in this because like a couple of other people have noted I’m finding both these sensors return consistently different distance for surfaces with different reflectance. I’m not using a cover glass, the sensors are perpendicular to the surface, I've been using a 100ms timing budget averaged over 50 ranges and am measuring fairly short distances (between 177-279mm). Some results for different materials arranged from shiniest to least shiny (according to my best judgement) are attached.As you can see the error trend is fairly consistent between

I'm using Zigbee3 with Silicon labs EFR32MG21A020F. I want to read the Distance of ToF sensor which is based on ST library. They mentions that it support multiple IDE. I want to know how to use it in simplicity studio 5. Can anyone help me to figure it out.

I have multizone ranging mode enabled along with SHORT distance mode.I am getting a lot of readings with 65XXX values, for example:[8191, 65277, 65243, 65257, 65312, 65267, 65238, 65168, 65241, 65263, 65239, 65211, 65227, 8191, 65217, 65173, 65244][8191, 65297, 65250, 65251, 65317, 65231, 65233, 65173, 65247, 65266, 65236, 65211, 65218, 8191, 65212, 65223, 65227][8191, 65171, 65191, 65135, 1129, 1078, 1067, 1104, 1097, 994, 976, 1065, 1031, 1039, 1038, 1069, 1067]I am aware of the 8191 error code, but what do the 65XXX values indicate?ThanksTim

I'm using a X-NUCLEO-53L5A1dev board that I have wired up to a Raspberry Pi. I have also wired the interrupt line from dev board (cn-8 pin 3) to the Raspberry Pi GPIO1 (pin 28 on the 40 pin header). In the examples 9 and 11 there is a dummy function called WaitForL5Interrupt that the user is supposed to populate. I have populated the function with code that sits and waits for the GPIO1 line to change from low to high. What I'm experiencing is that the interrupt line from the dev board is always high. Is there a step that is needed to be done to enable the interrupt line?

More specifically, the doc's say status 6 means "wrap around not performed". What is wrap around? Is this a bad condition?Thanks,Dave

Hi ST team and community!I am trying to develop a People Footfall Counter for commercial use using the two VL53L1X Sensors on Esp32 using the Sparkun Library from the following:https://github.com/sparkfun/SparkFun_VL53L1X_Arduino_LibraryFirst of all, I set two different addresses using XSHUT pins for the respective VL53L1X sensor. On calling getI2CAddress() function, I receive the set addresses again. But strangely, when i2c scanner code is executed(the i2c scanner code written just below the getI2CAddress()), I receive a single i2c address ie. 0X0B after scanning and not the assigned addresses of VL53L1X. Also it shows as 1 device found which is again strange as it should scan the VL53L1X Sensors as two separate entities since we have assigned two separate addresses. Please ignore address 0X68 as its of RTC.Since its for commercial use, I need the VL53L1X sensors to cover maximum area too. I get better output in ROI Configuration: x=8, y=8 and opticalCentre = {167, 223}. But when the

Hello,I have spent some time reading through the VL53L0X API and all documentation related to this sensor.I was hoping your team could clarify the usage of a few functions and features."Pre-Range" vs "Final-Range"This distinction is made througout the API, but the two are never actually defined. I was reading this document on TOF principles and on pg.37/38 it mentions a technique where the integration period is divided into two halves, each with a different frequency. Is that what Pre/Final refers to? This is my first guess since the VCSEL periods are split like this (i.e. 14/10 or 18/14).Scheduler Sequence StepsWhy are two of these disabled by default?Limit Checks:0: SIGMA_FINAL_RANGE (mm)1: SIGNAL_RATE_FINAL_RANGE (Mcps)2: SIGNAL_REF_CLIP (????)3: RANGE_IGNORE_THRESHOLD (Mcps/SPAD)4: SIGNAL_RATE_MSRC (Mcps)5: SIGNAL_RATE_PRE_RANGE (Mcps)What are the use cases for these, especially #2, #4, and #5? For RANGE_IGNORE_THRESHOLD, is this limit check meant to be a constant rate like the oth