Imaging (sensors)

The VL53L1 GUI does not see the sensor.But the SimpleRanging works with the board:================================================================VL53L1X Examples...VL53L1X Model_ID: EAVL53L1X Module_Type: CCVL53L1X: EACCRanging loop startsCount=   0, #Objs=0Count=   0, #Objs=1 status=6, D= 1983mm, Signal=4.13 Mcps, Ambient=0.16 Mcps..................................=================================================================

Hi, I am working on VL53L1CB sensor for designing Obstacle detection sensor.I have tested with accuracy and range of sensor.I am encountering the problem of random ranging when there is no target in front of sensor.I kept the sensor at height of 15cm from base and there is not obstacle in front of it within FOV of 27 degree. Still, it is showing ranging distance varying from 850cm to 1200cm sometimes.I am not getting weather this is the case of ground detection or there is any other reason.Please assist me dealing with thisRegardsAkansha

Hello,I can find the "VL53LX_MAX_RANGE_RESULTS" parameter in "vl53lx_platform_user_config.h".But I can't find the usable range of the "VL53LX_MAX_RANGE_RESULTS" parameter.The documentation only mentions the default value 4.​What is the usable range of the ​"VL53LX_MAX_RANGE_RESULTS" parameter?Thanks.

Greetings.If I point the sensor at a wall and then slowly move my hand into the sensor's viewing area, the sensor gradually changes its reported range from the distance to the wall to the distance to my hand as shown in this graph.Is it possible to set up the sensor to immediately report my hand's true distance as soon as it is detected instead of reporting a false distance until it has been fully moved in front of the sensor?Here is my API setup code:VL53L1X_SensorInit( 0 ); VL53L1X_SetTimingBudgetInMs( 0, 20 ); // 20ms sample time VL53L1X_SetInterMeasurementInMs( 0, 20 ); // Sample every 20ms VL53L1X_StartRanging( 0 );Thank youScott Wild

..

..

I checked the Application note "AN5561", VL53L3CX maximum ranging performance improvements. I had a question about "1.3 Maximum ranging distance".The performance of Medium distance mode seems to be better than the one of Long distance mode. I thought these tables were exchanged .Is it correct the spec of Table 1? The distance of Medium distance mode is longer than the one of Long distance mode?Thanks at advance

Hello, I am trying to set up a custom PCB with multiple sensors, including the VL53L3CX. As MCU, we are using the STM32G441KBU6, which seems to be too small for the bare driver API, and we did not find any acceptable alternative to the MCU. Is it possible to use the much smaller API from the VL53L1X with the VL53L3CX?

If I want to take multiple readings on a VL53L1X at different ROI's, I need to set the optical centers for each ROI sequentially, one for each measurement.But when exactly do I do that, and what are the pitfalls?e.g. I have a timing budget of 20ms, and an inter-measurement period of 25ms (so 5ms gap between measurements).Then I start ranging on the sensor. Is the first sample wasted? Can I set the ROI before I start ranging?Can I only set the ROI after ranging has started, in the time-budget (actually measurement) phase?Can I only set the ROI after ranging, but in the same inter-measurement period? (the 5ms window in my example)?If I can set the ROI in either phase, what are the safety time budgets? (i.e. how close can I get to the ends of the time-window)Thanks!

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); status += VL53L1_DataInit(Dev); status += VL53L1_StaticInit(Dev); status += VL53L1_SetPresetMode(Dev, VL53L1_PRESETMODE_RANGING); status += VL53L1_SetDistanceMode(Dev, VL53L1_DISTANCEMODE_LONG); status += VL53L1_SetMeasurementTimingBudgetMicroSeconds(16 * 1000);status += VL53L1_StartMeasurement(Dev);My Query sequence is like this: VL53L1_ClearInterruptAndStartMeasurement(Dev); VL53L1_WaitMeasurementDataReady(Dev); VL53L1_GetMultiRangingData(Dev, &MultiRangingData);But returned data is totally bogus:MultiRangingData.DmaxMilliMeter: 0 MultiRangingData.EffectiveSpadRtnCount 24408 MultiRangingData.HasXtalkValueChanged: 0 MultiRangingData.NumberOfObjectsFound: 3 MultiRangingData.RecommendedDistanceMode: 3 MultiRangingData.RoiNumber: 0 Mul

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 disconnected from the power supply, or will the new address of the sensor be permanently saved?Many thanks in advance.

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 results. No matter if it is the left or the right one.If I initialize first one sensor, (changing device address while initializing)then the other (also changing device address while initializing),the second sensor while initializing always runs into API Status: -50 : Reference Spad Init ErrorMy setupcustom PCB with STM32F091 + usual components on PCB TOP2 VL53L0X devices 23cm apart on PCB Bottom.STM32CubeIDEVersion: 1.4.2Build: 7643_20200813_1322 (UTC)VL53L0X_1.0.2 API from en.STSW-IMG005 slightly modified platform stuff in order to run on bare metalNucleo or discovery st-link to program the device------------------------------------------------------------------------------------------------I traced the error down to vl53l0x_api_calibration.

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 stuck with error type 2, and a sig rate at 0 for 90% of their measurements (using different ROI and different time budget. Usually I use 16x16 and 100ms and it is doing great, but here it seems nothing goes). It is not in direct sunlight, but one wall is open to the exterior, so the ambient light is partly sun, partly artificial light from neon light bulb. However the ambient rate doesn't seem to pike higher than I use to see in other cases. The floor is a bit dirty, its paint is dark but reflects light a lot. However errors are the same when an object is present, so the floor may not be the cause.Is it possible that an unknown source of 940nm could mess this up ? An IR CCTV for instance ?

