Imaging (sensors)

Hi everyone,I tried to use the eval board nucleo 53L1A1 with nucleo F767ZI with the API STSW-IMG005.I adapted the API without the serial line, i used the HAL_I2C lib etc .I used the example single ranging in the example folder in API.the first part work fine i get the info of the device juste device ID wich not display anything.After that the function perform calibration and spad management, the sub function measurment poll for completion does not work, the get measurment data ready function does not get the information about new data ready.And i don't get ranging mesurement data.But the rest is ok as staticinit return ok.I attached some pictures for display some parts of my explaination. i can share the code if necessary, I don't know what is the problem....

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.

e are operating VL53L0X in High Accuracy mode with time budget configured to 9000msec.Please help us to understand how sensor taking multiple sample and gave final stable output in high accuracy mode.We are going to use this sensor for distance measurement of piston inside syringe. For same plan is to put sensor on cap of the syringe. During initial testing with multiple sensor board, when piston is at top of syringe, we observed variation in reading. That indicate, we might need to store application specific factor with sensor. For same we might need to make provision of eeprom with Vl53L0x sensor on sensor board. We wanted to know, is there any possibility to store such "Application specific factor" on VL53L0X sensor, so we can avoid eeprom?If answer is No, then is there any alternative part available (similar in size of VL53L0X ) where we can store "Application specific factor"?

Hi!I notice that in the datasheet of both VL6180 and VL6180X, there is EXACTLY the same plot of distance measurement. So that's leaving me to the question: Who is best for short distances, VL6180 or VL6180X?Have a look at page 12/87 here:Proximity and ambient light sensing (ALS) module (st.com)And have a look at page 32/73 here:VL6180-Datasheet.book (st.com)Both same plot. Why?I assume that VL6180X is better for short distances, but I can be wrong too?

Hi all,I'v developed a board with my microcontroller and one VL53L1X-SATEL - Breakout board that came with my X-NUCLEO-53L1A1 kit. I use a 3v battery for the board without regulator and 1K pull-up for the I2C line(100khz).I use the VL53L1X ULD API files for the initialisation and the one shoot ranging measurement. After the initialisation (SetDistanceMode=short, SetTimingBudgetInMs = SetInterMeasurementInMs = 20mS) of the VL53L1X my CPU go to sleep mode and the current consumption is 6uA, every 30s my CPU wake up start measurement (StartRanging, CheckForDataReady, GetDistance, ClearInterrupt, StopRanging) consumption=14mA, the Distance value is ok and go to Sleep again.All works like I expected, BUT every time I change the battery or I do a reset to my CPU, if there is no target in front of the VL53L1X, after the initialisation phase (sleep mode) the current consumption is 3mA (expected 6uA) and every 30s the CPU wake-up send a good distance measurement and go to sleep with 3

Hi ST team and community !I'm here because i have some troubles on the processus of initialisation of multiple sensors VL53L1CB.I use the following library available on gitHub : https://github.com/stm32duino/VL53L1The processus is the following :Shut down reset pin XSHUT of each sensorThen, in a for loop (to setup my 3 sensors) :Power ON the first sensor with XSHUT pinI2C scanner to detect my only sensor ON (normally at address 0x29)Create my C++ component with the I2C link and XSHUT digital/analog PINInit sensor with the new address with InitSensor function in the class VL53L1 of C++ APII2C scanner again to check if the address has been changedThen, switch to another sensor in the for loop until initialisation of my 3 sensors.My problem is when the for loop arrives on the third sensor, it's impossible to execute InitSensor function and the program turn to infinity. Question is, there is a RAM probleme when i create C++ component with "new/delete" ? (load the entire VL53L1 class ?) I h

