Imaging (sensors)

Can TOF sensors such as VL53L1X and VL53L5CX be cleaned with alcohol and/or cleaning wipes or be submerged in cleaning alcohol?

I am trying to compile the drivers for the ToF sensor: VL53L4CX for an embedded Linux application. I am running Ubuntu 22.04. When I try to make the drivers I get the following error:   CONFIG_STMVL53LX=m make -C /lib/modules/`uname -r`/build M=$PWD make[1]: Entering directory '/usr/src/linux-headers-6.5.0-15-generic' warning: the compiler differs from the one used to build the kernel The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 You are using: gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0 CC [M] /home/USERNAME/programs/VL53L4CX_LinuxDriver_1.1.2_bare_1.2.8/driver/vl53Lx/stmvl53lx_module-i2c.o /home/USERNAME/programs/VL53L4CX_LinuxDriver_1.1.2_bare_1.2.8/driver/vl53Lx/stmvl53lx_module-i2c.c:567:19: error: initialization of ‘int (*)(struct i2c_client *)’ from incompatible pointer type ‘int (*)(struct i2c_client *, const struct i2c_device_id *)’ [-Werror=inc

Does anyone know where I can find a Cadence/Allegro footprint for the TOF sensor VL53L5CX?  This is the optical LGA16 package.  I would also like to find a Cadence/CIS symbol. thank you!

Hi all, I am trying to use a PIC18LF47K42 to read the distance from the Light Ranger 2 click board, which uses the sensor VL53L0X. I copy two folders: core and platform, which are  inside the folder en.STSW-IMG005\VL53L0X_1.0.4\Api I add these file into the project header files and source files  In the main.c, I try to call only one function VL53L0X_DataInit(); same as below void main(void)  {   VL53L0X_DataInit();   while(1)   {      }  } The problem is that I cannot compile. The MPLabX shows the below error: ./../../Year2/MGMT102/0-Datasheet/01-ST_VL6180/API/en.STSW-IMG005/VL53L0X_1.0.4/Api/core/src/vl53l0x_api_core.c:29:10: fatal error: 'vl53l0x_api.h' file not found #include "vl53l0x_api.h"      ^~~~~~~~~~~~~~~ 1 error generated. (908) exit statu

I am using the VL6180 (not the X version).  This is TOF only.  When reading in continuous mode, I'm getting a tolerance of +/- 1mm and sometimes more.  I'll list my settings below.    My application will measure distances from 10mm to 100mm.  Right now I have the inter-measurement period set to 500ms and this is flexible.  How can I optimize my settings further for accuracy? thanks     VL6180_WriteByte(0x0207, 0x01); VL6180_WriteByte(0x0208, 0x01); VL6180_WriteByte(0x0096, 0x00); VL6180_WriteByte(0x0097, 0xfd); VL6180_WriteByte(0x00e3, 0x00); VL6180_WriteByte(0x00e4, 0x04); VL6180_WriteByte(0x00e5, 0x02); VL6180_WriteByte(0x00e6, 0x01); VL6180_WriteByte(0x00e7, 0x03); VL6180_WriteByte(0x00f5, 0x02); VL6180_WriteByte(0x00d9, 0x05); VL6180_WriteByte(0x00db, 0xce); VL6180_WriteByte(0x00dc, 0x03); VL6180_WriteByte(0x00dd, 0xf8); VL6

Hi,We have an issue with a production build of a VL53L1X based design. The VL53L1X is interfaced to a PIC18F micro, I have inherited the codebase and hardware. The initial production run was for 500 units, of these approx 260 passed our production tests and some have been working well in the field for some time.The remaining 240 all exhibit an almost identical failure mode. Basically the readings will only  1 - Uart Output (Legacy Code - Good Sensor) VTOF=345mm (5989) (0) VTOF=346mm (5978) (0) VTOF=346mm (6020) (0) VTOF=344mm (5949) (0) VTOF=345mm (6153) (0) VTOF=346mm (5979) (0) VTOF=347mm (6098) (0) VTOF=345mm (6147) (0) VTOF=347mm (6176) (0) VTOF=346mm (6166) (0) Min: 344, Max: 347, Avg: 345.70, Std Dev: 0.95   2 - Uart Output (Legacy Code - Bad Sensor) 

I have a VL53L8CX time of flight sensor connected via I2C on a custom board. The Board has other devices that can talk on I2C no problem. now i cant see the i2c address of the ToF device. from my understanding everything seems to be fine and in accordance with the datasheet. However there are two things that might be not correct and i want to make sure that my assumptions are not wrong. about the LPn pin (A2) in the datasheet this is written:Enables communication. Drive this pin to logic 0to disable I²C communication when the device isin low-power mode. Drive this pin to logic 1 toenable I²C communication in low-power mode.This pin is typically used when you need tochange the I²C address in multidevice systems. Ifit is not used, or if interfacing via the SPI,connect to IOVDD with a 47 kΩ p

I tried using VL53L5CX with ULD API v1.3.6 with an ESP32-S3. I successfully ported the base C function for I2C, as I can talk with the sensor during the first part of the initialization process. Unfortunately, when I reach the NVM part, the function _vl53l5cx_poll_for_answer() fails, and I keep getting VL53L5CX_MCU_ERROR as the return value: I was looking for answers online, especially around ST Community, but I cannot find anything about this specific part of the function failing. As I haven't modified the API itself, I really need some external help to resolve this issue.Does anyone know how to revolve this ?

Hello.I am working with a vl53l1x sensor and i need to know if this sensor report a distance when the target is not detected and the measurement is valid, like the vl53l3cx sensor that report back 8191. Does this sensor report the same number or other number in this condition? Or does not report back anything when this happen?

Hello !I'm working on the VL53L5CX sensor with a Nucleo L432KC.Using the ST example, and after succeeded the initialization of the VL53L5CX, the sensor's data are never ready. In the following function, the p_dev->temp_buffer[1:4] are all equals to 0 :  uint8_t vl53l5cx_check_data_ready( VL53L5CX_Configuration *p_dev, uint8_t *p_isReady) { uint8_t status = VL53L5CX_STATUS_OK; status |= RdMulti(&(p_dev->platform), 0x0, p_dev->temp_buffer, 4); for (uint8_t i = 0; i < 4; i++) printf("0x%02X", p_dev->temp_buffer[i]); printf("\n"); if((p_dev->temp_buffer[0] != p_dev->streamcount) && (p_dev->temp_buffer[0] != (uint8_t)255) && (p_dev->temp_buffer[1] == (uint8_t)0x5) && ((p_dev->temp_buffer[2] & (uint8_t)0x5) == (uint8_t)0x5) && ((p_dev->temp_buffer[3] & (uint8_t)0x10) ==(uint8_t)0x10) ) { *p_i

"2.1 Software Interface" in the VL53L5CX datasheet states that the driver (C code, reference Linux® driver) is delivered.How can I get this driver?Please let me know if there is a download URL for the source code.

I just purchased the VL53L5CX-SATEL Breakout Boards for VL53L5CXhttps://estore.st.com/en/vl53l5cx-satel-cpn.htmland i have been trying unsuccessfully to get it to work with an Arduino Mega 2560. Does anyone know if it is possible to get it working with the Arduino Mega 2560 ? If not, should it work with an Arduino Due ?

Hi:I'm testing the VL53L4CX and I'm experiencing some problems:1. When an object is within 3.5m and there's a wall 5 metres away, sometimes the returned distance alternates between two distances.2. When there is a mirror within 3.5m, VL53L4CX sometimes will return a distance more than 3.5m incorrectly.After researching the returned data, I found that "Extended Range" is turned on incorrectly.Can I know how the "Extended Range" function works and how to control it? Thankyou.Cyt

I have been testing with the VL53L1X TOF sensor and am curious on the durability of the sensor in rugged environments. Such places would look like an industrial environment where vibration and impacts in inevitable. The sensor PCB would be potted and fully enclosed in a containment box. However, an opinion by others on how it would fare would be greatly appreciated. I know the data sheet shows shock as being an issue. Thanks!

Hello, I'm trying to use a ToF-Sensor to track the distance of metal parts (sheets, cog wheels etc.) usually in the range of 0-60cm. The thing is that I am only interested in the distance of the surface that is directly below the sensor, the center of the FoV of the Sensor so to speak. I tried using the VL53L4CD Sensor, which is a Single Zone Sensor and while the readings where accurate for flat surfaces, they weren't for surfaces with sudden changes in height within the sensors FoV(obviously). Hence why I'm considering using a Multi-Zone Sensor to get the distance measurement I'm interested in. So is it possible to only measure the distance of the surface which is in the center of the sensors FoV this way? Which sensor should I consider and what settings should I use to get the most accurate measurement?

In the ULD driver for the VL53L8 is the file vl53lmz_api.c. In line 354 to 364, the firmware is loaded in pieces of 0x8000 bytes:My microcontroller has not enough ram to handle such big blocks, so I have to load the firmware in smaller pieces. But for what are the write commands to register 0x7FFF between loading the FW blocks in line 358, 361 and 364?What has to be adjusted to write the FW e.g. in blocks of 0x2000 bytes?Used product: SATEL-VL53L8

As shown in the figure is a ball, the depth difference of one pixel is less than 3.7mm. But as shown in the histogram, the depth difference is more than 15mm. I would like to know if this is caused by noise or some other reasons? 

Hello,I noticed a difference of ranging time on VL53L4CX in function of target presence or not.My parameters : AVG = 3 ; DTIM = 33 ms ; INTERMEASUREMENT = 100msCurrent measurements : Without target : pulse width = 38 ms ≈ DTIMWith target : pulse width = 69 ms ≈ 2 x DTIM

I got a custom board made with these two ics and I tried to program the mcu. However, when facing FLASH and RAM size constrains I decided to remove certain parts of the library to make it fit(I removed crosstalk calibration since I don't have a cover material).  However I am now facing issues with the sensor not working(I2C works), and I have to determine if it's because of something I did, board design or something wrong with the sensor. The measurements that I'm getting have the 255 status, and while debugging I found that the sensor returns less streams than expected. So a couple questions first:1) Does the sensor require restarting via XSHUT to properly work?2) Would the ST-LINK programmer be able to supply enough power for both chips?3) How should I proceed with debugging?4) Does ST have a smaller library for this sensor(I have been unable to find one)?

..

The SATEL-VL53L8CX dev boards were all out of stock, so I picked up the LS53LX-SlL8 Light Saber Sensor VL53L8CX by Gilisymo for debugging before I build my own PCB. I am interfacing with the sensor via the Adafruit itsy bitsy nRF52840 (but have also used the xiao nRF52840 Sense and the ESP32-S3 QtPy for debugging purposes).I had previously been able to work with the VL53L5CX easily using the Sparkfun library with a very similar set up. However, using the STM32duino library I can't communicate with the sens

Hello, I noticed that using the X-CUBE-TOF Package with the STM32WL55JC Nucleo-Board has an issue with the I2C-Peripheral(I2C-2). This genrates the I2C code in the IDE. 

If I want to use the Mini-PCB of the VL53L1X SATEL, which type of plug do I need to plug that in? (I would like to label this with "Time of flight" but unfortunately, this seems to be not possible for me ;-( ).

Need a help.Got VL53L1B (with a letter "B" at the end), unfortunately can't find any reference to it.Please help me recognise what is "B" suffix mean? Is it VL53L1 or VL53L1X or ...?Thanks a lot!

Hi, I'm new to the community and I hope someone could help me with the following. I was wondering is there any way to distinguish between a human body and a static object, like a piece of paper when detecting obstacles with ToF sensors(e.g. VL53L4CX, VL53L5CX)? Is there a way to detect some sort of body heat or any particular aspect of the body that will differentiate the human presence from other constant entity?Are there any colour limitations of the ToF sensors such as very dark(black) surfaces that absorbs the photons and hence limiting the reflection of the emitted light?I've read in some articles that these sensors don't like curved surfaces as the laser beam will not bounce back to the collector...would this compromise the human body detection?I would appreciate any advise or input and thank you in advance.