MEMS and sensors

Hello, I'm using (ISM330DHCXTR) accelerometer to calculate the phase difference between two axes to measure the movement of a system. configured ODR at 6.6 KHz and measured the operation frequency of the system which has a 10% error while measuring the FFT and adjusted the ODR on the math lab logic to match the operation frequency of the system but still the phase difference has a major deviation, can someone confirm what is the ODR deviation on this sensor and how to correct the same on the firmware instead of modifying on the paired application.  

I am trying to understand one point in the official VL53L8CX datasheet.In the pin description table, pin C5 (MISO) is described for SPI as:“SPI: Main input secondary output. Push-pull output, driven to IOVDD level.”But in Figure 6 (“Typical application schematic for SPI”), the MISO line seems to have a 47 kΩ pull-down resistor to GND.I attached two screenshots:1. the table entry for C5 / MISO2. the SPI typical schematic with the suspected 47 kΩ pull-down highlightedMy question is: how should this be interpretedcorrectly?Does ST mean that MISO is a push-pull output, but an external weak pull-down is still recommended as a default line state? Or is this schematic being misread, and that 47 kΩ resistor actually belongs to another signal?I would appreciate clarification from anyone who has used VL53L8CX in SPI mode or has already resolved this ambiguity.

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?

Hi     I am looking for example code for the LIS2DW12 using Arduino code . I am using an Expressiff module esp32 C3  Does anyone have some example code ?

Hi Team, Greetings! Mems studio is used and LSM6DSV320X is kept on the sensor tile box pro, We are currently performing drop tests using the SensorTile Box pro platform mounted on a flat board casing. The tests are conducted from the same height under two configurations: Wired mode with an ODR of ~7.6 kHzWireless mode with an ODR limited to ~1 kHzWhile analyzing the accelerometer (high-g) data, we observe a variation in peak acceleration values of approximately ~20 g between different runs, even though the drop conditions are kept identical.We would like to understand the following:Is such a variation (~20 g) in peak acceleration expected under these conditions?Could the difference in ODR (7.6 kHz vs 1 kHz) significantly impact the captured peak values for short-duration impact events?Are there any known limitations in wireless mode (e.g., filtering, bandwidth constraints, or data handling) that could lead to underestimation of peak g values? and Free Fall interrupt

We want to use the Sensor TileBox pro to measure temp pressure and acceleration in structures.   We have been using some of your boards the MKI versions and they will run at a maximum of 1400 time steps per second when configured for about 2000.   I have the tilebox pro exporting on the USB and picking it up with a new C# program.   See below.  It is reading at 18 cycles per second, I need to adjust the freq output, I thought I had a higher rate.  it is really easy to use, but I have the Android Program setting 75 from pressure and temp and 480 for acceleration and getting 18 time steps per second.  Is this your board's limitation on exporting via the USB cable.   Where am I supposed to post this?  

Hello. I have LIS2DUX12 accelerometer and have sucessfully ran machine learning example from STMems (activity_recognition_for_mobile) on our custom hardware.https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lis2dux12_STdC/examples/lis2dux12_mlc_activity_mobile.cFor our application, we need to be able to reliably detect when our device is being transported with a car but its not so straightforward. The few difficulties include:1. The device orientation is not fixed2. The device may shake gently or move very slowly during its normal application. This is perfectly fine and we should somehow not detect that. I have looked at different application_examples :https://github.com/STMicroelectronics/STMems_Machine_Learning_Core/tree/master/application_examplesbut not sure which would work best for us. If we cant find any suitable application example, we can try and train our own model with our own data.I would appreciate if someone could share their insights and pr

Hello,We have the ISM330DHCX designed into a new product but I am having trouble getting reliable readings using the I2C interface. I am able to read the WHOAMI register and get 0x6B but OUT_TEMP_L (20h), OUT_TEMP_H (21h) always return zero.I have the interface instrumented and I can see that the signalling is correct, with repeated start and everything, but only zeros.Does anyone have a suggestion of how this is happening?  Do I need to do something special to enable temperature readings?Thanks

 Hi everyone,I am working with the  LSM6DSM and an external LIS3MDL magnetometer and have the FIFO ODR set to 208 Hz, with no decimation configured.I am trying to understand exactly how the FIFO handles data in the following four scenarios. Could someone clarify what happens to the samples in the FIFO for each case?The Accelerometer or Gyroscope ODR is set higher than 208 Hz.The Accelerometer or Gyroscope ODR is set lower than 208 Hz.The external Magnetometer ODR is set higher than 208 Hz.The external Magnetometer ODR is set lower than 208 Hz.Any clear explanations on how the samples are handled (e.g., are they dropped, duplicated?) in these specific situations would be greatly appreciated.Thanks!

