MEMS and sensors

Hi,I'm working with the LIS2DW12 accelerometer in a low-power IoT application. The sensor is configured to wake the MCU via an interrupt on INT1, connected through a monostable multivibrator (Schmit trigger IC). The setup is designed so that a rising edge on INT1 triggers a reset of the MCU.Here’s the issue:When the MCU wakes from a previous interrupt (caused by actual motion), it starts reinitializing the LIS2DW12 — performing a soft reset and reconfiguring the registers into polling (standard) mode. Then, after some time in polling mode, if no motion is detected, the program switches the LIS2DW12 back into interrupt mode.At this point, the INT1 pin briefly goes high, creating a glitch pulse even though the system is stationary. This unexpected edge triggers the monostable multivibrator, which in turn resets the MCU — essentially creating a loop. This behavior is not acceptable for my use case.What I’ve tried:Delaying the CTRL4 write until after all other registers are configured (CTR

Hi.i am having a STEVAL-IDP005V1, STEVAL-UKI001V1, 10-pin-IDP005V1 Cable, M12female connector.i am referring this document ( https://www.st.com/resource/en/product_presentation/steval-bfa001v1b_quick_start_guide.pdf ) i am not able to connect the board to my PC.  please anyone suggest me to do the analysis of accelerometeris that any clear document? Thank you  

Hi all, I have installed the LPS22HHTR on my custom circuit to communicate with a STM32F4x via I2C. I have pulled up the SCL (pin 2), SDA (pin 4), SA0 (pin 5), and CS (pin 6) lines to 3.3V via 4.7k resistors, grounded the two ground pins (8 and 9) and RES (pin 3). I have also provided a 100nF decoupling capacitor for the VDD and Vdd_IO pins and left INT_DRDY floating. My issue right now is that when i try to call on the device using its address (0b1011101 << 1) and the HAL_I2C_IsDeviceReady() function, I am not getting a response and a NACK is thrown (I2C_FLAG_ADDR = RESET and I2C_FLAG_AF = SET). I have double checked the configuration of the circuit several times and voltages at pins but I'm still not getting a response.  I would appreciate any help as to why this is happening or if I'm doing something wrong.

HiI am trying to run the STEVAL-IDP005V1-GUI.Current setup:STEVAL-IDP005V1-GUI - > STEVAL-IDP004V1->STEVAL-IDP005V1:I am unable to connect to the IDP004V1 dev kit from the GUI, the comms just gives an error suggesting to restart the GUI. I have tried re flashing the firmware with the 485 and USB binaries provided in en.stsw-io-link (https://www.st.com/content/st_com/en/products/embedded-software/evaluation-tool-software/stsw-io-link.html)I have tried both 485 and USB connections but it does not work. Please advise on how to get the demo's up and runningRegards

Hello! I've designed a custom PCB very similar to other breakout boards on the market, because there are additional components I want to fit in a small package alongside the VL53L1X sensor. When testing my PCB, the sensor does not initialize. I've been using the same library that works with other breakout boards. The PCB is supplied with 5V from an Arduino Nano, stepped down to 2.8V with an LDO and then logic shifted with two BSS138's to the SDA and SCL pins.  At first I thought it was an I2C timing issue, so I made the pullups stronger on the bus (~3.6k) but that was unsuccessful. I've done a continuity test on all components. I'm wondering if there's anything I've missed or if there's a chance something went wrong in manufacturing. I can provide the PCB layout if needed.  Any help is appreciated, this is one of my first PCB designs! Thank you!

Hi, I am using STM32CubeMX to configure STM32CubeIDE project. I have Nucleo-U385RG-Q with MEMS X-Nucleo-IKS01A3. I am trying to read pressure sensor LPS22HH. According the X-Nucleo documentation the I2C default addresses for LPS22HH are: BA and B8. But the C code for the sensor defines BA and B8.Using the STM32CubeIDE project generated by STM32CubeMX I am not able to read sensor ID. The following code gives me an error. In the code I first define: stmdev_ctx_t dev_ctx; dev_ctx.write_reg = platform_write; dev_ctx.read_reg = platform_read; dev_ctx.mdelay = platform_delay; dev_ctx.handle = &SENSOR_BUS;Then use it: whoamI = 0; lps22hh_device_id_get(&dev_ctx, &whoamI);In STM32CubeMX i configured PINs PB6 and PB7 for I2C1. The sensor files "lps22hh_reg.*" I got from GitHub.Can someone please point me to the right direction. Thank you in advance.

Hi all,I'm currently developing test code for the VL53L1 ToF sensor using STM32CubeIDE, and I'm aiming to optimize the sensor's performance for close-range measurements — specifically in the 10mm to 200mm range — with a target accuracy of around 1–2%.I'm currently using the bare driver files provided by ST, which I’ve manually integrated into my STM32 project.I'm aware of the various distance modes (Short, Medium, Long) offered by the sensor, and I plan to experiment with them. From what I understand, the Short distance mode is generally preferred for close ranges due to better ambient light immunity and reduced signal crosstalk. I'm also considering manually configuring a Region of Interest (ROI) centered around the sensor’s optical center to help reduce edge-related anomalies.My questions to the community are:Which distance mode and ROI settings have yielded the best results for others in this close-range context?What other parameters should I tune to achieve maximum accuracy over th

HI folks.I would like to wake up my ESP8266 using an interrupt from the VL53L0X sensor.I have configured the sensor to use both threshold detection and to trigger an interrupt. I tested whether the interrupt is being triggered, and it is— the GPIO pin goes from HIGH to LOW when the threshold is reached. However, I noticed that the GPIO remains LOW until the interrupt flag is cleared. If I connect this GPIO pin directly to the RST pin of the ESP8266, the program will never run because the RST pin stays LOW.To solve this, I implemented a pulse generator that triggers on the falling edge of the GPIO signal.Here is the circuit I implemented:From: https://forum.arduino.cc/t/esp8266-deep-sleep-forever-and-interrupt-wake-up/574185/20 i am using a 0.33uF capacitor instead 100uF. Resistor values are the same. The diode is a 1N4007.In this setup, "H" represents the GPIO pin connected to the VL53L0X sensor, and the right side of the image shows the connection to the RST pin of my E

Hello,I am using the VD56G3 connected to a STEVAL-CAM-M0l1.  There is a very small ribbon cable between the sensor and the connector on the CAM-M0l1 - roughly 5mm.  I am working on a mock-up of some smart glasses where I'd like to extend that cable to a considerably longer length - ideally 1 meter.  Is there a way to create an extension to this cable or a product that has a lengthened connection?I know that there is also a ribbon cable from the STEVAL-CAM-M0l1 which could easily be lengthened, unfortunately, the form factor of the STEVAL-CAM-M0l1 is not suitable for my mock-up.Any suggestions/recommendations as to how to lengthen this connection along with any pitfalls would be appreciated. Thanks,Dan Luka

Hi!I have a question about calibrating vl53L4CD and using a coverglass. I am doing experiments with a sample flat panel from Gilysmo, and I have noticed that if the panel is 2-3mm from the sensor, the calibration doesn't compensate for it. It looks like it just ranges to the glass and that's it. Is that normal? What is the maximum distance the glass should be from the sensor? Or perhaps I am doing something wrong?Thanks!

Hi all,Could you please tell me if the temperature sensor of the LIS2DW12 is used to correct the acceleration sensor?Thanks all,

Has anyone tested the LIS2DE12TR accelerometer using lower input capacitance? I am interested in trying it out and possibly using it in an intrinsically safe design and the recommended 10uF capacitor is a deal breaker. Alternatively, does ST have a similar low power model that has lower capacitive requirements? 

HelloI would like to get the lis2mdl magnetometer data using the lsm6dsv second i2c line using the sensor hub.so far I get the accelerometer and gyroscope data via SPI and I want to add the magnetometer data.The code I have to configure the sensor hub and retrieve the data doesn't work. The i2c line doesn't even move (I checked with an oscilloscope)I checked with the example here  https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsv_STdC/examples/lsm6dsv_sensor_hub.c#L504 but I have trouble understanding the codeI have a nucleo board l476RG not the demo board given in the example but since my spi communication works it shouldn't be a problem. I also have several lsm6dsv connected to my MCU but right now I try to make it works for at least one.I use the lsm6dsv_reg and lis2mdl_reg libcan anyone tell me what is wrong and why I can't make this i2c line work?? I've been trying for 3 days alreadyI attached my project  

Hi I purchase a STEVAL MKBOXPro. It connects to phone and app fine but i'm having trouble to get the device connected to MEMS studio and Unicleo GUI  BLE Connection issue... 1. device manager detects STBOX but does not connect on MEMS studio and Unicleo GUI. I Problem with usbc connection.. 2. serial usbc sees COM9 with MEMBS studio but cannot connect to it when I hit connect button  Wondering what's causing the connection issue via bluetooth or via cable? I see a driver titled en.stsw-mkbox-bledk but i there is no exe button to install the driver.       

Hi,I'm developing a prototype based on an already existent product that contains an LSM303AGR, the goal is to install the device in a tower and detect when the tower is tilted or fallen, for this task the idea is to wake up the device via the interruption pin on the magnetometer as the device is battery powered and frequent checks on the status woud decrease the life span on the device too much. The main issue i'm facing is that my device seems too prone to false positives maybe caused by induced vibrations  by the wind on the tower, so far the best results are with the ODR to 1Hz, FS at 2g and adjusted the sensitivity acordingly but this is not an ideal sollution (each device has to be adjusted as the characteristics and eviroment of each tower is different and behaves differently), what is the right way to sense movement but filtering impacts? any sugetions about a good approach for detecting tilt and crash while being power efficient?

Hi all,Could you show me the temperature accuracy of LIS2DW12 ?Thanks all,

Hello Team,                I am finding the sensor which have the up to 15 meter range.                                i am using this sensor in my water level detection project so according to suggest me the sensor.  Thanks and regard'sASHISH K.

Hi,I’m encountering an issue with the LSM6DSOX IMU INT1 pin behavior during initialization. The expected behavior is for INT1 to remain LOW by default, including after a software reset. However, what I’m seeing is:After power-up or reset, the INT1 pin stays HIGH by default.It only transitions to the expected state (LOW) after the interrupt is configured and routed to INT1.I have checked the INT2, it is OK (default LOW)This is causing some unintended behavior during system startup, as other components relying on the INT1 state assume an interrupt has already occurred.Expected behavior:The INT1 pin should be LOW by default and remain LOW after a software reset, until a valid interrupt condition is met.Has anyone experienced similar behavior, or is there any recommended workaround or configuration to force INT1 to stay LOW until explicitly triggered?Appreciate any insights or guidance on this.Thanks

Hello everyone,We recently tested the VL53L7CX and ran across an issue with very high reflective fabrics. Here are two images of such fabric. The first is a picture taken with flash light off, second picture is taken with flash light on. From the moment I wear this and come in front of the sensor I "disappear", the sensor also outputs status 255. Is there a way to handle this? Is there past experience with such items?  Here is an overview of our setup:The VL53L7CX module from POLULU with a cover glass from GILISYMO is connected to a Raspberry Pi Pico 2040. Currently we're testing without the cover glass. We're using the SparkFun VL53L5CX Arduino LibraryThank you for your help.

Hi, i am trying to connect the nrf54L15 with the VL53L4CD sensor. I am having trouble with library and the code. Struggling with connecting the nrf54L15 to the sensor in the different libraries. Are you able to share the different register adresses for the VL53L4CD sensor? Do you have an examples using the nrf54L15 and or device tree with the VL53L4CD?

Hello,I am using a VL53L0X sensor with a NUCLEO-64 F411 board, and I am trying to achieve accurate measurements and low power consumption for the development of a LiDAR system.I have one problem and one question: Problem:The measurements are a bit inaccurate. For example, when I measure an object at a real distance of 5 cm, the sensor detects it at around 7 cm. Also, for some objects beyond 20–25 cm, the readings become irregular. Question:I would like to use the sensor with interrupts, but the User Manual for the API is not very clear on how to implement the interrupt feature.I am attaching my main.c file and the library I am using, which includes the API and its .h file. Thank you very much for your help! //This is the main.c /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention

Hi,im currently working on interfacing the STM mems sensors with Beagle Vahead board, im using a kernel version of 6.13 and i tried patching the STM MEMS IIO drivers from link. Im aware that the STM has confirmed the testing of the driver with kernel 6.6.While patching i faced few errors ie mis match in the headders and i have successfully resolved them.im able to boot the device and able to get the device node in the /sys/bus/iio/device  when interfacing the lps22df sensor.when any other sensors (lsm6dsox, lisduxs12,lsm6dsv32) are interfaced on the same bus, im not able to detect the device. i have the same hardware set for lps22df  also. but in that case i was able to get the raw pressure and temperature data.I want to understand the issue why it happens so.i have mentioned the mininal properties on the i2c bus node in DTS file. and have omitted all the optional parameters.have a look at the STM driver booting errors[ 1.143802] st_lsm6dsox_i2c 2-006b: supply vdd not fo

Hi ST Community,I’m trying to use the LSM6DSO32XTR in Mode 2 (SensorHub) to stream data from two accelerometers, two gyroscopes, and a magnetometer into the 9-kbyte Smart FIFO for motion tracking over 10–30 minutes, aiming for low MCU interrupts and power usage.What I’ve Tried:I’ve set up one LSM6DSO32XTR as the master (using its internal accelerometer and gyroscope) and planned to connect a second accelerometer (e.g., LIS2DH12), a second gyroscope (e.g., L3GD20H), and a magnetometer (e.g., LIS3MDL) on the secondary I²C bus (SCx/SDx).I’m using Zephyr RTOS, referring to the datasheet (Section 7.2, 5.4), but learned I can’t connect another LSM6DSO32XTR as a slave on the secondary bus.Questions:1. Has anyone done a similar Mode 2 setup with these sensors? How did you handle I²C addressing?2. Any pitfalls in the Mode 2 config to ensure FIFO streaming works?3. Tips for power optimisation and avoiding data loss over long periods?4. Any alternative methods for this multi-sensor setup?I’d appr

Hello everyone, I'm stuck and I need some help. I have the LIS2HH12 accelerometer connected to my raspberry pi via SPI. So far, I have been able to collect real-time accelerometer data . But my goal is to only get data once the accelerometer is titled or moved(I've noticed that z goes to less than 0.7g when tilted). I'm trying to program the INT1 pin to send a high or low signal to my gpio once movement is detected. But so far, I've failed.   Here's my code, if anyone can please look at it and help a desperate PhD student I would be very thankful! import spidevimport RPi.GPIO as GPIOimport time # SPI Configurationspi = spidev.SpiDev()spi.open(0, 0) # Bus 0, Device 0spi.max_speed_hz = 10000000 # 10 MHzspi.mode = 0b11 # GPIO ConfigurationINT_PIN = 22GPIO.setmode(GPIO.BCM)GPIO.setup(INT_PIN, GPIO.IN, pull_up_down=GPIO.PUD_UP) # Register addressesCTRL1 = 0x20CTRL2 = 0x21CTRL3 = 0x22CTRL4 = 0x23CTRL5 = 0x24CTRL7 = 0x26IG_THS_X1 = 0x32IG_THS_Y1 = 0x33IG_THS_Z1 = 0x34IG_DUR1 = 0x35IG_CFG

Hi, Is it possible to obtain more information regarding the typical performance characteristics of MEMS accelerometers? We are currently evaluating the LSM6DSO32 sensor, and the datasheet is mostly just +/- in terms of accuracy. We would like to see the performance graphs over a range of frequency / temperature / etc.