MEMS and sensors

I test the LSM6DSOW I3C IBI interrupt, I set the accelerometer FIFO mode, and FIFO full, the interrupt is triggered, and I got payload from LSM6DSOW. What does this mean?i:0,read value:0x1i:1,read value:0x20i:2,read value:0x5i:3,read value:0x0i:4,read value:0x0i:5,read value:0x0i:6,read value:0x0i:7,read value:0x0i:8,read value:0x0 

A minimal example of wake-on-motion detection and inertial data logging based on the LIS2DW12 3-axis accelerometer using the STM32WB5MMG as MCU host and Thomas Roell's excellent STM32WB Arduino core.

Hi,ASM330LHH datasheet states that "compensation for high stability over temperature" are embedded in the device. Could you provide more information about the correction algorithms applied ?In particular, when we measure the bias at 0°/s of the ASM330LHH in a temperature chamber, we get strange non-linear behaviors that we suppose to be a consequence of these algorithms. For instance, in the following figure (filtered bias at 0°/s depending on temperature) some "steps" can be observed. Could you provide a description of the corrections applied / the reason of this behavior ? It would make the device more predictable for us.Furthermore, is there a way to disable these corrections ?Thank you a in advance. 

Hi，   vl53L0x goto sleep and wakeup to reduce power.  I used single_mode,program as follow:   I find add          sensor_init(dev,vl53_mode);            //activa  The measurement time was 600 mS. long more than not add  this function？  how  to reduce the time?      

Hi, When performing two measurements per second, how can the power consumption of the VL53L0x be reduced? Is a single measurement or continuous timed measurements preferable? I adopted continuous timed high-speed measurements, setting the measurement duration to 22 ms with a 900 ms interval between measurements, resulting in an average measured current of 19 mA (according to the specification). Based on this, I calculated the average power consumption.(22 mS × 19 mA + 5 μA × 878 mS) / 900 mS = 0.4693 mA. I don't understand why others can achieve 20 μA.

Hi, I am experiencing a technical issue with the ST 16GZMAI camera when connected to the EVK-U0I1 control board. While the system works fine with my 55G1MBI1 camera, the EVK GS 1.1.2 GUI fails to recognize this specific model and displays the following error: "Error: could not broadcast input array from shape (341,280) into shape (340,280)" I am also unable to change the detector format. Could you please refer me to a technical expert who can assist with the configuration of this model? Best regards, Sean

Hello group,I'm a humble hardware guy integrating the LSM6DSV16X into a robotic application.We are going to use it in control loops, between 3kHz and 5kHz sampling.Between the main mode and the OIS mode, there are tons of ODR to choose from.However, is there a way to make the ADC sample at EXACTLY 5kHz?? Like a triggered or synced ODR?Or do I have to set the ODR at 7.68kHz and read the latest value from the FIFO and deal with the small discontinuities?I see the Triggered-ODR section 6.6 in the datasheet. Does it means enabling this will sync the ADC with an external INT2 pulses? Does the new values appears in the FIFO after a defined short delay?Thanks!

I am using MEMS Studio (v2.3.1) with ST1VAFE3BX to train an MLC model using AFS (Automatic Filter & Feature Selection).My input data contains:- 3-axis accelerometer: A_X [mg], A_Y [mg], A_Z [mg]- vAFE channel: vAFE [LSB]The CSV header follows the format described in AN6208:A_X [mg], A_Y [mg], A_Z [mg], vAFE [LSB]However, when running AFS, I get the following error:"External sensor unit mismatch between provided external sensor name magnetometer and units LSB.Correct units are gauss or mgauss."This is confusing because:- No magnetometer data is used- Input type is set to accelerometer + vAFE- vAFE [LSB] is consistent with ST documentationI have already tested the following:1. Verified CSV format (no missing values, consistent headers across all files)2. Tested minimal dataset (only 2 CSV files)3. Tried different headers:- vAFE [LSB]- vAFE_X [LSB]- tab-separated

Connected STEVAL_$MKI243AA board to a nucleo-g491re board using 4 wire spi interface. The spi bus is setup to run @ 146 Kbits/sec. Reading back bad data. WHO_AM_I is 0x48PIN_CTRL is 0x3E Not sure but seem like the device is power

Hey, I am using MotionFx 9D, and it works pretty well, except in one case:  when a fast movement is done, and we stop, the IMU is not in the correct orientation due to the update being disabled just before the end of the movement (like a 10-30° error). As I read on that forum, this is intended behavior; however, in our application, it is a pretty useless bug rather than a feature. We tried many thresholds, trusts, various sampling times, etc. No luck. Please provide any information on how we can control updates to achieve almost no movement. That looks like hidden settings, and we are so desperate to even inject a 'noisy' input as input data to trigger updating at the end of movement (as we have noticed that small vibrations are causing orientation to be corrected with every single small movement).Thanks! 

