Imaging (sensors)

Hi, I use the VL53L5CX in my own developped board .Everything seems to work, but i can't get the guesture control code from static lib libGesturesMZ.a working (downloaded from STM website).Initialisation goes fine , all statusses are OK , but the moment i run GW_run(....) the STM goes in HardFault_Handler().All parameters i send with GW_run are valid and contain data .Are there people that had the same problems?Anything i can do to figure out why this is crashing?these are the steps in software, all steps execute fine with STATUS_Ok but at GW_run() it crashes.1) vl53l5cx_init2) gesture_library_init_configure(); -> GW_init(&gest_predictor, &hand_tracker, &sensor_data); -> HT_set_square_resolution(&hand_tracker, &sensor_data, Params.Resolution); -> GW_set_frequency(&gest_predictor, &hand_tracker, &sensor_data, 1000.0/Params.RangingPeriod); -> GW_set_params(&gest_predictor,.... -> GW_set_frequency(&gest_predictor, &hand_track

Hi everyone,I am facing a problem where my VL6180X hangs indefinitely until reset after a seemingly random period of time. The sensor runs in continuous mode and samples at 100 Hz (thanks to this post). I configure the sensor by setting the SYSRANGE_INTERMEASUREMENT_PERIOD and READOUT_AVERAGING_SAMPLE_PERIOD registers (see code example). The SYSRANGE_INTERMEASUREMENT_PERIOD seems to be where the problem lies. If I set this register to 0x0, then the sensor will eventually hang. If I set it to 0x1, the sensor will not hang, but my sampling frequency will be significantly reduced. However, the datasheet states that [0-254] is the acceptable range of values for this register (see datasheet image); so, 0x0 shouldn't be a problem. Additionally, matters become more confusing when you look at the VL6180X API (see code screenshot). The input variable `InterMeasTime_msec` is bounded to at least 10 milliseconds. This means that `SetTime`, and therefore the inter-measurement register, will always

Hi Team,Need assembly flow and internal geometry of parts for VL53L5CX. If you have relevant information, is it convenient to share it? those are very much useful to us. Thank you very much.Regards,Ma Yufeng​

I'd like to know how the tof sensors technically work in detail. I know about the principle (photons were sent and time taken until receiving the reflection), but how is the field of view created and how can some sensors have a lager FoV than others? What is the difference to a typical laser sensor?

Hi, I am having issues getting my X-NUCLEO-6180A1 to work with the NUCLEO-F401RE. I have followed the instructions in the manual and the troubleshooting guide, although still cannot get things to work. I believe I need to flash FW manually. although the box to do so is greyed out, as seen in the attachments. I can see COM6 in the device manager which is the COM port associated with the device, so it looks like its talking. I had to download link007 and link009 from the website since the links in the pdf didn't work, and i tried rebottling my computer afterward as well. Please let me know any additional troubleshooting steps. I noticed on the install i had this warning come up, maybe its related to the issues I am seeing. I am using a windows x64, running windows 10.

Hi,I have some questions about the latest ToF released VL53L8CA (only databrief released at the moment):Is the VL53L8CA footprint/pinout-compatible witth the VL53L5CX?Is the VL53L8CA on-board microcontroller RAM-based (like VL53L5CX)? If yes, what is the time (or size) to load the on-board FW at the initialization phase?Could you update the comparison between ToFs by adding the VL53L8CA?Thank you

..

Hello, I am working on vd6283 sensor to interface with NRF52 chip, I able to get data from the sensor, for ALS values and flickering extraction, but the problem I am facing is that I am unable to operate the sensor both for flickering frequency extraction and ALS values... at the same time.And unfortunately, I am unable to find an example pseudo-code that tells us how to use the sensor for both operations at the same time.Thanks.

Hello,I am developing a system using VL53L1X.Occasionally, when the host microcomputer is asynchronously reset, there is no response from the sensor after that.It can be detected that the sensor's SDA is stuck at Low. We can handle it.The situation I am encountering is that the sensor's SDA line is high, but I2C communication is not possible.Is there an internal state that ignores the start condition from the host microcomputer?If so, please tell me the transition conditions to that internal state.Best regards.

