MEMS (sensors)

Sometimes, I am reading zeroes from IIS3DWB FIFO. I thought maybe it is because I am using a protoboard (using MKI208) so I connected it directly (with cables) to RPi 4 but it still happens.I guess it is not normal to find these in FIFO, can it be due to SPI communication/electrical issues ?

Hello,For the asm330lhhx device, when does the scale value change and get set?  I am trying to determine if the scale factor needs to be checked only once at power up or continually while reading the raw x, y, and z values for both the gyro and the accelerometer.In Linux Terminal, the scale and raw values show up as the following for the x component of the gyro: in_anglvel_x_scalein_anglvel_x_raw I plan to read the scale once and the raw value continuously.  But if the scale value changes, then I need to read both continuously.  Please confirm how they work as the datasheet was not clear on this.Thank you!

Based on power measurements I infer that using the LSM6DSV embedded SensorHub with a single slave (LPS22DF) costs ~6.4 uA. I can't find the expected current consumption for the LSM6DSV Sensor Hub in the data sheet or application notes. Is this a reasonable value and should I expect this value increase as more slaves (ex the slave current usage) are added?

Where can I find the proper documentation for the functions in X -Cube - MEMS package and clear explanations for the use of functions

Hello,I'm evaluating the LIS2DUX12 accelerometer by using the combination of STEVAL-MKI109V3 and STEVAL-MKI238A. In the datasheet it stablishes that it can reach down to 10 nA during deep power-down:But when I measure the current consumption through Unico-GUI, it says it consumes 2 uA which is similar to the consumption described as "ultralow-power mode" in the datasheet.I would like to know if I'm missing something to modify in order to achieve the datasheet value or is it just that STEVAL-MKI109V3 is not capable to measure such low current.Regards,Pascal.

Hello! I'm evaluating the LIS2DUX12 accelerometer by using the combination of STEVAL-MKI109V3 and STEVAL-MKI238A. In the datasheet it stablishes that in order to achieve certain current consumption is necessary to have the Temperature sensor off:But after going through all the documentation and description of the registers, I can't find any that explicitly state that by modifying certain bit I will be able to turn off the Temperature sensor. I hope you could guide me to identify where is it. The datasheet I'm reading is DS14071 - Rev 2Regards,Pascal.

Hello,We have been using the LIS3DH for some time and recently acquire some LIS3DSH' as well.With both modules there is an internal pull-up for the SDO pin, and with the LIS3DH there is a register to control this pullup:CTRL_REG0I am not able to find a similar register for the LIS3DS, and that register address is referenced as something else.I recall that in earlier versions of the LIS3DH datasheet, this register was not provided, but added in later revisions.Is there some unlisted register for the LIS3DS to disable this internal pull-up? Or some other method?Thankyou.

I have four FSM programs working with the LSM6DSV sensor, all set to AODR/GODR of 30Hz in line with the examples I copied. Tap detect requires significantly higher ODR.  I might also want to run the SFLP at a rate higher than 15 or 30 Hz, so does this mean that I can't run the FSM when running the AODR/GODR at higher rates than 30 Hz or that I simply need to change the FSM program configuration (gulp!) to account for the desired higher rates?

 Hi, the datasheet for the LIS3ML does not mention any dedicated offset registers that can be used to deduct an offset vector from the measurements: However, when I view the LIS3MDL app note, it says they are there: The app note points to 05h through to 0ah. According to the datasheet, these registers are reserved.I tried them out and wrote zero values to 05h ... 0ah . After that, my X axis reading become really messed up! Is the app note wrong? or the datasheet? Please indicate what can be done with the offset, apart from deducting the offset vector in the application in the microcontroller. Thanks, Ewout Boks

LSM6DSV16X chip does not work.I purchased the LSM6DSV16XTR chip, then looked at the datasheet and built a simple circuit.But SPI communication doesn't work.I used the LSM6DSV16X arduino library provided by Sparkfun, but communication was not possible.What's really strange is that I took the chip from the Sparkfun LSM6DSV16X breakout board and attached it to the circuit I designed, and it worked fine.When I first start up the sensor, do I need to initialize it in a specific way?Or maybe the delivery was wrong? The LSM6DSOX chip also has the same pin layout, and I tried soldering it the same way, but SPI communication does not work.Is there something I need to set up first? I'm sad because I'm a beginner.

