MEMS (sensors)

Hello,I am using MEMS Studio (latest version) with the LSM6DSV320X to configure the Machine Learning Core with 2 decision trees.Steps I follow:Open MLC tool, set workspace via BrowseImport mlc_settings.json — data patterns load correctlyARFF Generation tab — add features, click Generate ARFF File — generates features.arff successfullyDecision Tree Generation tab — set 2 trees, assign labels to each treeClick Generate Decision TreeError:Unable to open features_DT0.arffI notice two problems happening:MEMS Studio generates features.arff but then looks for features_DT0.arff when generating 2 trees. With 1 tree it works fine.When the error occurs, the file features_DT0.arff (which I manually copied/created) gets deleted from the workspace folder.After the error, mlc_settings.json gets reset — the dectrees[].filename fields are cleared back to empty strings, and sensor settings revert to defaults.What works:1 decision tree generates successfully every timeWhat fails:2 decision trees — always

Hello ST Community, I am currently in the hardware selection phase of a product development project and am evaluating STMicroelectronics accelerometers for our production design. I am hoping the community and ST engineers can help clarify driver availability and support options for our target platform.Platform OverviewOur production platform is based on the Quectel SC200U module running Android 14. The key processor specifications of this platform are as follows: Application Processor: Octa-core 64-bit ARM Kryo™ 260 CPUDSP: Qualcomm Hexagon DSP, Dual-HVX @ 512 MHzGPU: Adreno™ 610 @ 950 MHzOperating System: Android 14A critical hardware design constraint of this platform is that the dedicated SENSOR_I2C interface exclusively supports sensors operating under the ADSP (Audio Digital Signal Processor) architecture. Specifically, the hardware design document explicitly states:"SENSOR_I2C only supports sensors in the ADSP architecture"Accelerometer Candidates Under EvaluationW

Hello, I am trying to build a simple firmware for my SensorTile.Box PRO to stream any data. Using MEMS Studio's AlgoBuilder, I have set the correct Toolchain (STM32CubeIDE), and the target (SensorTile.box Pro). Then I built a simple design with Quaternions 9X attached to the Sensor Hub (Data Rate: Timer/100, Accelerometer Full Scale: 2g, Gyroscope Full Scale: 245dps), outputting to a Fusion component. I can generate C code and build and program my device in DFU mode.However, when I connect it over Serial after rebooting the device, I can connect to it but the "play" button is grayed out and I cannot stream any data.Using STM32CubeProgrammer to flash other compatible firmware that came with MEMS Studio (steval-mkboxpro, steval-mkboxpro-ble), I can connect and stream (play button is enabled) data as per normal so I doubt the problem lies with the hardware.I have also tried other designs with SensorHub -> Any other sensors -> Value instead of Quaternions 9X, but none of it work

i have a new phone and the app that is used to get the data is in an oldest version and no newer were done and so i cant acces the data anymore the app is the ST BLE sensore clasic

I have an X-NUCLEO-IKS4A1 mounted on top of a NUCLEO-L476RG and I am trying to connect that to Mems Studio. I get one of the two errors in the attached screenshots. Either "Board not identified" or "Some device is already connected".

I've been using this part from NXP (originally Freescale, I think)  for a while now.I've just noticed that it now has an ST Product Page:https://www.st.com/en/mems-and-sensors/fxls8967af.htmland the datasheet says:The ST Accelerometers portfolio page also lists a few other NXP part numbers: Is this a 2nd-source arrangement, or have these products fully transferred from NXP to ST ?  

Hello.I'm working on project with LSM6DSO and I use FSM.For easier programming I use the FSM Feature in MEMS studio, but it looks like it's buggy:1 - SRP doesn't change the graphical diagram of FSM. It always point to start of the program on RNC.Example: 2 - Adding STIMER3/4 lead to error when I try to export the register config (save device configuration as):There are also missing settings from the Fixed Data section (CONFIG_A, CONFIG_B, SETTINGS) which could be important.Thanks

