MEMS (sensors)

It appears that the longest spi operation that could be used to access the LSM6DSV (and related parts) would read a single fifo entry (7 bytes) and it is not possible to read all the available fifo entries in a single dma operation.  Am I missing something? Geoffrey

Regarding the behavior of temperature drift of the IIS2ICLX, I would like to ask for your guidance.- When the temperature increases, how does the zero-point temperature drift behave?- Does the amount of zero-point drift change depending on the rate of temperature increase?For example, after heating rapidly to 80°C and then allowing the temperature to stabilize sufficiently, compared with slowly heating to 80°C and allowing the temperature to stabilize sufficiently.

We are considering using IIS2ICLX for product development.I would like to know the following specifications for this product. ① “stability” of “bias” with respect to a fixed calibration value over a period of one year② “stability” of “scale factor” with respect to a fixed calibration value over a period of one year 

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

Dear Community,I am currently following the official MEMS Studio tutorial "Module 5 - MLC Configuration and Visualization" available on YouTube.I am using the following hardware and software setup:MEMS Studio version: 2.4.0 Board: NUCLEO-F401RE with X-NUCLEO-IKS4A1I was able to successfully complete all tutorial steps up to the Automatic Filter & Feature Selection (AFS) stage. However, whenever I click "Run" in the AFS tool, MEMS Studio displays the following error message:"Unexpected error with code 104 occurred during AFS request processing."The issue occurs consistently, even though I am following the tutorial exactly as shown in the video.Additional information:The PC has internet access. I tested both my company network and a mobile hotspot, but the error persists in both cases. No firewall events indicating blocked connections were detected. The board is correctly recognized by MEMS Studio and all previous steps work as expected.Could you please help me identify the cause of

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.  

Hi, I'm seeing a consistent issue where every sensor connected via I²C (as far as I can tell) produces 0 bytes of streamed data over USB:HTS221 (temperature + humidity) LPS22HH (pressure + temperature) STTS751 (temperature) IIS2MDC (magnetometer)At the same time, all SPI-based sensors stream normally:IIS3DWB IIS2DH ISM330DHCX (accelerometer + gyroscope)Both microphones also work correctly.Execution details:Board: STEVAL-STWINKT1BFirmware package: FP-SNS-DATALOG1 v1.5.1 (Utilities/HSDPython_SDK included)Host SDK: HSDPython_SDK (st_hsdatalog 3.0.1, st_dtdl_gui 2.1.0, st_pnpl 2.1.0), Python 3.10, Windows 10Connection: USB (WinUSB), using hsdatalog_cli.pyResult (consistent across multiple runs and after a full USB power-cycle of the board):Name                  Length----                  ------AcquisitionInfo.json     226DeviceConfig.json      28090HTS221_HUM.dat             0HTS221_TEMP.dat            0IIS2DH_ACC.dat         76608IIS2MDC_MAG.dat            0IIS3DWB_ACC.dat      1542000IM

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,      It appears that the LSM6DSO32X has a higher shock/acceleration rating when compared to the automotive rated ASM330 IMU modules. 20’000g rating for the LSM6DSO32X and a 3’000g rating for the ASM330 modules.  Am I reading that right? The automotive modules have a lower shock rating than the consumer module?  thanks   

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 ST team,We are using the LSM6DSV80X SFLP quaternion output for a smart racket project. The quaternion is used by the mobile APP to control the game character posture.During our test, we found that when the racket is powered on in a flat/horizontal position, the SFLP Yaw output can stay close to 0°, which is expected. However, when the racket is powered on or reset in a tilted position, the Yaw value is affected by the current Pitch/Roll posture and cannot remain at 0°.For example, when the racket is powered on in a tilted position, the output is:Roll = -0.58°Pitch = -37.61°Yaw = -9.40°For our racket game application, the expected behavior is:When the game starts or when the user performs posture reset, the current racket facing direction should be defined as the game coordinate system Yaw = 0°. At the same time, Roll and Pitch should still reflect the real physical tilt of the racket.So the requirement is not a full orientation reset. We only need a Yaw-only reset:Yaw should be rese

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!