I am enabling the LSM6DSV FSMs, SFLP, and SensorHub (LPS22DF slave) to send data to the FIFO where I read it upon INT1 pulses. I also have the embedded TILT function working routed to INT1. If I try to route the activity/inactivity detect to INT1, I get no interrupt function at all. If I instead choose INT2 for the activity/inactivity INT routing, or specify no interrupt for this function, everything works. That is, I see the FIFO data until the inactivity condition is met, and then the data stops until I move the device, as it should. However, without an interrupt for the activity/inactivity detect I have no indication when the device changes state, which I use to power off other devices in the system.To repeat, this all works as it should when I have the activity/inactivity detect routed to INT2, but I am using the LPS22DF now as a slave to the LSM6DSV master and the LPS22DF data ready interrupt is on LSM6DSV INT2. This allows the LPS22DF data to get into the LSM6DSV FIFO for FSM pro

Hello Community!I hope you are all doing well. I'm currently working on a project that involves interfacing an LSM6DSOX accelerometer and gyroscope with a LIS3MDL magnetometer. My goal is to set up the LSM6DSOX in Sensor Hub Mode to collect and store data from the LIS3MDL into the LSM6DSOX's FIFO. However, I'm encountering some difficulties in configuring these sensors to work together effectively.Here's an overview of the problem:Hardware Setup: I have connected the LIS3MDL is connected to the LSM6DSOX via Sensor Hub Mode and LIS3MDL's DRDY is connected to the LSM6DSOX's INT2 pin (see AN5272 p.64).Development Environment: I'm using nRF Connect IDE for VSCode for my firmware development.Individual Configurations: I've successfully configured each sensor individually, but I'm struggling to configure the LSM6DSOX in Sensor Hub Mode to collect and store data from the LIS3MDL into its FIFO.  It works for the Accelerometer and the Gyrometer Data, but no data from the LIS3MDL

I am evaluating LIS2HH12. Before starting to collect data, I simply reboot it, set FIFO to stream mode (010), enable FIFO, and enable the sensor by setting ODR=800Hz (110). Then I collect 800 samples (each sample=6 bytes, 2 for each axis) by reading the output registers when FSS>0 and as many times as FSS and checking OVR also (which never happens) and maximum FSS I see is 4 or so (the sensor is connected to an RPi 4, SPI@1MHz). I expect 800 samples to be collected around 1 second, but 800 samples are collected in 0.5 seconds. Why would this happen ? I double checked the FSS values I have read and they sum up to 800 in 0.5 seconds as well.

I connected the MKI231KA board to the Nucleo-L073 board to test the STHS34PF80.And I downloaded the PresenceDetection_STHS34PF80 example in the MEMS1 package.Afterwards, I ran Unicleo-GUI and connected it to the COM port, but the data was not read Normally.Do I need another setup? 

I had an idea to start recording accelerometer data in the FIFO by switching to FIFO mode at one point in the Finite State Machine. This would be done by setting FIFO_MODE bits in the FIFO_CTRL register by using the SETR command. However, in the an5902-lis2duxs12-finite-state-machine document there is a small note that "FIFO_MODE change not supported." when using the SETR command.Is there a way to start recording in the FIFO mode when the FSM reaches a certain point in the program?The reason why I want to do it like this is that when the FIFO is filled the main processor does not need to hurry to read out the FIFO buffer, the values stays there until it is ready to read. 

Hi team, I am using MP23DB01HP mems pdm microphone.I am new to this PDM DATA format.i know about pcm.Llease provide information and pseudo code for pdm  to pcm  and vice-versa.Waiting for ur response...!Thank u,Alex

I use the lis3dh sensor to communicate through SPI, and the sensor settings are as follows：lis3dh_gvWriteReg(LIS3DH_CTRL_REG0,0x90);lis3dh_gvWriteReg(LIS3DH_CTRL_REG1,0x37);lis3dh_gvWriteReg(LIS3DH_CTRL_REG2,0x00);lis3dh_gvWriteReg(LIS3DH_CTRL_REG3,0x40);lis3dh_gvWriteReg(LIS3DH_CTRL_REG4,0x30);lis3dh_gvWriteReg(LIS3DH_CTRL_REG5,0x00);lis3dh_gvWriteReg(LIS3DH_CTRL_REG6,0x00);lis3dh_gvWriteReg(LIS3DH_INT1_THS,30);lis3dh_gvWriteReg(LIS3DH_INT1_DURATION,0);lis3dh_gvWriteReg(LIS3DH_INT1_CFG,0x2a);Question 1：The read acceleration value is less than the set threshold, and an interrupt occurs when it exceeds the threshold。why?Question 2：Why can a slight tap on the sensor detect an acceleration of 12 grams?Question 3：Is the conversion to acceleration values correct？lis3dh_gvReadReg(LIS3DH_OUT_X_L, &val[0]); //28lis3dh_gvReadReg(LIS3DH_OUT_X_H, &val[1]);*p_x = val[0] | (val[1] << 8);*p_x >>= 6;*p_x *= 48;

