Imaging (sensors)

The picture i uploaded is a screenshot from the datasheet. And according to the datasheet, Effective max convergence time depends on the actual convergence time plus readout averaging sample period setting. Please i want to know how to calculate the convergence time. This is simply because i want to be able to calculate speed. Since the sensor reads distance, if i know the time, then i can calculate speed. Or if there is a better approach to be able to calculate speed with the VL6180X sensor, please help me out.Thank you

I am using Pololu's adaptation of the ST library for Arduino. When I call VL53L1_GetCalibrationData() and print the optical center x and y values, I get 0x70 for both. How should I interpret this value? I've tested on an Arduino Uno as well as a MKRZERO. I was expecting these values to be in the range 0x00 .. 0x0F since the SPAD array is 16 X 16. Is nibble order simply reversed? If so, should one reverse the nibble order when identifying a SPAD for other API functions, e.g. VL53L1_SetUserROI()?

Hi allMy vl53l0x sensor is currently giving the "no update" status. The API only mentions that the error will not trigger. What does that mean?What could be wrong when this status is received and how could I resolve it?Thanks in advance

I was testing the returns from the VL53L1X to build up an algorithm for a project, and one of the edge cases is an object outside of a transparent 'wall'. Normally, when there is an object outside of the transparent 'wall', the sensor picks up the object with a slightly lower signal strength than usual. However, when I did it with a reflective object (sheet metal, mostly), the shape of the object seems to be projected where the glass is. Even with a cylinder of sheet metal, the sensor returns that there is a cylindrical shape of points where the (flat) transparent wall is.It's fortunately very good for me for this to behave in this way, but I'd like to see if I can confirm that this is a reasonable return, and not just a lucky scenario.

I have a custom circuit board and below is my setupMCU: STM32L151C8T6Sensor: VL53L0XIDE: AtollicLanguage: CI came to notice that I must include the VL53L0X library to use it, and I'm having trouble doing so. I have downloaded the "en.STSW-IMG005.zip" that contains the library for VL53L0X. I have included the "core" and "platform" folders into my project, but the compilation kept giving me the following error "fatal error: vl53l0x_api.h: No such file or directory #include "vl53l0x_api.h"I have included the .h to my main.c but the compilation error jumps from file to file, "vl53l0x_api_core.c", "vl53l0x_api_ranging.c", etc.

I need to use multiple V6180x SATEL sensors to get distance measurements, however I do not know how to make it work directly through the I2C connection, since once connected the sensor is not even found by the I2C.Is it possible to use this sensor by connecting it directly to the SDA, SCL, 3,3V and ground pins and use it as a common i2c device or do I need to use specific libraries and specific configuration?

HelloI'm trying to go from the frequency 30 Hz to the frequency 100 Hz and I used the manual that ST provides on this and I have the error code -18 which corresponds to#define VL53L1_ERROR_STREAM_COUNT_CHECK_FAIL      ((VL53L1_Error) - 18)/*!< Stream count check fail - API out of sync with device */ on this fonction VL53L1_GetRangingMeasurementData(Dev,&RangingData)I am using an Arduino Mega 2560 to display SPADscould someone explain to me how to fix this?

Hello CommunityAfter a long time of figuring out the api and file structure, I got the I2C communication working. I copied the Single Range Measurement Example from the API-ZIP into my programm. Additionally I ran the I2C-Verification Code, which came out good.Following is my code:// ====================================   #include "mbed.h" #include "vl53l0x_api.h" #include "vl53l0x_platform.h"   I2C i2c(p9, p10); BusOut led(LED1, LED2, LED3, LED4); Serial pc(USBTX, USBRX, 9600); VL53L0X_Dev_t vl_device;   void i2c_test(void); int rd_write_verification(uint8_t addr, uint32_t expected_value);   void i2c_test(void) { int err_count = 0; int expected_value = 0;   uint8_t buff[4] = {0x11, 0x22, 0x33, 0x44}; uint8_t ChipID[4]; int i = 0;   for (i = 0; i < 4; i++) { VL53L0X_RdByte(&vl_device, 0xC0 + i, &ChipID[i]); } expected_value = ChipID[0] << 24 | ChipID[1] << 16 | ChipID[2] <&lt

for VL53L1X sensor, if one target (distance is 1 meter) is partial in the FOV, and another target ( distance is 2 meters) is also in the FOV, so how the sensor calculate the distance, will it average the distance based on lights it got from different target? or it can detect only the nearest target distance? another question is: we tested the eval board, we put the target within the FOV, but not cover whole FOV and not in the center emission line ( 0 degree direction), it can not be detected. only when the target is close to the center emission line, it can be detected. we tried different kinds of target, no one can be fully detected. so the FOV is really 27 degree, or smaller than that? ( we set to short range, middle range, long range, but no help) 

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 unimp

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 fr

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&emkin

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

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   #ifn

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_CON