MEMS and sensors

Hi, I am currently testing the VL53L7CX ToF sensor. During my evaluation, I came across the parameter "range sigma", but I could not fully understand what it actually represents.In addition, while creating a correlation map, I noticed that the most influential feature affecting distance measurements is the range sigma value.I would greatly appreciate it if anyone clarified what exactly "range sigma" indicates, and how the sensor calculates or measures this value. Can anyone enlight me?Thanks

I use the KIT STM32F411 DiscoveryWhen I choose:SPI CPOL: LowSPI CPHA: 1 EdgeIt works But when I choose:SPI CPOL: HighSPI CPHA: 2 EdgeIt does not work Could you explain why? Thank you! 

I'm now using LSM6DSOX with I3C protocol. And I'm trying to use ibi to notify a tap event. Here are the following information to configure the sensor register: LSM6DSOX_INT1 0x0D 0x00LSM6DSOX_INT2 0x0E 0x00LSM6DSOX_CTRL1_XL 0x10 0x3CLSM6DSOX_CTRL2_G 0X11 0X7CLSM6DSOX_CTRL3_C 0X12. 0x04LSM6DSOX_CTRL4_C 0X13. 0x00LSM6DSOX_CTRL5_C 0X14 0x00LSM6DSOX_CTRL6_C 0X15. 0x00LSM6DSOX_CTRL7_G 0X16. 0x00LSM6DSOX_CTRL8_XL 0X17 0x00LSM6DSOX_CTRL9_XL 0X18. 0x70LSM6DSOX_CTRL10_C 0X19 0x00LSM6DSOX_TAP_CFG0 0X56 0x0ELSM6DSOX_TAP_CFG1 0X57 0x0FLSM6DSOX_TAP_CFG2 0X58 0xFFLSM6DSOX_TAP_THS_6D 0X59 0x06LSM6DSOX_INT_DUR2 0X5A 0x1FLSM6DSOX_MD1_CFG 0X5E 0x48After I configure these, it works fine until I tap the sensor and I can see ENDLESS ibi on logic analyzer.  ENTDAA and some of the command command set and endless ibi ibi content:During the endless IBI, I cannot send any command like read TAP source or reset sensor.Am I doing anything wrong? Thanks 

I want to do some testing and experimenting with the FSM features of the LSM6DSO. I have MEMS Studio downloaded, and I also downloaded the X-CUBE-MEMS1 expansion software package. I see on the documentation for X-CUBE-MEMS1 that the NUCLEO-L476RG was replaced with the NUCLEO-U575ZI-Q in November 2022. I also found X-CUBE-MEMS1-V4, but on the page, I cannot find a download link. I was wondering if someone could provide me the firmware for my setup, or some guidance on how I can get it working with MEMS Studio, so that I can play around with the FSM on the LSM6DSO.

I'm currently trying to use the VL53L5CX to detect motion in the range of about 1m in front of the sensor.This seems to work fine indoors - but outdoors - I don't seem to be able to get anything more than around 30cm, even with xtalk calibration, and a shroud.I don't actually need 8x8 or even 4x4 - i basically just need to see if there is something passing in front of the sensor (think beam breaking - but with just one device)Am I missing something ?Is there some config to increase outdoor performance ? Should I use a different sensor ? Any thoughts gratefully received.

Hi,Been a while :) Seeing some odd readings after the sensor has no real changes.  After some time when a change in the sensor distance happens it "seems" to take many readings to get good readings.Is there a sleep I don't know about? What is the recommended way to "wake up" the sensor if it has been dormant for some time......or am I imagining this? Thanks,Will 

When using the VL53L1CB for ranging, we want to achieve lower power consumption by reducing the measurement frame rate. I performed the following two experiments:A 50ms measurement budget (integration time) followed by a 50ms waiting period.A 50ms measurement budget followed by a 100ms waiting period.I observed that the power consumption in both scenarios is nearly identical, with no significant difference. Using a photodetector, we confirmed that the ToF sensor's light emission time aligns with the measurement budget; a 50ms integration time results in approximately 50ms of light emission, confirming my parameter settings are effective. The power consumption curve shows that the power level remains high even after the ToF sensor has finished emitting light.How can we reduce the power consumption during the waiting interval between measurements (without shutting down the sensor)?If shutting down the sensor after each measurement achieves lower power consumption, what is the reason for

