Imaging (sensors)

​Can someone point me in the direction where I can find a document giving the I2C register locations to control the VL53L0X. I am trying to read out ranges using an FPGA and the standard I2C bus but all I have found is the device address is 0x52.Thanks

..

Hi all,I have been experimenting with the X-NUCLEO-53L1A1 and the NUCLEO-F401RE and here are my results. Actual distance White Box Black Box Difference20cm 20.4cm 19.4cm 1cm45.5cm 46cm 56.7cm 10.7cm64.1cm 65.6cm 80.8cm 15.2cmTiming budget:100msDistance Mode: ShortI did try to calibrate, but did not seem to make a huge difference.I did try medium mode but did not seem to change much.Everything else is left to default in the GUI.Is there something that I might be missing?Thanks,

We'd like to measure distance in a tube with VL6180X. Tests with a diameter of approx. 5 cm show that the max. distance is reduced and the sensor is underranging. That is probably because the sensor receives some light reflected from the side walls. Is it possible to filter these measurements using FoV change or with something like cross talk compensation?When using VL53L1X we can narrow the FoV using less SPADs and it works fine then. But I haven't found any way to do so with VL6180X.

According to the docs I've read maximum FoV using 16x16 SPADs is 27 degrees and minimum FoV using 4x4 SPADs is 15 degrees. But if my math is correct, when side of the measured area is 1/4th then the FoV should be approx. 6.7 degrees. Aren't the SPADs of the same size or is there something else affecting the calculation?

When comparing the data sent from VL53L1X ULD and from VL53L1X_Gui I can see some differences.In particular, I was comparing values sent to registers 0x005e and 0x0061 that are used to configure timing budget. I'm not going to write all measurements here, but e.g. for long distance mode and 50 ms budget the ULD sends 0x00ad and 0x00c6, while GUI sends 0x02f9 and 0x038e. Why such a difference? Which one is correct?Same problem applies to some other registers:0x005b - ULD: 0x08, GUI long: 0x00, GUI short: 0x010x005d - ULD: 0x00, GUI long: 0x00, GUI short: 0x02

Hi I was watching this official video on youtube about protective glass covers: https://www.youtube.com/watch?v=BHM2CZVXZGcIn the video there is a mention that the 3D model is available for the protective cover, and I even did see that there is a protective cover when you buy the P-NUCLEO-53L1A1. But quite frankly I only want to buy the covers, because we are already using these sensors in deployment.How/where should I go to purchase these? Searching the internet left me without an answerCheers,Roy

I just got the VL53L1X ToF sensor and I have a k64f board using ARMmbed. I have been searching all day long, but I could not find a library for the board for mbed, does anyone know if there is any library available for this sensor on mbed?

I use Xshut pin to save energy, Do I have to call VL53L1_DataInit() every time that I pull Xshut to wake up the device or only the first time after my microcontroller reset?And the same question with VL53L1_StaticInit()I do not have clear what to do or what not to do every timeI wake up the VL53L1 using Xshut.I have tested both options and it seems that it is not difference but I want to know the best way to manage the situation.

I feel this would solve a couple problems. First, it would allow for more energy to be returned to the detector, increasing the signal to noise ratio and second, it would allow customers to focus on more specific areas. My questions are - can this be done? (imported question)

..

Hi,I am porting the one of legacy VL53L1 stack (STM api ver 1.1.37.12156 ) for one of the project. This stack is stable and well tested. However, i am surprised to see the RAM consumption(5.43KB) of the VL53L1_Dev_t  object. This is different in new STM api ver 1.2.11.1840 (932B). I can understand that new api might have optimized or deprecated some of implementations. Why is VL53L1_Dev_t  object consuming RAM memory of 5.43KB? It will really help me if any change list file is available to download or can provide here.

Hello, Is it possible to setup ROI to read SPAD array sequentially one by one or matrix of 4*4 SPADs. I.e to get a map of the measurings?

I'm currently using the VL6180x in a project, and I'm encountering some issues where I believe the prox sensor is being reset. I'm operating in Interrupt + Continuous mode. The symptom is that after running an unpredictable amount of time, while being handled, and moved, the VL6180x no longer produces an interrupt when the minimum distance threshold is passed. I am trying to discover a way to read out the mode of the VL6180x on a periodic basis to determine if it is operating correctly. If it is not, a reset and reconfiguration will recover the device. My confusion is this. I can't seem to find a register that reflects whether continuous mode is running or not. The SYSRANGE__START register is the closest, but it only shows which mode it is set to, and not if it is currently running. I also can't simply set the start_stop bit of this register, because if it is running correctly, this would halt operation. Main question:

..

We are using your VL6180X Proximity sensor, gesture and ambient light sensing (ALS) module for a time of flight sensing application. We are experiencing a problem with unreliable measurement results from the sensor: some sensors output a low value (10 - 20 mm) with no target present, and sometimes low readings (50 - 60 mm) when a target is ~800 mm away. These problems seem consistent with cover glass selection and air gap distance. Do you have any experience with these types of problems? NOTE: This question and answer originated from a customer support case which was handled by us. We regularly review support cases and add any helpful ones here for all to benefit from.

..

Everywhere I look, the VL53L1X Tof Sensor says that it has a standard fov of 27 degrees (or 16x16) and can be reduced to 15 degrees (or 4x4 SPAD array). But how do I do this on the Raspberry Pi (in python)? In your VL53L1X_register_map.h there is a function called: #define VL53L1_ROI_CONFIG__MODE_ROI_XY_SIZE 0x013F   /*!<   type: uint8_t \n   default: 0x00 \n   info: \n   - msb = 7   - lsb = 0   - i2c_size = 1   groups: \n   ['nvm_copy_data', 'roi_config']   fields: \n   - [7:0] = mode_roi_xy_size   */How do I use this or another function to make my ROI 15 degrees (4x4 SPAD) instead of 27 on the Raspberry Pi like your documentation says it can? Or do I have to hook it up to some software and do it in there to change it?

Is three any driver available for LPC 1769.

..

In Section 5 of the datasheet for the VL6180X you are presented with Normal Operating conditions.It lists that the optimum voltage range [2.7,2.9] and the functional range [2.6,3.0].What exactly does the functional range mean ? If I am 3.1V or 3.3V, will the device not work ?What is the difference between functional and optimum ?

I have VL53L1X SATEL development board, I checked the performance of sensor indoors It was accurate and sturdy. But when I checked it outdoors-in sunlight readings varies continuously and haphazardly for steady position of sensor and obstacle. If this sensor is not suitable in sunlight then please suggest me any other sensor for my obstacle avoidance device which must have minimum range of 400mm and operatable in sunlight.

I checked datasheet of part VL53L0CXV0DH, but i cannot find information about laser power. There is description about power consumption of whole device but no data for laser only. We need this information for application certification process.Is there anybody who have this information ?

..

Hello,I made a PCB with 7 VL53L1x, that I soldered by myself. I'm using the ST VL53L1 API.6 of them are working great, but the # 7 return error -13 : VL53L1_ERROR_CONTROL_INTERFACE, referenced in vl53l1_errror_codes.h as : "/*!< error reported from IO functions */" Everything works until I start VL53L1_StartMeasurement() which returns no error.After that, when I try to get any values, (with VL53L1_GetMeasurementDataReady(Dev1, &measure) for example) It returns error = -13.I changed this sensor with a new one and still get the same error.Do you have any idea to get this solved? Or to disable IO functions? I didn't find anything in the manual.Thanks a lot,Pierre