Imaging (sensors)

Is there any way to get the signal rate for each individual SPAD of the SPAD array ?

..

Hello, I am trying to connect a VL53L3CX (a module I purchased on AliExpress) with the ESP32. I have found the Arduino library but it does not fit the ESP32. I will highly appreciate your help in helping me get this working. Thanks a lot, Motti

Can anyone offer any guidance on the best way to port an existing application from one stm32 nucleo to a different stm32 nucleo? Specifically I would like to use the People Counting example written for the Nucleo-F401RE and X-Nucleo-53L1A1 ToF sensor expansion board on the P-Nucleo WB55. My understanding is because both run applications on the M4 chip I should be able to operate the application on both boards. I found a 6 year old youtube video ( https://www.youtube.com/watch?v=YU4jivUZJm8 ) that is somewhat helpful but I think that I have some knowledge gaps.One particular point of concern is the interrupt files. I'm not sure if I should try reworking the file used in the original code, grabbing one from a working example for the WB55, or generating a whole new interrupt file using STM32CubeMXAny suggestions or resources you can provide on the topic are extremely helpful. Thanks!

Hi,I designed a sensor array containing multiple VL53L1CB sensors. They are configured to scan a 3x3 grid inside its view with multizone scanning. That works great at small distances but suffer a distances above ~1,5m.Experimentation shows that the sensor never yield reliable results (even with 16x16 zone, 550ms budget, completely dark room with covers down, target is a white wall which should cover the entire FoV) above 2m.Another issue is the flickering of datapoints. The video shows the issue: VL53L1CB Flickering issue - YouTubePoints in green are valid ranging results (RangeStatus = 0), cyan means RangeStatus = 14 and black is RangeStatus = 7.The issue is that ranging results cycle through "Not Present", "VL53L1_RANGESTATUS_WRAP_TARGET_FAIL" and "VL53L1_RANGESTATUS_RANGE_INVALID"even though the RANGE_INVALID is not realy invalid. It is exactly where i think it should measure.I hope that someone can help me with that issue.SincerelyDaniel

Hi there,I am working with tfmini lidar and i am using USART3.However i am getting the garbage in the virtual port any idea how can i resolve this but i am getting the right header i.e YY in decimal. Any suggestion would be appreciated.Thanks

..

I would like to know which VL53L* family works better for gesture detection, I have both VL6180 and VL53L3CX but I find that VL53L1CB looks more interesting due to the multizone measurement!Thanks

The VL53L1X outdoor performance is hindered by huge amounts of noise, and wildly fluctuating results, compared to indoors. I notice that the demos I can find online about this sensor conveniently never show it outdoors, although some articles mention it being used as a reversing sensor, or even a drone landing sensor...Also, since this is supposedly the official Q&A place for ST devices, why is there such a dearth of answers here? A previous query regarding this outdoor problem received no satisfactory answer.I found somebody asking about a filter, only to be told it's not a visible light sensor anyway.Is it me, or is this sensor not meant for outdoor use? I'm only a hobbyist roboticist, and the simple code I've written so far works superbly indoors, but point this sensor towards daylight and all bets (and readings) are off. Am I missing a code setting, or is there actually a filter that will solve this issue. I know I'm repeating questions asked before, but the lack of definitive

We have sensors failing because of what looks like dust or debris that is getting on the sensor. Also, often it is difficult to detect and remove the Kapton tape covering the sensors. The tests we run pass even though the film has not been removed sometimes. This is a problem because there are performance issues later on that are easily fixed by removing the kapton tape.

Hello, Is is mandatory to add inter measurement period function when I use the function Timing budget

Hi thereI am working on lidar but everytime i am getting fixed value in the buffer i.e 0x59 which is 89 in decimal (Y in ascii) which is the header of transmitted data as indicated in lidar datasheet.below is the code snippet.Any suggestion would be appreciated.

Hi,I am planning to use VL53L1X ULD API for calibration functionality. Host system is Raspberry PI and I got source code of VL53L1X ULD and Example Application from https://my.st.com/content/my_st_com/en/products/embedded-software/imaging-software/stsw-

Hello, I hope someone can help me with this.I have 3 VL53l1x and i have connected and programmed all of the 3 sensors to a arduino nano and I am receiving data from all three at the same time.I tried to perform 5x16 RoI for all three VL53L1X sensors with 200 ms timing budget , but am not really sure how to program it correctly cause m not getting the results I need. Is there any sample code that I can follow, Thank you soo much

Hi, We have been testing the VL53L1X for a while. The primary intend is to measure liquid level. Liquid can be water, coffee, windshield washer fluid, etc. We are seeing some issues that we cannot seem to figure out. Hoping for any insights.Premise.We are using Arduino platform for testing.We have tried multiple libraries (sparkfun, polulu, etc)Test involves a large container filled with liquid (say 10 inches), and sensors are placed above the liquid at 3-5 inches from the surface of the liquid (13-15 inches from the bottom of the container). Readings are taken every few seconds.Concerns.When we have multiple identical sensors placed over the liquid, We observe a variation in measurement of upto an inch in some sensors, which is a huge percentage error. Is this normal? Just need to set offset adjustment?We did read somewhere that liquids can absorb some light. However, when we start the test, it looks like the sensor readings make sense. ie IT measures around 4 inches. (disregardi

Hello, I use a VL53L3cx sensor and API STSW-IMG015. I am having two problems. The first is that in the interruption mode, the VL53L3cx stops sending the interruption after 20 received measurements, speed i2c 400khz. The second problem is that the sensor does not measure a distance of more than 1.8 meters, at this distance it gives chaotic results in the range of 20-300mm, I use this setting VL53LX_DISTANCEMODE_LONG. Tell me what could be the problem?

We are using the VL53L1X sensor with the ULD API in one of our products. During final evaluation we encountered situations where the sensor delivers wrong measurement values with status OK. In the attachment you will find the documentation of measurement series which were performed using a white wall with even surface covering the full FOV of the sensor (target is larger than 1.5x1.5m) within the range of 4m. The measurement setup is in a cellar room without ambient light and only room lighting (low IR). Timing budget and inter-measurement time were both set to 15ms and short range distance mode was selected. In the attached Excel sheets you will find min/max values for distance value, ambient and counter values for the different status values (e.g. number of results flagged with status 4 -> cnt4). We call these statistical values and can read them / reset them via commands sent to our product.The measurement was performed as follows:1.      Position ou

We are currently investigating an issue with corrupted measurement results of an VL53L1X using the ULD API in short range mode. The sensor delivers results with status ok but completelely wrong ranging values at target distances exceeding the range of 1.4m (e.g. at 2.3m). This holds true especially for the lowest timing budget of 15ms, and becomes more unlikely with larger timing budgets.When looking at the timing values which are configured by the full API some differences occured (please see the following picture for details).Especially the register values VL53L1_MM_CONFIG__TIMEOUT_MACROP_A and VL53L1_MM_CONFIG__TIMEOUT_MACROP_B differ, while others are identical.The values of the two registers VL53L1_RANGE_CONFIG_TIMEOUT_MACROP_A and VL53L1_RANGE_CONFIG_TIMEOUT_MACROP_B are close for larger timing budget values, but differ by a large amount for low timing budget values.Why do ULD and full API use different values for the same timing configuration ? Are the ULD values not correct and

Hi there, is it possible with any of the currently manufactured ToF sensors of the VL53L* family and the software that is available to private customers to obtain a depth image, or the raw sensor values for each SPAD to reconstruct a depth image?I experimented with a VL53L1X sensor by Pololu with the ported API for Arduino Uno R3, which only gives me a single range in millimeters, which from the API code appears to be a median of the valid ranges of all SPADs. I want to create difference depth images to the previous measurement, for which I would need access to all range values and do the aggregation (min, max, avg, median, ...) myself. But it seems that the median is acquired from the sensor via I2C already, not calculated in the accessible API code.I am aware that I can use the programmable ROI to create a depth image of medians over 4x4 SPAD regions of interest, but this would take too long (time budget in the application is ~100 ms per measurement) and is greatly reducing the resol

Currently we are using the VL53L1X ULD API which only supports autonomous mode. We would prefer to have a manually controlled measurement flow like the following:Start singleshot measurementWait for interruptRead measurement data and clear interruptStart from the beginningAfter indicating a finished measurement the VL53L1X sensor must not perform any further measurement and wait for the host MCU to service the interrupt.Is there any possibility to realize this ? The full API provides code for singleshot operation, unfortunately it seems like it is not fully implemented.

Hi forum,I am working on nrf52 , I was communicate with sensor through I2C.GPIO_configuration:- nrf_gpio_cfg_output(VSHUT); nrf_gpio_pin_write(VSHUT,0); nrf_gpio_pin_write(VSHUT,1); nrf_delay_ms(10); nrf_gpio_input_disconnect(TRACEDATA1);// gpio1 interrupt pinSequence of APP_function are below:- VL53L1_comms_initialise(uint8_t comms_type, uint16_t comms_speed_khz);VL53L1_SetDeviceAddress(VL53L1_DEV Dev, uint8_t DeviceAddress);VL53L1_DataInit(VL53L1_DEV Dev);VL53L1_StaticInit(pMyDevice);VL53L1_run_ref_spad_char(pMyDevice,&pcal_status);other function for calibration .but data_init() function return -15.i did supplied 3.3volt external supply to my device.Actually i device gives 2.59volt thats why i connect external supply for sensor power up. Device is externally pullup through 10k resistor.please help me to solve this error. Is their any setting required for this sensor to power up.

Hello guysi want to print lidar sensor data (digital) to virtual port.what is the way to do it.do i need to change the received data to string?TIA

I am interested to know the key differences between the VL6180 and VL6180X ToF sensors.I understand that the VL6180 has no ALS and also it appears to operate over a longer range.Is it as accurate in the 0-100mm range as the VL6180X?Thank you

..