MEMS and sensors

HelloI have custom PCB with STM32G491KE connected to an LSM6SV80X IMU directly via SPI. I'm having an issue with not being able to receive any data from the IMU, the the read value is always 0xFF which I've read is usually an issue with the slave/subnode/agent device not responding. Here's how the SPI interface is configured (via CubeMX with X-CUBE-MEMS1)__weak HAL_StatusTypeDef MX_SPI1_Init(SPI_HandleTypeDef* hspi) { HAL_StatusTypeDef ret = HAL_OK; hspi->Instance = SPI1; hspi->Init.Mode = SPI_MODE_MASTER; hspi->Init.Direction = SPI_DIRECTION_2LINES; hspi->Init.DataSize = SPI_DATASIZE_8BIT; hspi->Init.CLKPolarity = SPI_POLARITY_LOW; hspi->Init.CLKPhase = SPI_PHASE_1EDGE; hspi->Init.NSS = SPI_NSS_SOFT; hspi->Init.BaudRatePrescaler = SPI_BAUDRATEPRESCALER_2; hspi->Init.FirstBit = SPI_FIRSTBIT_MSB; hspi->Init.TIMode = SPI_TIMODE_DISABLE; hspi->Init.CRCCalculation = SPI_CRCCALCULATION_DISABLE; hspi->Init.CRCPolynomial = 7; hspi->In

I am trying to use the LIS2DUX12 on the STEVAL- MKI109D and use MEMS studio to merge a MLC config I developed and an example FSM config. I have the merged file, but how do I run/test the config onto the board and see if it works?

