MEMS (sensors)

Hello,I once compared your eCompass application (STM32F401RE/X-NUCEO-IKS01A3) with the compass on my smart phone.The compass on my smart phone behaves much better than the ECompass; it is not affected by rapid changes in the angle of inclination or by vibrations.What is the reason for this? Is it due to the sensors or the software?

HIWhen using the FIFO mode on the lsm6ds3tr-c sensor, there appears to be an issue where occasionally the pattern value read from the FIFO buffer is incorrect, leading to potential errors in the subsequent data retrieval process. This issue also results in the possibility of erroneous FIFO data being read.ERROR 1：00> <info> app: level: 18, read_level: 1800> <info> app: pattern: 0, index: 0, count: 213525, raw: -100> <info> app: pattern: 1, index: 1, count: 213526, raw: -200> <info> app: pattern: 2, index: 2, count: 213527, raw: 700> <info> app: pattern: 3, index: 3, count: 213528, raw: -11900> <info> app: pattern: 4, index: 4, count: 213529, raw: -5200> <info> app: pattern: 5, index: 5, count: 213530, raw: -407000> <info> app: pattern: 6, index: 6, count: 213531, raw: 81500> <info> app: pattern: 7, index: 7, count: 213532, raw: -2867500> <info> app: pattern: 8, index: 8, count: 213533, raw: 000&gt

I am currently working on modifying the sampling rate for the LSM6DSO32G IMU sensor in a Samsung Android kernel. After reviewing the device tree and sensor driver files, I noticed that certain parameters like odr (output data rate) seem to control the sampling rate. However, I am not sure of the exact steps to apply these changes and ensure that the modified sampling rate is reflected correctly in the system.Here are my specific questions:Which files in the Samsung Android kernel should I modify to change the sampling rate for the LSM6DSO32G?Do I need to make changes in both the driver source code and the device tree, or is one sufficient?Is there a way to dynamically update the sampling rate (e.g., via sysfs or a similar interface) without rebuilding the kernel?Are there any specific steps or precautions I should take to test and validate the changes?Any guidance, code examples, or references to related documentation would be greatly appreciated!Thank you in advance for your help.Best

Posted on March 13, 2014 at 00:22I am interested in the LPS25H MEMS barometer chip, but I am having a hard time figuring out the footprint of the HCLGA-10L package. Here is what is called out in the datasheet: I cannot decipher from his what the dimensions of the pads should be.  I believe that e1/2 might give me the width, but I cannot determine the length.  Maybe that's what B is supposed to mean, but I don't see it. Also, I found that there is a http://www.st.com/st-web-ui/static/active/en/resource/technical/document/application_note/DM00064026.pdf but cannot find one for the LPS25H.  I realize it's a very new part, but this would help -- it provides some guidance on how the pads should be laid out. Can someone more mechanically inclined parse this for me? Thanks. #hclga-10l

Hey Everyone,  I bought this sensorhttps://www.sparkfun.com/products/21325 and it is default to work as i2c. Which I do. I can read from this imu using regular polling, but I would like to use interrupts. But the issue is, interrupts to do not fire at all, I am not sure why. I am following the stm32 examples on githubhttps://github.com/STMicroelectronics/STMems_Standard_C_drivers/tree/master/lsm6dsv16x_STdC/examplesand I still have issues getting this sensor to work as an interrupt. Am I missing something? Do I need a pull down or pull up resistor on the interrupt pin? I worked with interrupts, theyre not difficult, but not sure why this specific sensor I cannot get to work.for example, what i am experiencing right now whether I go with fifo or data ready signal, the int pin is always high. It does not go low. I did put a pull down to see if I can bring it down, but even with a 10k resistor, the int2 in this example, is always high. I also checked status regist

Hello everyone.I and my team are a bunch of BSc students in electrical engineering currently working on a gimbal project at our uni. My task is to prepare our IMU, the LSM6DSV16X by ST, for the readout of the game rotation vector so that we can get quaternions from it. The FIFO-Tag which should read 0x13 in the first five bits still reads 0x00, so there's apparently still no FIFO-Functionality enabled.I've used the ST-library found at https://github.com/STMicroelectronics/lsm6dsv16x-pid to implement the necessary functions and the platform_read and -_write funtions seem to work - I can send and receive signals and write to wr-registers and have the written bytes "stay there" as I've confirmed using oscilloscopes (measuring the MOSI and MISO signals alongside the clk and sc signals).The clk polarity is set to low and the clk phase to 1 Edge in the SPI configuration, just in case the problem lies there.Attached is the IMU's datasheet for easy reference as well as the init_imu() and valid

I just bought the latest SensorTileBox (STEVAL-MKSBOX1V1) and it lost power and bluetooth connection, no LED lights. How do I restore it to its original firmware? The ST BLE Sensor app also doesn't have the create app option.

