Imaging (sensors)

We are using a VL53L8CX to detect seat occupancy from above in an environment which can have quite high levels of ambient light through adjacent windows.  We are wondering whether using a 940nm bandpass window in front of our sensor can help improve perfromance with high ambient light. If this idea has wings, I suppose something like this could do the job: https://midopt.com/filters/bn940/ Phil54  

My three ToF sensors on a finger ring are working (using a Portenta C33).https://youtu.be/qL_alTQpko0Next steps: train and realize gestures (and maybe visualize in Unity). So far, my sensors mounted on a finger ring (for RingGesture) is working (just to consider the power consumption and to do an active ranging in a sequence, just one sensor at a time). 

Hello,I'm trying to get a VL6180X sensor to work.I've downloaded the latest API: en.VL6180_API_V1.3.0.zipMy goal is to make the sensor work in I2c on a Raspberry PI in the c or c++ language.But I can't compile my code, or rather compile the api into a library.Where can I find an example of a makefile or command to do this?Thanks for your help.

we are using the early version 1x in a vertical detection mode.  it has a 23 degree fov. in some of our testing we determined we need more.. FOV currently we tilt the board holding the TOF sensor to eliminate wasted FOV where the sensor would be projecting on a wall.  tof mounted 8ft high on the wall, projecting down, so we have tilted the FOV out, so that the back edge of the FOV is parallel to the wall its mounted on.  the newer 5x/8x have bigger FOV.. 63 and 90 degrees.. we don't need that much, BUT  I would like to detect on the outer edge, vs a smaller square 4x4 with edge against the exclusion zone. or 6x4 with the 4 edge against the exclusion zone. pic attached, box mounted on wal, tof pointing down,  zoom in on box, pad layout and detection zoneis this possible?  we need 6-10ft of detection in a narrow band. maybe 20-24 inches wide.  

How can I find the CE Certificate for the VL53L0X?

I can't find any information about status 9, how can I resolve this status?

Hi I have 4 sensors in configuration all have separate address and initialize ok. when first sensor start ranging I check the state vl53l8cx_get_power_mode wake it up and it ganges with no errors. but then I want to put it to sleep, so I again check the state  vl53l8cx_get_power_mode and sensor gives me 0x05 value instead of 0x04 expecting for wakeup state. Any reason for that behaviour or what does state 0x05 mean?

