MEMS (sensors)

Hello ST Community,I am using LIS2DH12 sensor for the following purpose: Generate an interrupt when the acceleration exceeds 1.7 g in any axes and read the x, y and z-axis values after the interrupt is generated. Generate an interrupt when the acceleration goes below 350 mg in all axes and read the x,y and z-axis values after the interrupt is generated.Wakeup when the threshold is above 256 mg.For this purpose, I have set the registers as follows:CTRL_REG1 - 0x37CTRL_REG3 - 0x40CTRL_REG4 - 0x88CTRL_REG5 - 0x0ACTRL_REG6 - 0x28INT1_THS - 0x0BINT1_DUR - 0x0BINT1_CFG - 0x95INT2_THS - 0x38INT2_DUR - 0x01INT2_CFG - 0x2AACT_THS - 0x05ACT_DUR - 0x20When an interrupt occurs (INT1 or INT2), in the interrupt handler, I read OUT_X, OUT_Y, OUT_Z registers to get the acceleration value. If INT1 occurs, I wa

Please Provide the detailed procedure as I am a beginner to STM32 and do provide the source code and pinout

I am checking the difference between LSM6DSMUSTR and LSM6DSMTR. Distributer Mouser has both of them. But the data sheets are the same. Thanks,

Hello !I'm currently confronted with a misunderstanding..First, What is a "Know zone" and an "Unknown zone" ? My idea about it is :"Know zone" : somewhere (direction or orientation) you know you are going to."Unknown zone" : Unknown direction or orientation Is that correct ?Second, So if i'm in "01" the interrupt signal remains for duration ODR. In my case i'm at 25HZ so it will be remains only 40ms ? Even if the INT1 is latched ?I also saw in a document that the INT1_CFG is not taken into account when configuring the AOI-6D. That's why 6D, all direction are taken.(I'm using it in 2G scale, ODR 25HZ, all axis, no HP filter

Hi,so far we want to compare several MEMS accelerometers and their specifications. From ST, two sensors are on our list, the IIS3DWB and the IIS2DH.For the IIS3DWB, the data sheet offers a frequency response curve at page 19 and regarding aliasing the following information (see IIS3-Block-Diagram-Frequency-Response.PNG):"The IIS3DWB has been specifically designed to provide a wide bandwidth with very flat frequency response in thepass band and a very high attenuation in the stop band so to virtually eliminate any frequency aliasing."1) So for the IIS3DWB their is no "true" analog low pass filter before the ADC in order to prevent aliasing, its simply done by the frequency response of the senor itself right? Because the LPF1 is a digital low pass filter, in theory not capable of preventing aliasing effects.... Or am i on a wrong direction :) ?2) Does the frequency response for the IIS2DH

Hello STM-Community,I'm fairly new to STM programming and I use an STM32 microcontroller with STM32CubeMX encountered a weird issue with my functions.I've got an IRQ, which collects data every interrupt. Similair like this:void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin)   {   if (GPIO_Pin == INT_EXT_Pin)   {   ACCMETER_IRQ(accdata);   data_counter++;   }   }In the main function I want to see if enough data have been collected for an FFT.Similair like this in my while loop:while(1)   {   if (data_counter > 4096)   {   FFT_ACCMETER(accdata);   data_counter = 0;   }   }   while performing the FFT, the IRQ still collects data for a buffer function, therefore no data should be lost in between each FFT.Here's the issue, after gathering enough data, data_couner is se

I was wondering If anyone could provide me with detail step as I am new to stm sensor

We purchased late in 2020 an STEVAL-STWINKT1.Just learnt that this board has been deprecated and the  STEVAL-STWIN KT1B is instead the recommended reference designCould you please let us know:if we have to stop using the STEVAL-STWINKT1if get it replaced by the STEVAL-STWINKT1BBRDS

Hi, I want to drive an ISM330DHCX by an FPGA using SPI. Due to the fast operation and the exact timing I can realise this way, a few questions occured.Data sheet fig. 6 details the SPI timing. There is no value given for minimum time for CS=HIGH, i.e. the minimum time between two consecutive bus cycles. Am I right with e.g. 50 ns minimum CS=HIGH?Which time is necessary to internally settle written register values, i.e. which time I have to wait before i) I can read written values back and ii) written values are internally valid (e.g. ODR or full-scale selection)?A more general question: What is the meaning of CTRL9_XL bit 1 "DEVICE_CONF"? In the data sheet is written "It is recommended to always set this bit to 1 during device configuration.", but in STM's demo applications (