Hello,I am working with the Machine Learning Core (MLC) of the LSM6DSOX and I would like to better understand how to extend or reuse existing ST models.In particular, I am using preconfigured models available from ST (e.g. Activity Recognition), which are provided as .ucf files.My goal is to:reuse an existing ST model as a baselineadd my own labeled data (custom activities)generate a new combined model without starting completely from scratchFor this reason, I would like to ask:Is it possible to access or obtain the original datasets used by ST to train the provided MLC models?Is there a way to extract or inspect the underlying decision tree from a .ucf configuration?Is there an official workflow to extend an existing model (e.g. retrain by adding new data) rather than creating a new model from zero?I understand that .ucf files represent the final register configuration, but I am interested in working at a higher level (model/data level) if possible.Any guidance or recommended approach

Hi everyone,I'm working on a project involving the STEVAL-MKBox Pro and would love some guidance from the community, especially since I'm still relatively new to this ecosystem.Here's what I'm trying to achieve:• Configure sensors on the STEVAL-MKBox Pro via Bluetooth using PnPL commands• Control data logging (start/stop) remotely over BLE• Save the collected data locally on the SD card• Once logging is complete, transfer the data to a Raspberry Pi 4 via BLEThe reason I chose to log first and transfer later rather than streaming directly over BLE  is the bandwidth limitation of BLE. My application requires high-frequency data acquisition, so buffering to SD card first and transferring afterward seems like the more reliable approach.My main question is: where should I start?Should I build on top of an existing firmware like FP-SNS-DATALOG2, or would it make more sense to start from scratch given my specific requirements?I have a basic understanding of the tools involved, but I'd re

Hello all,I am developing a vibration measurement device using LSM6DS3TR-C. Most of the time the data were in good shape (99%).  However, I noticed some spike in my vibration intensity reading randomly. After checking the raw data I saw some step change at the same time point, indicating the data reading of the three axis are confounding.My configuration only requires the accelometer readings to be cached in FIFO:1. enable block update 2. set fifo accelometer decimation register to 1 (no decimation) 3. set fifo accelometer data rate to 3333Hz 4. set accelometer data rate to 3333Hz, bandwidth 1.5khz, LPF_BW_SEL to 1 5. set FIFO mode to bypass, then set to FIFO mode (clear and restart FIFO) 6. polling FIFO_STATUS2(0x3B) register for FIFO_FULL_SMART. 7. I2C bulk read the FIFO for 682(sample count) * 3(axis) * 2(16bit-axes) = 4092 bytes from buffer 8. repeat from 5.To identify the issue, I changed step 7 to the following: For i-th reading 7.1 Read the FIFO patte

Hello,after updating MEMS Studio to version 2.3.1 I am experiencing an issue when working with FSM configurations.Previously everything was working correctly, but now I cannot reload FSM configurations saved as JSON files.Steps to reproduce the issue:Create a new FSM in MEMS Studio.Save the configuration as a JSON file.Try to reopen the same JSON file.The file loads without any error message, but the FSM editor remains empty and the FSM configuration is not shown.However, individual FSM examples included in MEMS Studio open correctly without any issues.This happens both with:JSON files generated previously with an older version of MEMS StudioJSON files generated directly from example FSM projects in the current versionSo the issue does not seem to be related to the JSON content itself.My setup:MEMS Studio version: 2.3.1Sensor: LSM6DSOXQuestions:Has the FSM JSON handling changed in MEMS Studio 2.3.1?Is there a specific way to reopen a saved FSM configuration JSON?Is this a known issue o

Dear Sir or Madam,I require a RoHS declaration of conformity for the following component:STEVAL-MKI208V1KCould you please share it?Thank you very much and kind regards,Thomas

In the past, I have used an LSM330 to wakeup on a gyro z-axis threshold and activate the INT1 pin as shown below:Gyro_WrByte(GYRO_CTRL_REG1, 0x3f); // 95Hz DataRate : 25Hz Cutoff : Normal Mode : Enable All AxesGyro_WrByte(GYRO_CTRL_REG2, 0x07); // HPF Normal Mode : 0.045Hz HPF Cutoff Freq : HPF Normal ModeGyro_WrByte(GYRO_CTRL_REG3, 0x80); // INT on INT1_Gyro PinGyro_WrByte(GYRO_CTRL_REG4, 0x00); // Continuous Update : Little Endian Data : 250 dps FS : 4-Wire SPI IntfcGyro_WrByte(GYRO_CTRL_REG5, 0x04); // Normal Mode Reboot Mem Content : FIFO Disable : HPF Disabled : INT1 Select = 01b : OUT Select = 0 : Use HPF for INT1 to account for any incr gyro bias drift due to incr temperatureGyro_WrByte(GYRO_INT1_CFG, 0x20);      // OR Combination : Z-High EventGyro_WrByte(GYRO_INT1_TSH_ZL, 0x3b);   // Gyro_WrByte(GYRO_INT1_TSH_ZH, 0x02);   // Z-Threshold = 571(0x023b) * 8.75mdps = 5Deg/sGyro_WrByte(GYRO_INT1_DURATION, 0x8a); // WAIT Enable : INT Duration

