MEMS and sensors

Hello everyone. I'm a beginner to STM32 and STWIN. I'm experimenting with the DATALOG2 firmware on STWIN.My question is about customizing this firmware. What I want to do is keep the DATALOG2 functionality as-is, but add an extra feature: when the accelerometer value exceeds a certain threshold, output a High signal on a GPIO pin or turn on an LED.(I couldn't find any GPIO pins in the STWIN schematic!) STEVAL-STWINKT1 https://www.st.com/en/evaluation-tools/steval-stwinkt1.html   The firmware is here.GitHub : FP-SNS-DATALOG2 Firmware Package https://github.com/STMicroelectronics/fp-sns-datalog2     Since my development environment is STM32CubeIDE, should I open the .project file within the following STM32CubeIDE directory in the GitHub using CubeIDE and modify the source code there? https://github.com/STMicroelectronics/fp-sns-datalog2/tree/main/Projects/STM32L4R9ZI-STWIN/Applications/DATALOG2/STM32CubeIDE

In HTS221 sensor I have issue that H0_T0_OUT and H1_T0_OUT, H0_RH and H1_RH value is same like belowT0_degC float 20.5T1_degC float 52.5T0_OUT int16_t 1028T1_OUT int16_t 0H0_RH float 29.5H1_RH float 29.5H0_T0_OUT int16_t 0xf7f7 (hex)H1_T0_OUT int16_t 0xf7f7 (hex)This is my codeInit functionuint8_t HTS221_Init(HTS221 *hts221, I2C_HandleTypeDef *hi2c) { hts221->hi2c = hi2c; uint8_t data[2]; if (HTS221_ReadRegister(hts221, HTS221_WHO_AM_I, data, 1) != HAL_OK) { return 1; // Error reading WHO_AM_I register } if (data[0] != HTS221_WHO_AM_I_VALUE) { return 2; // WHO_AM_I value does not match expected value } // Read calibration data if (HTS221_ReadRegister(hts221, CALIB_0, data, 2) != HAL_OK) { return 3; // Error reading calibration data } hts221->H0_RH = (float) (data[0]) / 2.0f; // H0_rH_x2 hts221->H1_RH = (float) (data[1]) / 2.0f; // H1_rH_x2 if (HTS221_ReadRegister(hts221, CALIB_2, data, 2) != HAL_OK) { return 4; // Error reading temperature calibration data

The SDDataLogFileX example stores the wave file for the digital microphone but in the following docs it wrongly say that it store for the analog microphone :UM2626 at pages 15 (2.1.5) and 30 (2.2.6)FP-SNS-STBOX1_Quick_Start_Guide at page 27

Hello everyone, I plan to use the LPS28DFW barometer to measure the final pressure after a drop from 30 atm. I only need to sense the final pressure within the sensor’s specified working range, but I’d like to know whether exposure to the initial 30 atm would cause mechanical damage to the device. Or, at what pressure can I expect the sensor to break?Thanks!

My partner and I are creating an app designed for P2P as well as traditional user/vendor interaction. We need a wearable that can create a mutual event on the back end when the two wearables touch or are in close proximity. I see the ST25R3916 or STM32 chips may be suitable but wondering if there’s already a wearable with these capabilities or if one can be designed/created that’s suitable for kids. I also see there’s a wearable - STEVAL-WESU1. Can the STM32 be used in the WESU1? I have additional requirements, like haptics, visual indicators, etc, that I can provide info on but I can’t find a wearable that can create a P2P event. Any help is appreciated

..

I have a question regarding how the averaging filter works in the LPS28DFW pressure sensor (AVG[2:0] in CTRL_REG1).I am wondering whether:A) AVG controls internal ADC oversampling for each individual pressure measurement (i.e., multiple internal samples averaged to create one output sample),orB) AVG performs a moving average across multiple output samples after they are generated. In other words, does the AVG setting reduce noise by oversampling within one output period, or does it smooth several consecutive output samples?

I designed a small PCB for LSM6DSV but I got no signal on SPI-MISO and got NACK on I2C-SDA.I have replaced several chips but all the chips have the same behaviour(no signal reply).I'm very sure the SPI and I2C pins are correctly connected to LSM6DSV.(1)Custom PCB designThis is the PCB design of my custom board. All the net label are connected to pads on board. Never mind "LSM6DSOTR" in the schematic. Actually I soldered LSM6DSV on board since LSM6DSV has the same chip package with LSM6DSO.VDDIO and VDD are 3.3V and this board shares the same ground with stm32.(2)SPI communication issueSPI_SCK and SPI_MOSI signal is correct but SPI_MISO has no signal.I configured STM32H743XIH6 SPI in STM32CubeMX like this. No NVIC, no DMA.I implemented the SPI polling read/write function for official ST LSM6DSV driver code. int32_t lsm6dsv_spi_read(void* handle, uint8_t reg, uint8_t *data, uint16_t len) { reg |= 0x80; LL_SPI_SetTransferSize(handle, len+1); LL_SPI_Enable(handle); LL_SPI_StartMas

Hi i have a custom lsm6dsv  module  that is getting  a strange result  after 6a 9c then cycles through  int of the imu 9c seem to make it restart its process  and loop it for a for until 6a is back and 9c comes back and does the exact  same process   and unsure  what i should look at next [ i am new to logic  analyzing oscilloscope   scopes signals  seem fine  i feel like im missing  something  badly  Parts 100nf caps 5.1k resistor  tired  10k but I thought  lower  them could solve it? Before  I do anything  dumb I need input on what could cause this i can also provide logic files from pulse veiw Thanks   

Please tell me about the STATUS_REG for ASM330LHH. I'm using SPI communication. A similar question was posted earlier, but the situation is slightly different.When I ran the same program on 30 board-mounted samples, 29 of them showed a change in STATUS_REG within 400ms after the ASM330LHH setting, but one remained 0 without any change.I'm guessing from this that is not a sowtware problem, but I would appriciate a list of possible factors as the cause.

Hi Team,  We are working with the LSM6DSOX sensor and integrating it with two different MCUs: nRF5340 and ATSAMD51, using the I2C communication protocol. We have been able to successfully read the device ID, accelerometer data, and gyroscope data. Additionally, we've implemented our own logic for step detection and step counting. Recently, we learned about the Machine Learning Core (MLC) feature, which provides useful capabilities like detecting activity states (idle, walk, run). We obtained the .ucf file for MLC, used the UNICO tool to generate the corresponding .h file, and attempted to integrate it into our application. We followed the documentation and tried monitoring the MLC_STATUS (0x70) register to track activity states. Challenges faced: First Attempt with nRF5340 MCU: Initially, we tested the MLC functionality with the nRF5340 MCU using I2C communication. However, when we read the&nbsp

Hello, I am working on adding a pedometer to the Sensorwatch project using this chip.I have the step counter working well, and I also have it working with the LIS2DW. Here's a video of it :)The LIS2DW works by sending 12.5Hz worth of data from its FIFO every second to the host uC, which runs an algorithm to count the steps.I am finding with a Nordic Power Profiler that the LIS2DUX uses about 6uA to run the step counter.The LIS2DW uses nearly 15uA.But I found that I can heavily lower the battery-draw of the LIS2DW by only reading the FIFO and performing the math only if more than 0.06G is seen, which is seen by an interrupt signal, whic make sthe current draw for 90% of the day to be close to 1uA.Can anything be done with the LIS2DUX to bring it closer to that efficiency?The goal of the project is to only need to replace the battery once a year, which means that we'd want no more than an average 2uA draw from the chip. Questions:1) What is the most battery-efficient

Hi,according figure 3 in the datasheet, the pin in the middle (let's name it pin 11) is connected to GND, but this pin is missing in table 1.The linked technical note TN0018 advises to avoid any GND/copper/via below the IC (Figure 12).The eval board STEVAL-MKI220V1 has a pad for pin 11 but the pad is left floating.The SamacSys-symbol/footprint contains this as Pin 11 / GND_3I see multiple contradictory solutions:1. no pad for pin 11 in the footprint, pin 11 is left floating (complies with TN0018, but contradicts eval board, SamacSys-footprint and maybe the datasheet)2. add a pad for pin 11 in the footprint, but leave the pad floating (violates TN0018, but complies with the eval board)3. add a pad for pin 11 in the footprint, and connect the pin to GND (violates TN0018 and eval board, but seems to be suggested by the datasheet)What is the correct solution?RegardsBjoern

Hi everyone,I am using LSM6DSL IMU sensor for my project.  The LSM6DSL embeds a digital Slope filter. Is there any method to configure the "Slope filter" ?

Hello, I have a VL53 sensor that's outputing distance data but the distance measurements I'm getting are getting "stratified" into about 3 different distances seemingly randomly. I'm using the ULD driver on a custom PCBA with a TM4C1239 microcontroller and sampling the sensor at 10 Hz. This first video is with no obstacle in front of the sensor. You can see the data is not consistent This second video is with my hand about 10 cm away from the sensor, then approaching and retreating the sensor. You can see the data jumping between a few discrete distances even as I approach and retreat from the sensor Does anyone have any suggestions as to why this may be happening? 

We are feeding Gyro/Accel uncalibrated into motionFx as per app note UM2220 (getting started with sensor fusion). The app note says one does not have to feed calibrated and the library does gyro calibration on the fly. We have been seeing some drift issues in readings and as part of investigations have tried to use the "start_automatic_gbias_calculation".The get knobs seems to be returning gyro th 0.007, acc th 0.0028 and mag th .0008; this is just after the library initialisation; just reading the defaults. If we then run sensors and fusion for 10 seconds and read back these knobs we see no change in the values.Where does the library get the values of these thresholds?I was hoping to see a change in the values between library inititialisation and 10 seconds after firing up imu / fusion.At 10s on reading the knobs we have these values...Atime 0.899Mtime 1.5Frtime 0.667Lmode 1gbias_mag_th_sc 0.00079999gbias_acc_th_sc 0.0006999gbias_gyro_th_sc 0.00279acc_orinet nwugyro_orinet nwumag

I performed a temperature cycle check on the ASM330LHB chip. Relative to the warming process (red curve), during the cooling process (blue curve), it is prone to large zero-bias jumps (in the red box of the picture)。 The jump during the cooling process, I feel like there is a correction mechanism in the gyro in the chip, which recognizes a large shift in the gyro zero bias during the cooling process, and then immediately corrects the large zero bias shift.Can you please help explain what causes this?Note: These data on the image have been smoothed for 10 seconds.   

Datasheet 4.5 Maximum value for Symbol Vin in Absolute maximum ratings is 0.3 to Vdd_IO +0.3, should it be -0.3 to Vdd_IO +0.3?

In the datasheet of LSM6DSV80XTR maximum junction temperature is not mention. Maximum junction temperature is required to do the thermal calculation. please any guidance how to obtain the maximum junction temperature till which this IC can work safely. 

Hi there, I'm trying to program LSM6DSV80x to read sensor values in -500Hz for a certain period of time and send them for process (thus no realtime process, but need timestamps).  The sensor values include xl, hg_xl, gyro, and also Game rotation vector, gravity calculated by SFLP.  According to the use case, all values will be read through FIFO.  Mostly works well but I've come up with two questions.  - What timestamp means? Is it time of the latest FIFO entry,  or of the next FIFO entry, or irrelevant with other entries?- for game rotation vector, I got two consequtive entries having TAG=19 in FIFO everytime,  at the same timing.  Those two entries have completely different values. With the application note and the post in this forum, I understand the FIFO  entry for game rotation vector hold only x, y, z elements and w needs to be calculated at the host side.  For example (the order is, w - which I calculate, x, y, z):LSM6DSV80X_

I ordered one of these evaluation boards (https://estore.st.com/en/steval-mic003v1-cpn.html) and by the time I got it and went back to check the documentation now this microphone, and all other MEMS mics, are listed as "Not Recommended for New Design". Couldn't find anything about these being discontinued on the news section of ST's website so I'm asking here if this is a website glitch or should I look for a different source? And if the latter, does anyone have a good line on something comparable to replace these in a design? https://estore.st.com/en/imp34dt05tr-cpn.html 

Hi, I am using the LSM6DSV16BX IMU on a project where I need the Game Rotation data.I used the Github examples as a base, and reading the Game Rotation values works well and I am able to save the quaternion data in a file. I wrote a little script that takes the Game Rotation quaternion values and applies the orientation to an object, to mimic what is possible in Unico GUI with STEVAL-MKI234, however I do not get the same performance with my custom board. For instance, I sometimes get some weird rotations around two axis even though I rotate the device around a single axis. See video:I was wondering if any special setup was required to achieve this kind of performance ? Is there any calibration that can be made ?I configure the Accelerometer and gyroscope to 960Hz, but batch samples of Accelerometer, Gyrometer and Game Rotation data at 120Hz in FIFO. I realize this is not much information to try and help me, I am more than happy to provide more detailed information if needed,

Hello,Can the IMP23ABSUTR sensor go through a vapor phase oven?"Thx.  

We're looking to use the lsm6dsv320x in our product. I'm using this senser on the on the STEVAL-MKI247A adapter board for testing. We're currently in development using the adapter board with the Nordic nRF52840DK board. I'm having issues with getting the correct value from the WHO_AM_I with certain SPI pin configurations on the nRF52840DK. I can only get one SPI configuration to output the correct value of 0x73 which is SPI1. If I try change the pins or use one of the other SPI's available on the 52840, I consistently get a value of 0x64. Does that value mean anything to anyone? I've tried lowering the frequency to 500kHz, tried all four of SPI modes, I've tried performing a reset using the FUNC_CFG_ACCESS and CTRL3 registers before reading the WHO_AM_I register, but I still get the value of 0x64 except with the one configuration mentioned. I'm using the ST fsm_example for this test. We would like to change the SPI pins as the we want to use the smaller package of the nRF52840 which do

MEMS studio is working perfect on windows 11 and another windows 10 machine. But it is not working on one windows 10 pro laptop. Kindly guide what can be the reasons.