MEMS (sensors)

Hi, I came across this post:https://community.st.com/t5/mems-sensors/steval-bfa001v1b-wrong-cable-description/m-p/782314#M25282which says that the documentation for the device is wrong and wiring colors for 18V and GND are not correct as per the documentation.I am really confused with what the actual wiring is, kindly help

It seems that its CS is inactive, the LIS will assume that it should be in I2C mode.But if I have multiple devices on the SPI bus, then I want to be able to disable I2C mode altogether.Our board has exactly this setup and it seems that whenever I enable the LIS2DH, it corrupts SPI comms for the other device, presumably due to it entering I2C mode as soon as I de-assert the LIS CS-pin.I'm unable to find a register that controls this. So my question is: How do I use the LIS2DH on a SPI bus with other devices?

..

Hello,I'm looking for any available douments/application notes on how to mount the sensor on a device housing. For example I would like to know what is the suggest o-ring, is it safe to expose the sensor opening to the external world or it needs some protection? What will happen if sand/dust or salt gets in the sensor opening?   

Hi,I am using an LIS2DE12 in I2c mode.  During setup, my code:- wrote 0 to CTRL_REG4 (BDU=0, FS=00, ST=00, and SIM=0)- wrote 0 to CTRL_REG2 (no high-pass filtering)- wrote 0 to CTRL_REG5 (disable FIFO)- wrote 0 to FIFO_CTRL_REG (selects Bypass mode)- wrote 0b00111111 to CTRL_REG1 (sets ODR to 25Hz (40ms), LPen=1, X=1, Y=1, Z=1 which enables all 3 axes).Then, approximately once every 100ms, my code does the following:- It reads STATUS_REG and confirms that the 3 least significant bits are all 1.- With one I2c transaction, it reads 5 bytes starting with register 0x29 (with the 0x80 bit set). This gives me the value from OUT_X_H in the first byte, OUT_Y_H in the third byte, and the value from OUT_Z_H in the fifth byte.Will the values I get from OUT_X_H, OUT_Y_H, and OUT_Z_H always be coherent, i.e. from the same measurement?OR is it possible that the chip could update some of these registers with a new measurement at the same time that my I2c transaction is reading them, such that on

We have a ILPS22QS pressure sensor.We are getting an occasional i2c error.On investigation it seems the ILPS22QS sensor is holding the SCL line high during a pressure reading.I have read through the datasheet and see no functionality that would allow this to happen. We have observed the pressure sensor holding the i2c scl line high.This is shown in the below oscilloscope capture.Yellow = sensor side of i2c SCL series resistor R31Blue  = micro side of i2c SCL series resistor R31 It was suggested it could be manufacturing defect of a bad ground connection, however I do not believe this to be the case as:During a capture where I saw the SCL line being held high the SDA line wasn't:Yellow = micro side of i2c SDA series resistor R34Blue  = micro side of i2c SCL series resistor R31Note the lows start at ~0mV and change to ~416mV about 2/3rd the way through the transactionDoes anyone have insight as to what may be happening?Most of the time the sensor will recover, I saw a

hi! Please provide the zero bias(accelerometer) at 25℃ of ASM330LHHTR, thanks!

Hi Team,  We are working with the LSM6DSOX sensor and integrating it with two different MCUs: nRF5340 and ATSAMD51, using the I2C communication protocol. We have been able to successfully read the device ID, accelerometer data, and gyroscope data. Additionally, we've implemented our own logic for step detection and step counting. Recently, we learned about the Machine Learning Core (MLC) feature, which provides useful capabilities like detecting activity states (idle, walk, run). We obtained the .ucf file for MLC, used the UNICO tool to generate the corresponding .h file, and attempted to integrate it into our application. We followed the documentation and tried monitoring the MLC_STATUS (0x70) register to track activity states. Challenges faced: First Attempt with nRF5340 MCU: Initially, we tested the MLC functionality with the nRF5340 MCU using I2C communication. However, when we read the MLC_STATUS register, we consistently received 0x00, no matter the movement or activity. D

Hi everyone,I am currently trying to get a lsm6dsox to interface with a Nordic nRF52833 board using i2c communication. I am looking to read accelerometer/gyro values.I am able to write to the sensor but I am unable to read from the sensor without receiving a NMAK. I am using the STEVAL-MKI217V1 adapter board to connect to my nRF52833.I have connected the VDD/VDDIO pins to VCC, my SCL/SDA pins to the pins I configured for i2c communication, I have connected CS to VDD, GND pins to GND, and SDO to ground. This is my result from the Logic analyzer This is my source code:Main.c:/* * Copyright (c) 2020 Yestin Sun * * SPDX-License-Identifier: Apache-2.0 */#include <stdio.h>#include <zephyr/kernel.h>#include <zephyr/device.h>#include <zephyr/drivers/sensor.h>static inline float out_ev(struct sensor_value *val){    return (val->val1 + (float)val->val2 / 1000000);}static void fetch_and_display(const struct device *dev){&n