Hello,I'm currently working with the VL53L1X distance sensor on the nRF52. I'd like to use two of them with te same i2c busses. Therefore, I need to change the address of one of these.I have successfully used a single sensor (using the default address 0x29). Now I want to change the address of this sensor (still using a single sensor), but when I try to read the distance, I get error -13.The I2C address is correctly changed, because i do get this new address when I read the I2C address buffer (0x0001). Also, my logic analyser confirms that the new i2c address is used, but the read/write command is not acknowledged (so no distance is read of cource).I looked to the api and logic analyser results in more detail, and I added the following line in the function VL53L1_init_and_start_range() (from vl53l1_api_core.c):if (i2c_index == 0x001 && buffer[0] == 0x29 && Dev->I2cDevAddr != 0x29) { buffer[0] = Dev->I2cDevAddr; }(This line changes default i2c address (0x29) to the

My code and console are as presented below. Values are on the console are fixed, they don't change even if i move an object in front of the sensor. Also i dont understand what should i put in "index" byte that is shown in data sheet./* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * <h2><center>© Copyright (c) 2021 STMicroelectronics. * All rights reserved.</center></h2> * * This software component is licensed by ST under BSD 3-Clause license, * the "License"; You may not use this file except in compliance with the * License. You may obtain a copy of the License at: * opensource.org/licenses/BSD-3-Clause * ****************************************************************************** */ /* USER CODE END Header */ /* Includes -------------

Hi All,We foresee cross talk calibration ​for VL53L0X in our application as we are working on enclosure with filter glass on top of VL53L0X .To get understanding of cross talk calibration working, I tried "VL53L0X_PerformXTalkCalibration" with distance parameter as 100 (10 cm), 200 (20cm), 300 (30cm) and by keeping white and grey object at mentioned distance. I always found return value of function pXTalkCompensationRateMegaCps always zero.Why I am getting always zero? What I am missing during my testing?

Given that the VL6180-SATEL breakout board has no mounting holes, is there a preferred method to accurately and rigidly mount it in the desired position and parallel to the mounting surface?I would prefer to have it removable, so a permanent adhesive does not appear to be the best solution.Thanks

Hello everyone,I am currently trying to calibrate VL53L1X sensors which are covered by a 4mm thick glass.I am using the ULD from ST to calibrate the offset and xtalk.I achieve a better result with calibration, but I still don't get further than 70-80 cm.According to the user guide the ranging curve with calibration should look like this.But in my case it looks more like this:So basically just like the ranging curve without xtalk calibration, only now the deviation starts a little further away.In the calibration process I also noticed that the XTalk calibration distance (XCD) determines the achievable range of a sensor after calibration.For example, if the XCD of a uncalibrated sensor is at 85cm, the range to which the sensor can produce acceptable results after calibration is also around 85cm.But the above picture found in various user guides shows that after calibration the sensors should also produce good results for ranges bigger than XCD.Am I doing something wrong? Is it the cover

My application requires scanning multiple zones (ROIs) and comparing the results. When I do this I see an offset that varies somewhat randomly based on the shape and position of the ROIs. I see in the UM2133 user manual that there is a calibration procedure to correct offset per zone:VL53L1_SetOffsetCalibrationMode(Dev, VL53L1_OFFSETCALIBRATIONMODE_MULTI_ZONE);and to apply the correction per zone:VL53L1_SetOffsetCorrectionMode(Dev, VL53L1_OFFSETCORRECTIONMODE_PERZONE);My question is: Could you explain how this multizone calibration and correction works and where the per-zone data is stored? The data structure in the following quote from the user manual is only for the overall offset calibration right? There would need to be offset data stored for each ROI right? Thanks, Martin6.3.4 Offset correction options In multizone scanning mode, the offset correction can be improved by using a per zone calibration. If the calibration is made using this option, the user can apply a per zone calibr

We would like to know sensing distance target's size spec.Our team had tested with some small pole as 1inch diameter and 2 inch height cylinder that put on table.But from upper to bottom as in front of target VL53L0X cannot detect this cylinder distance.We have tested some another medicine bottle also, it shows similar result.My understanding of TOF is photon detect by SPAD with avalanche but it takes some level of volume reflection at surface in SPAD.If there are some spec of this issue please let me know.

I am testing the VL53L0X ability to accurately measuring the distance to objects of different materials and different sizes. The sensor is in continuous mode and I am using VL53L)X_GetRangingMeasurmentData to read the distance and reflectivity value. The parameter I am reading for distance is RangeMilliMeter and the parameter I am using for reflectivity is SignalRateRtnMegaCps. I have found that as the SignalRateRtnMegaCps value goes up the distance error increases. At 25�? the distance reading to a large sheet of brown cardboard is about 25.5�? and the reflectivity reading is 122,316. But at the same distance, the distance reading to a piece of white cardboard is about 35.3�? and the reflectivity value is 58,675. Are large distance errors to be expected as the reflectivity value goes down? Is there anything that can be done to reduce this error? Is it possible to use the Reflectivity reading to reduce this error? I see this question has bee

Hello, I have series of questions related to the data implementations using SPAD zone settings. After reading of manuals i made conclusions how to use this feature of the sensor, but i'm not sure if my conclusions are correct.1. I'm interested in accuracy of data returned by sensor in different zones. I tested all center zones started from 16x16 and reducing it to 4x4 size array. And each redusing gave me differense almost in 1.5cm, so the difference between value that retured in 16x16 case and 4x4 case equals 7-8cm! I had clear conditions of the experiment: sensor was fixed vertically in front of plane wall. I just wondered why the zones with the same center have such differents in output value.2. The second quastions is about if there any possobility to define geometric locations of the zones. User manuals said that 16x16 array has 27 FoV, 8x8 -20 FoV, 4x4-15 FoV. So i'm really wondered how those zones geometricly exists, because the reducing of the FoV is not uniform (if it was unif

I would like to use VL6180V1 in one of my project.I am interfacing it with STM8L MCU. For the sake of simplicity, I would like to copy the settings of the arduino library of VL6180X : https://github.com/sparkfun/SparkFun_ToF_Range_Finder-VL6180_Arduino_Libraryandhttp://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/DM00122600.pdfI would like to know if it would work or not because of the difference between VL6180 and VL6180X (Presence and absence of ALS). If not, then please guide me with the register setup. The API that is available is for STM32 and not STM8. Hence I am requesting for this clarification.