..

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 a cover glass on top of the sensor. Is there a strong benefit using this function or is it negligible ?- Does XSHUT=0 perform a full hardware reset (including the I2C logic) ?- Is it possible to use a ROI of 2x8 or 1x8 size ? If yes, are there any restrictions regarding configuration parameters like e.g. preset mode ?- Is it possible to clean a PCB with a VL53L1 with PCB cleaners without harming the sensor ?- The following parameters in VL53L1_CalibrationData_t are not mentioned in UM2133 regarding calibration, are they missing in the documentation or not required ? customer.global_config__ref_en_start_select ref_spad_char__total_rate_target_mcps xtalkhisto.xtalk_hist_removed algo__xtalk_cpo_HistoMerge_kcps add_off_

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 caused by reflection of the hole's wall like a crosstalk event. We want to make an offset and and a crosstalk calibration method, but it's not clear for me how to calculate the offset difference and the crosstalk difference . Should it be measured from the top of the sensor chip or from the top of the sensor house, like it would be a very thick glass cover? The datasheet writes "from top of the cover glass" but we don't have a cover glass.

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) register is 0x1F24 when VL53L1X_GetOffset is called and the returned offset value is 1993.I meet this issue when offset value < 0.

..

Hello,I am building an IoT level sensor for a vessel. The vessel is emptied at the bottom, and I would like to sense how much stuff is still in there from the top lid. The tank is approximately 40cm deep, and 10x10cm wide and it is dark inside.Considering the wide viewing angle of the proximity sensors (25 degrees) and the narrow vessel, I'm worried that I will get into trouble with false readings, so I was wondering if I could limit the view of the sensor, or that you might know another way of reasonably accurately (+/- 0.5cm) measure the amount of salt in the vessel.Kind regards,Samot

I want to implement LIDAR using multiple VL53L3CX.I have two questions about VL53L3CX.first,In the previous case of VL53L1X, LIDAR was implemented by setting an ROI.As far as I know, VL53L3CX does not have the function to set ROI.Indeed, is there no ROI setting function for VL53L3CX?second,I understand that VL53L3CX has excellent performance in detecting objects regardless of shape or size.Am I correctly aware of the characteristics of VL53L3CX?If so, is it possible to implement LIDAR using multiple VL53L3CX? 

Hi,I have a project with VL6180X sensor. Moving from first prototype to second revision, I have realized that I have no use for AWS sensor. Therefore I can switch the sensor to the non-AWS having, also cheaper VL6180V. Datasheets of these sensors are almost identical. The datasheet of the V model has a absolute range of 62cm. However, the range register in question is only 8 bits long. The X variant works fine with this, of course since it is not possible to measure mm values greater than 0xFF mm (255mm) with the sensor (acording to the datasheet of the X variant). Is there hidden register somewhere where it is possible to read rest of the data or is there a mistake on the datasheet?Here is a link to the datasheet in question. It is a download from your (ST's) VL6180V product page. https://www.st.com/resource/en/datasheet/vl6180.pdf

vl53l0x interfacing STM32F7I used Pololu libraries and replaced read and write functions with HAL functions, at first it worked properly for several hours, but after that it stopped working and returned 8191 value, after two hours it started working again while I changed nothing. Now again it doesn’t work and still returns 8191 and I don’t understand why it’s happening

I see from this GY530 schematic that the module has level converters for the I2C lines, but not for GPIO & XSHUT lines. When using a 5V micro-controller like an Arduino UNO or MEGA to run multiple VL53L0Xs using XSHUT to configure addresses, will driving XSHUT to 5V kill the module (I note from the VL53L0X datasheet that XSHUT/GPIO have max permissible voltage of 3.6V)? If so, what do you recommend for multiple VL53L0X systems and a 5V microcontroller?TIA,Frank

What is the difference betwen Long DM and Short DM in terms of principle of operation?For example in ULD API for Short Distance Mode these registers are used:status = VL53L1_WrByte(dev, PHASECAL_CONFIG__TIMEOUT_MACROP, 0x14); status = VL53L1_WrByte(dev, RANGE_CONFIG__VCSEL_PERIOD_A, 0x07); status = VL53L1_WrByte(dev, RANGE_CONFIG__VCSEL_PERIOD_B, 0x05); status = VL53L1_WrByte(dev, RANGE_CONFIG__VALID_PHASE_HIGH, 0x38); status = VL53L1_WrWord(dev, SD_CONFIG__WOI_SD0, 0x0705); status = VL53L1_WrWord(dev, SD_CONFIG__INITIAL_PHASE_SD0, 0x0606);What are they about?

I can use this senser only together ST micro controller.Also its freeware APIs not enough for this purpose.I think ST must provide neccessary support about this subject without need anycustomer feed back.( Because VL53L1X is belong you )Regards.