Hi all, I am working on the STEVAL-PROTEUS1 Board, which features the STM32WB5MMG module and the IIS3DWB high bandwidth accelerometer sensor interfaced via SPI_1. According to the IIS3DWB sensor datasheet, it supports up to 10MHz (CLK) and an ODR of 26667Hz (37 microseconds). My objective is to collect sensor data at an ODR of 26667Hz. Here are the steps I've taken so far: Configured SPI_1 to 8MHz. Configured the sensor to generate an ODR interrupt, which is successfully triggering every 37 microseconds. The issue arises when collecting data (6 bytes) from the sensor, which is taking 42 microseconds. Ideally, this should not exceed 10 microseconds using HAL functions. Could anyone help me understand if the HAL function is supposed to take 42 microseconds, or if I might be doing something wrong? Note: The M4 core is running at 64MHz and the M0 core at 32MHz. Thanks in advance!

Hello,section "4.5.1 Example of output data" of the LIS2DUX12 device application note (AN5909) provides an example of calculating the acceleration value from the FIFO.In the example 14 useful bytes from the FIFO are multiplied by the sensitivity in "mg/LSB":I think "LSB" in the sensitivity refers to the sixteenth bit of the FIFO word.Why aren't the raw values from the FIFO shifted right by two bytes (or divided by 4) before multiplication?

may i know lps22df temperature offset register?want to read the correct value at 25 degrees in the temperature chamber,but it seems to be read as an incorrect value. Please me, know if there are any other ways to compensate for the temperature

Hi,I am using MP34DT06JTR mic with my custom board with Micro-controller STM32U535CET6.I am unable to get the data form mic with my custom board. MIC schematic screen shot and Signal wave form of CLK and DATA screenshot given below.can you please verify this all.Yellow signal for CLK and Blue one is for Data.sample rate for audio data is 16Khz in software.  I have tried the same MIC with EVK Nucleo-U545RE with X-NUCLEO-CCA02M2, there sound from MIC is perfectly working fine with the same code..Please help me in this issue ASAPThanks  

In ASM330LHB datasheet, gyro and accelerometer self test to be executed only when device is in static condition. But in field operating environment, device may goes into high dynamic condition during self test active, thenis ASM330 device gets damaged ?  OR device will be ok but only self test results will be failed?Thanks is advance,Pavani.

Dear Sirs,I would ask how it is connected ISM330BX with STEVAL-MKI245KA in the webinar. In fact STEVAL-MKI245KA has inside different sensors and I don't see the connector to plug STEVAL-MKI245KA.Moreover in en.FP-AI-MONITOR2_V1.0.0_RC8 need to be installed in CubeMX?The en.FP-AI-MONITOR2_V1.0.0_RC8 use one of INT1 and INT2 or both of ISM330BX? Thanks

Dear,I'm testing the lsm6ds3tr-c free fall function, but it's hard to tuning the threshold, i attach the current registor settings, I want to dectect the 1m free fall, can you give some guide? thanks a lot.

Hi, I’m working with the IKS4A1 Nucleo expansion board and F401RE. I need to generate a PWM signal on INT pin 2. The documentation I found focuses on connecting the IKS4A1 with MEMS Studio, and I couldn’t find guidance on configuring PWM signals in MEMS Studio.Is it possible to configure the PWM signal in MEMS Studio, or do I have to use CubeIDE instead? Any guidance or resources would be greatly appreciated!

I am trying to do USB sensor data streaming Real Time Plot by conecting  my steval mkboxpro with hsdatalog_GUI.py but it keeps saying "Device Template Model Loading". Anyone can help?Thanks 

Hello,I am programming my ISPU code that work on interrupts INT1 and INT2 in STM32CubeIDE and testing it in STEVAL-MIK109V3 with adapter board MKI229A (LSM6DSO16IS) and showing my output value in MEMS Studio.I configured the conf.txt linking the interrupts NT1 to function "algo_00" and INT2 to function "algo_01".conf.txt:     acc_odr 104     acc_fs 2     acc_mode high_performance     gyr_odr 104     gyr_fs 500     gyr_mode high_performance     ispu_irq_rate 104     ispu_int1 enable     ispu_int2 enable     ispu_latch disable     algo 0 enable     algo 1 enable     algo_int1 0 enable     algo_int2 1 enable After building and uploading the ispu.ufc in the sensor with MEMS Studio happens that when INT2 is 0, it freezes all my custom ISPU Output data. And when INT2 is 1, it

I have been trying to get a connection to my sensortile kit using the serial  connection. I only get "Board not identified". I have tried loading the DatalogExtended.bin file to try get the board to be recognized but this didn't help. I also tried making a small "application" with the Algobuilder in Mems Studio but this seems pointless as there is no connection. Is there a tutorial or app note that could explain how to get the software to detect the kit? 

Hello, I am using the LSM6DSOX sensor and reading data from the FIFO, following these examples on GitHub (https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsox_STdC/examples/lsm6dsox_fifo.c). I've set the same frequency for both the accelerometer and gyroscope, but when I read the data from the FIFO in continuous mode, the samples are not aligned. For example, I receive the first two accelerometer samples followed by one gyroscope sample, then three accelerometer samples, two gyroscope samples, and so on.Since the frequencies are the same, shouldn't I receive one gyroscope sample and one accelerometer sample consecutively in a 1:1 ratio? Is this behavior normal? Or is it necessary to adjust the accelerometer's configuration in some way to ensure that the samples are aligned? If so, how should I do that?Thank you!

