Imaging (sensors)

Hello.I am working with a vl53l1x sensor and i need to know if this sensor report a distance when the target is not detected and the measurement is valid, like the vl53l3cx sensor that report back 8191. Does this sensor report the same number or other number in this condition? Or does not report back anything when this happen?

Hello !I'm working on the VL53L5CX sensor with a Nucleo L432KC.Using the ST example, and after succeeded the initialization of the VL53L5CX, the sensor's data are never ready. In the following function, the p_dev->temp_buffer[1:4] are all equals to 0 :  uint8_t vl53l5cx_check_data_ready( VL53L5CX_Configuration *p_dev, uint8_t *p_isReady) { uint8_t status = VL53L5CX_STATUS_OK; status |= RdMulti(&(p_dev->platform), 0x0, p_dev->temp_buffer, 4); for (uint8_t i = 0; i < 4; i++) printf("0x%02X", p_dev->temp_buffer[i]); printf("\n"); if((p_dev->temp_buffer[0] != p_dev->streamcount) && (p_dev->temp_buffer[0] != (uint8_t)255) && (p_dev->temp_buffer[1] == (uint8_t)0x5) && ((p_dev->temp_buffer[2] & (uint8_t)0x5) == (uint8_t)0x5) && ((p_dev->temp_buffer[3] & (uint8_t)0x10) ==(uint8_t)0x10) ) { *p_isReady = (uint8_t)1; p_dev->streamcount = p_dev->temp_buffer[0]; } e

"2.1 Software Interface" in the VL53L5CX datasheet states that the driver (C code, reference Linux® driver) is delivered.How can I get this driver?Please let me know if there is a download URL for the source code.

I just purchased the VL53L5CX-SATEL Breakout Boards for VL53L5CXhttps://estore.st.com/en/vl53l5cx-satel-cpn.htmland i have been trying unsuccessfully to get it to work with an Arduino Mega 2560. Does anyone know if it is possible to get it working with the Arduino Mega 2560 ? If not, should it work with an Arduino Due ?

Hi:I'm testing the VL53L4CX and I'm experiencing some problems:1. When an object is within 3.5m and there's a wall 5 metres away, sometimes the returned distance alternates between two distances.2. When there is a mirror within 3.5m, VL53L4CX sometimes will return a distance more than 3.5m incorrectly.After researching the returned data, I found that "Extended Range" is turned on incorrectly.Can I know how the "Extended Range" function works and how to control it? Thankyou.Cyt

I have been testing with the VL53L1X TOF sensor and am curious on the durability of the sensor in rugged environments. Such places would look like an industrial environment where vibration and impacts in inevitable. The sensor PCB would be potted and fully enclosed in a containment box. However, an opinion by others on how it would fare would be greatly appreciated. I know the data sheet shows shock as being an issue. Thanks!

Hello, I'm trying to use a ToF-Sensor to track the distance of metal parts (sheets, cog wheels etc.) usually in the range of 0-60cm. The thing is that I am only interested in the distance of the surface that is directly below the sensor, the center of the FoV of the Sensor so to speak. I tried using the VL53L4CD Sensor, which is a Single Zone Sensor and while the readings where accurate for flat surfaces, they weren't for surfaces with sudden changes in height within the sensors FoV(obviously). Hence why I'm considering using a Multi-Zone Sensor to get the distance measurement I'm interested in. So is it possible to only measure the distance of the surface which is in the center of the sensors FoV this way? Which sensor should I consider and what settings should I use to get the most accurate measurement?

In the ULD driver for the VL53L8 is the file vl53lmz_api.c. In line 354 to 364, the firmware is loaded in pieces of 0x8000 bytes:My microcontroller has not enough ram to handle such big blocks, so I have to load the firmware in smaller pieces. But for what are the write commands to register 0x7FFF between loading the FW blocks in line 358, 361 and 364?What has to be adjusted to write the FW e.g. in blocks of 0x2000 bytes?Used product: SATEL-VL53L8

As shown in the figure is a ball, the depth difference of one pixel is less than 3.7mm. But as shown in the histogram, the depth difference is more than 15mm. I would like to know if this is caused by noise or some other reasons? 

Hello,I noticed a difference of ranging time on VL53L4CX in function of target presence or not.My parameters : AVG = 3 ; DTIM = 33 ms ; INTERMEASUREMENT = 100msCurrent measurements : Without target : pulse width = 38 ms ≈ DTIMWith target : pulse width = 69 ms ≈ 2 x DTIMCan you give me an explanation for that please.Thank you in advance.Clément Macquet

I got a custom board made with these two ics and I tried to program the mcu. However, when facing FLASH and RAM size constrains I decided to remove certain parts of the library to make it fit(I removed crosstalk calibration since I don't have a cover material).  However I am now facing issues with the sensor not working(I2C works), and I have to determine if it's because of something I did, board design or something wrong with the sensor. The measurements that I'm getting have the 255 status, and while debugging I found that the sensor returns less streams than expected. So a couple questions first:1) Does the sensor require restarting via XSHUT to properly work?2) Would the ST-LINK programmer be able to supply enough power for both chips?3) How should I proceed with debugging?4) Does ST have a smaller library for this sensor(I have been unable to find one)?

..

The SATEL-VL53L8CX dev boards were all out of stock, so I picked up the LS53LX-SlL8 Light Saber Sensor VL53L8CX by Gilisymo for debugging before I build my own PCB. I am interfacing with the sensor via the Adafruit itsy bitsy nRF52840 (but have also used the xiao nRF52840 Sense and the ESP32-S3 QtPy for debugging purposes).I had previously been able to work with the VL53L5CX easily using the Sparkfun library with a very similar set up. However, using the STM32duino library I can't communicate with the sensor via my nRF52840. The vl53l8cx_set_i2c_address() function fails some of the time, and other times it will succeed but the following vl53l8cx_is_alive() function will fail. My physical set up (with this devboard) is connecting ground to ground, 3v to Vin, SDA to SDA, SCL to SCL, and the A3 GPIO pin of my MCU to the LPn pin. I have validated that the A3 pin is responsive when I digitalWrite high and low, so it should function as a LPn control pin. I am al

Hello, I noticed that using the X-CUBE-TOF Package with the STM32WL55JC Nucleo-Board has an issue with the I2C-Peripheral(I2C-2). This genrates the I2C code in the IDE. And the Sensor can be derived.while if I define the Sensor bus IO:The Generated code is without the I2C And the Sensor is not discovered.Is that normal? should I define something to make the I2C code get generated or this is a bug in the CUBEMX-Package for ToF?Thank youAmir

If I want to use the Mini-PCB of the VL53L1X SATEL, which type of plug do I need to plug that in? (I would like to label this with "Time of flight" but unfortunately, this seems to be not possible for me ;-( ).

Need a help.Got VL53L1B (with a letter "B" at the end), unfortunately can't find any reference to it.Please help me recognise what is "B" suffix mean? Is it VL53L1 or VL53L1X or ...?Thanks a lot!

Hi, I'm new to the community and I hope someone could help me with the following. I was wondering is there any way to distinguish between a human body and a static object, like a piece of paper when detecting obstacles with ToF sensors(e.g. VL53L4CX, VL53L5CX)? Is there a way to detect some sort of body heat or any particular aspect of the body that will differentiate the human presence from other constant entity?Are there any colour limitations of the ToF sensors such as very dark(black) surfaces that absorbs the photons and hence limiting the reflection of the emitted light?I've read in some articles that these sensors don't like curved surfaces as the laser beam will not bounce back to the collector...would this compromise the human body detection?I would appreciate any advise or input and thank you in advance.  

I'm collecting 100 samples on a 200ms timing budget and reporting the average once a minute, so if it's just one sample, it's high by what you see * 100. The behavior appears sensitive to the value for sensor.setSignalRateLimit(). I have it down from 0.25 (25kcps) to 0.025 (2.5kcps) for the bulk of the graph. For the right ~10% of the graph it is set to 0.005 (5kcps) to see if that reduces the frequency of occurrence.With higher SignalRateLimit() settings, or the default value, I get more frequent and several levels of spike indicating that one or more readings are just some overflow value x.01, .02. .03 or .04, depending on whether the condition occurs 1, 2, 3,4 etc. times in 100 samples. I can deal with it at this point and have a useful system, but it's bugging me. The L0X is installed in a ~half full steel 275V oil tank with zero ambient light and it has a cover with cross talk barrier.I know that the 4CD would probably be better, and I am experimenting with at present, but the ava

Dear Sir,We use VL53L1X for our application. We use a glass cover and found crosstalk problem.We try to compensate the crosstalk. There are three functions in VL53L1X ULD driver as1)VL53L1X_ERROR VL53L1X_SetXtalk(uint16_t dev, uint16_t XtalkValue);2)VL53L1X_ERROR VL53L1X_GetXtalk(uint16_t dev, uint16_t *Xtalk);3)int8_t VL53L1X_CalibrateXtalk(uint16_t dev, uint16_t TargetDistInMm, uint16_t *xtalk);Would you like to tell me how to use these functions to realize the crosstalk compensation?I would like to get information or calibration procedure steps for crosstalk compensation.Looking forward to hearing from you soon.best regardsDai Sai

