MEMS (sensors)

..

Hi, I solve a problem with reading more parameters from the inclinometer Murata SCL3300. The communication works without errors, the init state is OK and when I read more parameters, I get the wrong results. For SPI communication I use HAL_SPI_TransmitReceive(&hspi2, tx_data, rx_data, 1, 100); I attached my code. Does anyone have the same problem?

Hello!I am working on a project of sound source localization and want to lit an individual ws2812 Led in the direction of the sound source.I came across an expansion software package x-cube-memsmic1 which uses Acoustic SL library to estimate the angle of the sound source and send the angle along with some other things to PC via USB. The description says that the audio_application.c and usbd_audio_if.c contains some functions to get the angle from the source and send it.Now I don't know which function does this and how?/** ****************************************************************************** * @file audio_application.c * @author SRA * @version v1.3.0 * @date 17-Sep-2021 * @brief Source localization example. ****************************************************************************** * @attention * * Copyright (c) 2022 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file * in the root directory

Hello!I am working on a project I have 4 mems microphones and I want to get an angle from these 4 microphones, I have 12 neopixel Leds which lit up according to the voice direction on the 4 microphones. I have the Stm32cubeide project for it, but I don't how can get the angle with it.Here is the Code and I will also attach the files...Please guide me!/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body ****************************************************************************** * @attention * * Copyright (c) 2022 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. * ****************************************************************************** */ /* USER CODE END Header */ /* I

Hello Everyone!I am working on a project with 4 mems microphone and I want to get the estimated angle (sound source localization) using Acoustic SL library, but I don't know how to get it?I have Nucleo-F401RE board and I want to locate sound source with 4 mems microphones, please guide me.I have the library and the code but don't know how to use it. I am new to STM32 and mems technology.Why is no one answering me?I have changed the code, it's an acoustic_sl.h file. Just tell me how can I use it to calculate the angle?/** ****************************************************************************** * @file acoustic_sl.h * @author SRA * @brief This file contains Acoustic Sound Source Localization library definitions. ****************************************************************************** * @attention * * Copyright (c) 2022 STMicroelectronics. * All rights reserved. * * This software is licensed under terms that can be found in the LICENSE file in * the root directory of this soft

Hello!I want to interface 4 PDM microphones with STM32F401RE's SPIs in stereo config(like in the pic above), I have a problem of how to get its data using pdm to pcm library. As the data will be alligned in this form(M1bit1, M2bit1, M1bit2, M2bit2..........M1bitn, M2bitn).Can someone give me a piece of code or some kind of explanation on how to get the data?

Hello!I am working on a project with 4 mems microphones and I want to get the angle of sound(sound source localization) using xcubememsicmic1 sound expansion pack but I don't know how can I get it?Anyone who has experience in mems technology and sound source localization, please help me.I have some of the functions here, please tell me how to use it in my main()?uint32_t AcousticSL_Process(int32_t * Estimated_Angle, AcousticSL_Handler_t * pHandler); //taken from AcousticSL.c static float32_t GCC_GetAngle(libSoundSourceLoc_Handler_Internal * SLocInternal, int32_t * out_angles); //taken from libSoundSourceLoc.c

Please help me. I am trying to configure pins for reading the data coming from 2 microphones mount in a X-NUCLEO-CCA02M2. To read the data I am using a NUCLEO-F401RE. I read all the documentation for tthe expansion but nothing is working. In this moment watching the figure below I set using I2S2 the pin PB15 (I2S2_SD) and the pin PB13 (I2S2_CK). I add DMA in circular mode and set the frequency to 96kHz. The communication was set in half duplex in master reception mode. This pins were choose after watching the schematic of CCA02M2. ​Here the schematics of NUCLEO and expansion.​All the information used were taken from a STM pdf here is a screenshot​After all the configuration I used this function the start the reception mode:HAL_I2S_RECEIVE_DMA()​And the relative callback to check which data were read by the microphone. The problem is that the data read are always 0. Another problem is that I don't understand why the MOSI pin is used to read the data in the STM pdf. ​Please can some help