helloI need to interface about 20 small package inertial sensor via SPI and my MCU doesn't have enough GPIO for the chip selects so I'm looking for a module that can be daisy chained via SPI however I didn't find anything in the datasheets that indicate if these devices are compatible or how to do it.can anyone tell me if the LSM6DSOX is compatible or if not if there is a module with about the same capabilities that is compatible??best regards

We're using the LSM6DSV16X iNemo sensor and we're quite confused with the SensorHub feature (described in AN5763).Does this feature only store the external sensor data in the FIFO so that the main mcu doesn't have to read the other sensors directly? If the external sensor is a magnetometer, does the LSM6DSV16X use the data in the SFLP algorithm? Or do we need an ISPU sensor to be able to use the external sensor data gathered by sensor hub?

I have a question about the MEMS audio sensor MP23DB01HP. I think i already undertood that the output is a PDM, but my question is, how can I convert that to obtain a corresponding value in dB? Or some used unit? I have done the acquisitons, but know i don't know what to do with that values... Thank you in advance for your replies

Hello, We would like to integrate LSM6DS3TR sensor.For that to happed we need SEE (Secure Execution Environment) framework drivers for Qualcomm based processors. Could you please supply drivers for that? It is urgent. Thank you.Best regards,Miha

I tried to obtain roll pitch and yaw with the help of motionfx in the x-cube mems1 package by reading data with spi using ASM330LHH, LIS3MDL and LIS2DH12 sensors. I cannot try my code because I do not have the sensors available at the moment. Can you review the code, is there a faulty or missing part? I would appreciate if you can help me. I present the CS pin settings and the project in the attachment      /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS. * *****************************************

Hi,I am using the ism330dhcx and lis2mdl and run the MotionFX  algo.the ism330dhcx data rate is 104Hz and the lis2mdl is set to 100Hz (sensor hub ODR set to 104Hz)should i run MotionFX  algo at 100Hz or 104Hz ?on ST examples, when the ODR is set to 104, the ALGO_FREQ is set to 100 !is this difference can generate wrong values on fusion algo ?i notice that if i run the magneto calibration at 104Hz, the calibration is never reachif i use 100Hz for magneto calibration and 104Hz (or 100) for MotionFX  algo it is workThank you,Sincerely.

HiI am not an IMU expert. My current task is to upgrade an old board which used LSM6DSL(gyro abd accelerometer ) and lsm303agr(Magnetometer) to caliculate orientation of a human head.As far as I can see LSM6DSV would be providing orientation data without gyro. So I dont need a magnetometer?When it comes to orientation data, what is the benefit of having a magnetometer? How does it come LSM6DSV is doing the job without magnetometer?

[EDIT 03/04/25 09:15:35 AM] Well, it appears that, as usual, the real issue was sitting right in front of the keyboard… and could have been solved with a good old ‘Read The Freaking Manual.’ My deepest apologies for this classic case of user error! :grinning_face_with_sweat:Sensor_ID inversion (0x01 and 0x02) I'm struggling with programming the ISM330DHCX on a sony spresense. By following the documentation I write my register with these values:CTRL1_XL: 0b01001000CTRL2_G: 0b01001100FIFO_CTRL1: 0b10010000FIFO_CTRL2: 0b00000000FIFO_CTRL3: 0b01000100FIFO_CTRL4: 0b00000110FIFO_CTRL3C: 0b01000100The I read the FIFO (SPI) with this kind of code :    void ISMSensor::read_FIFO(uint8_t *buffer, uint8_t ism_watermark) { uint16_t transferSize = (ism_watermark * 7) + 1; uint8_t tx_rx_buffer[transferSize]; tx_rx_buffer[0] = ISM330::ISM_REG::REG_FIFO_DATA_OUT_TAG | 0x80; for (uint16_t i = 1; i < transferSize; i++) { tx_rx_buffer[i] = 0x00; } bus-&gt

Would it be possible to connect and send sensor data to a Pi Pico W from the STEVAL-MKBOXPRO? I’m looking for a way to connect them together via Bluetooth but a wired connection would be alright too. I have connected a Pico to the sensortile box via Bluetooth already but I do not know how I can gather sensor data from this. Also is there any official or unofficial documentation on any similar endeavors? I’ve found this link which seems promising but the implementation is not very detailed https://community.st.com/t5/mems-and-sensors/how-to-create-a-custom-gaming-controller-using-sensortile-box/ta-p/597296. 