Hello,​I am developing a system using VL53L1X.Occasionally, when the host microcomputer is asynchronously reset, there is no response from the sensor after that.​I've never used the xshut terminal.If communication with the sensor becomes impossible, I'm thinking of using the xshut terminal to synchronize the host microcomputer and the sensor.Please let me know the setup time required to start I2C communication after setting the xshut pin to high level.​From the topic below, I think 10ms is enough, but I would like some information as a specification. Title:vl53l1x-xshut-pin​​Best regards.

I have two 3-element arrays on my 4-wheel robot, one on each side. I use the arrays for simple distance measurements, and also to orient the robot parallel to a nearby wall by turning it until the front and back VL53L0X sensors (separated by 8.5cm) report the same distance. This works, but not as well as I'd like, so I started investigating. I found that the output from a single sensor is quite 'noisy' in that it's reported distance varies rapidly up and down +/- 0.5cm from the average. With two independent sensors, one can be reporting +0.5cm while the other is reporting -0.5cm (not parallel at all) when in actuality they physically at the same distance. I have included an Excel plot showing the output from the 'center' sensor on the right-hand side.Currently I have all sensors set for a 20mS measurement budget. Would a longer measurement budget improve this performance? Is there anything else I can do? I have looked through the VL53L0X manual and the API and I didn't see anything oth

Hi Team,Need specifications and materials for internal parts of VL53L5CX. If you have relevant information, is it convenient to share it? those are very much useful to us. Thank you very much.Regards,Arlen​

I have a VL6180X that I am running in continuous measurement mode and read from when a hardware interrupt is triggered by the senor. My issue is that I cannot get the sensor to signal at a rate of 100 Hz. Currently, the best I can achieve is 50 Hz.Has anyone had success with this? I have read that tweaking the inter-measurement and max convergence times can help, but I am not sure where to start with those values. Any advice would be greatly appreciated :)Also, within the VL6 API, I noticed that the `VL6180x_RangeSetInterMeasPeriod()` function has the following code block:/* doc in not 100% clear and confusing about the limit practically all value are OK but 0 * that can hang device in continuous mode */   if (InterMeasTime_msec < 10) { InterMeasTime_msec = 10; }This block appears to hard limit the inter-measurement time. Commenting out this check and setting `InterMeasTime_msec=0` helps with reaching 100 Hz, but makes the sensor prone to crashing. Does anyone know why this c

Hi, I've testet four Time-of-Flight-Sensors of the type VL6180. The results were all different, for a distance of eg 30mm I got 23mm (Sensor1), 21mm (Sensor2), 16mm (Sensor3) and 32mm (Sensor4). The measurements all took place under the same conditions. I'm very interested in the reason of the results.(Could it be, that the soldering of the pins and the causing higher temperature are the reason for that or is it because of the manufacting tolerance?)

I'm using the VL53LX API 1.2.8 to interface with the VL53L4CD in firmware and I implemented a tuner page in my android app to visualize it.So far I have this thing ranging pretty well with +/- 1mm accuracy. Not bad!I'm measuring a permanent grey 3D printed PLA object with a 10x5mm flat face that can move 10-45mm in front of the sensor.My only issue is that when I start/stop ranging, it starts off on the correct distance (object not moving) and then after ~1min it starts drifting up +2-3mm. However, it tends to cap out there. So, if I'm reading 45 it will climb up to ~48 and settle. If I start/stop again it will repeat.Is this due to temperature drift or something else? Is there anything to lessen this? I would think that if it was temperature then start/stopping would not cause it to jump back to reading 45mm right off the bat but instead leave off at the last drift value.Project details:Electrical:-I2C at 100kHz-VCC 2.8VTypical Operation:-Follows the UM2923 - VL53L4CX API ranging flow

Dear Sir,We are going to make our own PCB after confirming the action with X-NUCLEO-53L1A1 module. We found the connection of pins 4, 6 12 in VL53L1X breakout board is different with the Figure3 (VL53L1Xschematic) . In Figure 3, pins 4, 6 and 12 are connected tomain ground as same as described in Table2 (VL53L1X pin description). But in VL53L1X breakout board described in UM2359, pins 4 and 12 are connected to 1K resistors and pin 6 is not connected to any. We used schematic in Figure3 from datasheet. I wonder if thereis any problem for this schematic.best regardsSai Dai,