The only documentation on the Product Page is the Data Brief - which is extremely brief!This marketing presentation gives overall dimensions (even those aren't in the Data Brief):It tells us that it "can be soldered or plugged on a host board" - but there's no pinout or footprint details. 

There doesn't seem to be any (easy) way to get a full list of all the different "Sensor Box" variants?In particular, is there one which has at least IP65 protection?

Hello All,Apologies in advance for sounding like a noob (that is because I am). I am building a wearable device as a hobby, and I need a 6-axis gyroscope with IMU. Ideally, the device should have more than one IMU, but considering that I have absolutely no idea how to even assemble the device, I am reaching out to this forum to hopefully get an initial idea of what it is I need, so as to hopefully set me off in the right path. The sensors I am thinking in using: Initially I have been looking at ASM330LHHTR and A3G4250DTR, strictly because they are small. The idea I have is to begin testing with a simple setup connected to power, but to eventually make it battery-powered.A bit more information about what I want to measure: eventually I want to set up a strip of these IMUs in a straight line, and have them measure at the same time, and feed it to something like a raspberry pi so as to transmit BT signal. To make a setup where I have IMU --> [something] --

Dear ST,Now I'm testing my VL53L7CX sensor that is on the package P-NUCLEO-53L7A1 in Autonomous Mode with integration time = 2ms, ranging freq. = 4Hz and 4X4 Resolution, the attached screen-shot represents the output current related to my integration time and it's typically 2ms.My question is about the added peaks after the integration time peak, Why could this happen?and, How can I eliminate or reduce it?Knowing that the duration of these peaks illustrated in the other screen-shot attached.Thank you.    

Dear ST,Now as you mentioned in VL53L7CX_ULD the Firmware is uploaded through the I2C protocol to the VL53L7CX every initialization in (Hex form) from the Buffers.h file as also it includes the default configurations for the VL53L7CX While I'm testing it in the Autonomous Mode with parameters integration time = 2ms, ranging freq. = 4Hz and 4X4 Resolution, making also the host board (NUCLEO-F401RE) in sleep mode which means that, there is no communication data on the I2C Bus.I found the current peak as illustrated in the screenshot attached, the first peak represents the integration time which is typically 2ms as configuration.Now I need a detailed explanation about the wave regions illustrated after the first peak and how can I minimize or eliminate them.As also I need to know how to update this firmware and if it has a datasheet or source code.Thank you

Hello,I am evaluating the STMicroelectronics IIS2MDC magnetometer and measuring its supply current using a Joulescope. According to the datasheet, the device should draw approximately ~1.5 µA in idle mode, yet I consistently measure about 450 µA, which is far from the specified behavior.Test setup & observationsSupply: 3.0–3.3 V (also tested across the allowed 1.71–3.6 V range).Measurement instrument: Joulescope (µA resolution).Verified results across multiple PCBs and multiple IC samples.Tested the sensor stand-alone (no MCU connected, only power rails).Same behavior observed on the STMicroelectronics evaluation board.Datasheet behavior (expected)After power-on, the device performs a ~20 ms boot procedure to load trimming parameters and then enters Idle mode automatically.In Idle mode, most internal blocks are switched off to minimize power consumption, while I²C/SPI remain active.Idle mode is selected with MD[1:0] = 10 or 11 in CFG_REG_A.A single-measurement cycle (MD=01) perform

Hi, I am working on a TPMS project and I have migrated from FXTH to NTM88. With the FXTH I was using the MKW01 board for RF communication, on the NTM88 side, to use the same RF board I need the Starter Package for NTM88 and MKW01. The link can be found on NXP website but doesn't work. I have been advised to get in touch with you as the NXP MEMS sensor products have been transitioned to you since February 2026.   I have also search on ST website but with no luck. Would it be possible to advice how can I get hold of the info from the NTM88 and MKW01 package?   Regards,Mihnea

Hello, I am looking to use the LSM6DS032 accelerometer + gyroscope in a project, I intend to interface it with an MCU via I2C. I am wondering if it is possible to program the embedded finite state machines in the accelerometer using only I2C and writing to registers, and if there are any guides or application notes on how this can be done?

Hello everyone,I'm working with the LIS2MDL sensor (steval_mki181v1) , i made a connection between it and the nrf5340 and I configured it over I2C with pull-up resistors enabled.-VDD -- > VDD-VDDio --> VDD-CS --> VDD -PIN I2C  :: SCL to SCL et SDA to SDA-GND t GNDCurrent configuration:I2C communication working (i got the chip id 0x40)Block Data Update (BDU) enabledOutput Data Rate tested at 10 Hz or50 HzOffset cancellation enabledContinuous mode enabledI applied the offset XYZ as :: int16_t mag_offset[3] = {0xF500, /* OFFSET_X_REG */0xF800, /* OFFSET_Y_REG */0xF400, /* OFFSET_Z_REG */};However, I noticed that the values I read from the sensor remain almost always the same and do not update as expected, as shown in the photo below.Could anyone help me understand what might be causing this issue or guide me on how to troubleshoot it?Any help would be greatly appreciated. Thank you! 

Hello!We use the VL53L0X as a time-of-flight sensor on a custom PCB. We used Arduino to configure and read the VL53L0X during development of our embedded system. Now later in development, we find differences between Arduino readings and readings taken from our Linux-based Embedded System (LES). I am investigating what differences exist between our Arduino application used during development and the application running on the LES. While not every sensor is showing shifts in range measurement, the worst case shifts are 6-7mm difference and repeatable.I have collected all I2C communication with the VL53L0X from boot to when we enter the measurement loop for both Arduino and LES hosts. I see some differences and have investigated what I can, but I have a hard time understanding what exactly those differences mean without a register map and descriptions. I understand ST will not provide this information, so I am hoping you can instead provide any insight on my below questions. The

I am trying to capture video streams from two VD66GY cameras connected to the CSI0 and CSI1 ports of a Compute Module 5 IO Board. My OS is : Linux raspberrypi 6.12.75+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1~bookworm (2026-03-11) aarch64 GNU/LinuxBoth seem to be recognized:However, when I try to capture video from both cameras simultaneously, only the CSI0 port works. The CSI1 port returns the following error with this command ( rpicam-hello --camera 1):I also tried a GStreamer command, but it didn't make any difference.I don't have much experience with V4L2 or camera systems in general, so I'm not really sure how to fix this problem. Maybe I missed a step during setup, but that seems unlikely. Even after searching for similar issues, I haven't found anything conclusive.What I have already tested:When using two different cameras — CSI0 = VD66GY and CSI1 = IMX296 — I can capture both video streams successfully. The reverse configuration does not work if VD66GY is connect

Hello,  I am currently using the IIS2MDC in my design with the following configuration: As you can see, I am not using the INT/DRDY pin, so it is left unconnected. However, in idle mode, I am measuring an abnormal current consumption of around 400 µA. I noticed that this extra consumption disappears completely when the INT/DRDY pin is tied to GND via a pull-down resistor.The datasheet states that this pin is configured as a High-Z output by default. I do not understand how this floating setup could cause such a high leakage current. Furthermore, I could not find any specific hardware design recommendations in the datasheet regarding how to handle this pin when unused.I'd really appreciate it if someone could help me understand this behavior. What would be your recommended hardware setup when the INT/DRDY pin isn't used?Thank you in advance for your support.Best regards,

Flint is an accelerometer system in the Smithsonian Museum.  It is a MKI109 and MKI 210 pair.  It has been in place for about three years after a recommendation from your David Reynoldson, who is a really great guy and helps a lot. We have about six to ten such systems that were used and have now been pulled, but old Flint just keeps on working. It has a partially bespoke C# program.  The PI designed and manufactured some small boxes. But to hold the 210 onto the 109 I used a rubber band before it was boxed.  It worked well for three years and then broke. Flint had some minor problems:1. You have to use a USB Managed HUB to turn the device on and off if you reboot the computer.  The HUB is as expensive as the accelerometer pair.  Or you unplug the computer, the device does not reset to home if the computer is switched off - major design flaw in a complex system.2. You have to put a watcher program to monitor the accelerometer program that ca

Split from Sensor TileBox Pro - orientation of X,Y,Z axes ? - this is a new question.Ok, so I will go with what I measured.I have the output from MEMS Studio for temperature.  It says the temperature is 32.18C, which is 0x0c90 There is no such hex value in the entire file and so I am wondering how mems studio got the value file attached

Hello, I am currently working on a project where we want to use the VL53L7CX sensor for motion detection.  Looking through the documentation, I couldn't find any information on what the read and write addresses and values are for communicating with the VL53L7CX, there was just the X-CUBE-TOF1 Time of Flight expansion software for the STM32Cube IDE. I wanted to know if there was information available to communicate with the VL53L7CX via I2C, since I wanted to use the ESP32 for writing the firmware using the Espressif platform.

Hi,We are using a LSM6DSV16X unit to track pitch and roll in our product based on the quaternions reported by the unit's SFLP algorithm (High Accuracy ODR 120Hz)During the operation and in what seem to be arbitrary times, the pitch and roll signals for such unit present some unexpected overshoot or oscillation (see below) before returning to the expected value.The graph above shows the IMU pitch signal (purple) with the reading of an absolute encoder (blue) and both signals should be fairly similar. The roll signal below, although not compared to any other signal, should maintain the same oscilatory behavior that is seen before and after the anomaly (vertical axis in º). At the moment of the anomaly, no special movement happened that could have caused such readings.We have other LSM6DSV16X units in the same usecase and we do not see such behavior as of now.We were doubting whether this could be a calibration problem of the IMU? Is there any calibration procedure you recommend for these

If I use STEVAL-MKI208V1K to collect vibration data of bearings, do I just need to fix this board on the bearing where I want to take data?Thanks

Would it be possible to use a Time-of-flight sensor to measure water level in a pipe?The pipe is vertical with a diameter of 50 or 75 mm and a height  of 800 mm. At bottom there is a 90 degree bend. Sensor should be at top looking down the pipe. I assume that best sensor would be VL53L4CD since it has smallest field of view. Would reflection from pipe walls disturb measurements?   

Hello!I'm working on an Nucleo-H503RB board and trying to communicate with a LSM6DSO over I3C.I am now able to use ENTDAA to assign a dynamic address to the LSM6DSO.Next, I want to test using SETDASA to assign a dynamic address based on the static address (0x6A) of the LSM6DSO. I followed Getting started with I3C - stm32mcu(4.2 Dynamic addressing using SETDASA CCC section ), but encountered the following issue.Issue:The process stops at RSTDAA and does not continue to SETDASA.I have already verified via I2C that the static address is 0x6A.Question:How can I successfully complete the SETDASA procedure? Full Code:/* Includes ------------------------------------------------------------------*/ #include "main.h" /* Private includes ----------------------------------------------------------*/ /* USER CODE BEGIN Includes */ #include <stdio.h> #include "target.h" /* USER CODE END Includes */ /* Private typedef -----------------------------------

Hello,For the ASM330LHH, it's not clear which registers are covered by the BDU setting.  Although the datasheet and application notes list some registers that are covered, they are presented more as examples than an exhaustive list.In my testing, it appears the BDU register doesn't protect the temperature (non-FIFO) registers at all.  With BDU enabled, I would still get ~1 degC temperature spikes when the sensor was operating at the rollover boundary (LSB near 0x00 or near 0xFF), due to the slight time skew between the two registers.  I was able to work around this by using the FIFO.I also need to be able to sample the TIMESTAMP registers (TIMESTAMP1, TIMESTAMP2, TIMESTAMP3, TIMESTAMP4), from outside of the FIFO.  This is important because I need to periodically correlate the ASM330LHH's internal timestamp to an external time/clock; using the FIFO would introduce a large skew and a lot of complexity.Are the timestamp registers protected by the BDU feature?  Can

I am currently working on a project using Steval mkboxpro and I would like to implement BLE Mesh communication between them. I am still learning and I was wondering if you could give me some guidance or recommend resources on how to do this Any help or advice would be greatly appreciated.

Post edited by a ST moderator. Please use English in this community. Please read How to write your question to maximize your chances to find a solution   手册上写着在高分辨率模式下功耗 90 µA，在低功耗模式下功耗低于 1 µA。可是我用示波器串联电阻抓出来的功耗接近1MA，并且未使用MCU配置传感器时功耗就已经接近这个值了。传感器通过开发板的3.3V接口进行供电。电路图如下所示，哪里存在问题呢？ Translation: The manual states that the power consumption is 90 µA in high-resolution mode and less than 1 µA in low-power mode. However, the power consumption I measured with an oscilloscope using a series resistor is close to 1 mA, and this value is already close to the power consumption even without configuring the sensor using the MCU. The sensor is powered through the development board's 3.3V interface. The circuit diagram is shown below. Where is the problem?

We are currently working with the LIS2HH12TR accelerometer on our Smarttrak board, using an STM32U575VIT6Q as the main MCU, and are facing an issue with unstable sensor readings.Communication appears to be functioning correctly, we verified the I2C clock waveform and confirmed that the bus is operating at 100 kHz. The accelerometer responds properly, and we are able to read data successfully. However, the measured values are not stable.For example, the calculated angle values normally stay around 20–30 degrees, but occasionally they suddenly jump to 70–80 degrees without any actual movement. These abrupt spikes are causing instability in our application and affecting overall board operation.An additional challenge is that this behavior appears randomly and in 1 out of 5 devices, making it difficult for us to trace the exact source of the issue.We would appreciate any guidance on possible causes and recommended debugging steps. Specifically, we would like to understand:What could c