We are running the LIS2DH12 self test.  After completing the self test we go back and read stat reg 27 it is always returning FF.  We have tried reading it multiple times, but it always returns FF even if no new data is available.

 Digital output data rate (ODR) of LIS3DHH is given (typically) as 1.1kHz in the datasheet. Does it mean ODR is not fixed in one sensor or it is fixed in one particular sensor but there is an inter device variation ? In either case, I am confused how to use the sensor without knowing the exact data rate. For comparison, I looked at LIS2HH12 (and IIS2DH), and it has configurable ODR, and it does not mention this is typical or not, so I assume it means it is fixed. If I need a fixed ODR, am I looking at the wrong sensor (LIS3DHH), are some sensors like this and some sensors like LIS2HH12 have fixed (configurable or not) ODR ?

Hi,the LIS3DH datasheet (DocID17530 Rev 2) states on page 1 under Features:"Embedded 32 levels of 16-bit data output FIFO".However, on page 19, section 3.6 FIFO:"The LIS3DH contains a 10-bit, 32-level FIFO"Which statement is correct?

Hello, I'm using the STEVAL-MKI109V3 board in combination with STEVAL-MKI175V1 and trying to read the X, Y and Z values through the serial port using the commands described in the STEVAL-MKI109V3 documentation and I'm unable to see the Z axe value after running the *debug command:The initialization commands that I'm doing are:*setdb175v1*zoff*w206F*debugAnd then I start getting the data through the terminal as the picture below. When I stop it and I read directly the registers that has the X, Y and Z values, I get the next:As you can appreciate register 2D, which stands for OUT_Z_H, has a value of 0x36h and not 0 as in *debug.The firmware version that I'm using on the STEVAL-MKI109V3 is V3.53.3If I use Unico-GUI with the same register configuration, the tool is able to graph and read from the register the value of Z without any issue. For that reason is my believe that there might be something wrong in the STEVAL-MKI109V3 firmware.Please let me know if you need more informati

Hi Sir/Mam,I am using LIS2DW12 accelerometer for wake-up detection. I can detect the wake-up event by reading theregister,and I set the wake-up recognition routed to INT1 pad,  but I do not see that an INT1 interrupt being raised.This is my configure.CTRL2 08   CTRL6 00  CTRL4 20   WAKE_UP_THS 01   WAKE_UP_DUR 00  CTRL1 50 CTRL7  20Can you please suggest a solution for this?Regardshdy

I'm trying to use ILPS28QSW as a water level sensor. For that I want to convert the pressure into mmH2O. In order to make that conversion as easy as possible I'd like to substract the atmosferic pressure. The datasheet shows that there are two registers "RPDS_L" and "RPDS_H" that are used in the "one point calibration", but the datasheet says "To give better flexibility to the user, the OPC value can be written twice in the same register map.". I don't know if that means that after being written two times it's not possible to write them ever again, if so I'd need another way because there is a chance that I need that calibration to be made multiple times. Maybe I'm misunderstanding what that sentence means, but as I don't know what type of non volatile memory is, I don't really understand how that memory works. I've seen the application note AN5778 but found nothing related to this topic. I've seen that there is a mode called "AUTOZERO" that makes more or less what I want, bu

Hi, I'm Working with H3LIS331DL Accelerometer and STM32F410 for vibration test(Levels:0.04 g^2/Hz,2O Hz to 2000 Hz All 3 Axis, 5 Minutes each axis) at SPI mode.I have readed the raw data from the H3LIS331DL and communicated it by  UART. But after that,I have no idea how to use my raw data for my project requirement,can someone help me with this.About,How the raw Data conversion has been done and about the different output units of Accelerometer(for example-g,mg/digit.m/s^2). Thanks in advance.

I am looking to interface with a sths34pf80 on a nucleo-f401re. I want to set up I2C to R/W to the registers and use the included functions.  BSP_I2C1_Init(); uint8_t ret=0; STHS34PF80_Object_t pObj; STHS34PF80_IO_t pIO; STHS34PF80_Init(&pObj); STHS34PF80_RegisterBusIO(&pObj, &pIO); if(STHS34PF80_ReadID(&pObj, &ret)==0){ //check status }  I have tried this above using the functions in sths34pf80.c/sths34pf80.h. Have not been able to get this to work. Any suggestions?Thanks