Imaging (sensors)

Hi at allIm using the STSW-IMG005 API.The function 'VL53L0X_set_reference_spads(...)' gives an error -50.In another thread i read this could be ignored.All other functions after that worked well.But the function 'VL53L0X_PerformSingleRangingMeasurement(..)'allways gives the "no update" status. What could be wrong when this status is received and how could I resolve it?

Hello,I have a question regarding the calibration flow. I have narrowed the RoI to my needs and adjusted the timing/intermeasurement budget and I am using short distance mode.My question now is whether I have to use the same settings when calibrating the sensor, or whether the calibration has to be done without these settings. Cheers, Daniel

I want to add this sensor to stm32f1 https://pt.aliexpress.com/item/33036852017.html?src=google&albslr=222492145&src=google&albch=shopping&acnt=494-037-6276&isdl=y&slnk=&plac=&mtctp=&albbt=Google_7_shopping&aff_platform=google&aff_short_key=UneMJZVf&&albagn=888888&albcp=1626568036&albag=65942329430&trgt=800756788226&crea=pt33036852017&netw=u&device=c&gclid=Cj0KCQjwuNbsBRC-ARIsAAzITuc5rhZwMcfSjnbsi29-5_D-9N_J0fYj2cpW8-uwoA3kSIUGIBSNh9oaAl3JEALw_wcB&gclsrc=aw.ds

I need help with the vl53l0x sensor and stm32f103 board if anyone can help me with programming or any library.

Hi,We are using VL53L5 TOF sensor for our development, Unit for signal rate is MCPS (mega counts per seconds). What exactly is it counting? Is it measure of intensity of signal received? Does it mean that, Higher the signal rate, higher is intensity of received signal. Does higher signal rate means good confidence is reported range. Thanks,Satya

To use the VL53L1X with a 3V3 supply, I will have to select 2V8 mode.The default mode is 1V8 mode. The selection wil be done in 1V8 mode. Apperently I2C will function correct in 1V8 mode with a 3V3 supply.What is the difference between 1V8 and 2V8 mode?

The typical IOVDD (2V8 mode) and AVDD of the VL53L1X may be 3V3 according the datasheet.In ST applications (for example the X-NUCLEO-53L1A1) a levelshifter is used to interface the 2V8 powered sensor with the 3V3 powered MCU.I want to use the VL53L1X in a application with a 3v3 powerd MCU and thus I2c interface pulled up to 3V3. Can I power IOVDD and AVDD of the sensor with a 3V3 supply?

Hello everyone,I was searching the VL53L1X's Full API and I came across with a function in the "api_calibration" class called " VL53L1_run_spad_rate_map". My question is what quantity does the “SPAD rate�? indicate? And what task does this function exactly do? Also, one of the arguments for that function is ssc_config_timeout_us which I’m not sure what value I should pick for that.Thanks,Adrik

We are putting the VL53L0X in a device with a tinted lens cover. Example shown bellow. I wanted to know about the calibration process during manufacturing that is recommended in the Application note. Is the calibration different from each individual unit? I am thinking of getting the calibration numbers here in the lab and then using that info to set all the devices during manufacturing. Basically we don't require very accurate reading as long as it reads within a certain range.

request for member 'CurrentParameters' in something not a structure or unionrequest for member 'LLData' in something not a structure or unionrequest for member 'PalState' in something not a structure or union i am using nrf52832 and vl53l1x sensor

I have Nucleo-F446RE and  VL53L1x satel. I have connected pins as followSCL - D15SDA-D14INT-A2GND-GNDVDD-3v3When I open GUI software It says Sensor not detected.

..

I am using the vl53l0x tof sensor in one of my products but I am currently experiencing a huge amount of fallout on this product.On a batch of 30, I had 10 broken VLX53l0x TOF sensors after soldering.What occured, the sensor started to pull down itself automatically on the reset pin.My PCB assembler told he used the recommended solder profile for placement of this part.All of this is done in an ESD safe environment.The shock precaution, the PCBs that worked I put on a wafer applying 70G of force to them trying to get them to fail but all of the 20 leftover PCB  keeps working. We also think the hasn't been any of the components reels that had been dropped on the floor.Moisture sensitivity, all of the sensor were in between the boundries as described in IPC/JEDEC JSTD-020-C&nb

Can I use the GPIO1 from the first sensor on the I2C bus to control the XSHUT pin on the second sensor etc.Here is the plan.Assume that I do not use the GPIO1 pins to interrupt my microcontroller. I will use the API to check it there is new data. XSHUT on sensor1 is hardwired High. Sensor1 is in SW_Standby.On sensor1 GPIO1 is High until a measurement is ready. It is connected thru an inverting transistor to the XSHUT on sensor2 so sensor2 is in HW_standby. All the following sensors should also be in HW_standby also.Anything wrong yet?I use the driver to send a command to change the I2C address. Since only the first sensor is in SW_standby only it will accept the new I2C address.Now for the magic that I need from you folks!Since GPIO stand for General Purpose Input/Output I'm hoping that there is some way to use it as General Purpose I/O and Set the GPIO on sensor1 low thus switching XSHUT on sensor2 high and putting it in SW_standby mode.Than I send the change I2C address command to th

I have the X-NUCLEO-6180XA1 board working with an STM32G071 Nucleo board. However the range reading doesn't seem to change when the range to the object changes. If there is nothing in range, I correctly read 0x72 from the range status register, but if something is in range, I seem to always get a range around 0x09 to 0x0D, regardless of if the target is moved closer or further.Is there some setting I might be missing? I'm initializing the registers as follows:static const vl6180x_reg_value_t init_regs[] = { /* REGISTER_TUNING_SR03_270514_CustomerView.txt */ {0x0207, 0x01}, {0x0208, 0x01}, {0x0096, 0x00}, {0x0097, 0xfd}, {0x00e3, 0x01}, {0x00e4, 0x03}, {0x00e5, 0x02}, {0x00e6, 0x01}, {0x00e7, 0x03}, {0x00f5, 0x02}, {0x00d9, 0x05}, {0x00db, 0xce}, {0x00dc, 0x03}, {0x00dd, 0xf8}, {0x009f, 0x00}, {0x00a3, 0x3c}, {0x00b7, 0x00}, {0x00bb, 0x3c}, {0x00b2, 0x09}, {0x00ca, 0x09}, {0x0198, 0x01}, {0x01b0, 0x17}, {0x01ad, 0x00}, {0x00ff, 0x05}, {0x0100, 0x05}, {0x0199, 0x05}, {0x01a6, 0x1b}, {0x0

Rev 7 of the VL6180X datasheet shows the SYSALS__INTEGRATION_PERIOD register at 0x040, however Version 2 of AN4545 changed the address of what presumably is the same register from 0x040 to 0x041. Which is it?Thanks.

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] << 8 | ChipID[3]; if (rd_write_verification(0x

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)