VL53L1CB的最低投资回报率配置是 4x4？我可以将其配置为 1x1 吗？ Translated : The minimum ROI configuration for the VL53L1CB is 4x4? Can I configure it as 1x1?

Hello!I am using the VL53L4CD TOF Sensor as sold by Adafruit. I am running it with the circuit patched together as described in the example file VL53L4CD_Sat_HelloWorld.ino, also with the exact code (the only change being the port number). I am using an Arduino R4 WiFi. When I start the unit up, it runs normally for a bit (<1 min), and then stops.Starting... Status = 0, Distance = 37 mm, Signal = 232 kcps/spad Status = 0, Distance = 38 mm, Signal = 234 kcps/spad Status = 0, Distance = 35 mm, Signal = 233 kcps/spad Status = 0, Distance = 36 mm, Signal = 230 kcps/spad Status = 0, Distance = 39 mm, Signal = 236 kcps/spad Status = 0, Distance = 35 mm, Signal = 234 kcps/spad ...I have an Arduino R3 Uno, and tested the TOF sensor using that, and it seemed to run endlessly.Based on reading around, I am guessing this has something to do with the resistors required for I2C connections and some builtin difference between the R4 WiFi and the R3 UNO, but I am not sure where I should start here.

Hello,I am using the 53L8A1A to evaluate the VL53L8CH with the MZAI_EVK_v1.0.1 software. For my application, I need high CNH resolution for as long a histogram as possible, but for only one histogram. Because of that, I aggregated down to one row and one column with the following configuration settings. CNH_4x4_ONECNH: StartType: 0 Resolution: 16 RangingPeriod: 500 ZoneMode: 2 GlareFilter: 0 ExtendedMode: 2 cnhStartX: 0 cnhStartY: 0 cnhMergeX: 4 cnhMergeY: 4 cnhCols: 1 cnhRows: 1 cnhNumBins: 75 cnhSubSample: 1 isDefault: false isVisible: trueI see in the CNH_Data_Size sheet within the MZ-AI_Configuration Excel sheet that the MZ-AI GUI limits the cnhNumBins parameter to 75. The calculator says that the data size for more bins than that does work, however.Is there a reason that the parameter is limited to 75 and, if not, is there an easy way for me to change that limit?Thanks,Garrett

I am using a ST Sensor tile.box pro with FP-SNS-DATALOG2 function pack, I have already used the Python GUI software with USB connection and ST BLE Sensor app for data logging to save into the microSD card, which works fine. Now , I would like to use python program to start the data logging process and possibly selecting the sensors for logging, for this, I am looking for the UUID related to these, and I can not find from the FP-SNS-DATALOG2 program. Where can I find related information for these? I have used a BLE Sniffer app to look for the available UUID but little to no description I found from the FP-SNS-DATALOG2 code how it actually works with the app so that I can replicate for my needs. Primary service/Unknown service 01: COPY_CONSOLE_SERVICE_UUID 00 00 00 00 00 0E 11 e1 9a b4 00 02 a5 d5 c5 1b Unknown Characteristics: COPY_TERM_CHAR_UUID 00 00 00 01 00 0E 11 e1 ac 36 00 02 a5 d5 c5 1b COPY_STDERR_CHAR_UUID 00 00 00 02 00 0E 11 e1 ac 36 00 02 a5 d5 c5

Hey ST Community,I'm currently trying out the CCA02M2 MEMS microphone board on a NUCLEO-L476RG, using firmware compiled from X-CUBE-MEMSMIC1.The microphones work, but the signal seems to have some heavy filtering. For example:If I record with Audacity and snap/tap near the mic, I don’t see any response.If I play a frequency sweep from my laptop, it only gets recorded when I’m also speaking, but not if the sweep is played alone.This makes me think there’s a strong filter or noise suppression enabled by default. Where in the firmware should I look to disable these filters? Is it controlled by the PDM2PCM library, or another stage in the middleware?Thanks in advance for any guidance! 