While using the iis3dw sensor, I discovered that when I employed an interrupt-based polling method to read data—where, ideally, the sensor captures data, triggers an interrupt, and then the data is read—the data acquisition frequency should be around 26 kHz (based on SPI transmission and code execution time). However, I found that reading the data was taking up some of that time; when I disabled this process, the issue disappeared. My SPI rate is 18 Mbps. Subsequent testing with FIFO reading also exhibited this behavior. Specifically, when I disabled the function `iis3dwb_acceleration_raw_get(&IIS3DWB_ctx, accel)` during the read process, reading 10,240 data points took approximately 391 ms (about 26k). Without disabling it, reading the same 10,240 data points took 523 ms (about 19k). Below is my read code without using FIFO. The attachment contains the official ST driver. `uint8_t iis3dwb_init_drdy_mode(void)` is the initialization function without using FIFO, int16_t iis3dwb_read

Split from Any accelerometer supporting >400g with integrated free-fall detection ? - this is a separate questionHi Team,Could you please suggest a suitable wireless development board that supports LSM6DSV320X, or any latest high g accelerometer sensors, apart from Sensor Tile Box Pro?

I am working with the LSM6DSV320X for vibration analysis and potential crash detection applications, and I have a few questions regarding its capabilities and system integration:Is the LSM6DSV320X considered a high-end processing device? Does it support on-board processing such as FFT, or is an external MCU required for such computations?What are the maximum bandwidth and measurement ranges (g for accelerometer and dps for gyroscope) available for the 6-axis IMU? How suitable are these for high-frequency vibration or crash event detection?How fast is the communication interface (I2C/SPI)? Can it reliably support high data rate streaming for real-time applications?Is it possible to integrate this sensor directly with a CAN bus, or is an external microcontroller required for CAN communication?Are there any development boards available that include this sensor for quick evaluation and prototyping?I would appreciate guidance or references to relevant documentation.

Dear ST, For the ToF sensors supported VL53L8CH or VL53L7CH is it possible to make a hardware that depends on 4 x VL53L8CH or 4 x VL53L7CH integrated to increase the number of zones from 8 X 8 to 16 X 16 ?and if it is possible what would be the limitations in both HW and SW for this system?also provide me a reference for this implementation if exists.Thank you.

I am currently testing the VL53L7CX sensor(w/ vl53l5cx_api) with the STM32F7 MCU. The default resolution of 4x4, when running, would consistently return distances around 2.5 -3.0 meters with a target status code of 5 for multiple runs. I then tested 8x8 resolution and it began to return distances no higher than 1 meter with numerous error codes within the 64 zones target status (0,13,255 if I recall). Though, when I would hold my hand over the device it would return the ranges under a meter(this makes sense) with a target status 5 for all zones even when repeated. Please note that the room conditions of the 4x4 measurements and the 8x8 measurements were the same.  Is there any reason for the readings to be present incorrectly when 8x8 resolution is used but 4x4 seems to work as expected?   

In LSM6DSV16X DS13510-Rev 4 Page 8, Table lists sensor fusion performance: Question 1: are these values guaranteed over temperature and all angles, or at a particular angle and at room temperature?Question 2: without a magnetometer or GNSS heading input, what is meant by heading/yaw accuracy? Is it a drift value (over 5 minutes) from whatever value it is given at the beginning of 5 minutes?Thank you.

Many years ago, at ANU in third year physics, the professor provided an object and said explain and check it as a project.  Let us assume that I have a SENSOR TILE.BOX pro and I follow my training and check the output of the MEMS Studio. The first step was to provide the CLI_Example amended so that it provided the files in the correct location for our downstream software.  I would not use your MEMs software, it is just to kludgy.  But I wanted to confirm my program and understand your data.The next step is to use MEMS Studio to get the output file processed log. The third step is to write a simple C# program to take the .dat files apart and complete necessary analysis and upload the needed output to the MYSQL cloud storage. {"c_type": 2,"data_ext": ".dat","data_fmt": "HSD_2.0.0","description": "","end_time": "2026-04-02T17:48:41.013Z","interface": 1,"name": "SensorTile.Box_PRO_acquisition","schema_version": "2.0.0","start_time": "2026-04-02T17:48:30.000Z","tags

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

Hi, ST Community, I am working with an lis2mdl on a STEVAL-MKI217V1 board and I used lis2mdl_hard_iron.c this Application and I was able to get data_raw_magnetic and magnetic_mG I want API to get the Angle of Rotation of the sensor  

