MEMS (sensors)

On the BL47E-IOT01A2 there are two mems microphones (MP34DT01) both connected to DFSDM1_DATIN2. I'm trying to extract the data from just one of those boards and convert it to PCM using a DFSDM filter. I've configured DFSDM Channel 2 to connect to PDM/SPI and trigger on the rising edge, and filter 0 I've configured in one-shot mode, connected to DMA, with an oversampling value of 154, and an integral oversampling value of 3. The internal SPI clock on the board is configured to 1/4 the system clock which is 80MHz, thus the SPI clock should be 20MHz. The code to capture the audio is here:void HAL_DFSDM_FilterRegConvCpltCallback(DFSDM_Filter_HandleTypeDef *hdfsdm_filter) { micAudioBuf[micAudioBufIdx] = micRecSample << 8; micAudioBufIdx++; if (micAudioBufIdx >= AUDIO_LEN) { micAudioBufIdx = 0; audioFilterCplt = TRUE; } else { micReset(hdfsdm_filter); } }   void micReset(DFSDM_Filter_HandleTypeDef *hdfsdm_filter) { HAL_DFSDM_FilterRegularStop_DMA(hdfsdm_filter); H

..

Hello, ST engineers. I am working with a general purpose IMU for a tilt sensor application. I am observing some drift on the sensor while the device is off. I have heard that all IMU's can drift a bit, but I was under the impression that it would happen over a longer period of time. Do you have any specifications or testing data regarding the drift of this IMU over time? I am observing an offset drift of up to 3mg on some units just overnight. The readings are taken near 0g, but not exactly due to zero-g offset in device. The sensor is temperature calibrated, and the offset drift is measured near the same room temperature to minimize the effect of temperature related drift.I would also appreciate anyone else who has input regarding if you think this magnitude of drift is reasonable and expected for this sensor?Thank you,Russell

Hello. I am using a LIS2DH board (STEVAL-MKI135V1). I use the STEVAL-MKI109V3 board and the UNICO-GUI app to configure the LIS2DH board. I configure it for Wake-Up system for X axis. So, I change the register for only enable the axis x and it works ok. I get the interrupt in INT1 not only in the UNICO app but also in a cable connected to INT1. But if I just disconnect the LIS2DH of the STEVAL-MKI109V3 and then connect Vdd and Vddio to 3.3V and GND to GND and INT1 to our device.... we do not get any interrupt, always just 0V. It seems that after configure the sensor, if we take out the power, it lose the configuration. Even written the registers with the UNICO app.Anyone know how can we solved this? We do not have a I2C or SPI to connect the sensor, we just need to get the interrupts.Thanks for your help and best regards,Javier

Reset does not work.

Facing some problems with the ST BLE Sensor App. Whenever I try to connect the device to cloud (Azure) it shows connection error ( in both android and IOS Phones).The SensorTile.Box I´m using is STEVAL – STLCR01V1

..

I connected the ASM330LHHX(STM sensor featuring a 3-axis digital accelerometer and a 3-axis digital gyroscope) and INA228(one of the TI sensors measuring the current and voltage) via the I2C interface. What's more, I want to read the data from the ASM330LHHX registers(e.g. Sensor hub registers) which are for external sensors. However, I have noticed that the data stored in the INA228 registers is in the format of 16 bits or more, whereas the registers in the ASM330LHHX for the external sensor only have 8 bits of storage space.So is there any solutions that can help me to slove the problem?Thank you very much!

Hi,At Application Note 5027: "Interfacing PDM digital microphones using STM32 MCUs and MPUs" it described how to connect PDM microphone to SPI I/F of STM32. My question is:at SPI I/F clock is active only when there is SPI transaction, how can I cause the SPI clock to be active constantly?ThanksAaharon

Hi,I'm trying to use LSM6DSO32X to detect a short (<5ms) event isolated by at least 100ms from other events (before and after). It's on the Y axis and with a threshold of 500mg. I'm not having any luck setting up a single TAP event or by using FSM. Any advice would be appreciated.

Hi,I configured the AIS3624DQTR sensor by using standard driver given by ST on GitHub, I am able to set all parameter correctly but when I am trying to read X,Y and Z axis. It is returning same value on all axis and value is not changing by moving sensor.I configured the sensor by using poling example code: whoamI = 0; ais3624dq_device_id_get(&dev_ctx, &whoamI);   if ( whoamI != AIS3624DQ_ID ) while (1); /*manage here device not found */   /* Enable Block Data Update */ ais3624dq_block_data_update_set(&dev_ctx, PROPERTY_ENABLE); /* Set full scale */ ais3624dq_full_scale_set(&dev_ctx, AIS3624DQ_6g); /* Configure filtering chain */ ais3624dq_hp_path_set(&dev_ctx, AIS3624DQ_HP_DISABLE); //ais3624dq_hp_path_set(&dev_ctx, AIS3624DQ_HP_ON_OUT); //ais3624dq_hp_reset_get(&dev_ctx); /* Set Output Data Rate */ ais3624dq_data_rate_set(&dev_ctx, AIS3624DQ_ODR_5Hz); am I missing any step in configuration? please let me know.I checked all above