We have been using the ST MP23DB01HP microphone to measure the shockwave signature of assault rifles. When comparing the time signal with measurements performed with other microphones (e.g. B&K model 4948), we noticed that the typical N-wave signature looks different with the ST microphone. The initial compression wave of the shock appears negative when measured with the ST microphone, which is counter intuitive. Also, the expansion phase of the shockwave, which appears relatively clean when measured with the B&K microphone, is severely perturbed when measured with the ST microphone. Could it be that the perturbation observed with the ST microphone is of internal nature, e.g. caused by some internal flow due to the shockwave and not properly vented out of the casing? What other possible causes would you see? Exceeded acoustic overload point? Tthe shockwave has very strong gradients, that might interact negatively with the ST microphone.

So, I was showing some friends in England how to use the Sensor TileBox Pro to measure a building, using the modified CLI_EXAMPLE program.  So starting analysis, the X axis now representing gravity vector in the table, I knew I had the box sitting on its side in a slot in the column, so if I am looking at the box, I was wondering what axis system matched the box and the unit.  Your data sheet showsThe whit dot is important

We had three Sensor TileBox units. In an interesting morning of work, I got the one I have in the USA running, in the hope that the people in the UK who have them could use them.  I got it running, during the reading to get it running, I found a note in one of the PDF files that said the CSV files would be padded to the highest ODR.  First time I had actually seen that other than in a ST reply.  The TileBox recorded nicely once I worked out the boot key, which is one of three buttons and the PDF does not show it that I could find.  I knew I had seen it once, but I could not find it.  I enjoy playing with the combinationsThe CLI_Example program worked nicely.  The sample files json files were challenging. Following the instructions, it proved difficult, I could not do transfer the data to CSV, Unicleo GUI did not help as suggested.  Anyway we are throwing them away, but it was some fun. &nb

