MEMS and sensors

Hi,Currently, we are testing vl53l8cxv0gc/1 by placing an object in front and moving it and reading the values. Is there a way to test the functionality of vl53l8cxv0gc/1 in a production environment? Is there a self test mechanism for this sensor?Thanks,Jagan 

Hi, I'm trying the VL53L7CX sensor for a prototype and I'm trying the example codes provided within  this page https://www.st.com/en/embedded-software/stsw-img036.html I'm experimenting the Example_10_motion_indicator and I'm able to display the "motion power" of the 16 zones within a 10-iteration loop. I just can't figure out what the results mean ! Even when the sensor is totally masked (I mean, physically), the Motion powers seem to start at 0 for all zones (which looks relevant) and increase to apprently random values up to 50-something. Lacking information from the datasheet, I wonder how to use this data and what is its signification. Thanks for your help!

Hi everyone,I’m currently using the VL53L0X sensor to measure the liquid level inside a container, and I have a question regarding the offset calibration procedure described in the documentation.Is it really necessary to perform the offset calibration in this type of application, considering that I later apply a custom correction algorithm to compensate for systematic errors? I’d like to know if the calibration provides any meaningful improvement in accuracy when working with liquid surfaces, or if it would be redundant in my case.Additionally, if the offset calibration is required, should it be performed with respect to the liquid surface itself, or should I follow the recommended method using a white target as described in the official documentation?I’d appreciate any insights or experiences from anyone who has worked with ToF sensors in liquid level measurement setups.Thanks in advance!Edit: I am not using a cover glass with the sensor.

Hello,I have been using the this ToF sensor along an ESP32-WROOM MCU for a while without major issues. My impementation of the i2c interface seems to be working well since in most simple ranging cases everything works well.However, recently, i have been playing around with detection thresholds. I discovered that when I enable detection thresholds while in autonomous mode, I am unable to start ranging. In fact, the sensor gets properly configured (resolution, ranging mode, integration time, frequency and detection thresholds) but when it starts ranging (function vl53l8_start_ranging), error VL53L8_STATUS_ERROR occurs. The error gets raised in this part of the function  /* Read ui range data content and compare if data size is the correct one */ status |= l8_dci_read_data(p_dev, (uint8_t*)p_dev->temp_buffer, 0x5440, 12); (void)memcpy(&tmp, &(p_dev->temp_buffer[0x8]), sizeof(tmp)); if(tmp != p_dev->data_read_size) { status |= L8_STATUS_ERROR; }&nb

On page 9 of https://www.st.com/resource/en/datasheet/vl53l1x.pdf, it is written:"Ranging is continuous, with a programmable delay between two ranging operations (called anintermeasurement period)"This is wrong. It should be:"Ranging is continuous, with a programmable delay between two ranging operations (called anintermeasurement, see Figure 9)"The "intermeasurement" and the "intermeasurement period" are two very different things, as shown in Figure 9 page 12. The "intermeasurement" goes from the END of a measurement to the start of the next one, whereas the "intermeasurement period" goes from the START of a measurement to the start of the next one.

I am using the sensor LIs2DH, and I've read the datasheet and tried multiple values and manipulations of its registers.Now I want to use the sensor should be on a car and detect when will the car move.the problem I'm facing that it generates an interrupt at any vibratoin/touch on the board, and I want to avoid that.Also what are the best configurations for a free fall detection (because I think that would be the best solution for my case) Thanks in advance Register values are Register 0x0f has 0x33Register 0x20 has 0x27Register 0x21 has 0x00Register 0x22 has 0x40Register 0x24 has 0x08Register 0x25 has 0x00Register 0x30 has 0x2aRegister 0x32 has 0x27Register 0x33 has 0x00Register 0x34 has 0x00Register 0x36 has 0x00Register 0x37 has 0x00Register 0x2e has 0x00

Hello,  I use LSM6DSO with my stm32L476. I use I2C 100kz with 10k pull up resistor. The LSM6DSO is next to the STM32. I use INT1 with wakeup parameter to indicate the movement and wake the STM32.I have a problem, sometimes the LSM6DSO freeze. There is no edge to INT1 pin and we cannot communicate throught the I2C bus. So I cannot reset by I2C. I don't understand why, it can appears after 1 weeks or 3 months of uses. It depends. I have to cut off the power to resolve the issue. The LSM6_INT1 pin directly connected to the STM32.   Thank you for your time Aurelien 

