MEMS (sensors)

Hello, I cannot make the LIS2DU12 working in the Sensor.Tile module. I followed the instruction in the AN5648 but I get random values for X, Y, Z. At first, I'm trying to get the readings in normal continuous mode without FIFO. I can connect the device, WHO_AM_I returns the correct 69 value, I read X, y, & Z registers when the DRDY bit is set but these values are not correct.... In attach my configureLIS2DU12 and getLIS2DU12 functions and the X, Y, & Z values I get via serial Thanks, J.

Hey, I wanna use MKI221V on MKI109V2, the sensor datasheet says that it's - "Compatible with STEVAL-MKI109V2 by changing resistor settings". Couldn't find any references to what resistor settings are needed and how to implement them, any help would be appreciated :)  

Hi,I am working on project using ZephyrOS and I am trying to link in and use some of your motion libraries.I have successfully linked but the call to MotionAC_GetLibVersion() is returning zero. Looking at assember in my debugger a variable is being tested at the start of that routine "licenses_ok". This leads to the call exiting.What must I do to use the library? Are any license files necessary; I thought the libs were free to be used if you are using ST chipsets?Regards,Owain

Hi,I want to design a capacitive touch application with a brass metal plate. So, i need a sensor that is suitable with brass metal. Is there any advised product for me?

Hi All,I am using a P-NUCLEO-WB55 development board in BVLINKWB1_V2.0.0 project. Project ST Link Here: https://www.st.com/en/embedded-software/fp-aud-bvlinkwb1.htmlIn this project, I would like to change the SAI1_SD_PIN from PA10 to PB15 in P-NUCLEO-WB55 board. But I faced a weird situation which is excessive noise. I will appreciate if you can help me to solve the problem. During this journey, I will mention about my progress step by step to be clear. I'm just a beginner with PDM microphones. As much as I learned, I had some trials in line with my needs. In this process, I'm sorry if I have made some mistakes that annoy you or that should not be done.In this project, if I directly build and upload the .elf file the firmware is working very well. You can listen the recorded voice (voice name "PA10_Test_Record.wav") that was recorded by "ST BLE Sensor Classic" IOS app through P-NUCLEO-WB55.As you can see the screenshot below: (The voice can be seen clearly)Until here everythin

Hello I'm acquiring data from an ISM330DLC per I2C, and I'm having several issues:-I probably have the config wrong several levels. For instance I have the Reg CTRL1_XL configured to 0x75, CTRL2_XL to 0x7C, CTRL8_XL to C8, CTRL7_G to 40, CTRL6_C to 0x00  and my and when the IMU is still I get values from 10.5 to 9.0, everything except 9.81 m/s^2. I don't know whether I have to calibrate the sensor and how to do that or if I have a filter configured wrong. I just get bad values. And I am using the right value to convert the raw data FS 16 g , 0.488 and FS 2000 dps , 70. My driver file will be attached.

Or in other words if we are triggering SOFT_RESET,  is this necessary after that also explicitly re-read the trimming parameters  via BOOT  in CTRL2 register? Or this soft reset does not affect the calibration registers.Background: We use different modes(ODR, with/without FIFO,LP/HP ) of lis2dw12 sensor and  when switching we are  triggering SOFT_RESET(CTRL2)  just to make sure that all configuration is in the default state before changing modes. The question comes up: is this necessary to trigger the BOOT as well on this stage to re-read calibration settings or is this not mandatory. Thanks in advance!   

We have following configuration in CTRL1: ODR[3:0]: 1001b (High-Performance / Low-Power mode 1600/200 Hz)MODE[1:0]: 01b(High-Performance Mode (14-bit resolution))And the value in the  "LP_MODE[1:0] " might be different depending on the state we came from. The question here does the value in the "LP_MODE[1:0] " have any affect in this configuration when high performance is selected in MODE[1:0]?

Posted on January 10, 2018 at 10:32I am trying to interface LIS2DH12 with NRF51822 chip using SPI communication no matter in what way i configure my spi, it is always returning fixed values 0x80,0x40,0xc0 in all six registers for x,y,z co-ordinate.I am not using FIFO but trying directly to read from register is it right way or should i choose FIFO mode.thanks in advance.