Hello!I need to interface 4 PDM microphones with Nucleo-F401RE(I2S1 and I2S2) in stereo mode.Is it possible to connect 4 PDM microphones with F401RE?Please provide me with a simple circuit diagram and a sample code to how to get data from these mics using pdm to pcm library(if possible)?

To make a successful read via the spi bus of the fifo in rouding mode should return 7 bytes, the tag byte plus 3 words but the device does not return correct data or count as a successful fifo (and update the fifo size). What data is returned is rubbish data. we have previously used rounding successfully with the lmsd6DSL and the lmsdso32 app notes describe exactly the same process for rouding reading of the fifo. Any ideas why it may not be working on the lmsdso32.

to make a successful read via the spi bus of the fifo in rouding mode should return 7 bytes, the 3 tag byte plus 3 words does not return correct data or count as a successful fifo (and update the fifo size). What data is returned is rubbish data. we have previously used rounding successfully with the lmsd6DSL and the lmsdso32 app notes describe exactly the same process for rouding reading of the fifo. Any ideas why it may not be working on the lmsdso32.

The LSM6DS3's datasheet recommends setting BDU=0 for the FIFO's status and data registers, which makes sense in my opinion.The LSM6DS33's datasheet recommends setting BDU=1 for the same register block, however. I can't find any recommendations for sensor products in the same family.So does anyone have experience with FIFO reading from these 2 sensors (they are included in the Arduino Nano 33 IOT and Arduino Nano RP2040, respectively) with regard to Block Data Update?

I am using two PDM microphones(mems transducer) with STM32 to measure the intensity and if the intensity of the left microphone is higher than the right one then an LED should turn on and vice versa.We measure the intensity of analog signals like when the signal is higher than a certain threshold then do something(if(ADC_Val >= 3000)do something...), so is it possible to do such things with digital microphones?Is it possible to measure the intensity of sound level from PCM samples?

..

1) Please tell me how to mount the micro SD on the STEVAL-PROTEUS1.2) Please tell me how to test the above parts in the Windows10 environment as in the Android environment (st ble sensor).