After soldering process, IMU sensor and magnetometer need to do calibration after power on, such as flip axis, 8 shaped pattern, or real-time calibration.For ST sensor such as LSM6DSV and LIS2MDL, I want to know how to confirm whether sensor has been calibrated?Is there any levels to judge the status?  

I am trying to use the VL53L3CX with an STM32G070 for water level sensing. The app is based upon the Simple Ranging example.What I am seeing is that the distance read by the sensor alternates between two values, quite far apart. The sensor is mounted in a stable position for this testing, a little less than an inch from a flat white target.Pointers on how to debug this would be much appreciated.Sid 

Hello ST team,I'm currently working with the **SmartPresenceDetectionEVK v1.0.0** on a setup consisting of:- **NUCLEO-F401RE**- **X-NUCLEO-53L8A1**- Firmware version: **1.7.0.0**- Driver version: **VL53LMZ_2.0.10**When I interact with the board using **Tera Term via UART**, everything works perfectly. I can use commands such as `enable`, `help`, and receive presence detection results in real-time.However, when I try to launch the provided **SmartPresenceDetectionEVK.exe** GUI on Windows 11, I encounter the following unhandled exception: --------------------------------------------------------------------------------2025-04-03, 10:32:13--------------------------------------------------------------------------------<class 'wmi.x_wmi'>:<x_wmi: Unexpected COM Error (-2147217396, 'OLE error 0x8004100c', None, None)>--------------------------------------------------------------------------------File "SmartPresenceDetectionEVK\__main__.py", line 77, in createWindowFile "Smart

Hello everyone,I’ve been working with the STHS34PF80 sensor and would appreciate some insights regarding its detection range and field of view (FOV). In my tests, I’ve observed that the sensor detects presence effectively up to a range of about 1 meter when I set the presence threshold to 100 LSB. Additionally, the FOV seems to be around 30 degrees.I’m wondering if these results align with what others have experienced. Is this the typical range and FOV for this sensor under similar conditions, or could there be some optimization or calibration that I’m missing? Any feedback or suggestions would be greatly appreciated!Thanks in advance! Notesensor config:lpf_m: 04, lpf_p: 04, lpf_p_m: 02, lpf_a_t: 00sths34pf80_gain_mode_get 7sths34pf80_tobject_sensitivity_get 2000sths34pf80_odr_get 8sths34pf80_block_data_update_get 1sths34pf80_one_shot_get 0sths34pf80_presence_abs_value_get 1sths34pf80_tobject_algo_compensation_get 1sths34pf80_presence_hysteresis_get 25sths34pf80_motion_hysteresis_

I am using the STHS34PF80 sensor (SparkFun Presence Sensor - STHS34PF80) with an ESP32 in my ceiling fan to automatically turn the fan ON and OFF based on human presence and motion. However, the sensor is providing continuously varying output values even under the same conditions. How should I properly use this sensor? Does it have a refresh time or delay setting? Please reply as soon as possible.

Our use of the VL534LCD is within what we call a bin.  A long rectangular container.  The sensors job is to measure the distance to items placed into the bin.  Very contained environment with little interference.  When we calibrate the sensor we do this when our bin is empty.  There is a white panel always at the beginning of the container bin which moves forward (backwards) along a track when items are placed in it or taken out.  When it is empty it is stationary at 231mm.  So,  we calibrate using 231mm.When we calibrate to 231mm we get back offsets from the sensor > -45.  These seem unusually large to me? Why would this be?  

