MEMS (sensors)

Hello!This is what I have done yet:I started by launching STM32CubeMX and creating a new project for my specific STM32 Nucleo board.Once the project was created, I moved to the Pinout & Configuration tab. There, I enabled the I2C1 peripheral. I then set the SDA and SCL pins in accordance with the I2C configuration for my board.Next, I went to the "Software Packs Component Selector" and entered "lis3mdl" into the search bar. This allowed me to locate the lis3mdl component, and I opted for the I2C interface (over SPI) as this is how I plan to communicate with the sensor.Moving to the "Project Manager" tab, I changed the Toolchain / IDE to the one I am using (for example: KEIL or STM32CubeIDE). I also set the firmware package name and the project's location.In the "Advanced Settings" under "Code Generator", I chose "Copy all used library files into the project folder", to ensure all necessary files are available locally.After these configurations, I navigated to the "Middleware Config

Estoy probando el SensorTile.box y he intentando reiteradas veces probar alguna de las aplicaciones que ya están diseñadas, he intentado en IOS y se queda cargando el overwrite y nunca termina, y he probado en Andriod y me da un error de Timeout.¿Alguien sabe lo que me está pasando? He probado conectar y desconectar la bateria, intente con varios telefonos y probe apagando y encendiendo la placa

Hello,I have an issue with my STM32G431 MCU communicating with an LSM6DSV16BX sensor via 4-wire SPI. The problem occurs randomly when the device is stationary and mounted securely. The gyroscope provides incorrect measurements consistently, with gy_raw_data[axis_0] always being 8192, gy_raw_data[axis_1] being something normal, and gy_raw_data[axis_3] equal to 704. Similarly, the accelerometer occasionally gives a 1g acceleration in the Y axis instead of the expected Z axis.I have ruled out communication errors through various tests, including the use of a high-end logic analyzer. The inconsistent data from the LSM6DSV16BX sensor occurs randomly.My question is: How can I determine if the sensor is malfunctioning? Can a self-test sequence be used to identify any errors?

..

The ispu example could be interesting for me. It would be nice to have the source code of the libMotionFT. In general, it would be helpful to publish code without object code.

Hello Community!I am looking for a reference design of a Data acquisition & Data logging application using STM32L562 series MCU. Your assistance in locating relevant reference design shall be highly appreciated! We are further looking for references to help interface a USB-based OTG device to transfer the data logged on the MicroSD card to an OTG-enabled smartphone.Thanks in advance.Regards

Hello everybodyFor a project I need to use the evaluation board STEVAL-STWBXCS1 (evaluation board with differents sensors). I read the fuide "Quick Start Guide STM32Cube function pack for high speed datalogging and ultrasound processing" (www . st . com / resource / en / product _ presentation / fp - sns - datalog2 -quick- start -guide .pdf) and follow the different steps:1-Connect the STEVAL-STWINBX1 to my PC with an STLink/v2 and a USB Type-C (picture)2-Open "STM32CubeProgrammer" and connect3-Dowload the "DATALOG2_Release.bin" on the evaluation board4-Try the example "USB_Datalog_Run.bat" 5-And I get the error message: "STWIN Command Line Interface exampleVersion: 2.0.0Based on : High Speed Datalog DLL v2No devices, exitingPress any key to exit"I don't no why the example didn't work?Thanks you for your help

hello everyone:I encountered an issue with inaccurate readings when using the LIS2HH12TR Please take a look.First of all, my application scenario: installed on a device, FPGA reads the current position through IIC at all times, without any sudden vibration or interruptionMy testing environment: I installed the board with an accelerometer on a three-axis platform. Firstly, it was horizontal, and the X reading was 0.1 °. Then, the three-axis platform rotated thirty degrees around the X axis (with an accuracy of 0.01 °), and the reading angle was 30.1 °. But after being powered on and off again at this position, the reading angle is 31.1 degrees.My question is, every time I power on or off again, the angle read is normal. Why does the angle deviate as the turntable rotates.Exclude a few issues: 1. The turntable rotates very slowly, and the stopped reading also takes a long time to eliminate the impact caused by the acceleration of the turntable;2. I also use mean filtering in the program,

..

Hello,I have bought one of ST sensors on LCSC. It's called LSM6DSDTR and after it arrived i was looking for details about this sensor but it seems to not exist outside of china. Is there any way i could find more information about this product or maybe compatibility with other ST MEMS devices?Thank you in advance.

I am using LIS2DH to detect the tilt angle of a vessel. Sometimes the XYZ reading will freeze, and not update anymore, the only way to reset it is to power on/off the system.

Hi ST team,I use MP34DT05-A microphone in my design and I measure an addition of ~8.5mA to the average consumption current while the microphone is active.The datasheet specifies 650µA consumption in normal mode, and up to 10mA short-circuit current.Sorry for my newbie questions but can you help me understand what exactly is the short-circuit current in a microphone? Is it possible that I am operating the microphone incorrectly?Thanks!

I am surprised to see half of the MEMS sensor datasheet do not mention sensor resonant frequency. Sensor Noise values feel misleading as we have no clue what noise are we going to receive in our shipment. Also, noise levels are not documented well either.Is ST purposely misleading product designers into choosing their MEMS sensors?I am surprised how can one use a 2.4kHz resonant frequency sensor in industrial vibration sensing applications.

From this picture in application note looks like HP_REF_MODE  should not have any effect to the output data when purple path is selected. But in tests we see differences in output data with and without HP_REF_MODE set to 1.

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"

Q&A - webinar "In-sensor monitoring with intelligent MEMS sensors"