I want to read acc and gyro data from my ASM330LHH sensor with spi communication, but I can't try the code because I don't have a sensor at the moment, can you take a look at the code, is there anything wrong or missing?(I selected the SPI_CS pin as PA4 and set it as in the screenshot, is it correct?)(Do I need to write BSP_SPI1_Init(); in main function?)(Should I use the ASM330LHH_Init(&imu); function last after scale and enable functions?)  /* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2025 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory of this software component. * If no LICENSE file comes with this software, it is provided AS-IS. * ******

there are two kinds of linux driver for lis2dw12 in LIS2DW12 - 3轴MEMS加速度计，超低功耗，可配置单/双击识别，自由落体，唤醒，纵向/横向，6D/4D方向检测 - 意法半导体STMicroelectronics which is LinuxDriverIIO and LinuxDriverInput,1.what's the difference, which should we use, Do you have an application note about this?2.now we use LinuxDriverInput, we have already add into kernel driver, and IIC is now OK, and we have got device node, but when we configure ./accel/enable, the software is stocked. Could you give some help, thanks! 

Could you tell me the differences between the IIS2DLPC and LIS2DW12?According to the reference URL, are there any differences between these two devices other than product longevity and guaranteed parameter values? I am particularly interested in whether there are any differences at the wafer level.From a business continuity perspective, we would like to evaluate both the IIS2DLPC and LIS2DW12. However, it would be a waste to evaluate the same hardware twice. If it can be confirmed that there are no differences, we would like to evaluate only the LIS2DW12. Reference URL:https://community.st.com/t5/mems-sensors/iis2dlpc-vs-lis2dw12/m-p/179418

Hi all,I'm trying to understand how can I use this ST lib to activated interrupt if accelerometer data ready. I already use this lib but I don't use interrupt mode, right now I'd like to try it.So if I understand well I have to use int32_t lsm6dso32_pin_int1_route_set(const stmdev_ctx_t *ctx, lsm6dso32_pin_int1_route_t *val) I've find it in the datasheet :. Write INT1_CTRL = 01h // Accelerometer data-ready interrupt on INT1 in Startup sequence part 4.1, so if I want to activate the interrupt I have to write 0x01 in INT1_CTRL register, but I'm little lost to how to use typedef struct { lsm6dso32_int1_ctrl_t int1_ctrl; lsm6dso32_md1_cfg_t md1_cfg; lsm6dso32_emb_func_int1_t emb_func_int1; lsm6dso32_fsm_int1_a_t fsm_int1_a; lsm6dso32_fsm_int1_b_t fsm_int1_b; } lsm6dso32_pin_int1_route_t; and typedef struct { #if DRV_BYTE_ORDER == DRV_LITTLE_ENDIAN uint8_t int1_drdy_xl : 1; uint8_t int1_drdy_g : 1; uint8_t int1_boot : 1; uint8_t int1_fifo_th : 1; uint8_t int1_fifo_

Hello, @Andrea VITALI,After using the WESU board (https://community.st.com/t5/mems-sensors/lsm6ds3-lis3mdl-calibration/td-p/762534)we decided to move forward with the sensor tile box PRO. We want to record human activity recognition and pedometer information in the SD card, with a timestamp. We managed to record HAR and pedometer information separetly, on BLE or in a SD card file, but :* If we add the RTC value (for timestamp) to the HAR example, we got the message FLOW_COMPATIBILITY_ERROR* If we enable pedometer, adding gyroscope and accelerometer (60Hz, same as HAR example) in input, add HAR in function, there is no data in the SD card (only header in the csv file), and no updates in Bluetooth (event when SD_Log is updated in log status)Is it possible to get timestamped HAR + pedometer data in a SD card file ?Bonus : if We can also log raw data (ACC, GYR, MAG + BARO) at 240, 100 and 1Hz, that's will great. For now, we can't use this eval board for our need.PS :&nb

Hello!We are developing with the sensor IIS3DWB. I am able to interface it by spi like mentioned in st's github example, and I'm able to use st's platform independend c-drivers. It works fine, I get Acceleration, Temperature, device-ID...In that example the SPI is used in blocking mode and the NSS pin is set by software. Now I want to drive the SPI (with st's SPI-HAL) in non-blocking mode, and I want to drive the NSS-Pin by hardware. Refering the sensor's data sheet, it seems that I need to configure the SPI with CPOL high (CPOL-bit =1), and CPHA to second clock phase (CPHA-bit = 1). But the MCU's reference manual (RM0394, page 1326) says, that the NSS-Hardware-Output-Mode requires clock-pahse-configuration CPHA-Bit==0 (=first clock edge). Is there any way to bring it to work? (If that helps: The sensor will be the only spi device connected to the mcu)Does the sensor accept any other spi setup which is compatible to the MCU when the MCU generates the NSS by hardware? Is there any furth

Hello, we are using the ASM330LHH in our product and are doing some bandwidth testing and trying to model the gyro channel behavior. Our settings are ODR = 6667Hz, LPF1 bandwidth = 470, LPF2 =3333Hz. Looking at the data sheet "Gyroscope filtering chain" (Figure 11 of DocID031239 Rev 4) can you describe the pre-ADC analog anti-aliasing low pass filter corner frequency and order , and the ADC output sample rate? For some of our test conditions we suspect we are seeing unexpected aliasing of energy into the gyro outputs, and so wish to understand better that filter and ADC output rate.Also, do you have any application notes regarding use of the gyro High-pass filter (Table 55, HPM_G)?Thank-you, tjbh