MEMS (sensors)

Hi,I am developing an application with the LIS2DW12 accelerometer where it is reconfigured depending on which state the application is in. In one state, the accelerometer should detect when it is stationary/in motion and trigger pulsed interrupts on INT2. In another state, the accelerometer should wake up the system upon movement by triggering a latched interrupt on INT1. The only way I have managed to get this functionality is by, when the accelerometer is being reconfigured for wakeup, setting INT2_ON_INT1 in CTRL7. Without this setting, INT1 does not react to movement at all. I figure there must be a way to get INT1 to fire without having to route INT2 to it, so what am I missing?I have tried following the wakeup example without success.These are all the register c

I am looking for an overview over the different models in the LSM6 family. On the product selection page there are smaller differences in noise and current consumption, but I guess there are larger differences between those models.I found the following sub-families:LSM6DSVLSM6DSRLSM6DSOLSM6DSLLSM6DSTWhat are the main differences between those models? In addition there are different "suffixes" denoting specific features, including the following:"32": Max. Acceleration Range is +/-32g instead of +/-16"X": Machine Learning Core included"P": ?"IS": ?Best regards,Johannes

Dear forum,I'm actually working on LIS3DH module and I'm facing some issues according power consumption.The board on which this module is mounted is the RAK2270 Sticker (schematics in attached files).The module is driven by a STM32WLE5JCI6 and put in stop mode 2 with analog input for SCL and SDA lines.I've also send the command to set the SDO_PU_DISC bit because pull-up is disconnected to SDO/SA0 pin.First wrong behavior is the current consumption in Power-Down mode.According AN3308 p.13 the device has to enter automatically in this mode after power-up and boot procedure (5ms)But in this mode it still reacts and consumes power when there are activity like several shocks next to the module (see power-down_behavior.png).As we can see on the screenshot, I can get correct v

 I am currently working with the LSM6DSLTR IMU sensor, interfacing it with an ESP32-S3-WROOM-1-N8R2 using the I2C protocol. However, I have encountered an issue where one of the accelerometer axes is not providing any data.Issue Observed:The sensor initializes correctly, and two axes provide valid acceleration values.However, one axis does not provide any readings or returns a constant value.The gyroscope readings appear normal.I have verified the I2C connections, sensor power supply, and tested multiple units, but the issue persists.

The sensor IMU is LSM6DSL model, the magnetometer is LIS3MDL model, and the motionfx library is used for attitude calculation, and the heading angle is inaccurate.I checked the value of the geomagnetometer and it is normal, but the heading angle is abnormal: for example, the sensor points to due north, the X axis of the geomagnetometer is 40uT, the Y axis is 0uT, but the heading angle is 300 degrees. After slightly vibrating the sensor to change the values ​​of the accelerometer and the gyroscope, the heading angle stabilizes to 270 degrees. I don’t understand why the magnetic field input is normal but the heading angle output is abnormal?After consulting the information, I learned that after changing the inclination angle, the fusion algorithm will dynamically adjust the projection of the gravity vector through the accelerometer and gyroscope, forcing the geomagnetic data to re-participate in the calculation, covering the wrong horizontal compensation, and correcting th

I’m running MEMS Studio 1.4.2 on Win 10, 64 bit latest version. And trying three different Nucleo boards:Nucleo-C031C6Nucleo-64-STM32L476Nucleo-64-STM32F303MEMS Studio will not recognize any of these three Nucleo boards, with or without the MEMS inertial  and environmental expansion board plugged in - X-Nucleo-IKS01A3. I have also tried plugging a DIL24 adapter into the expansion board - no effect.Any suggestions on what I’m missing?

I am operating a LSM6DSL with a LIS3MDL in sensor hub mode, where the DRDY pin from the LIS3MDL is connected to the INT2 pin of the LSM6DSL. Basically, it works. However, there is a problem during initialization.In order to configure the LIS3MDL, the I2C master interface of the LSM6DSL requires a trigger signal. As long as the LIS3MDL is not in continuous mode, this trigger can only come from the accelerometer. This means that in the MASTER_CONFIG register, START_CONFIG is set to 0. This allows me to switch the LIS3MDL to continuous mode using the appropriate commands but configures the INT2 at the same time as an output.However, when the LIS3MDL starts controlling the DRDY signal, there is a short circuit between the INT2 and DRDY pins because DRDY is also an output. In this case, around 70 mA flows through the pin, which can't be good. Only when START_CONFIG is set to 1 the INT2 pin is switched to an input.I haven’t found any solution to this issue. I would li

