MEMS (sensors)

OverviewThe LSM6DSV80X represents a breakthrough in wearable technology. Its ability to measure both high- and low-acceleration ranges, combined with high energy efficiency and advanced processing capabilities, makes it an ideal choice for users who need detailed data analysis and improved performance tracking in high-impact sports and activities such as volleyball, football, tennis, boxing, and explosive jumping.This IMU provides a comprehensive solution for wearable devices, high-impact detection, and activity tracking, delivering an excellent combination of accuracy, integration, and efficiency.The LSM6DSV80X is the world’s first IMU to combine high-g acceleration measurement of up to 80 g and low-g sensing capabilities in a single package. It integrates advanced features, including edge processing and sensor fusion, to provide consistent performance and valuable data for sports-wearable tracking and high-impact detection.  The device supports edge AI capabilities, using a finite st

Hello,I tried to get the HP properly working for hours now, but I get zeros on all axes every third output.What ist wrong? I tried a lot of different setup variation buts always with similar result.When disabling FDS (HP function), there are no zeros in the data stream.In this example I shaked the sensor.##########################WHO_AM_I: 0x33LIS3DH found.--- Register-Verification ---TEMP_CFG (0x1F) = 0x00CTRL_REG1 (0x20) = 0x2FCTRL_REG2 (0x21) = 0x08CTRL_REG3 (0x22) = 0x00CTRL_REG4 (0x23) = 0x80CTRL_REG5 (0x24) = 0x00CTRL_REG6 (0x25) = 0x00REFERENCE (0x26) = 0x00FIFO_CTRL (0x2E) = 0x00INT1_CFG (0x30) = 0x00INT1_THS (0x32) = 0x00INT1_DUR (0x33) = 0x00INT2_CFG (0x34) = 0x00INT2_THS (0x36) = 0x00INT2_DUR (0x37) = 0x00CLICK_CFG (0x38) = 0x00CLICK_THS (0x3A) = 0x00TIME_LIMIT (0x3B) = 0x00TIME_LAT (0x3C) = 0x00TIME_WIN (0x3D) = 0x00ACT_THS (0x3E) = 0x00ACT_DUR (0x3F) = 0x00--- Configuration finished --- ms; X; Y; Z;INT1 56; 184; 1

Hello,I would like to evaluate  IIS2MDC mounted on MKI185V1 evaluation board using MEMS Studio. in the “Save to File” section I can choose Timestamp, Magnetometer, Magnetometer [LSB}, and Interrupt 1, but not Temperature, although the device has an internal temperature sensor. my setup:STEVAL-MKI185V1 on STEVAL-MKI109V3, FW: 3.79.1. MEMS Studio ver. 2.4.0 on Windows 11.Please advise,Shmulik

Hello, we are planning to use LSM6DSO in Mode 1, but PCB is fixed and pins 10 and 11 are connected to GND. This conflicts with LSM6DSO datasheet but I was wondering if it is still OK to connect them to GND. Can you clarify on this?

Please support to update how LPS27HHW pressure sensor can detect the fall of a human being.

Hi,I am using the NBP8FD4ST1 pressure sensor with the S32K146 microcontroller. The CS_B/WAKE-UP pin of the sensor is connected to a GPIO pin on the microcontroller.The logic analyzer signal mapping is as follows:D0 → SCLK D1 → CS_B D3 → READY D5 → MISO D7 → MOSIDuring the communication sequence, when I pull the CS_B pin low to request SPI communication, the READY pin is asserted as expected. After READY goes high, I send the SPIOPS register read command (0x00E1). However, the sensor always returns 0x0000 on MISO. As a result, the firmware validation fails, and the CS_B pin is subsequently driven high to terminate the transaction.Could you please help me understand whether my SPI communication sequence is correct or if I am missing any required step, such as the wake-up sequence, dummy transfer, or SPIOPS handling described in the datasheet?I have also attached the logic analyzer screenshots for reference.Thank you in advance for your support.Best regards,Pratyusha.  

9 axis gyroscope mems sensor available?