EDIT [Solution]: The register 0x0014 needs to be set to 0x04. (I put more details in the reply but it has been marked as spam for some reason). I am in process of interfacing an Attiny85 (not Arduino) with a VL6180X board (with I2C level shifter built-in).I wrote my own I2C master interface (USI) and I am able to successfully to get the VL6180X work in a single shot mode (after many hours of struggle).I spent a lot of time wild geese chasing due to VL6180X "pretending" to respond correctly to some of the register read/writes but not being able to actually read the actual distance until I moved the whole thing to battery power (adding additional capacitors to 2.8V or 3.3V supplies didn't help).One thing that lead me astray was the fact that I never bothered to check the actual contents of the 0x0062 register after setting the 0x0018 register, as I was following somewhat scarce documentation and polling the 0x004f register for a ready bit set (as per the application note): &nbs

I just wanted to check the validity of an old post from 2022.The VL53L8CX, like other TOF devices returns a 8x8 grid of distances.The distances are tuned, so if a flat surface for example a wall is directly in front of the sensor (sensor is facing the wall with no offset or rotation) at a distance of 1 metre. Then all the 8x8 Zones will report a distance of 1 metre (assuming no floor, ceiling etc..., so there are no other reflections etc...). The measured distances are in fact larger for angles offset from zero, but they compensated for the requirements of the mobile phone manufacturers etc... Is this still true. Link to post:-Solved: VL53L5CX Distances Don't Match Theory - What am I ... - STMicroelectronics Community

I am looking to purchase an evaluation board for the VL53L8CH in order to take advantage of the CNH data for potential use in AI models.The below expansion board web page has the below text (Link below) Time-of-Flight expansion board based on the VL53L8 series for STM32 Nucleo:VL53L8CX Low-power high-performance 8x8 multizone ToF sensorVL53L8CH Artificial intelligence enabler, high performance 8x8 multizone ToF sensorI already have a VL53L8CX, which lacks the CNH data. The info on the web page has both part numbers, however I think only the VL53L8CH has the functionality I require.X-NUCLEO-53L8A1 - Time-of-Flight expansion board based on the VL53L8 series for STM32 Nucleo - STMicroelectronics This is just the expansion board. I guess the main board could be the following board.This page has the main board and expansion board. P-NUCLEO-53L8A1 - STM32 Nucleo pack with X-NUCLEO-53L8A1 expansion board and NUCLEO-F401RE development board - STMicroelectronics&nb

Hello,I've been working with a SATEL-VL53L8 sensor for a while. For this I've used the L4RZI board and now i moved into the nRF52 board for more tests.I've been having trouble trying to implement this. I've tried to use the VL53L0 configuration, (CONFIG_VL53L0X_PROXIMITY_THRESHOLD    and   CONFIG_VL53L0X).This because i did not find any configuration for the VL53L8 available (besides the one available in the GitHub for the ST32duino (https://github.com/stm32duino/VL53L8CX)).I've tried examples for the L0, and the L8, including using the one available in GitHub. Is there any CONFIG for the VL53L8 that can be used for this board (nRF52 DK)?   (I've checked examples between nordic-ST regarding the L1 and L0)

Hello everyone,I just received my X-Nucleo-53L7A1 board and I'm trying to get it working with my Nucleo-F429ZI. In CubeMX,I've selected my board and the appropriate software pack. For the pin configuration, I followed the example provided for the Nucleo-F401RE.The code generates without any errors or warnings, but when I check my serial terminal, I see the following error:VL53L7A1_RANGING_SENSOR_Init failedCheck you're using ONLY the center device soldered on the shield, NO satellite shall be connected !I can't figure out where the problem is coming from. If anyone could offer some help, I would greatly appreciate it!

Hello,We are using the VL53L1 sensor in autonomous mode to range data, mostly indoors but sometimes outdoor.Following the Table 3 in UM2133, we use the short distance mode in order to have better ambient light immunity when outdoors.However, in the AN5573, Table 6, it says that the outdoor capability in autonomous mode drops to a max distance of 200mm, but our targets are often in the 60cm-100cm range.Is the sensor not usable in autonomous mode at all for our application outside ?Please share any insights, experiences or recommendations regarding the VL53L1's autonomous mode ranging performance in outdoor/ambient light scenarios.

I have used the VL53LCX Linux driver to operate the ToF sensor on the IMX8M Nano board, and the Linux driver is functioning correctly. However, I am encountering issues with implementing gesture recognition functionality. I have used the gesture recognition static library M7 Version, which cross-compiled successfully, but the gesture recognition is not working properly. Could you provide the appropriate .a file for the Linux architecture?

Hi all,         What is the part to part variation of ST VL6180 ToF sensor? During testing, we keep the sensor at a distance of 50mm from a retro reflector tape. In a batch of 50 sensors, the readout was from ~ 37 mm to  ~51 mm (expected readout is 50).We made a larger batch of 1800 boards and ~130 boards had a readout from 25 mm to 60 mm (expected readout is 50) . We have used the below settings as per the datasheet.  # Recommended settings from datasheetself.writeI2C(0x0207, 0x01)self.writeI2C(0x0208, 0x01)self.writeI2C(0x0096, 0x00)self.writeI2C(0x0097, 0xfd)self.writeI2C(0x00e3, 0x01) #VL6180_WriteByte(0x00e3, 0x00); (seen this in ST forum)self.writeI2C(0x00e4, 0x03) #VL6180_WriteByte(0x00e4, 0x04); (seen this in ST forum)self.writeI2C(0x00e5, 0x02)self.writeI2C(0x00e6, 0x01)self.writeI2C(0x00e7, 0x03)self.writeI2C(0x00f5, 0x02)self.writeI2C(0x00d9, 0x05)self.writeI2C(0x00db, 0xce)self.writeI2C(0x00dc, 0x03)self.writeI2C(0x00dd, 0xf

Hi allI have successfully implemented a single vl53l0x sensor, but wish to add more. I found the "AN4846 Application note Using multiple VL53L0X in a single design" documentation:https://www.st.com/content/ccc/resource/technical/document/application_note/group0/0e/0a/96/1b/82/19/4f/c2/DM00280486/files/DM00280486.pdf/jcr:content/translations/en.DM00280486.pdfUnder "VL53L0X API management" it specifies:In vl53L0x_platform.h API file set VL53L0x_SINGLE_DEVICE_DRIVER macro to 0 so that API implementation will be automatically adapted to a multi-device context.But I cannot find anything called "VL53L0x_SINGLE_DEVICE_DRIVER" in the vl53L0x_platform.h file.Where can I find it? Or has the files updated without the documentation being updated? If so should this step just be skipped?

Hello, We've been developing a tank level monitoring system using these sensors: VL53L4CD (18° FoV)VL53L3CX (25° FoV, multitarget)VL53L4CX (18° FoV, multiobject, multitarget) First question is the definitions and distinctions between the terms multizone, multitarget, and multiobject. We couldn't get a clear information about these on the datasheets.Secondly, we are just using example libraries to get measurements. We are still discovering how to filter the readings that are not within the central zone. We've made a spreadsheet that we'll be happy to share privately. It shows the minimum tank diameter and the maximum tank depth that won't cause signal bouncing around the inner walls.Thank you. 

Hi there,   I read this document and it mentioned that the function "vl53l8cx_set_VHV_repeat_count" can be used to compensate for the ranging error caused by temperature. I would like to know the principle of VHV calibration compensation. Is it related to the signal power of VCSEL?   Does VHV calibration also apply to the compensation mechanism at low voltage (2.5~3V)? Or are there other functions that can compensate for voltage drift?  

@John E KVAMI ported the gesture recognition example (STSW-IMG035_F401) from the STM32F401RE to the NUCLEO-U575ZI-Q with the X-NUCLEO-53L8A1 and the gesture library (STSW-IMG035_M33).  If I used the VL53LMZ_ULD_API driver included with the GestureKit it seemed to work fine; all gestures were recognized. If I used the VL53L8CX_ULD_API driver (STSW-IMG040), it worked poorly; only the TAP gesture was recognized (and even that was inconsistent).  This was repeatable on the same hardware;  I could load and calibrate the MZ based project and it worked fine, then I could load and calibrate the 8CX based project and it would only recognize the TAP gesture.  I was surprised that the driver intended for the specific part performed worse than the generic one.I've attached the two ported projects (one using the MZ driver and one using the 8CX driver) for comparison.Have I missed something? Note: One significant difference I just found was that If I held a book at about 20c

Currently I connected the X-NUCLEO-53L8A1 to F401RE, and I notice that on the web page of VL53L8CH, the sensor can get the data with 64 zones with 18 bins at 15 Hz. But when I use the VL53L8CH with the Example_12_cnh_data which use VL53LMZ_ULD_API, I found that when I set the cnh config to get the data with 64 resolution, 16 bins, and 15Hz, the fps I get from the serial port is only 3.6Hz, not 15Hz. Is there any way to improve the FPS of the code?

Hello,I'm currently using VL53L8CX with an STM32U535 on a custom PCB.I'm using X-CUBE-TOF1 package.I'm able to identify the sensor with SPI at 2MHz using vl53l8cx_is_alive function.I was able to successfully init and use VL53L8 on U-585I-IOT02A dev board with the same code.there is my function to send data throught SPI :And to receive data  : The problem is in function vl53l8cx_init.There is timeout in various function depending on SPI frequency and apb frequencytimeout can come from this line (325) or from _vl53l8cx_poll_for_mcu_boot function.Often timeout appear at the third occurrence of _vl53l8cx_poll_for_mcu_boot function.I'm clearly lost in the search for the causes of this problem. I tried to increase or decrease the SPI frequency but this only change the line where the timeout occurs. I remain available for any further information.Thx for every kind of help ! 

Hi everyone, I am currently using the VL53L8CX for people counting. However, I have encountered an issue where occasionally, changing the data acquisition rate during the data collection process causes a disruption and prevents further data acquisition.1. How can I dynamically change the acquisition rate during the data collection process?2. How can I dynamically change the integeration time during the data collection process? 

HiI refer to the VL53L0X Datasheet DoclD029104 rev5 page 15 article 2.10 Ranging Sequence.There not a lot descritption in your documentI need to understant how GPIO1 stay down before the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 1/ GPIO1 is not pulled up, the sensor pull it down, then the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 2/ GPIO1 is pulled up by 10k ohms, the sensor pull it down, then the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 3/ GPIO1 is not pulled down, the sensor pull it up when , then the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 4/ the API pull the GPIO1 down and wait that the sensor pull it up when init/ranging/housekeeping phase is finish. Thanks in advance for answers

As far as I know, dToF has two illumination modes. One is spot dToF (iPhone) and the other is flood illumination. Which one is VL53L8CH? Thanks.

Are formulas 1-4 correct in AN5894?Segment [AC] is the hypotenuse of triangle ACE, and the angle between segments [AC] and [CE] is half the dihedral angle HFOV. Then formula 1 should have a sine instead of a tangent.If I am right, in the example the angle between the segment [CB] and the opposite segment of the pyramid should be [DFoV] = 2*ASin(Sqrt(2*(Sin(60/2))^2)/Sqrt((Sin(60/2) )^2+1)) = 78.5 degrees. This value agrees with measurements made on the 3D model.