Hello ST Brightsense Team,Would like to know if the VD66GY Linux driver (STSW-IMG503_V4L2) will work on an NXP IMX8M Mini (no hardware ISP) ?  If not will it work with the IMX8M Mini Plus (with Hardware ISP).Currently using the STEVAL-66GYMAI.In the STSW-IMG503_V4L2 package, the provided driver / device tree seems for the Raspberry PI, what would be the required changes for that to work on NXP IMX8 platform ? Is the vd56g3.json ISP tuning file required ( no libcamera installed, only using Gstreamer)... Thank you.

Hello,   I am having a hard time finding which software pack this file vl53l8cx_def.h is in? I think once I get that I should be get the zones if Im understanding the error correctly. Please advise.  If it helps with the solution I am trying to use the P-NUCLEO-53L8A1 and VL53L8CHV0GC to generate 3D point clouds.            

I need to cut off all the power supplys of VL53L8 to save power. Does the firmware need to be re-downloaded every time the device is powered on? loading firmware is in the function uint8_t vl53lmz_init( VL53LMZ_Configuration *p_dev)​

I'm encountering many issues while using the AIS2120 accelerometer sensor and would greatly appreciate your assistance. Thank you very much!After the sensor is powered on, a series of initializations (default configuration) are performed, then it enters normal mode, and then the corresponding acceleration data is read. Are these actions performed automatically by the sensor?Do I need to perform any operations to make the sensor enter normal mode?If I need to set it to 1600Hz, how should I operate? (I tried setting a soft reset and then writing to the configuration register, but it didn't work).I keep having communication issues, especially I'm not sure if the CRC check is correct. The manual is very vague. Attached is my CRC check function.I'm also unsure how to fill in the position indicating whether it is sensor data in the SDI frame.uint8_t AIS1120SX_ubCrcVal(int32u ulCrcVal) { uint8_t crc = 0x00; uint8_t poly = 0x97; for (uint8_t i = 0; i < 4; i++) { crc ^= (uint8_t) ((ulC

Hi everyone,I'm working with the VL53L0X sensor and have a couple of questions:Does noise affect the sensor's measurements? Does the sensor include a checksum or mechanism to verify the integrity of I2C messages? Can adding capacitors to the I2C bus help reduce noise interference?Thanks in advance for your help!

The datasheet of STM32U585 say that "For operation with voltage higher than Min (VDD, VDDA, VDDUSB, VDDIO2) +0.3 V, the internal pull-up and pull-down resistors must be disabled." (chap. 5.3.1).The STEVAL-STWINBX1 use a VDDA of 2.75V and a VDD of 3.3V => Min (VDD, VDDA, VDDUSB, VDDIO2) +0.3 V = 3.05V < VDD = 3.3V.But in the examples provided for STEVAL-STWINBX1, pull up and down are used with a VDD of 3.3V.So which is correct, the datasheet or the examples ?

Good morning.I am trying to evaluate a P-NUCLEO-53L8A1 evaluation kit. I downloaded the software example from your website and am trying to carry out some tests with water and cofffee.I am wondering whether I could ask you another question to the GUI for the cup and liquid detection software. I seem to be able to detect the cup ok. Also the cup height and diameter measurements are ok. However, I struggle with the liquid level detection, using water or coffee (two liquids I got readily available) in a coffee mug. The issues I see are:- The measured liquid level is often too low in comparison to the actual fill level.- Often the measured fill level increases initially but then decreases even though the actual fill level increases monotonically. - Often, when the liquid level reaches the top of the cup, several of the pixels in the 8x8 ranging image are black without any value, while others show very large distance values (i.e. several times larger than the actual distance to th

I'm using several VL53L7CX sensors in a robotics application.  They work well except for when a retroreflective surface is present, which blinds the entire sensor, including SPADs not pointed at the retroreflective surface.  A large retroreflective area is not needed, only a few cm^2 patch.This is a big problem for us since industrial environments are full of retroreflective surfaces (e.g. safety vests, markings on the ground, etc.).I'm currently using the default values for sensitivity, sharpener, etc.  Any parameters you recommend tuning/adjusting to make this sensor more robust?

I am using the STHS34PF80 IR presence/motion sensor on a Linux platform . According to the datasheet, the sensor can detect human presence up to 4 m (for a 70×25 cm² object).Currently, my configuration is as follows:echo 1 > /sys/bus/i2c/devices/3-005a/iio:device5/algo_resetecho 4 > /sys/bus/i2c/devices/3-005a/iio:device5/sampling_frequencyecho 2 > /sys/bus/i2c/devices/3-005a/iio:device5/lpfecho 3 > /sys/bus/i2c/devices/3-005a/iio:device5/sensitivityecho 150 > /sys/bus/i2c/devices/3-005a/iio:device5/thresholdecho 50 > /sys/bus/i2c/devices/3-005a/iio:device5/hysteresisecho 1 > /sys/bus/i2c/devices/3-005a/iio:device5/scan_elements/in_temp_y_enecho 1 > /sys/bus/i2c/devices/3-005a/iio:device5/events/in_temp0_thresh_rising_enecho 0 > /sys/bus/i2c/devices/3-005a/iio:device5/buffer0/enableecho 256 > /sys/bus/i2c/devices/3-005a/iio:device5/buffer0/lengthecho 1 > /sys/bus/i2c/devices/3-005a/iio:device5/buffer0/enableHowever, in practice, I am only getting a dete

Hi ST Support. The VB1940 camera has IR smart upscale.I think IR smart upscale separates only the IR data from RGBNIR and compensates for any missing data.Is there a way to send IR data without interpolating this missing data (without changing the image size)?If possible, please tell me how to set it up. Best, regards.

Hello everyone,I’m evaluating ST ToF sensors (VL53L5CX / VL53L8CX) for an outdoor motion-tracking use case and would like to understand the general feasibility before investing in prototypes. Setup:A ToF sensor would be placed approximately at ankle height behind a moving person, facing upwards. The goal is to detect center-of-mass shifts and general arm/torso positioning while the person moves — not detailed skeletal joints, just coarse body-position indicators. Environment:Potentially strong sunlight and ambient IR exposurePossible water droplets, spray, and wet surfaces near the sensor (but not submerged)Target surfaces are typically dark fabrics or wetsuit-like materials at a distance of 0.5–2 m QuestionsGeneral feasibility – Can VL53L5CX or VL53L8CX reliably detect human body shape or coarse motion under these lighting and environmental conditions, or would performance degrade too much in direct sunlight and with occasional droplets on the cover glass?Environmental

Could anyone give me some advice on debugging the AIS2120 accelerometer sensor? I've included my CRC check function above, as well as the data sent and received via SPI, but I still can't read the correct sensor ID. Thank you very much for your help!

I was looking to wire these 2 items together to acquire a LiDAR 3d point cloud data set for a research project im working. I wanted to get some input, feedback and guidance on utilizing this hardware for LiDAR 3d point clouds? VL53L8CHV0GCP-NUCLEO-53L8A1

Is this the correct way to calculate the CRC check code?

Hello,It seems that the library MotionMC_CM7F_wc32_ot_hard.a is missing the called function, here the error :c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_2.0.0.202105311346\tools\arm-none-eabi\bin\ld.exe: ../Middlewares/ST/STM32_MotionMC_Library/Lib\MotionMC_CM7F_wc32_ot_hard.a(motion_mc.o): in function `MotionMC_Initialize':motion_mc.c:(.text.MotionMC_Initialize+0xde): undefined reference to `MotionMC_SaveCalInNVM'c:\st\stm32cubeide_1.6.0\stm32cubeide\plugins\com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.9-2020-q2-update.win32_2.0.0.202105311346\tools\arm-none-eabi\bin\ld.exe: motion_mc.c:(.text.MotionMC_Initialize+0x1fc): undefined reference to `MotionMC_LoadCalFromNVM'I'm just doing like the example, I erased and reinstalled MEMS and this library at the previous version but nothing changes, can you help me ?Here the call :#define VERSION_STR_LENGTH 35#define SAMPLE_TIME 20/* Magnetometer

Hi, I asked for help because my measurements took >> 15 seconds (up to 30s) in:https://community.st.com/t5/imaging-sensors/vl53l1-measurement-takes-up-to-30-seconds/td-p/843640Now after hours of debugging i found a bug in the API at least for platforms where an Integer is not 32 bit, in:vl53l1_core_support.c:114 the code is:pll_period_us = (0x01 << 30) / fast_osc_frequency; but on AVR uC like atmega644 0x01 is 16 bit wide. Which leads to pll_period_us = 0.The wrong value messes up all tim_cfg and gen_cfg, and introduces weird behavior.Fix:pll_period_us = (0x01UL << 30) / fast_osc_frequency;Telling the compiler to use unsigned long fixed the problem for me.This bug should be fixed to be more platform independent I suggest.Kind regards,Philip

Heya,  Is it possible to see the background light (intensity/histogram) without actually transmitting, using a VL53L8 or VL53L9?We don't want to measure the distance to objects. We just want to be able to use the SPAD array to get histogram for each zone. Its a high volume use-case, so would be great if we can achieve this. regardsShjayago

What's the difference between the following sensor variants:VL53L7CHVL53L7CXFrom what I've seen from going through the available product documents, they are all the same, performance-wise (range, frequency, FoV etc).Difference between the CH and CX seems to only be the firmware with the CH being able to output histogram data?Is this correct?Can the CH still output the normal processed data?