Hello,I have a couple of devices using LPS28DFW pressure sensors.The sensors are configured as follows:INTERRUPT_CFG = 0x00, THS_P_L = 0x00, THS_P_H = 0x00, IF_CTRL = 0x00, CTRL_REG1 = 0x3C, CTRL_REG2 = 0x00, CTRL_REG3 = 0x01, CTRL_REG4 = 0x02, FIFO_CTRL = 0x02, FIFO_WTM = 0x64,All other registers are left at their default values.Usually they work fine, filling the FIFO with new data and generating an interrupt every second. However, I occasionally encounter an issue where the sensors appear to stop filling the FIFO for a period of time. The duration of this stall is not consistent, it can range from a few seconds to a permanent lock-up. During this locked state, I can still successfully read the temperature, and reading back the configuration registers confirms they are set as expected. After a power cycle and reconfiguration, everything returns to working correctly.Have you ever experienced this issue? Do you have any idea what might be causing it?

Hi,NUCLEO-F401RE + X-NUCLEO-IKS02A1, MEMS Studio v2.4.0. Flashed DataLogFusion (Applications\IKS02A1\DataLogFusion), connects fine (X-NUCLEO-IKS02A1, FW: 12.1.0), but I only get "Library Evaluation" (Data Table, Charts, Sensor Fusion...). No "Quick Setup" / "Sensor Evaluation" anywhere, including under Advanced Features. DataLogTerminal gives "Board not identified."An older tutorial (MEMS Studio v1.3.0) shows a "Sensor Evaluation" section with Quick Setup, Registers Map, FSM, MLC, Qvar — raw register access, not fusion output.Question: Which X-CUBE-MEMS1 firmware (if any) enables "Sensor Evaluation"/"Quick Setup" for this board combo? Is it firmware-specific or was it removed in MEMS Studio v2.x?Thanks!

Hi,We've been working on a project using v1.3.1 of MEMS Studio, but I've had to use a new laptop and it doesn't have this installed. Unfortunately, when I go to the downloads page I can only see v1.4.1 of MEMS Studio and it's forcing me to upgrade the firmware, which I don't want to do as all our testing & benchmarking has been based on a specific configuration.Does anyone have, or can you point me to, the older version of the application? ST don't seem to have an archive of older builds anywhere and their support team has been unable to help.Thanks,Simon

I am trying to establish an accuracy figure for our product based on an MPX5500 MEMs pressure sensor.We calibrate at many set pressures across the devices span, so we can reduce non linearity errors.I need to determine the sesnors accuracy with improved non-linearity figues but need to know error corficients for aspects such as temperature, hysteresis, aging etc     There is talk of an orignal “sensor development kit” ASB200 from Motorola (Freescale, then NXP), which had SPICE model.Does anyone know of this kit or have the SPICE models available?Or any other application notes that might help?Thanks. 

In the stm32 cubeMX Board selector menu I cant find board MKI-109D.How can I develop the board firmware? 

Hi all, i am just trying to figure out how to connect the Stwinbox board with Rs485. if you have any advice in terms of applications i must use and the recommended firmware?  regards

Hi,I am using LSM6DSV320X for my project. Initially to save power I have Low G accelerometer with 15Hz ODR and 16G with fifo enabled. Once an activity is detected i want to switch on High G as well with 4000 Hz (with High Accuracy mode) and use both high G and Low G accelerometer for data collection. Is this possible if I dont use FSM or ASC and will High Accuracy then work ?. or can this only be achieved with FSM ? I look forward to your reply.

Board: STEVAL-MKI109D (STM32H563ZI) + STEVAL-MKI207V1 adapter (ISM330DHCX)Goal: Bare-metal custom firmware reading WHO_AM_I over SPI1Following up on my earlier thread about GPIO pin mapping [link to old thread] — pin mapping is now resolved (SPI1_NSS on PA15, confirmed via community input; PA4/PA5 are DAC1 Vdd_set/VddIO_set as discussed). Thanks for the help getting there.I'm now stuck on a different issue and would appreciate a sanity check. WHO_AM_I consistently reads 0xFF, but every layer I can verify from firmware/multimeter checks out correctly:CS on PA15 (GPIO output, confirmed via MODER/ODR register dump) SPI1 Mode 3 (CPOL=1, CPHA=1) — confirmed via CFG2 register decode SCK/MISO/MOSI on PB3/PB4/PB5, AF5 — confirmed via GPIOB MODER/AFRL dump VDD/VDDIO measured 3.3V at the DIL24 breakout header (J13/J14 area on JP1/JP2), in spec HAL_SPI_TransmitReceive returns HAL_OK, ErrorCode=0x0, every call — no timeout, no fault Tested at both SPI_BAUDRATEPRESCALER_32 and _256 (extremes) — ide

