MEMS and sensors

We are currently experiencing issues with the LPS28DFW.We observe pressure values dropping to 0 or even negative ranges (e.g., around -400 mPa), as well as unexpectedly high values (up to approximately 1200 mPa), while the expected range should be around 950 mPa. We are also seeing abnormal temperature outputs, including unrealistically low values (e.g., around -400°C).this happens when the sensor is in contact only with air and also when it is in contact only with water. When the sensors from the field they are brought back in the lab the sensors seem to recover on their own and return to normal readings.

Hi,I'm using the LIS2DUXS12 in FIFO Stream mode with DEC_TS_32. FIFO watermark is set to 64. Looks like every ~17 FIFO reads (~1055 XL samples), exactly 1 accelerometer sample is lost. The pattern is consistent and repeatable.Each FIFO read of 64 entries normally contains 62 XL samples + 2 timestamp tags. However, every 17th read contains 63 XL + 1 timestamp tag. Looks like before this batch with 63 XL samples, there is 1 XL sample gap in data.I use only the timestamp present in the FIFO batch to calculate timestamp for each sample. And with that approach samples in that FIFO batch aligns with next FIFO batch exactly - no gaps, no overwriting, fixed period. So despite the fact that this FIFO batch contains one XL sample more than the other, there's still a gap in data. Configuration:- ODR: 200 Hz (HP mode)- FIFO mode: Stream (continuous)- bdr_xl: ODR- dec_ts: DEC_TS_32- xl_only_fifo: 1-

I've installed MEMS Studio v2.3.0 and trying to evaluate ST1VAFE3BX sensor -- in particular the vAFE ONLY operation in FIFO mode -- using the STEVAL-MKI109D evaluation board with STEVAL-MKI250KA evaluation kit plug-in module. Previously I had MEMS Studio v2.2.0 installed and that was working. I've just updated to v2.3.0 and now the setup is not working.- I did update the FW on the MKI109D board; MEMS Studio indicates "FW: 2.6.17".- I see a tiny fraction of a second of data in the plot window, and then nothing.- The pink "Run" button becomes grayed out/deactivated.- Most options typically under the "Sensor Evaluation" panel disappear. How do I use MEMS Studio to evaluate the ST1VAFE3BX sensor in "vAFE only" mode?

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.Wha

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 cons

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

Can you increase the delay between Start and end frame packets.I want to make sure there's enough time for it to be detected with the STM32N6. Registers i've tried to use.  * VSYNC_START_DELAY - is for gpio output* FSYNC_IN_DELAY - not sure what it does  VD56G3 cam End frame packet.  

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

Hi, i am a student using the VL53L0X time of flight sensor for a final project. I am having trouble getting the sensor data to settle the measured distance is very jumpy and out by 6 cm when measured with s ruler. how would i calibrate the sensor to stop jumping around and spit out the correct distance?. I am plotting distance vs time in MFC visual studios. the resolution of the sensor is + or - 1mm and i am out by 6cm. 

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:

Hi, I'm using the image sensor evaluation kit with STEVAL-66GYMAI, STEVAL-EVK-U0I and the PC software of STSW-IMG501 to capture video stream. I would like to change the setting of MIPI lane from default dual-lane to single-lane operation. But, I failed to change it, so please tell me how I can complete to change the setting. I tried to change the MIPI lane setting by changing the register value of OIF_CTRL at 0x030c. I changed the register value via the PC software from 0x0082 to 0x0081 in accordance with the VD66GY manual. The ROI size, the frame rate and the MIPI data rate were set at 288x288, 12 FPS and 1500 Mbps, which seemed to be enough for single-lane operation. The frame rate was adjusted by changing LINE_LENGTH register. However, I couldn't get the video stream. The excution rate displayed on the top left of the PC software window was 0.5 in streaming, and any picutures were not shown on the PC software.  I could

Any way how can I get in touch with ST on availability on this product? We would like to implement this into our devices, a devkit or hardware preview would help, we had previously integrated with the VL53L8 and VL53L5 which the result are good, and with the release of VL53L9, it will produce even better result for 3D mapping. ThanksVince 

I'm trying to figure out how to make a driver for your camera. The problem seems to be the licensing. The driver is all GPL which would be fine because with the datasheet i could figure out all the calls i need to make my driver work on a non linux device. The problem is the patches. The only place i can find about the patches are on the github driver page. Are they located another place thats not under GPL.* https://github.com/STMicroelectronics/vd56g3-linux-driver

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):

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 represen

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

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

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.

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

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., Motion

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.

Hi, just wondering if these constants (specifically NONE and OR both being 0) in the ULD for VL53L8CX are correct#define VL53L8CX_OPERATION_NONE ((uint8_t)0U) #define VL53L8CX_OPERATION_OR ((uint8_t)0U) #define VL53L8CX_OPERATION_AND ((uint8_t)2U) it look like it should be a sequence (0, 1, 2) so the repeated (0, 0, 2) appears out of place. It's hard to tell from the examples if this is intentional though.

I`m doing project using connection of Pololu VL53L7CX multizone sensor to STM32 NUCLEO-F103RB. It`s my first expirience with that. I would like to ask more experienced developers for help and, if possible, an example of the code. Thank you!