Hello,I am testing LSM6DSO and LSM6DSO32 on Zephyr.As these 2 sensors are pin compatible, I prepared 2 identical boards, one is mounted with LSM6DSO and LSM6DSO32 on another. (The sensors are connected to MCU through SPI interface.)My purpose is that I can use one single Zephyr image to drive the IMU sensor no matter which one of these 2 sensors is mounted on board.It looks promising because one lsm6dso.c driver is provided in Zephyr, and this driver defined DT_DRV_COMPAT for LSM6DSO32. And Zephyr's official document also confirmed this compatible as well.So I use the default sample/sensor/lsm6dso app for a simple testing.The sample can be built and run for the board with LSM6DSO. The output from the uart console looks making sense.But I encountered some problems when configure the dts file for the board with LSM6DSO32.At first I config the dts file like this:lsm6dso: lsm6dso@0 { compatible = "st,lsm6dso32", "st,lsm6dso"; ... }This can not compile, the c

Hi, I am looking for the burn-in specifications for a MEMS accelerometer device/sensor. Could you please help me with this information? Thank you

Hi Team, do ST offer a high-g accelerometer, similar to the LSM6DSV320X on the STEVAL-MKI251A, that supports over 400g with integrated free-fall detection?

I am using the STEVAL-MKI238A kit with the LIS2DUX12 chip. This is connected to an NRF52840DK and interfaced using Zephyr's lis2dux12 driver. The eval kit is connected to the SPI3 device using its default settings. I am running an SPI clock of 1Mhz and the VDD and VDIO pins are supplied 1.85V+GND from a shared power supply with the nrf52840dk. The Zephyr lis2dux12 driver is hard coded to use SPI mode 3, so CPOL+CPHA.The lis2dux12 driver fails its INIT sequence by mismatch of the WHO_AM_I readback. The device seemingly returns 0x0C.I have connected a logic analyzer to the pins of the eval kit shows this sequence:- 0x01 is written to register 0x3E to wake the device up from sleep- Once the CS signal is disabled, 50ms passes before the next CS enable to allow the sensor to wake up- A read request is made to register 0x8F (bit 7 read + 0x0F)- The clock idles for 48.5µs before pulsing for the response- The sensor effectively pulses 0000.1100b- However the sensor seems to attempt to set

I notice there is now a github repo with FSM examples; very useful!However, in comparing what I have been successfully using, for example, for shake detection on the LSM6DSV (or LSM6DSV80X) where 30 lines are written to page 0x7A: _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0xC0 | 0x20 | 0x02); // write to CONFIG_A (three thresholds, two masks, two short timers) _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to CONFIG_B _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x1E); // write to SIZE (30 byte program) _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to SETTINGS _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to RESET POINTER _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to PROGRAM POINTER _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x66); // write to THRESH1 LSB _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x3E); // w

Hi everyone,I am a beginner working with the VL53L1X sensor on an STM32F103C8T6 using the STSW-IMG009 (Ultra Lite Driver). I am trying to implement a calibration routine, but I am encountering two specific compilation errors inside my VL53L1X_calibration.c file:The errors:1. 'VL53L1X_ERROR_TIMEOUT' undeclared (first use in this function); did you mean 'HAL_DMA_ERROR_TIMEOUT'?2. implicit declaration of function 'VL53L1_WaitMs' [-Wimplicit-function-declaration]I have checked the driver files but cannot find their declarations.I have not changed any of the driver files. Am I missing something? Any help is appreciated. Thank you!

I'm stuck at trying to make motion_fx call MotionFX_LoadMagCalFromNVM and MotionFX_SaveMagCalInNVM - a problem which is mentioned already in link1 and link2 but to which actually there is no working solution (the rest of the motion_fx seems to work without any issue). I implemented the functions as below, but already when compiling, they get optimised out and end up being discarded - hence the motion_fx library never calls them, in contrary to what UM2220 suggests. My code does actively call MotionFX_MagCal_init(MFX_MAGCAL_SAMPLE_PERIOD_MS, 1); and MotionFX_MagCal_init(MFX_MAGCAL_SAMPLE_PERIOD_MS, 0); which as per UM2220 should trigger the call of the NVM functions. Here is my implementation:volatile int deb_load_nvm_called = 0; volatile int deb_save_nvm_called = 0; char MotionFX_LoadMagCalFromNVM(unsigned short int dataSize, unsigned int *data) { Message_Logger("hi from save %i", deb_load_nvm_called); deb_load_nvm_called++; nvm_status_t s = NVM