Part is ~10-20 years old. Found some vague info that says there is an STM part# 35AX. Package is 14 pin, 14-VFLGA/LGA (3mm x 5mm). Pretty sure its an IMU/Accelerometer but trying to track down a pinout for a possible replacement.

Hi, I am planning to use IMU ASM330LHB for my project and test the sensor functionality using board STEVAL-MKI236A.I want to know whether I can plug STEVAL-MKI236A into the DIL24 connector of the SensorTile.Box PRO and test the functionality using SensortTile.box smartphone app ST BLE Sensorhttps://community.st.com/mems-and-sensors-62/getting-started-with-sensortile-box-192I want display the below values as mentioned on the link.Is it possible? Thanks,Sucheta

Hello ST Community, I've noticed that the STHS34PF80 is now marked as EOL (End of Life) across distributor platforms. Is there an official ST replacement or successor planned? Any advice would be appreciated. Thanks!

acc + gyro + timestamp, ODR 208 hz, FIFO continous mode, timestamp resolution 25us, following is my register settingimu.__write_reg(CTRL3_C, 0x44)imu.__write_reg(WAKE_UP_DUR, 0x10)imu.__write_reg(CTRL10_C, 0x34)imu.__write_reg(CTRL1_XL, 0x5c)imu.__write_reg(CTRL2_G, 0x5c)imu.__write_reg(FIFO_CTRL2, 0x80)imu.__write_reg(FIFO_CTRL1, 45)imu.__write_reg(INT1_CTRL, 0x08)imu.__write_reg(FIFO_CTRL3, 0x09)imu.__write_reg(FIFO_CTRL4, 0x08)imu.__write_reg(FIFO_CTRL5, 0x2E)Occasionally, I get incorrect timestamp value in FIFO (acc and gyro value is ok), following are some example530929, 531123, 531316, 531510, 531704, 531898, 532092, 532286, 532224, 532673 (timestamp go backward)165672, 165866, 166060, 166254, 166448, 166641, 167087, 167223, 167417, 167611, 167804 (timestamp jump) Thank you very much for helping

Hi ST Team,I understand that the SensorTile.Box PRO is supported by MEMS Studio, can you please confirm?Currently the device/kit is not recognized by MEMS studio but the ST BLE App only.Thanks!  

Hi,Hardware: STEVAL-MKI109D (STM32H563ZI), ISM330DHCX on DIL24I'm developing custom bare-metal firmware for the STEVAL-MKI109D motherboard (STM32H563ZI), flashed via DFU, to communicate directly with an ISM330DHCX sensor on a STEVAL-MKI207V1 DIL24 adapter — not going through MEMS Studio.Problem:I can't get a valid SPI response from the sensor — WHO_AM_I consistently reads back as 0xFF. I've verified the following are correct against the ISM330DHCX datasheet:GPIO alternate function mapping (AF5, SPI1) confirmed via register dump SPI1 configuration matches Mode 3 (CPOL=1, CPHA=1), master mode, 8-bit frames, software NSS Read command format (0x80 | reg + dummy byte) and HAL_SPI_TransmitReceive sequence match the datasheet's read protocolThe sensor and DIL24 socket are confirmed good — sending the stock firmware's power-on/voltage-set commands over the same UART interface correctly reads WHO_AM_I = 0x6B.I'm currently using PA4/PA5/PA6/PA7 for SPI1 CS/SCK/MISO/MOSI in my firmware, but I sus

Sensor is LSM6DSV16X.When I use this .h file in my MCU driver. There is no wrist tilt, but “Wrist tilt detection with accelerometer and gyroscope” can.I don’t know why?

The top line is S4 then there is a QR Code and then 513. I think it to be one of the iNEMO Inertial Modules but I don’t know how to go about checking which one. I don’t know the dimension of the package  

Very disappointed and frustrated not to find the flat connecting cable.

Hi community, I have been having trouble with finding the correct steval-mki217v1 motionFX 9axis fusion Sensor orientation: NED, ENU, SEU, NWU. the only resouce I had was from IKS01A1 Nucleo eXpansion board. I had tried several combination and had the best combination shown below.Please feel free to correct what I got wrong here.Could someonr confirm this sensor orientaion I use on the right is correct as well as how can I determine the north east west south from this shield?