MEMS (sensors)

I am working with the X-NUCLEO-IKS4A1 expansion board and NUCLEO-F401RE.I’ve successfully programmed and run the examples provided by MEMS Studio and those in the STMems_Finite_State_Machine/application_examples/lsm6dsv16x repository. Additionally, I’ve used .ucf files and AlgoBuilder to generate C programs.But I have no idea how to program my own FSM from scratch. I have read some of AN5882 but I am not sure if that is the right way to learn about FSMs. Are there any tutorials I am missing?How do I implement my own FSM from scratch based on my own requirements and application? I would like pointers to some good tutorials with examples which explain how to program the FSM.

Hi ST technical support，Our product need to pass Certification, this certification requires thermal resistance of LIS2DW12TR, LGA-12 package, Certification body required write “thermal resistance” into datasheet or provide formal test report of thermal resistance. Otherwise, it will not be recognized. Could you please provide LIS2DW12TR’s datasheet with “thermal resistance”, or provide the test report of thermal resistance? Thank you very much. Best wishes,Susan

Hello, I am currently working on a project concerning the degradation of a rotary machine overtime. To detect this degradation, we want to study vibration using the IIS3DWB accelerometer which is on the STWINKT1B. Till now, I am taking 30 seconds of data "manually" every 2 days by using the ST BLE Sensor app. With those data I am checking the evolution of the spectrum to try to find a pattern.I was wondering if it is possible to make the acquisition process automatic and if yes how.For now, I am using the firmware FP-SNS-DATALOG2_Datalog2. I have very little knowledge in firmware programming so if you can use a simple language in your answer I would really appreciate it :) 

I recently began working on an driver software for a magnetometer application, which is intended to support both the LSM303 (the LSM303DLHC, to be exact), and the HMC5883L from Honeywell.And I didn't fail to notice that both devices have identical I2C addresses and identical values for the identification register values (IRA, IRB and IRC).My question would be, is this intentional ?Not that it is of utmost importance to me, I found another way to distinguish between both. The HMC5883 has no accelerometer part, and when I can write into a RW accelerometer config register and read the same value back, I deal with a LSM303, else with a HMC5883.