I'm trying to get the SAI working in receive mode with a MEMS microphone, but when i try to receive data it only returns 0? Here is the SAI setup:saiHandle.Instance = SAI1_Block_A; // audio block A.   saiHandle.Init.Protocol = SAI_FREE_PROTOCOL; saiHandle.Init.FirstBit = SAI_FIRSTBIT_MSB; saiHandle.Init.AudioFrequency = SAI_AUDIO_FREQUENCY_44K; saiHandle.Init.AudioMode = SAI_MODEMASTER_RX; // block a must provide clock signals and receive from the data line. saiHandle.Init.Synchro = SAI_ASYNCHRONOUS; // we only want to use this one audio block. saiHandle.Init.SynchroExt = SAI_SYNCEXT_DISABLE; // disable sychronizing the 2 audio blocks. saiHandle.Init.OutputDrive = SAI_OUTPUTDRIVE_DISABLE; // assume to power the data? saiHandle.Init.NoDivider = SAI_MASTERDIVIDER_ENABLE; // any frame length allowed. saiHandle.Init.FIFOThreshold = SAI_FIFOTHRESHOLD_EMPTY; // used for interrupts. saiHandle.Init.MonoStereoMode = SAI_STEREOMODE; // mono mod

Hi,I am currently working on DMA combined with I2C bus. I want to read acceleration data from IKS01A3 with HAL function HAL_I2C_Mem_Read_DMA(). I want to read at 6 different memory registers. How can I use that function to get it work properly? Can I queue read calls one after another? Is there any option to differ read i2c callbacks between reads (just to rise a flag that memory read from particular region was successful)?Thanks in advance.Lukasz