Hello,​I am working on a project with nRF52832 MCU and LSM9DS1TR IMU sensor with I2C connectivity. The code is written on KeilThe driver is according to the datasheet but was observed that the data from IMU received exchanged LSB with MSB. Regarding Datasheet "the value is expressed as a 16-bit word", the 1st 8 bits are the LSB and the 2nd 8bits are the MSB. The driver is built according to the datasheet but was observed that the data from IMU received exchanged LSB with MSB. The Datasheet mentions "the value is expressed as a 16-bit word", the 1st 8 bits are the LSB and the 2nd 8bits are the MSB. e.g. OUT_X_XL (28h - 29h). The data from the register 28h are the LSB and from 29h are the MSB, right??As you can see in the attached files, the address of the registers and the reading from I2C is correct, but my data looks like they are swapped.The correct order of data is MSB and LSB.So first we are reading the MSB byte (29h) and then the LSB byte (2

Hello, I had a STM32F3 Discovery board which version label is "MB1035-F303C-E02" and its Compass mode is LSM303AGR. But I found the code in STSW-STM32118 is use LSM303DLHC, and the demo code not work. Where could I get the latest demo code for STM32F3 Discovery board ?And hers is a working hex file which is newer than https://www.st.com/resource/en/compiled_demos/stm32f3discovery_demo.zip Thank you

Hi support,I'm using the LIS2DUXS12. I make you a short recap about the use of the LIS2DUXS12 with our prototype:We use 3 FSM:FSM_1: To detect the significant motion;FSM_2: To detetct the no motion;FSM_3: To detect the situation where the acceleration is above a threshold;All the FSM use as input the filter differential of the MLC engine;In our application we need to change some parameters of the FSM. For example regarding the FSM_2, we should change the threshold or the timer ( we use the timer in order to verify that that samples of the differential filter is under the threshold for a period specified ).To manage these situations, as I anticipate you in the previous mail, we implement these steps:Stop the FSM (using the register FSM_ENABLE – 1Ah);Re-configure some FSM’s parameters;Restart the FSM (using the register FSM_ENABLE – 1Ah);To re-configure the FSM’s parameters, we update the FSM’s code; as example, I report you the code that we’re using to update the timer od the FSM2:int32

I'm trying to interface with the LSM303AGR using the 3-wire SPI protocol. I'm polling the registers 0x28 - 0x2D in high-accuracy mode, and what I've noticed is that the least-significant nibble of each axis is occasionally 0x1 instead of 0x0 as expected. I understand that the data needs to be right shifted by one nibble, but I would've expected the least significant nibble to always be 0x0 if the data is 12-bit left-justified. Does this last bit have any significance? Example data (Queried with 0xE8):X LSB   X MSB   Y LSB   Y MSB   Z LSB   Z MSB0x00 0xFE 0x20 0x20 0xC1 0x1A0x00 0xEF 0x61 0x2F 0x 21 0x9C0xC1 0xC9 0x41 0xF0 0x61 0x8B

I have a custom setup which contains a microcontroller (non-ST) and a LSM6DSL (actually this is mounted on a STEVAL-MKI178V2) for evaluation purposes. I tried to communicate with the LSM6DSL via SPI (4-wire, tried both 1MHz and 100kHz) using the command 0x8f to READ the WHO_AM_I register (thanks for implementing that!). Yet, I get back a 0x40 and not a 0xa6. I then observed the signals in a logic analyzer (salae Logic8) and also the logic analyzer decodes the transfer as 0x40 so the software works as expected.I then further observed the signals on the scope and the MOSI signals are perfectly fine (no overshoot, nice edges). There are 100Ohm resistance between the SCK, MOSI, MISO lines.BUT: The signal on the MISO is just plain ugly. At first it seems like another device is trying to actively drive the signal so I thought this was related to the microcontroller. But even after disconnecting the MISO trace I can still see this behaviour. The first few bytes look like the clock is driving

I have the Nucleo-L476RG board. How I can program the Sensor Tile.box?Can I program the Sensor Tile.box with Nucleo-L476RG or only I can program it with STLinkV3? STLinkV3 is very expensive...do you know any alternative?Kind regards

Please provide the code for calculating the slope angle using ASM330LHHTR gyroscope. My code is attached here.Note:- Switch case is used to cancel the noise.

* Initialize the LSM6DSL sensor */ LSM6DSL_Init(&MotionSensor); /* Configure the LSM6DSL accelerometer (ODR, scale and interrupt) */ LSM6DSL_ACC_SetOutputDataRate(&MotionSensor, 26.0f); /* 26 Hz */ LSM6DSL_ACC_SetFullScale(&MotionSensor, 4); /* [-4000mg; +4000mg] */ LSM6DSL_ACC_Set_INT1_DRDY(&MotionSensor, ENABLE); /* Enable DRDY */ LSM6DSL_ACC_GetAxesRaw(&MotionSensor, &axes); /* Clear DRDY */this code is used for another gyroscope in the example in the link. I'm trying to use this code for my im330dhcx but these parts are getting errors in CubeIde. How can I solve it? (I am the version I adapted io_ctx . BusType   = ISM330DHCX_I2C_BUS; io_ctx . Address   = ISM330DHCX_I2C_ADD_L; io_ctx . Init    = HAL_I2C2_Init; io_ctx . DeInit   = HAL_I2C_DeInit; io_ctx . ReadReg   = HAL_I2C_ReadReg; io_ctx. WriteReg  = HAL_I2C2_WriteReg; io_ctx . GetTic

..

I am using a STM32-NUCLEO-F401RE and expansion board x-NUCLEO-CCA02M1. I am not using the library provide by STM. I trying to understand which serial communication protocol is better for this type of application and why it is better.Can someone help me?​