Hello,For a project I would like to use the VL53L4CD or VL53L4ED to measure distances in the range of ~1 cm to 80 cm. The expected ambient temperatures can vary (maximum between -10°C and +80°C, although the temperature will usually be in the range of 0°C to 50°C). Initial tests showed promising measurement results under real conditions.The project requires a minimum service life of 10 years for the components used. I know from other projects that such a long operating life is often a problem e.g. for laser diodes.Are there any recommended strategies for maximizing the sensor's service life?Should I e.g. provide a cut-off option for the sensor's supply voltage to protect it when it does not need to be active? Or would the HW standby state have the same effect?Thank you in advance for your help.

INT_SLEEP_STATE无法通过INT_2阅读。  

Hi, Is it possible to get some sort of frame timestamp from the evaluation boards? Ideally, I would love to have start and end of exposure timestamps but any timestamp from the sensor would be great. I could timestamp when I receive the frame on my device, but that might not be accurate enough for my application since it would also include other delays from my computer. Inaccuracies in the 10s of microseconds range are acceptable. Thanks.

The STSW-IMG009 VL53L1X ULD API (Ultra Lite Driver Application Programming Interface) has a bug in the function VL53L1X_SensorInit that blocks the code from being executed if  status |= VL53L1X_CheckForDataReady(dev, &tmp);  write 0 constantly in tmpThe block  while (tmp == 0) { status |= VL53L1X_CheckForDataReady(dev, &tmp); }has no timeout implemented and, for instance, if a cable or a sensor breaks for some reason, the code will endup stuck therePlease also see this github issue exit VL53L1X_SensorInit() after timeout if no sensor / sensor doesn't work · Issue #29 · sparkfun/SparkFun_VL53L1X_Arduino_Librarywhere a timeout is added Add timeout to sensorInit · sparkfun/qwiic_vl53l1x_py@1154d07 · GitHub

Do the current VD56G3 drivers support the CM5 module? I have followed the installation guides several times (including building libcamera from the ST source files) and I can't get libcamera to stream the camera. Here is the error message:$ libcamera-hello [0:18:08.863706754] [1547] INFO Camera camera_manager.cpp:326 libcamera v0.5.0 [0:18:08.870764844] [1548] INFO RPI pisp.cpp:720 libpisp version v1.2.0 50426319aa1a 02-07-2025 (19:52:09) [0:18:08.887921079] [1548] INFO RPI pisp.cpp:1179 Registered camera /base/axi/pcie@1000120000/rp1/i2c@88000/fox@10 to CFE device /dev/media2 and ISP device /dev/media0 using PiSP variant BCM2712_D0 Preview window unavailable Mode selection for 562:682:12:P R8,320x240/0 - Score: 3558.98 R8,480x640/0 - Score: 2470.14 R8,640x480/0 - Score: 2614.48 R8,768x1024/0 - Score: 2359.14 R8,1024x768/0 - Score: 2327.98 R8,720x1280/0 - Score: 2973.64 R8,1024x1280/0 - Score: 2337.14 R8,1120x1360/0 - Score: 2310.55 R8,1124x1364/0 - Score: 2311 R10_CSI2P,

Hello,I'm working on an IMU project. I need to measure pitch/roll/yaw rotation in quaternions.For my first test, I am using a STEVAL-MKI227KA connected to an Arduino micro, which already allows me to extract the quaternions.I send the data via I²C.My first question is, do you know if the two are compatible?I am using this Arduino library, https://github.com/stm32duino/LSM6DSV16X, to communicate between my Arduino and my devBoard. (I had to change the float_t to float to make it work.)With this library, I only get the same value regardless of my rotation: Quaternion: 0.7562, -0.0055, 0.0001, 0.6543Have you ever had this problem?Thank you 

Hello,I was having fun with the Sensortile.box Pro I bought a month ago. When I reset the device to its factory settings (SensorTile.boxPRO.bin in file en.stsw-mkboxpro-fs.zip) using the STM32CubeProgramming tool, the device blinks the red LED once and cannot be found by the ST BLE Sensor app. This happens for any sample FW.If I click the "Verify programming" checkbox, I get the following message in the log:19:28:09 : Error: Data mismatch found at address 0x08000000 (byte = 0xF8 instead of 0x98)19:28:09 : Error: Download verification failedPlease advice. Thank you,A.