in main callplatform_init_h12();while(1){ lis2dh12_read_data_polling(); HAL_Delay(1000);}The read_data_polling.c code is as follows:/* Includes ------------------------------------------------------------------*/#include <string.h>#include <stdio.h>#include "lis2dh12_reg.h"#include "stm32G0xx_hal.h"#include "usart.h"#include "gpio.h"#include "spi.h"#include "tim.h"#include "IMU.h"/* Private macro -------------------------------------------------------------*/#define  BOOT_TIME      300 //ms 5#define CS_up_GPIO_Port GPIOB#define CS_up_Pin    GPIO_PIN_12//#define SENSOR_BUS    hspi1#define SENSOR_BUS    hspi2 stmdev_ctx_t dev_ctx; lis2dh12_reg_t reg;/* Private variables ---------------------------------------------------------*/static int16_t data_raw_acceleration[3];static int16_t data_raw_temperature;static float acceleration_mg[3];static float temperat

HelloIn the IIS3DWB datasheet, it is said that the embeddeed temperature sensor offset can vary within a [-15°C : +15°C] range.Does that mean that the reading from OUT_TEMP_H/L can vary within [-256*15 LSB : +256*15 LSB] at 25°C ?Having tested 2 chips myself, I got a much better result.I am then wondering whether I was just lucky, and if I really need to calibrate.Thanks

I am trying to validate a new board layout and am looking for the minimal configuration to read accel data.I'm using SPI.  When the WHO_AM_I register of the LSM6DSR is queried, the correct response of 0x6B is returned.I take that as validation of the at least the layout and soldering.Looking at AN5358 "Mode 1 - Reading output data" the minimum configuration is to write 0x60 to CTRL1_XL (0x10U), section 4.1. Enabling an ODR of 416 Hz at +/- 2g.AN5358 in section 4.2 then indicates read STATUS_REG until the LSB, which is XLDA, is set.That bit is never getting set.  Why? STATUS_REG always reads as zero. 

Please provide the following details of  ASM330LHB IMU1.MTBF(Mean time between failure)2.Longevity.3.Shelf life or storage life.

Hi,The LPF2 filter on the IIS3DWB can set the cutoff frequency to ODR/4, ODR/10, ODR/20, etc. Figure 6 in the datasheet "Frequency response with LPF2 enabled" shows the bandwidth when LPF2 is set to ODR/4 to be 5.6 kHz. Is this correct? ODR/4 would put the cutoff at 26.67 kHz / 4 = 6.67 kHz. Does "ODR/4" simply describe the LPF2 stage and not the actual resulting bandwidth? Thanks for your help,Steve

Hi,It seems that accessing the i2c bus add noise to acceleration values read by the LIS3DH. The graphic represent 270 X,Y,Z 10bit samples read at 1344KHz. The FIFO is enable and a watermark level interrupt of 28 is set. At each interrupt, I'm doing a bulk reading of the output registers (28*6 bytes). We can see a cyclic glitch especially on Z axis in yellow that match the bulk reading period. Before using the FIFO, I was doing multiple single reading but the result was very noisy.Is somebody had this problem? Is it a known issue? Is there a way to solve it?I also include the layout of the PCB of the chip.  

I have multiple LSM6DS3 (with SH SMD markings) and all of them show the same strange behavior.The chip is soldered to a breakout board that is set up on a breadboard. And is connected to the MCU breakout with 20 cm jumper wire.1. When I read a register, they return the registers address as the register value. The exceptions are the ID register, which is correctly returned as 0x69 and the Data registers that contain the acceleration and gyro data.2. Reconfiguration (for example the resolution) will take effect only after a power cycle and another write. I tested it multiple times while changing the SPI wire lengths to make sure it's not some kind of glitch from bad wiring.3. The Gyros Z Axis is always outputting zero.4. Configuring the secondary I2C for reading a slave magnetometer does not work, the I2C does not show any activity on the lines. I implemented it according to Application Note AN4650.The sensor values that are put out are correct (except gyro-Z), and change as expected whe