I am using LIS2DTW12 MEMS,1. I configured this sensor in continuous mode.2. Set the FIFO threshold to 16 samples.3. Selected ODR register value is 100.4 Selected Low power 1 mode.Expected:Periodic interrupt from FIFO must happen every 160ms. But I am getting FIFO interrupt at ~158.4ms.Could you please explain the cause of this time drift and how to fix it?Note: our operating temperature range is -5 to 60 degrees C.

I have an LPS22DF sensor connected via I3C. I can enable I3C in-band-interrupts (IBIs), and see the IBIs occur on data-ready events.I see the IBIs have a 5-byte data payload, but I can't find any definition of the data in this payload. Is this described somewhere? Is the PEC byte present?

Refer to the RoHS pack 22 Final report, RoHS exemptions 7(a) and 7(c)-I are possible to be expired on July 1, 2024. Could you please advise if STMicroelectronics has any plan to remove exemptions for the below parts? LD1117DT33TRSM15T100CASTPS8H100G-TRLPS25HBTRThanks,Yingxin Yao

I'm working with the LIS2DH accelerometer and I'm trying to obtain acceleration data at a rate of 100 Hz. However, I've noticed that the accelerometer interrupts have a frequency of 99 Hz. Also this frequency changes if I use another accelerometer of the same model.I'm curious to know what kind of clock the accelerometer is using and what error is causing this discrepancy in the sampling frequency. What percentage of error in frequency is expected?Any help or insights would be greatly appreciated. Thank you!

..

Hello I want to connect to the STEVAL-MKI208V1K via STEVAL-MKIGIBV2 (conected those both togheter) , with Nucleo-F401RE. I conected pins as it is shown belowF401RE-> MKIGIBV2MOSI (PB3 -> SDAMISO -> SDOSCK -> SCLPWM/D6 -> CS3v3 -> VDDGND- >GNDI want to use SPI 4 wire interface but immediately after connecting nucleo to the PC I lost conection to the board and led LD1 starts blinking red. Do I need to connect some other pins as well with a board? Do I need to use some pull up resistors to the pins?

can anyone provide answer.

Hi,I trying to get the wrist tilt working. I have used the example in AN5040 page 55.I using the simple example setup, nothing else is set. Write 20h to CTRL1_XLWrite 84h to CTRL10_CWrite 01h to DRDY_PULSE_CFGWhen reading the FUNC_SRC2 it always returns 0x84 which should be impossible according to datasheet. The bit WRIST_TILT_IA never goes high no matter how much the unit is tilted.I have already have accelerometer and gyroscope with FIFO and up and running so my drivers and the chip are working. However this I have disabled and are using only the 3 commands above.What am I missing, any ideas?Thanks

helloI tried to reduce the current consumption of LIS2DH12, but there was always a gap. When I measured the GSENSOR data, the current consumption was 100+uA, while it was only 3uA when not measured. So I want to know how the data in this table is obtained?

..

I am using​ LSM6DSRTR, and the device-tree compatible is "st,lsm6dsr".I can see two iio device node under​/sys/bus/iio/devices/iio:device1 /sys/bus/iio/devices/iio:device2But when I try to read in a python loop, it gets really slow.​Anyway better to read it? def getData(self, path): fd = open(path, "r") data = fd.read().strip() fd.close() return data def testData(self): iio_oneshot_path = "/sys/bus/iio/devices/iio:device2/in_accel_x_raw" fd = open(iio_oneshot_path, "r") while self.refresh: self.accX = self.getData('/sys/bus/iio/devices/iio:device2/in_accel_x_raw') self.accY = self.getData('/sys/bus/iio/devices/iio:device2/in_accel_y_raw') self.accZ = self.getData('/sys/bus/iio/devices/iio:device2/in_accel_z_raw') self.gyroX = self.getData('/sys/bus/iio/devices/iio:device1/in_anglvel_x_raw') self.gyroY = self.getData('/sys/bus/iio/devices/iio:device1/in_anglvel_y_raw') self.gyroZ = self.getData('/sys/bus/iio/devices/iio:device1/in_anglvel_z_raw') print(self.accX) tim

Hi all,I am currently working with STEVAL-MKSBOX1V1 to estimate the angle and 3D orientation of a static device. As I am limited to using the capabilities of the lis2dw12 chip only, I am relying on the accelerometer to provide the forces in the XYZ planes in order to determine the tilt.I am interested in using this functionality, but have a few questions:Can the accelerometer measurements be used accurately for tilt estimation and 3D orientation, and do they remain stable over time without significant drift?If yes, what is the purpose of the 6D orientation functionality described in the data sheet?https://www.st.com/resource/en/design_tip/dt0097-setting-up-6d-orientation-detection-with-sts-mems-accelerometers-stmicroelectronics.pdfI would appreciate any insights and recommendations on this topic. Thank you!

Hello,I am working on an IOT project where we use motion sensors. Our prototype works with STM32WB55 + iKS01A3. We would like now to go further and replace iKS01A3 with LSM6DSO and print the PCB to put "between" the STM32WB55 and LSM6DSO. I've read articles on the internet and I think we call it an "adapter card"?However, we are a bit "lost" and we do not know exactly what to do. No tutorial fits to our situation online...Could you help us a little bit? Any advice is welcome :) Thank you,Théo

..