Hello I am working with an ST magnetometer sensor to detect movement along the X-axis. I have a custom board featuring an L4 microcontroller, which enters STOP MODE 2 until an interrupt is triggered. I use the following function to initialize the sensor for this mode, after which the device goes to sleep. When the magnetic data exceeds a specified threshold, the magnetometer generates an interrupt and the device wakes up. However, I am facing a challenge regarding maintaining the device's proper functionality when exposed to temperature variations. The interrupt generation is based on raw magnetic data returned by the function lis2mdl_magnetic_raw_get(). I am aware that the temperature fluctuations, such as reaching 50 C, can distort the magnetic readings, potentially causing inaccuracies. The magnetometer will require calibration, but my question is how to apply the calibrated values in the system?   Currently, my approach is to keep the device in sleep mode and wake it up o

I want to collect data wirelessly using the SensorTilebox.PRO and an STEVAL-MKI240KA (LSM6DSV32X) connected via the DIL24 socket. When I flash the DATALOG2_Release binary, I can see the onboard sensors using the ST BLE Sensor app, but not the external IMU. When I flash the MEMS Studio datalog extended firmware, I can log data from the external IMU but the device must be connected to a computer using a USB cable. Are there any pre-existing solutions allowing for datalogging (either through BLE connection or automatically on startup) with data from the external IMU, or does this functionality require directly modifying and flashing custom firmware?

Hi, I have been working with iis3dwb since 2020 and a week ago me and my colleague found something that looks like a design mistake from ST side, we found something like sample losses during FIFO buffering I am not sure but further I will try to provide as much info as possible to be understood. There will be a lot of details because the question isn’t easy.Prehistory:Me and my team designed a vibration sensor(further VTS) based on iis3dwb mems accelerometer (spoiler: it’s great, but…) and we are happy about it. Until recently we thought everything is ok and data reading is working as it should be, I did a lot of tests to see if we have some sample losses, I tested it on 8192 samples num for each axis due to internal uC memory limitations (and this amount was enough to calculate FFT and then acc RMS, velocity RMS… with required frequency dimension and accuracy). But this was the first step in production of VTS, then we installed 8MB RAM to store 1minute, 2 minute etc amount of RAW data

Hello!  First I would like to state my issue:  1. My software cannot connect to the LSM6DSO IMU sensor.   A little background on my project is that I am trying to use the IMU sensor to provide accelerometer readings in x, y, and z directions. I purchased a breakout board from Sparkfun that uses the LSM6DSO to test the sensor first with my Arduino-compatible controller via SPI communication. This proved that it works.  We then created our own design and referenced the way Sparkfun wired the LSM6DSO. Now when I run the program on the new board, the sensor doesn't work.  I looked into the library that Sparkfun uses for programming in Arduino and I see that it cannot connect to the IMU sensor. In the library I can see where it fails and it fails when checking the part ID. I keep getting a part ID of 255 which is 0xFF. I should be getting a part ID of 108 or 0x6C. Any ideas on what I can do to make it work?       uint8_t partID; re

Hi,We are working with the LPS22DF pressure sensor to be used in our device adapting a 3.3V system and have encountered issues related to the interaction between VDD_IO, VDD, and the I²C bus. When VDD_IO and VDD are connected to the same 3.3V supply:The I²C bus behaves as expected. (No issues here)However, when we disconnect VDD_IO and VDD, while I2C is active to be used for other sensors to communicate, the sensor seems to backfeed through VDD_IO's internal pull-up to VDD, interfering with the I²C bus (e.g., pulling lines to ~1.5–1.6V). (this is our theory at least)When VDD_IO is powered but VDD is not:I²C communication is disrupted.The sensor seems to partially power itself through internal pull-ups, potentially backfeeding into VDD.In addition, CS pin will sometimes influence the I2C bus if its connected to HIGH.We have tested it using the evaluation kit and also on a breadboard. What we did was add a diode between VDD and VDD_IO to temporarily eliminate the issue. However, the

Hi, I am using MotionFX with BlueCoin, for a solution that can detect vertical movement within 2 meter range with high precision.  I took the ALLMEMS2 example when I logged linear acceleration and gravity, it showed some unprecise values likelinear acceleration around 0.2 when the device wasn't moving. When I increased the full scale factor for ACC to 16.0f and Gyro to 2000dps, the linear acceleration value improved to the range of 0.05-0.1, which is still not as expected. Gravity value is strangely too high and stable 9.99, shouldn't it be closer to 9.81 max in the stale state?  NFO:__main__:Linear Acc -> x: 0.0290, y: -0.0090, z: 0.0190 INFO:__main__:Gravity -> x: 0.0590, y: 0.0310, z: 9.9990 INFO:__main__:Linear Acc -> x: 0.0090, y: -0.0180, z: 0.0490 INFO:__main__:Gravity -> x: 0.0580, y: 0.0300, z: 9.9990 INFO:__main__:Linear Acc -> x: -0.0110, y: -0.0190, z: 0.0390 INFO:__main__:Gravity -> x: 0.0580, y: 0.0310, z: 9.9990 INFO:__main