Dear Team,We are integrating lsm303AGR accelerometer and magnetometer sensors on NXP's imx8 Android 10 platform.https://github.com/STMicroelectronics/st-mems-android-linux-sensors-hal for HALhttps://github.com/STMicroelectronics/st-mems-android-linux-drivers-iio for linux 5.4 kerneldevice registers as iio:device0 and iio:device1 x,y,z raw value we can see in cat sysfs files.HAL finds 2 IIO devices but furtherthere is lack of implementation of loading bias and save bias functions in legacy because of this the sensors app is not able to  read the sensor data values . apps says there are 2 sensors from stm accel and magn but data is not able to read.it

Hello ST Friends,Here we are using H3LIS331DL in our product, using SPI interface. Below is the schematic. and related code is below.    /* Check device ID */ static uint8_t whoamI, tData; whoamI = 0; h3lis331dl_device_id_get(&dev_ctx_xl, &whoamI); user_printf("\r\nh3lis331dl whoamI: 0x%x\r\n", whoamI); //REG1 tData = 0x27; //0010 0111 nrf_H3LIS331DL_write_reg(H3LIS331DL_CTRL_REG1, &tData, 1); //REG2 tData = 0x00; //0000 0000 nrf_H3LIS331DL_write_reg(H3LIS331DL_CTRL_REG2, &tData,

HiI purchased the TSL2591 product and used it on the STM32 board.I am reading the datasheet and creating the code.I initialized the first writable registers to 0x00.I then looked at the datasheet and gave the control register a value of 0xB0.The configuration uses 0xD3 in the enable register, 0x00 in the control register, and 0x09 in the persist register.I read the PID and ID registers and got a 4 digit number.After that, I read the thresholds 0x14 and 0x15 (the value of 5 came out).The lower and upper bytes of CH0 and CH1 have been read (CH0 is 21, CH1 is 18).The two values did not change with illumination.I have an interrupt in the datasheet and I do not know how to handle it.Then I got a question, Is the INT pin in the product a pin for an external interrupt?I think I do not have much use for the INT in the datasheet.Could you help me?What is ALS? ALS interrupt is also required.

I  am writing my own library in C++ to operate the LSM6DSO and when the sensor is at rest it reads 0.5 G on the z-axis, I've tried the code with 2 ICs, one in an Adafruit breakout board, and another one in an old PCB that had the sensor soldered one and both got the same error, so I believe that the issue might be in the code, but I can't identify where is the problem. Btw, I am using the dev kit NUH7AZIQ$ATZ3A140012 (STM32H7A3ZIT6Q). Also, when i turn the sensor 90 deg the 0.5g moves to the other axis, and regardless of the range scale I choose, the readings adjust themselves so that it still gives the 0.5 G after applying the conversion factor .

I am making a simple inclinometer using IIS2DLPC. The 'Zero-g offset change vs. temperature' of IIS2DLPC is specified as a maximum of ±1mg/℃, but some of the boards I made have reached 2.93mg/℃.Some have relatively good values ​​of 0.3-0.4mg/℃, while others have values ​​of 0.8-1.6mg/℃, so the characteristics vary.2.93mg/℃ is the worst value evaluated.Since most of the units can be measured cleanly, I think that it is not a problem with the circuit board, but some external factor is at work. Please let me know if there are any possible factors.Note that the measurements are taken only on the printed circuit board, without being assembled into a case.

I am trying to interface LSM6DSOWTR with stm32 using I2c interface. This is the schematic i have made for this module While connecting SD0/SA0 is connected to GND, I have tried to run the I2C scanner and found that it its address is 0x6A but in the main code i am unable to get the accelerometer and gyroscope value from its address.In the attachment, i have  attached main.c, and the library created for it.

I wanted to try the STEVAL-IDP005V1 from STEVAL-BFA001V1B,I followed the description given in UM2438and nothing worked,Finally I realized that the cable description is wrong (or may be I've got a bad cable),the ground is on white, not on blue wire

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 me

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

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

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  

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?