I have a sensor part no VL53L1CBV0FY/1 I use driver version 6.6.1.GetDeviceInfo reports:Name: VL53L1 cut1.0Type: VL53L1Product type: 0Version major: 1Version minor: 0My initialization sequence is like this: status += VL53L1_WaitDeviceBooted(Dev); st...
I have 6 VL53L3CX sensors connected via the same I²C bus. For this reason, the I²C address of each sensor must be changed as described in the UM2778 User's Guide.Does this procedure have to be carried out each time the device is restarted or disconne...
That's not meant as a question, more as an input/feed-back for ST developers or users of the VL53L0X device.I have a custom PCB with STM32F091 and two VL53L0XSymptom:If I initialize one only of the sensors, that sensor works great and gives good res...
I am using VL53L1X for indoor presence detection, mounted on the ceiling and looking at the floor, and it is doing great. However recently I tried it in a new location, and I have nothing but errors. I have several sensors there, and all of them are ...
While evaluating the VL53L1 TOF sensor the following quetions arose. Thanks in advance for any feedback.- The full featured API provides functionality known as RefSPAD calibration (missing in UltraLite API), which is suggested to be used when adding ...
Hello my company we use VL6180X for proximity sensing, in a robot gripper's finger. The sensor is located in the middle of the finger 10mm deep 7mm wide hole. The range measurements data of the finger's sensors are so different. I think this is cause...
I use VL53L1X ultra lite driver.For example:The value written to ALGO__PART_TO_PART_RANGE_OFFSET_MM(0x001E) register is 0xFF24 when VL53L1X_SetOffset() is called with OffsetValue -55.The value got from ALGO__PART_TO_PART_RANGE_OFFSET_MM(0x001E) regis...
HelloI open this thread as a continuation of this other one, which is very long. My problem is that the boot states I read with "VL53L1X_BootState" (0x02 and 0x03) do not match the documentation (0x00 and 0x01).As John says in the aforementioned thre...