After reviewing the website, we noticed that the LSM9DS1 is currently listed as obsolete. We would therefore appreciate your guidance on the following points:Is the LSM9DS1 still recommended for new designs, or should it be avoided given its obsolescence status?We understand that the LSM6DSO (https://www.st.com/en/mems-and-sensors/lsm6dso.html) is currently recommended. However, this is a 6-axis IMU. Our application requires a full 9-axis solution including a magnetometer.What is your recommended 9-axis solution today?Do you recommend pairing the LSM6DSO with a specific ST magnetometer device?If we implement a 6-axis IMU together with a separate ST magnetometer, do you provide a 9-DoF (Degrees of Freedom) fusion algorithm that supports such a configuration?Can your fusion algorithms (e.g., MotionFX or equivalent) run on any ARM-based MCU, or are they restricted to STM32 devices?Are there licensing requirements associated with using your fusion libraries?Are there any usage limitations

Hello, I have encountered some issues while developing with the  ASM330LHH. During the initialization sequence of the ASM330LHH interface, I first read the WHO_AM_I  register. After confirming that the value is correct, I proceed to access other registers. In my tests, the WHO_AM_I value read back was correct. After checking the datasheet, it mentions that DEVICE_CONF set 1 to enable configuration. Now, after reading WHO_AM_I and before accessing other registers, I set DEVICE_CONF to 1. When I test again, the value read back from WHO_AM_I becomes incorrect. Could you explain why this happens? I am using SPI for communication in both cases, and the SPI configuration has not be changed at all — I only added the DEVICE_CONF operation.

I am evaluating the MotionFX library for a 9-axis orientation project. To confirm our hardware selection and production path, I have three quick questions:MCU Lock: Is the MotionFX static library (.a) restricted to STM32 microcontrollers only, or can it be linked and executed on a generic ARM Cortex-M platform?Sensor Lock: Does the algorithm require ST-branded sensors (Accel/Gyro/Mag) to function, or can it accept raw data from any 3rd party sensor?Commercial Licensing: Is there a "per-unit" royalty fee for shipping MotionFX in a commercial product, or is it royalty-free for use with STM32 silicon?We need to know if we are "locked" to the STM32 ecosystem before we begin development.

Dear STMicroelectronics Support Team,I am currently working with the A3G4250D gyroscope and evaluating its temperature sensor output over I²C.According to the datasheet, the temperature sensor output change versus temperature is specified as −1 °C per digit. I would like to clarify one point regarding the absolute digital value.At an ambient temperature of 25°C, is there a specified or typical digital output value for the OUT_TEMP register? Or is the temperature output only defined relative to an internal reference without a guaranteed absolute value at 25°C?In other words, should we expect a specific digital code at 25°C, or is the temperature register intended purely for relative temperature measurement and compensation?Your clarification would help ensure correct implementation and validation during thermal chamber testing.

I'm using a LIS3MDL magnetometer on my board, and I figured out how to calibrate it to account for distortions  caused by the board, and the procedure works. However, it seems that every time the same magnetometer is turned off and re-powered, the measurements received are different. I saw somewhere that the LIS3MDL will self calibrate at startup and I think this might be what causes the differences. Is there any way to disable this process, and if that isn't the issue, do you know what it might be?

Hi everyone,I am developing a custom board using an STM32U5 and the LSM6DSV16BX. I am using MEMS Studio to train and configure the Machine Learning Core (MLC), but I noticed that the generated .h configuration file seems to set INT1_MLC1 bit at MLC_INT1 register by default.Even though I haven't explicitly set up physical pin routing in my project, the exported C array includes bank-switching logic that forces this configuration. I see the following sequence in my generated header:  { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x01, .data = 0x80 }, // Switch to Embedded Bank // ... [other configs] ... { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x0D, .data = 0x01 }, // MLC_INT1: Route MLC1 to INT1 // ... [other configs] ... { .type = MEMS_CONF_OP_TYPE_WRITE, .address = 0x01, .data = 0x00 }, // Return to Main Bank Because of this, INT1 pin is firing on MLC state changes. Since this is a custom design, I need strict control over my interrupt routing.My questions are:Can s

I'd like to validate ST1VAFE3BX vAFE measurement data against test signals as part of hardware design validation of a custom ECG sensor design based on ST1VAFE3BX. I intend to input reference signals (differential or single ended) into the two bio channels of the ST1VAFE6BX, capture the raw ADC data, convert to mV, and then compare to the reference signals.- Conducting this test will help validate the data processing, especially reading and interpreting vAFE data from the FIFO, which is different than if reading from registers.Are there any documents or guides for how to do such tests?Currently the vAFE waveforms I capture look correct except for the amplitude. 

Hello,I am evaluating the STMicroelectronics IIS2MDC magnetometer and measuring its supply current using a Joulescope. According to the datasheet, the device should draw approximately ~1.5 µA in idle mode, yet I consistently measure about 450 µA, which is far from the specified behavior.Test setup & observationsSupply: 3.0–3.3 V (also tested across the allowed 1.71–3.6 V range).Measurement instrument: Joulescope (µA resolution).Verified results across multiple PCBs and multiple IC samples.Tested the sensor stand-alone (no MCU connected, only power rails).Same behavior observed on the STMicroelectronics evaluation board.Datasheet behavior (expected)After power-on, the device performs a ~20 ms boot procedure to load trimming parameters and then enters Idle mode automatically.In Idle mode, most internal blocks are switched off to minimize power consumption, while I²C/SPI remain active.Idle mode is selected with MD[1:0] = 10 or 11 in CFG_REG_A.A single-measurement cycle (MD=01) perform

Hi Team,We have designed and manufactured several thousand PCBs that include the LIS2MDL (LGA‑12L) sensor. All boards are functioning correctly from an operational standpoint. However, because our devices run on battery power, load current is critical.We have observed a leakage current at the LIS2MDL power supply input, ranging from approximately 10 µA to 1500 µA. We are currently unable to determine whether the cause is related to the assembly process or the component itself.Notably, when we clean under IC to remove flux residues, the leakage current decreases significantly. While this confirms that contamination is influencing the issue, manually cleaning every board is not a feasible solution for our production scale.Could you please advise on possible root causes or provide recommendations to prevent this leakage issue without requiring manual cleaning for each unit?Your support would be greatly appreciated. 

Hello guys,I am using the STEVAL-MKPRO BOX, i want to use MLC with this box. For that i tried to log data(Accelerometer data) with BLE Sensor application. The data is stored inside the micro SD . I connected the SD card to my computer and saw that  it was a .dat file. I tried to convert it into a format which is compatible with ST Mems studio with stdatalog_to_unico.py in the stdatalog-pysdk but it is not working  .I also tried using the nb_stdatalog_converters.ipynb under how_to_notebooks section but literally only the cell with conversion to unico was not working, all the other cells were working. What can i do ?Thank you in advance

Hello,I'm using the IMP34DT05 microphone and it records fine but there is always a noise overlapped and it is very annoying.I have tried recording the background noise in anechoic chamber (see attached audio, high-pass filter alpha is 0.98). Do you know I to get rid of this noise? Is it related to microphone self-noise? Is there some processing library available from ST to remove such noise?Could it be related to some issue with the pdm2pcm conversion? I’m using 24bits on 32 frame. The PDM2PCM filter gain is set to 30.Best,

Hello Team,We are using SensorTile.box Pro, and the board has been successfully flashed with the DataLogExtended.bin firmware.However, we are unable to establish a BLE connection with the board, even after flashing the DataLogExtended firmware. The device does not connect via MEMS Studio / BLE application as expected.Could you please confirm if there are:Any known issues with BLE connectivity when using Data Log Extended on SensorTile.box ProSpecific firmware versions or configuration steps required to enable BLEAny additional setup or reset procedure needed after flashingKindly advise on how to resolve this issue.Thank you for your support.Best regards,Ahilesh