The LSM6DS3TR-C datasheet "Gyroscope LPF1 bandwidth selection" table mentions BWs for 800Hz, 1.6kHz, 3.3kHz and 6.6kHz ODRs. In the same datasheet, the "Gyroscope ODR configuration setting" table lists ODRs of 12.5Hz, 26Hz, 52Hz, 104Hz, 208Hz, 416Hz, 833Hz, 1.66Hz, 3.33Hz, 6.66Hz.Question: Why don't the ODRs mentioned in these two tables have the same values? Am I supposed to assume 800Hz in one table is the same as 833Hz in the other table?Question: I'd like to set my gyro ODR to ~200Hz with a ~100Hz BW acting as an anti-aliasing filter. Is that possible? I can achieve this with the accel. Why is it not mentioned in the "Gyroscope LPF1 bandwidth selection" table? If this is not possible, what is the reasoning to provide such an ODR-BW combination for the accel, but not the gyro?

I have been looking at the STEVAL-STWINKT1B sensor tile and the X-CUBE-MEMSMIC1 library. Is it possible to record 8 mems microphones to SD card with this board? I need phase coherence for array processing. All the examples seem to be a maximum of 4 microphones.I could use analogue or digital microphones. It would be nice to store PCM data on the SD card but I could do the decimation from PDM recordings on a PC along with the array processing.

Hi,I am currently working on a STM32F303RE wired to a STEVAL-MKI195v1 throught a nucleo-iks01a2. When I tick the box corresponding to the mems package I use for data-retrieving from the lsm6dsrx on the STEVAL-MKI195v1 board. It does not add some code generating an i2c handle nor it initialise the i2c communication protocol. But when I don't tick the box and then can't use the provided lsm6dsrx.c and lsm6dsrx_reg.c and corresponding files .h. If someone knows a solution to this problem or could tell me where my I2C protocol is initialized it would be of great help. I joined a screenshot to give a bit of context if needed.The tickbox. Thank you in advance.-Loïc

Hello,I am trying to count steps from a Poky linux. I have already a driver configured which can be used to get accelero and gyro data. I've seen on the LSM6DSL's datasheet that the register FIFO_CTRL2 (07h) can enable the step counter that can get in the register in 4Bh.In the existing linux driver, that functionality is not implemented. Do you have a version of the driver where it is possible to use it ? Or any documentation or example to modify this driver ?Thanks,Arthur

Hi,I'm using an ISM330DHCX in a couple of boards.The output looks great on the desk but when subject to high shock and vibration the gyro signal shows a lot of noise (to the point where the rotation value is lost).Is this just something that happens with this device, or is there a way to mitigate this effect?

Hey, i am currently planning to work with the ISM330DLC and am wondering if its possible to change the full-scale selection of Accelerometer (CTRL1_XL (10h) - FS_XL [1:0]) during operation. Or is it mandatory to stop the ISM to change the control register values. I could not find any  information regarding that topic in the datasheet attached. 

I am currently working on a project that involves angle measurement, and I'm using the LSM6DSRX sensor in conjunction with an STM32 microcontroller. I have encountered some challenges, and I would greatly appreciate your expertise and guidance to help me overcome them. Project Details: Microcontroller: esp32s3 Sensor: LSM6DSRX Objective: To accurately measure angles using data from the LSM6DSRX sensor. Challenges I'm Facing: Not able to calculate appropriate angle measured by sensor

At the moment I am making an application for 3D sound detection, in which I am making use of the STEVAL-STWINKT1B and the STEVAL-STWINMAV1 microphone array (which I haven't used yet). I am just starting, and I can not understand the operation of the SensorTile, previously I was using the SensorTile.box and it was easier to handle APP ST BLE SENSOR, in which I could easily extract the data, however, in the SensorTile it is getting complicated, I guess it is because of the FW used that I can not see the APP as in "cap2" and rather I see it as in "cap1".Finally, speaking of the microphone array, I would like to ask how to connect it to the device? physically I have already connected it (in the CN4) but I understand that this is not enough to make use of it (besides I am not very clear how to receive the data that it gives me).Sorry for so many doubts.

I'm looking for a mechanical survivability spec for shock/vibration for the gyroscope MEMs sensors offered by ST, and was wondering if this information is available somewhere?Specifically interested in the A3G4250D and I3G4250D sensors. Is this information available?Thank you!