I've manufactured 160 boards implementing the VL53L0CXV0DH/1. Many work as expected but some of them (approximately 50 units) give 8191 always as a result. I've noticed that these devices should be treated carefully using a recommended reflow profile. Also they are susceptible to shock damage.What could be the cause of the result being 8191, in those defective devices?thanks in advance,gaston

Hello,I am trying some settings on VL6180x for avoing "Max_Signal_To_Noise_Ratio" when ranginf under sunlight conditions.I have tried to disable DMAX (#define DEF_DMAX_ENABLE     0), but still I get the MAX snr errror.I have been trying to set other limit to SNR, Which I managed to do it, But no succes when ranging at sunlight.I do not need high accuracy.Regards, Ramon.

Hi.Regarding the VL53L7CX, I downloaded STSW-IMG036 (API Source) from the product page and tried running the Nucleo board and sensor using the example project included there. However, the default sensor operation setting in the code is 16(4×4) zones, but I don’t know exactly how to change it to 64(8×8) zones.In the user manualThey say it can be changed in vl53l7cx_set_resolution(), but there is no detailed explanation, so it is currently not possible to modify it. It may be because I don't know C language well, but please help me with a detailed explanation.STSW-IMG036https://www.st.com/en/embedded-software/stsw-img036.html

Hi ! I'm using the VL53L4CD sensor's example with the Nucleo-L432KC.A first problem I solved was that the VL53L4CD didn't have the adress 0x52 as in the documentation, but 0x29 (this problem has already mentioned in a topic).My current problem is that the following code return a good status but a wrong id :'''/* (Optional) Check if there is a VL53L4CD sensor connected */status = VL53L4CD_GetSensorId(dev, &sensor_id);if(status || (sensor_id != 0xEBAA)){printf("VL53L4CD not detected at requested address\n");printf("Sensor ID : %d\r\n", sensor_id);return status;}'''It gives back the address 0.It should be the basic code, but it doesn't work.Have you got a solution ?Thank you ! Clément Poisson.

There is an explanation about Zone mapping in the document as follows ： The area number in the above figure is consistent with the example VL53L5CX_ How do the return results in VL53L5CX_SimpleRanging ?In VL53L5CX_SimpleRanging ，There is the following code：(long)Result->ZoneResult[j + k].Distance[l],I printed the output of [j + k]（Taking 4 * 4 as an example）：3 2 1 0  7 6 5 4 11 10 9 8 15 14 13 12 Is this value of [j + k] the corresponding area number？

Hi @John E KVAM and @Anne BIGOT I'm attempting to mimic the ideal operation of the VL53L8CX in simulation. I've traced out 64 rays from the sensor within the the 45x45 degrees FOV as shown. Consider the top row (underlined in black) the rays are drawn at a vertical angle of 19.6875 and a horizontal angle of [-19.6875, -14.0625, -8.4375, -2.8125, 2.8125, 8.4375, 14.0625, 19.6875] with the centre positioned at (x, y, z) = (0, 0, 0). The intersection points with the plane presented slighly drop down resulting in a curve as shown by the black line due to the plane being closer to the sensor for the smaller horizontal angles. This ensures the ray is centred in each ~5x5 pixel. Does this accuretly depict the sensor operation? Please find the picture attached. Looking forward to hearing your reply and any suggestions!Kind regards,David