Imaging (sensors)

I'm working on a design for a PCBA with enclosure, using the VL53L0X. There's a chance the cover glass will get dirty, so we took some tips from this youtube video regarding the use of an opaque divider: https://www.youtube.com/watch?v=BHM2CZVXZGcIdeally, we'd like to be able to build the divider into our enclosure instead of ordering an additional component. We'd also like to mold the enclosure from one type of plastic (no double-shot molding, to keep costs down). We can achieve clear cover "glass" no problem, and then texture the mold to make the rest of the enclosure semi-opaque to the human eye. My question is whether we can use texture in a similar way on the divider between emitter and receiver. Is that opaque enough to function like the divider in the video? We wouldn't expect photons to pass through unimpeded on a straight path, but I'd call it closer to translucent than fully opaque.Is this a scenario you've encountered before? Or can you dive a little more into the sensor's t

Hi all,there is a way to set a Threshold for VL53L1  and keep the setting even if a power off / power on?

Hi,I came across of this video of people counter recently from STMicroelectronics. I was wondering where can I find more information about it or code. Because , I don't understand how field of view is divided into two zones. I couldn't find anything like that in the API.

..

..

On our prototype circuit boards with VL6180x sensors there are 6 sensors per board. On a couple of our prototype boards (about 10% of our boards) we have seen just a single sensor able to respond over I2C but cannot start ranging. The result range status register always reports a  result__range_error_code: 1 - VCSEL Continuity Test error. I2C communications are fine and all other 5 sensors are able to range.What is this power up test doing and what could cause this error?

..

I need to simply add VL53L0x API STSW-IMG005 to my project without any compilation errors. And need to know the necessary functions to get the distance.Regard

 The general API user guide, UM2356 (rev 2), says that the min timing budget is 20ms, but the ultra-lite driver guide, UM2510 (rev2), says 15ms is the minimum. I've tested with 15ms (I'm using the ULD) and it seems to work fine, but just wanted to make sure that is within the recommended operating range.Similarly, for the inter-measurement period (IMP), the two guides give different info. The ULD guide says the min is greater than or equal to the timing budget, whereas the generic guide says it must be at least the timing budget + 4ms. Wondering which one is correct? The ULD also further confuses matters by showing a timing diagram that seems to indicate the 'get ranging data' and 'clear interrupt' operations occur after the timing budget has expired. So it seems that if I want to run multiple sensors on the same I2C bus (which I do), I might need to take into account that extra time before I can move on to the next sensor? Is that where the extra 4ms is coming from?

VL53L1X overshoot?In my initial testing with the VL53L1X, I'm seeing that by rotating the sensor from directly facing an object to facing the ceiling, which is well over the max distance away (I'm operating in 'short' mode, so that should be 1.3m), I get spikes up to about 1.8m at the max acceleration points - when I stop rotating the PCB, and when I start rotating it again. Is this kind of 'overshoot' normal? Interestingly, I observe it with 100ms timing budget/inter-measurement period, but not with 15ms (see attached graphs).link: https://community.st.com/s/question/0D50X0000AqqOzI/vl53l1x-overshoot?s1oid=00Db0000000YtG6&OpenCommentForEdit=1&s1nid=0DB0X000000DYbd&emkind=chatterPostNotification&s1uid=005b0000001s1yU&emtm=1559063592550&fromEmail=1&s1ext=0

Dear members,I am currently trying to interface Arduino Atmega 328p with VL6180X via I2C Bus. I have prepared basic code for reading Range value in single shot and continuous mode, it is working file. Now I changed I2C SCL to 100 KHz, 50 KHz, 20 KHz , sensor seems to be working file. I have connected DSO Oscilloscope and checked the I2C data frames, everything seems to be fine.Now due to project requirement I must use I2C SCL = 10 KHz only. With this freq, the data value always remains to either 0 or 255, and the RESULT__RANGE_STATUS registe r(0x04D) has value 0x01. I tried disabling sysrange__early_convergence_enable from register SYSRANGE__RANGE_CHECK_ENABLES (0x02D), still no help.Surprisingly I can read device ID (IDENTIFICATION__MODEL_ID) at this frequency, which confirms that there is no any issue on I2C side. I suspect there is some issue on writing register value or some timing parameter on sensor side. Does anyone has tried to use this sensor at 10 KHz.

May I use X-NUCLEO-53L1A1 with 53L0-SATEL-I1 and vice versa X-NUCLEO-53L0A1 with VL53L1X-SATEL

Hello I'm currently trying to create a driver for the mbed platform (especially the LPC1768, as I work with this one the most) and I wanted to know, if the following header files are actually needed:windows.htime.hSERIAL_COMMS.hAlso, are the log files (vl53l0x_platform_log.h and vl53l0x_platform_log.cpp -> I'm using C++) and the vl53l0x_i2c_win_serial_comms.cpp needed?

Hi all,I'v modified the example of MultiSensorRanging in STM32CubeExpansion_53L1A1_V2.1.0. I'v fitted JMP U11 and U18, and modified the file X-NUCLEO-53L1A1.h as indicated.All sensors renging but only the centered generates interrups! #ifndef VL53L1A1_GPIO1_SHARED /** * @brief select use of shared interrupt * * Must be set to 0 (or not defined) for one interrupt per sensor * Must be set to non 0 for shared interrupt line * see @sa VL53L1A1_GPIO1_C_OPTION */ # define VL53L1A1_GPIO1_SHARED 0 #endif    /* X-NUCLEO-53L1A1.h */ #ifndef VL53L1A1_GPIO1_C_OPTION /** * @def VL53L1A1_GPIO1_C_OPTION * @brief select GPIO1 to exti mapping for center or shared interrupt * * Set option value or un-define it to match with board configuration * @li not defined or 0 : U14=On and U17=off => GPIO1_C = PA4 * @li defined and not 0 : U14=Off and U17=on => GPIO1_C = PC1 */ # define VL53L1A1_GPIO1_C_OPTION 0 #endif   #ifndef VL53L1A1_GPIO1_L_OPTION /** * @def VL53L1

Hi all,Someone know if VL53L1X-SATEL have a cover glass or if it is necessary to buy apart?Thanks

Hi.Please help me with VL53l1.1)     Is it possible to read distance from individual pixel or is it only some kind of interpolation of the 4 x 4 region?2)     Is there a description of registers which should be modified (and how they should be modified) to set size and coordinates of ROI (or pixel if it is possible)? I managed to run en.STSW-IMG009, however it doesn’t have the above function (it is possible to set size only, but not coordinates). I tried to run en.STSW-IMG007 and failed.Light lib has the following function:VL53L1X_ERROR VL53L1X_SetROI(VL53L1_Dev_t dev, uint16_t X, uint16_t Y) { uint8_t OpticalCenter; VL53L1X_ERROR status = 0;   status =VL53L1_RdByte(&dev, VL53L1_ROI_CONFIG__MODE_ROI_CENTRE_SPAD, &OpticalCenter); if (X > 16) X = 16; if (Y > 16) Y = 16; if (X > 10 || Y > 10){ OpticalCenter = 199; } status = VL53L1_WrByte(&dev, ROI_CONFIG__USER_ROI_CENTRE_SPAD, OpticalCenter); st

​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.