Hi everyone,We are using the STEVAL-STWINKT1B board as a reference for the study of condition monitoring applications.In particular, we have always used the board with the default firmware. For the configuration and acquisition of data on the SD card, the STBLESensor application was used (https://www.st.com/en/embedded-software/stblesensor.html)Instead, for reading and converting data, we used the FP-SNS-DATALOG1 function package (https://www.st.com/en/embedded-software/fp-sns-datalog1.html). In the specific case of microphones (both digital and analog: IMP34DT05 and IMP23ABSU), it is not possible to configure a different amplitude/volume by STBLESensor app; it happens that wh

I am working on ism330dlc to find gyroscope x, y, and z values. I am getting x, y, and z values. I am also getting variable x, y, and z values when the board is maintained constant. I wrote registers are 0x1204,0x1160,0x1060,0X22,0X23,0X24,0X25,0X26, and 0X27. Pleas

Hi all,We got odd issue with LSM6DSO32 IMU on our device. After like 6-10 hours of working it begins to not response correctly and it stays until completely power replug. Our code tries do reinitiate IMU when it happens, but within that "frezze" state it reads chip id as 0x00 using lsm6dso32_device_id_get (which we're using to determine which chip is on board) instead of 0x6C.We're using latest libraries from https://github.com/STMicroelectronics/lsm6dso32-pid Whole init sequence:imuSoftReset(); imuErr = imuReadID(&imuID); if(imuErr != imuOk){ return GRAVITY_VECTOR_INIT_ERROR; } imuErr = imuInit(imuID); if(imuErr != imuOk){ return GRAVITY_VECTOR_INIT_ERROR; } ------------------------------ void imuSoftReset(void) { uint8_t resetValue = 1; // Set the IMU's software reset bit and

Hi, stNow I've found some new problems.​Sometimes the value read from who AMI register will be 0x48. After finding this problem, I suspect that the connecting wire is unstable. After replacing the DuPont wire, the value read back to normal (0x6b). I want to ask what is the reason for this strange phenomenon.In addition, I found that the accelerometer data rate can only be set at 833hz or below. If the accelerometer data rate is set above 1667hz (1667hz,3333hz,6667hz), the value read from the register is still the previous value, that is, the data setting above 1667hz always fails. By the way, there is no such phenomenon in the setting of gyroscope.​

I just bought the latest SensorTileBox (STEVAL-MKSBOX1V1), can I add RTC to the Level function? I need timestamps added to the accelerometer output. Level Function is missing in the available functions under Custom Apps.

 We want to use iio buffers to read accelerometer data. I tried the following, but it did not work. root@FAFUSION:/sys/bus/iio/devices/iio:device2# ls buffer current_timestamp_clock events in_accel_scale_available in_accel_y_raw mount_matrix of_node sampling_frequency scan_elements uevent buffer0 dev in_accel_scale in_accel_x_raw in_accel_z_raw name power sampling_frequency_available subsystem waiting_for_supplier root@FAFUSION:/sys/bus/iio/devices/iio:device2# cat name ism330dhcx_accel root@FAFUSION:/sys/bus/iio/devices/iio:device2# root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_x_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_y_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_z_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > buffer0/in_accel_x_en root@FAFUSION:/sys/bus/iio/devices/iio:devi

Hi All,My name is Stefano, and I developed firmware for an embedded sensor that integrates the LIS2DW12 MEMS accelerometer. We encountered the following issue:At the end of the firmware development, we tested the current consumption across many of our new sensors, and the results were as expected;The new firmware was then put into production;After a few months, we noticed that some sensors had a lower-than-expected battery level, despite their typical lifespan;We retrieved those sensors from the field for analysis;Upon analysis, we discovered that the issue was due to abnormal current consumption by the sensor, with an average current (Iavg) of approximately 300 mA instead of the expected 7 mA;The sensor's current consumption returned to the normal range when the firmware powered off the accelerometer;After extensive investigation, we determined that his abnormal consumption is due to the resin

I am reaching out regarding an issue I am experiencing while reading register values from the ISM330DLC sensor using a Python script over SPI. Specifically, I am encountering incorrect data when accessing certain registers.For example, when reading the WHO_AM_I register (0x0F), I receive a value of 0x7F instead of the expected 0x6A. This discrepancy suggests there may be an issue with the communication setup or the sensor response.Here is a brief outline of my setup and process:Hardware:Raspberry Pi 5 connected to the ISM330DLC via SPI.Correct wiring verified (VDD, GND, SCL, SDA, CS).Software:Python with spidev library for SPI communication.SPI mode set to Mode 0 (CPOL=0, CPHA=0).SPI clock speed: 1 MHz.Code Snippet:import spidev spi = spidev.SpiDev() spi.open(0, 0) spi.max_speed_hz = 1000000 spi.mode =

Hello ST Forum,I am currently working on a project that aims to help surfers analyse their surfing sessions. The goal is to use a LSM6DSV16BX attached to a surfboard, using the IMU to analyse the board's movement, and one of the QVar channel to detect whether the board is put in water.I was wondering about how to use the second QVar channel. In particular I was wondering if it could be used to detect the presence of the surfer on the board without contact.In the August 2022 revision of AN5755, the document states that using a single electrode is recommended for presence detection, especially in cases where powerline noise is weak, which seems to be my use case. However, the surfer and his/her surfboard will be immerged in seawater. Do you know if it is possible to detect human presence in these conditions ?Additionnaly, since QVar channels seem designed to be used differentially, do you know if I can use one channel to detect if the device is in water, and

I need the thermal resistance Junction to Ambient for LIS2DH12, LGA-12 package. 

Hi. I have both the ST1VAFE3BX and the X-NUCLEO-IKS4A1 and I'm trying to read data from the biosensors using MEMS-studio, but I don't see how to get MEMS-studio to recognize the biosensors.  The documentation for the biosensors has instructions for working with the ProfiMEMS tool (a different motherboard).  In that documentation, it shows that there are biosensors. The docs for the ST1VAFE3BX also indicate that it will work with the IKS4A1 but it's not obvious to me how to make MEMS-studio "see" the biosensors as a data source.any help would be appreicated.TIA.-Rich 

We are designing an STHS34PF80 into an occupancy sensor and the plan is to have an HDPE window to protect it.  To test the response in the actual product we purchased 1/16" (1.5mm) HDPE sheet and put it over the sensor.  The fresnel lens with the dev kit was removed.  Surprisingly the Tpresence triggers when the sheet is over the sensor, and so the device doesn't seem to be seeing through the HDPE sheet.My first thought is that the HDPE is doped or just wrong somehow but I thought I'd ask if anybody else has seen something like this.Thank you.

Hi all, I am currently working with the STEVAL-PROTEUS1 Board, which incorporates the STM32WB5MMG module and the IIS3DWB high-bandwidth accelerometer sensor, interfaced via SPI_1. According to the IIS3DWB sensor datasheet, it supports a clock frequency of up to 10MHz and an Output Data Rate (ODR) of 26667Hz (37 microseconds). My objective is to collect sensor data at an ODR of 26667Hz. Here are the steps I have taken so far: Configured the core to 20MHz. Configured SPI_1 to 10MHz. 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 125 microseconds using HAL functions in blocking mode. Ideally, this should not be the case. I have also tried using non-blocking mode (DMA), but it is taking more time (175 microseconds). Could anyone help me understand if the HAL function i

Hi,I recently bought a SensorTile(STEVAL-STLKT01) and I want to modify the default project for my own usage case.Based on the information I found, I downloaded the source code from https://www.st.com/en/embedded-software/fp-sns-allmems1.html (Github source) and then I opened the project "STM32L476JG-SensorTile" with CubeIDE Version: 1.17.0 and then I tried to build this project without any modifications.The first problem I encountered is that the defined variable "STM32L4xx" seems not exist so I have to add it manually into the path and symbol property:

Hello,for a new project we are avalutaing the use of an iNEMO inertial module in conjunction with the motion fx library with the goal of doing position estimation with dead reckoning.My doubt is about the library, since we are forced to use a thrid party MCU (an ARM M4), can I import the library on any ARM M0/M4/M7 mcu? Or does it target ONLY st devices?Thank you,Davide

Hello,I searched the forum and found out a topic regarding the sensing technology of LIS3MDL sensor. The topic mentioned that LIS3MDL is a TMR sensor, however no support documents are included to further investigate the integrated circuit of the sensor.Moreover, I found several studies/papers claiming the LIS3MDL is an AMR sensor.My question is: Is there any official document available regarding the underlying sensing circuit and phenomenon the LIS3MDL sensor is using?Thank you for your time and support.

Hello,can anyone tell me what I am doing wrong?For example, I can't get app_mems.c (eCompass) to debug.The debugger does not stop when I set a breakpoint on subsequent function calls because, for whatever reason, the “SensorReadRequest” always has the value 0.:RTC_Handler(&msg_dat);Accelero_Sensor_Handler(&msg_dat);Gyro_Sensor_Handler(&msg_dat);Magneto_Sensor_Handler(&msg_dat);Humidity_Sensor_Handler(&msg_dat);Temperature_Sensor_Handler(&msg_dat);Pressure_Sensor_Handler(&msg_dat); I also need direct access to the variable “heading”. 

We have an issue with LSM6DSM and LSM6DSV. Sometimes they start consuming abnormally high current of 2.5 mA, which is about 200 times more than normal. Most reliably this can be reproduced when their SPI clock input pin 13 is driven by a week 47k pull-up / pull-down resistor.It seems that LSM6D becomes unstable and begins to oscillate. This happens when LSM6D is in any operation mode: in a full shutdown mode just after cold start, in a low power mode, any SPI speed, I2C disabled, etc.The reason why we drive SPI clock input by a week 47k pull down resistor is that LSM6D suppose to wake up the STM32L496RGT6 MCU from the shutdown mode. In the shutdown mode, the STM32L496RGT6 has only a week pull up/down option to drive its pins. But the voltage on the LSM6D SPI clock input pin 13 is about 7 mV and hence is well below the required logical 0 level. Documentation does not mention clock driver impednce and neither SPI nor I2C standards require low impedance input drivers

I am trying to use the DATALOG1_V1.1.0\Utilities\Python_SDKWhen I call the script hsdatalog_data_export I get an error: "No module named 'click'What to do to make these scrpits work? Pyhton is V3.7.8

Posted on October 16, 2016 at 11:59The LIS3DSH has a three channel 10 bit A/D converter but I can't find any information on it. What is the accuracy? (I could tie one channel to a voltage reference for calibration if necessary) What is the input voltage range? What is the maximum input current? (will I need to buffer the channels) #lis3dsh

Hi, community,   I have a bespoke board running an rp2040 and have been coding the LSM6DSO from the spec, along with using web-found python and cpp examples as starter code. There are several things I haven't found enough detail on and would like help.  1. if I read 2 byte temperature from the fifo data address, do I have to still read the full 6 bytes from the fifo data register and toss the 4 unused bytes, to keep the fifo syncronized with 6 byte data reads? Or can I read 2 for the temperature tag, then read 6 on the next gyro or acc tag? 2. how do I uncompress compressed data from the fifo? The only reference I could find leads to a dead URL. And same thing, if compressed, do I still need to read 6 bytes? Related to that, the driver cpp code on github seems to be empty, as if it was once there but was removed. 3. How do I decode the fifo timestamp info? thank you,   bob s