Hi Team, Greetings! Mems studio is used and LSM6DSV320X is kept on the sensor tile box pro, We are currently performing drop tests using the SensorTile Box pro platform mounted on a flat board casing. The tests are conducted from the same height under two configurations: Wired mode with an ODR of ~7.6 kHzWireless mode with an ODR limited to ~1 kHzWhile analyzing the accelerometer (high-g) data, we observe a variation in peak acceleration values of approximately ~20 g between different runs, even though the drop conditions are kept identical.We would like to understand the following:Is such a variation (~20 g) in peak acceleration expected under these conditions?Could the difference in ODR (7.6 kHz vs 1 kHz) significantly impact the captured peak values for short-duration impact events?Are there any known limitations in wireless mode (e.g., filtering, bandwidth constr

Hi, I was trying to create a small 8x8 / 4x4 point cloud using a VL53L5CX sensor, and I can get the depth data for each zone, but I was wondering if there was a way to get x,y,z from this information? Like if there was a way to know the vertical and horizontal angle for every zone on the VL53L5CX and then calculate the x,y,z location of the points using that and the depth data. Any help would be appreciated!

Hello,I know there are already other threads on this topic, but none of the replies have convinced me.Perhaps someone can help me.My real problem is with the pedometer in the LSM6DSO.I am setting the following values in the registers:ODR = 52 HzLOW_POWER_MODEPEDO_CMD_REG -----> FP_REJECTION_EN = 1EMB_FUNC_EN_A -----> PEDO_EN = 1EMB_FUNC_EN_B -----> PEDO_ADV_EN = 1PEDO_DEB_STEPS_CONF = 0x0A (default value)PEDO_SC_DELTAT_H = 0 (default value)PEDO_SC_DELTAT_L = 0 (default value)I am not using the interrupt for the pedometer, I am polling the value in the register STEP_COUNTER_H | STEP_COUNTER_LSetting AD_DET_EN = 1 in PEDO_CMD_REG didn't make any difference for me.I have 2 question about the pedometer:1 - Do I need to configure anything else to improve the performance of the pedomter ? Is possible to improve it ?2 - What is the STEP_DET_INIT bit in the EMB_

I am trying to understand one point in the official VL53L8CX datasheet.In the pin description table, pin C5 (MISO) is described for SPI as:“SPI: Main input secondary output. Push-pull output, driven to IOVDD level.”But in Figure 6 (“Typical application schematic for SPI”), the MISO line seems to have a 47 kΩ pull-down resistor to GND.I attached two screenshots:1. the table entry for C5 / MISO2. the SPI typical schematic with the suspected 47 kΩ pull-down highlightedMy question is: how should this be interpretedcorrectl

Dear ST Support Team,I am writing to express my interest in the VD55H1 iToF sensor for an upcoming project.Currently, we are preparing for development using the i.MX8MP platform running on a Linux Kernel. Upon reviewing the technical specifications, I noted that the VD55H1 utilizes a MIPI-CSI data interface.Could you please confirm if ST provides an official Linux driver for the VD55H1?As driver availability is a critical factor for our initial integration and development phase, we would appreciate any information regarding existing software support or a roadmap for Linux integration.Thank you for your time and assistance.Best regards,seobi

I am using STEVAL-MKI109D + STEVAL-MKI238A. I have evaluated motion-stationary FSM example as it seemed closest to what we want to use for our application. It seems to work fine, however it is too sensitive and needs some upgrades.What I want to achieve:Setup timer (TI3) to some value such such as 5 seconds. During this 5 second period, I want to detect specific number of events above certain threshold (GNTH1). If specific number of events were detected during 5 second period, generate an interrupt and repeat over and over again. If specific number of events were not detected during that 5 seconds period, just reset the counter and repeat.My cofiguration:

Hello,I am currently working on a drone project based on the STEVAL-FCU001V2 board. My hardware setup consists of:Motors: 4x 8520 Coreless DC motors (3.7V).Battery: 1S LiPo 600mAh (30C).Frame: Custom micro-drone frame (~60g AUW).I am looking for a reliable and fully functional firmware (source code or .bin) that is compatible with the latest mobile application for flight control of STM.I’ve noticed that the original ST Drone (or ST BLE Drone) application sometimes has connectivity or stability issues with recent Android/iOS versions.My questions are:Is there a specific version of the STSW-FCU001 firmware that you recommend for best stability in 2026?Is the "ST Drone" app still the official way to fly this board via BLE, or is there a community fork or

I am using MEMS Studio to evaluate FSM and MLC on the STEVAL-MKI109D + STEVAL-MKI238A . I noticed few strange things. I am attaching my FSM gui config and reg config (config.zip)1. When I open the FSM tab and load the state machine files and device configuration fileone thing I notice right away that its not loading the Long Counter Max value correctly.In my saved FSM configuration I have set it to 0x14 but when I load the configuration it still showing up at 0001

Hi - when I attempt to download the driver for this device the download never completes; I get a file "Unconfirmednnnn.crdownload" in my download folder. I'm using Edge browser on a Windows 11 Home 64 bit operating system. Using Norton, can't see anything there that would prevent the download. Have successfully downloaded from other sites many times with no issues.Anyone with any insights?Thanks.

Hi,I've P-NUCLEO-6283A1 and downloaded the graphical user interface STSW-IMG301. The quick start guide does not seem to be up to date as I did not find "VD6283_setup.exe" I was supposed to install, just a plain exe in the zip.At the first try GUI complained that it cannot communicate with the board. Next I updated the firmware with the GUI. Now when trying to start I get error complaining about invalid product version. What is going on here? Does the GUI ship with incorrect firmware binary?My board

Greetings! I am using the LIS2MDL magnetometer in continuous mode (10 Hz) with hard-iron offset and interrupts enabled. (Full settings: CFG_A: 0x90; B: 0x0A; C: 0x50; INT_C: 0xE5) And I am trying to detect a magnetic object coming near the device. The interrupt threshold I have currently set is 80 (int). The sensor is powered with a stable 1v8.When I leave the sensor to measure and wait for an interrupt in an environment with no stimuli, the sensors that I have at hand all seem to generate weird false impulses out of thin air. They appear in the form of bit/byte flips, that happen only on the MSB part of the 16-bit data block.For example, if I am constantly reading the sensor values (at 10 Hz, same as sensor), there is a possibility that I will read the false vector value from the axis registers. The raw values for the X axis would look like: "0x0028; 0x0027; 0xFF28; 0x0029". As far as I have observed, this has only happened on the X axis (for the ~5

Hello community ,I am going to do 9 axis sensor fusion (6axis accel and gyro + 3axis magnetometer) and got across to the MEMs-Studio suite. I've bought STEVAL-MKI109D for motherboard and STEVAL-MKI217V1 as the shield. STEVAL-MKI109V3 is out of stock at that time.I pluged the USB for STEVAL-MKI109D with mounted STEVAL-MKI217V1, but the STEVAL-MKI217V1 isn't recognised but was recognised as STEVAL-MKI197V1 instead. The features of 6axis are fine but I need to test the 3axis mag also. Here are my software setting.STEVAL-MKI109D firmware was updated to v 0.8.14MEMs Studio  1.4.2