Strange behavior of the VL53L0CXV0DH sensor.I get the correct data (distance to the obstacle), with a normal change in the position of the obstacle (zoom in / out), the data changes correctly and corresponds to the real distance.If the obstacle is sharply removed from the "field of view" of the sensor, I get 0 (or very small, 0-25mm, values), although it is logical to get infinity. I can’t understand, is this the usual behavior of the sensor, then I will make a code check or is it some kind of problem with my sensor?Before that, I used sensors soldered on the board and did not encounter such behavior. The described situation occurs on the board of my PCB ordered in jlcpcb, but once again I will pay attention, most of the data is correct! This baffles me.

It would be nice to state clearly in the datasheet what does 'range' means.This is actually not the distance between the sensor and the target, but the projection of this distance on the axis orthogonal to the plane of the sensor... (i;e. the height of the target assuming the sensor lays horizontally)It would save us lot of precious time trying to run fastidious experiments trying to understand the observed behavior.JYL

Hi,I can read the VL53L1X sensor data via i2c. But the values are not consistent when I keep my object from 1cm to 20cm the values are not accurate and not matching with the distance level.Regards,Kumar

Dear Sir,We will make our own PCB for VL53L1X application. There are some difference betweenVL53L1X breakout board schematic in UM2359 and VL53L1X schematic in the datasheet.In Figure3 of datasheet, pin 4, 6, and 12 are connected to ground directly. But in VL53L1X breakout board, pin 4 and 12 are connected to a 1K resistor , and pin 6 is float status.We use the connection shown in Figure3 in the datasheet of VL53L1X, I wonder if the connection is OK or not. or should we use the connection of the breakout board?thank you very much for your help in advance.best regardsSai Dai

Hi. I want to measure the water level in an 1.5m height and 1200 litters container. A lot of condensation is created inside it. What if some water droplets are formed in the sensor input and output holes? Would this "water lenses" affect the readings? In my application there is not way of avoiding condensation. Thank you!#VL53L5CX #VL53L4CD

I We purchased this sensor to apply it to our own board. I want to know the command to control the sensor on the board, but the data sheet only provides for simple i2c communication and address, index, and data structure.

I'm using the latest API version (1.2.8) available from the VL53L4CX product page.In my project I have implemented an interface to set configurations or run calibrations.I am also using this driver for both the VL53L4CD and VL53L4CX, since the driver seems to be universal for all VL53LX parts. Correct me if I'm wrong.(Problem 1 )I noticed the function VL53LX_PerformOffsetPerVcselCalibration(~) would hang seemingly at random calls.Below is the block of code with the issue and a potential fix. After I changed it, I've had no issues running it.while ((Status == VL53LX_ERROR_NONE) && (inloopcount < Max) && (inloopcount < OverMax)) {   Status = VL53LX_WaitMeasurementDataReady(Dev);   if (Status == VL53LX_ERROR_NONE)   Status = VL53LX_GetMultiRangingData(Dev, &RangingMeasurementData);   pRange = &(RangingMeasurementData.RangeData[0]);   goodmeas = (pRange->RangeStatus == VL53LX_RANGESTATUS_RANGE_VALID);   ics = pdev->ll_state.

Hi all,i'd like to know the typical resource requirements (mainly required computing power / DMIPS value) of running the TouchLessControl library (STSW-035) library on a host MCU. The GestureEVK-UM.pf mentions a typical RAM and FLASH footprint :I know that the library is also availble for Cortex-M0...But I can not find maximum usage of (D)MIPS, required to run the STSW-035 SW stack.Even if its may hard to give an exact value due to mapping of DMIPS to real world algorithms -  There are interrupts, DMA, peripherals, RTOS, .... - an indicative DMIPS range would be quite helpful.

I have read that ST will be releasing code to show how to do gesture recognition on the VL53L5CX, when is this due to be released?