..

I have connected VL53L1X sensor to Onion omega2+ controller i2c driver. I2c clock frequency is set to 100khz. For Detecting Slave Devices we have used below command:"i2cdetect -y 0"Output of above command:root@***:~# i2cdetect -y 0   0 1 2 3 4 5 6 7 8 9 a b c d e f00:     -- -- -- -- -- -- -- -- -- -- -- -- --10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --40: -- -- -- -- -- -- -- -- -- -- -- -- -- 4d -- --50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --70: -- -- -- -- -- -- -- --As per the datasheet default slave ID is 0x29 but the sensor is responding to 0x4D.Even if we connect XSHUT pin to GND, VL53L1x sensor is responding .We have connected the pullup resistor across the I2C pin and XSHUT pin .

..

I've got a custom board with the VL53L3 connected to a Silicon Labs chip. The interface to the sensor works. Saving and restoring calibration data is kicking my ***.My calibration code makes these calls: GPIO_PinOutClear(VL53L3_ENBL_PORT,VL53L3_ENBL_PIN); vTaskDelay(2); GPIO_PinOutSet(VL53L3_ENBL_PORT,VL53L3_ENBL_PIN); vTaskDelay(2);VL53LX_WaitDeviceBooted(Device);VL53LX_DataInit(Device);// start calibration here:VL53LX_SetDistanceMode(Device, VL53LX_DISTANCEMODE_SHORT); // before calibration, eh?VL53LX_PerformRefSpadManagement(Device);VL53LX_PerformXTalkCalibration(Device);VL53LX_PerformOffsetSimpleCalibration(Device, 4);// (I have also experimented with VL53LX_PerformOffsetZeroDistanceCalibration)After this calibration data, I print the result...  VL53LX_CalibrationData_t calibration; VL53LX_GetCalibrationData(Device, &calibration);  printf("static uint8_t calibration[] = { \n ");  uint8_t *cal = (uint8_t *)&calibration;&

Hello,I'm trying to use the VL53L1X on my nRF52DK, but I experience some problems.Previously, I've successfully used the VL53L1X with an Arduino UNO using the pololu Arduino library (link below). For my project I need to use this sensor on the nRF52, so I've rewritten the vl53l1_platform.cpp and main .ino code to C (the other files are from ST's VL53L1 API, which are already in C).When the sensor is not connected, the nRF52 is writing the correct data to the SCL and SDA lines, but if I connect the sensor, these lines give incorrect data. Instead of sending to address 0x29, it sends to address 0x7F or 0x00. And instead of sending the data 0x01 and 0x0F, it sends 0xFF and 0xFF (or 0x00 and 0x00).I have correctly connected and initialized the INT and XSHUT lines.I'm not sure what the problem can be, because it worked with the Arduino UNO, but not with the nRF52 (even though the I2C is working correctly without the sensor).My setup:nrf52DKVL53L1X Time of Flight sensorLogic analyser to read

Hi,Total newb here, so here it goes:I have previously used the Arduino BLE Sense board with a VL53L1X sensor. I am now trying to use 1 (if possible, 2), VL53L3CX sensors from Pololu:https://www.pololu.com/product/3416/blogA couple questions:1.    Can I use the Arduino BLE Sense board with the VL53L3CX, without much if any additional code and get distance and timestamp features? I am learning Python, but am completely unfamiliar with C++/C. It appears I could use the BLE Sense board because:a.    The X-Nucleo-NFC04A1 board’s code is compatible with the BLE Sense architecture: https://www.arduino.cc/reference/en/libraries/stm32duino-x-nucleo-nfc04a1/                                              i.    Re

Is there any way to configure the VL53L1X sensor to deliver either the strongest or nearest reflector (reflector at closest distance) ? The latter case would be preferrable for our application scenario.

Hello,is there any way at all to make the offset calibration data (and maybe the cross-talk-calibration data) sent to the VL6180 not volatile like this? What is the reasoning behind it being overwritten after every restart? The same goes for the device address. Although that seems at least a little more reasonable to me.Background: For an IoT Project we will be using multiple VL6180 (together in one case called "Sensorbox" for this purpose) controlled by one MCU. However, the MCU will not be in the same "Sensorbox" but connected to it via a short cable. Therefore, the MCU is interchangeable between multiple "Sensorboxes" and by extension multiple sets of VL6180s. It is next to impossible for us to do the calibration with the exact same MCU that will be used in the final application. Transferring the different sets of calibration data for each Sensorbox between MCUs is more than just annoying. In addition to that, the MCU is battery powered where energy consumption is a major factor and

It looks like the ambient rate delivered by the sensor drops, the better the reflector is (the higher the signal rate is). In a practical evaluation the ambient rate dropped from 40 kcps to 0 kcps when the signal rate increased from 400 kcps to 12000 kcps.Is this behaviour normal ? How does the sensor measure the ambient rate ?