Hi,I have a LSM303D, compass, and acceleration sensor. I can communicate with the sensor, and I get the magnetometer data on all of the axes, unlike the accelerometer. Accelerometer Z-axis data comes "-32760" all the time. I work on stm32f103c8t6Here is my sensor initialization code:AESK_StatusTypeDef AESK_LSM303_Init(){ //This Register must be set to ‘0’ for the correct operation of the device. if(AESK_LSM303_Write_Reg(CTRL0, 0x00) != AESK_OK) { return AESK_COM_ERROR; }  // Accelerometer  // 0x57 = 0b01010111  // AODR = 0101 (50 Hz ODR); AZEN = AYEN = AXEN = 1 (all axes enabled) if(AESK_LSM303_Write_Reg(CTRL1, 0x57) != AESK_OK) { return AESK_COM_ERROR; }  // 0x57 = 0b01010111  // AFS = 0 (+/- 2 g full scale) if(AESK_LSM303_Write_Reg(CTRL2, 0x00) != AESK_OK) {

Hello ST Community,I have some hardware samples with LIS2DH12 accelerometer. For all the samples except one, the value of WHO_AM_I register is read as 0x33 (which is expected). However, for one of the samples, it is read as 0xFF. What could be the possible reason for this? Note that this behavior was observed after being in use for a few months. Could physical damage or such incidents cause this? Regards,Anusha

Hello,I have an issue with my LIS2DE12, when i'm starting up my board i'm doing the configuration of the device and then i need to put the boad from 1,8V to 3,3V to communicate with an other component. BUT when I come back to 1,8V the LIS2DE12 have take back his default configuration... (REG0 = 16 ; REG1 = 7 ; OTHER = 0) Do you have ever seen this ?I have been looking with an oscilloscope the power supply and it never fall under 1,8V and never go more than 3,3v. (1,71v to 3,6v in the doc so looks good)Thanks,Regards,Goulwen LE BOZEC.

Hi,We've been using LIS3DSH for a few years now and are now searching for alternative sensor because of availability problems.In LIS3DSH there are offset compensation registers OFF_X(Y,Z) for fixing the read axle values with correction values stored in manufacturing phase (TyOff).However I can't see any such registers in LIS3DH documentation, although there are same chapters in document (3.1.2 Zero-g level and 3.5 Factory calibration).I haven't yet been able to test the sensor, but just for preparing to the sensor change, are the offsets detected on manufacturing phase of LIS3H taken care somehow automagically, or am I missing something here?Best regards,Jukka

hello,​Can I use MP34DT05-A PDM digital microphone to get sound DB data on STM32G431RBT6 ？

I have developed a firmware in sensortile.box and I'm using accelerometer data(lsm6dsox imu sensor) for that specific application. The problem I encountered is that, scaling of the accelerometer automatically changed, because after the long time the accelerometer values will go out of the scaling boundary. Can anyone suggest a way to trouble shoot this issue. or is there any flags or register that show the errors encountered in the accelerometer in running time.thank you.

The H3LIS100DL has no fifo, and the ODR can be set to 400Hz. This would make it update the axes data each 2.5ms. I have programmed it to interrupt a mcu when a threshold is reached. This wakes the micro controller from deep sleep. Unfortunately it takes the Mcu about 8ms before it has woken up and is ready to read back the samples (X,Y,Z) that caused the interrupt.Is there a way to make the accelerometer to keep the data and not overwrite it? I read something about BDU (Block Data Update for LIS3DH); something like that the output data would not be overwritten until all axes had been read out. Is there anything similar that would work for H3LIS100DL? Any other trick?I know there will be lost samples, but I'm mainly interested in reading back the sample that caused the interrupt.

Dear a ST engineer,​I had purchased VL53L1-SATEL and evaluated the function with NUCLEO-F401RE and "VL53L1 Gui". I connected VL53L1-SATEL board to NUCLEO-F401RE board directly through some wires.However the GUI didn't recognize the connection of VL53L1". Then I checked the circuit of the breakout board, I found that the pull-up registers for XSHUNT pin and GPIO1 pin were not exist. But the datasheet of VL53L1 showed the note. I have a question;is it necessary for me to add some pull up registers to VL53L1 Mini PCB?Thanks in advance.

Figure 2 of the LIS2MDL datasheet shows the following picture of the magnetometer axes orientation. However, it's completely unclear if they are labeling the positive direction of the axes. If they did label the positive directions with the X/Y/Z label, it would have a Left-handed orientation (against all convention).Are the positive axis directions indicated by the axis labels? Is this a left-handed coordinate frame?

Hi, stThe MCU platform I use is nrf52840. The sensor uses steval-mki207v1. The hardware connection method is mode 1. The SPI mode of MCU is mode0, the frequency is 8MHz, and the bit order is MSB first. On this premise, no matter how many times I read the chip ID, the value is 0.What is the problem?

High Precision Inclinometer for Industrial Applications: Learn how to create innovative solutions with the latest MEMS-based high precision tilt sensor for industrial applicationsWatch the 1-hour, on-demand webinar to discover the newest addition to our expanding line of industrial-grade sensors with 10-year longevity commitment—the IIS2ICLX high precision inclinometer.Register

I am currently interfacing the LPS22HH component and have been encountering some very strange pressure data.Currently I am interfacing this in I2C mode and reading the pressure sensor values from PRESS_OUT_XL (28h), PRESS_OUT_L (29h) and PRESS_OUT_H (2Ah). At the start I usually set CTRL_REG2 (11h) to the value 0x04 to reset all the buffers.Strange due to two reason:1) My BMP280 barometer and Android mobile phone both show pressure values(1002) that within 1-2 hpa of each other while the LPS22HH is different by almost 15Hpa. The value of 1002 is my expected value.2) I am in an apartment, with open windows. The pressure value of 1018 does not make sense at all because the sea level pressure based on the met station is 1009. This seems to indicate that I am actually below sea level which is not true because I am in an apartment.3) The value of the pressure is fluctuating by a significant amount.Does anyone or

I need several LSM9DS1 sensors one the same SPI line. However, I noticed that when CS is high, SDO (aka MISO) is not tri-stated but pulled down to GND.I thought this was due to the default double-interface (SPI/I2C), so I have enabled the I2C_DISABLE bit in REG9, but nothing has changed.Thus, I need a tri-state buffer on MISO lines of each sensor.But the answer here seems different: https://community.st.com/s/question/0D50X00009XkXIPSA3/lsm9ds1-on-single-spi-bus-with-other-devices?t=1611822778772Anyone can shed some light on this?Thanks!

I want to ensure that the user fits our portable battery powered radar onto the back of a vehicle in the correct orientation. I want to monitor this using an accelerometer, I am considering using the LIS2DH12 but I'm not sure if this is suitable and therefore need help in selecting an accelerometer. Also I did look at using the ADXL345 from Analog devices but don't understand why there is a huge price difference when compared to the LIS2DH12.