MEMS (sensors)

I designed a fsm Design for high G application. The odr of high G and fsm are same. The said functionality is generating interrupt when done on eval kit Nucleo board with iks4a1 kit in Mems studio. But when I converted it into header file and loaded in another sensor board with lsm6dsv320. It is not working. Earlier Free fall Fsm was done on same sensor, it worked both in mems and on this sensor board. I have called the fsm load function and enabled the embedded interrupt in MD2_CFG as I am generating interrupt on int 2. Odr and range settings of high G have been done seperately. What can be the reason of non functioning. 

Hi,everyone.I measured the power consumption of LIS2MDLTR on the same board in power-down mode.and found that the LIS2MDL chip on STEVAL-MKI217V1(from mouser) consumes less power than the LIS2MDL purchased separately from mouser.We have some question and need your help.​ What is the power consumption LIS2MDL in power-down mode ？  Why do the parameter differ between LIS2MDL chip on STEVAL-MKI217V1 and LIS2MDL purchased separately？

I have previously used a large quantity of LSM6DSV16XTR products from batch 426, and their data was completely normal. My device utilizes 16 gyroscopes simultaneously. Recently, I started using products from batch 509, and they have exhibited a peculiar phenomenon. Specifically, it includes two parts: (1) When the temperature slowly increases from -40°C to 85°C, observing the data of a gyroscope at rest, some gyroscopes show data jumps at certain temperature points (the jump temperature point varies for each gyroscope). For example, the data may jump from -0.98°/s to -0.08°/s. (2) For the same gyroscope, at the same temperature, the bias data varies significantly at different times. This phenomenon does not occur in every gyroscope, but it greatly troubles me because I cannot record and compensate for the bias data in the temperature chamber, as these biases have become highly irregular. This phenomenon did not occur in batch 426. Does anyone know why this is happening?

Hi,I'm trying to write custom firmware for the MKI109D. I am currently using an MKI251A adapter board with it for evaluation. How do I set VDD_DUT and VDDIO_DUT to 3.3V on the MKI109D board without using MEMS Studio?   

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, In the datasheet of the gyroscope I3G4250D, page 21:CS: 0: SPI communication mode / I2C disabledMy question is: I have to configure the CS pin PE3 as Low at the beginning to make the gyroscope understands that I wants to use SPI? (PE3 is CS in the KIT STM32F411 Discovery) 

Hello, I am currently reading the ASM330LHH May 2020 DocID031239 Rev 4 datasheet and its Chinese version: ASM330LHH: Automotive Inertial Module Digital 3D Accelerometer and Digital 3D Gyroscope User Manual. During the design process, I have a few questions to confirm: Question 1: For CTRL9_XL (18h), when should DEVICE_CONF be set to 1 and when should it be set back to 0? Do I need to set DEVICE_CONF to 1 first before performing any write operation on any register of the ASM330LHH, and then set it back to 0 after all register write operations are completed? If DEVICE_CONF is never set to 1, what impact will this have? Will the written register values fail to take effect? Question 2: In the Chinese version of the ASM330LHH User Manual, Table 8. Accelerometer Samples to Discard, Table 12. Gyroscope Samples to Discard (LPF1 Disabled) and other tables all mention the term "number of samples to discard". What does this mean? How should I handl

Hello,My goal is to test the IBI functionality of my custom I3C master driver using the LSM6DSOX sensor. For this test, I need the Linux I3C slave driver for LSM6DSOX with IBI support. The file linux/driver/iio/imu/st_lsm6dx/st_lsm6dsx_core.c does not contain any IBI-related code, such as i3c_device_request_ibi. If anyone has an example or code for using IBI with I3C in a Linux environment, could you please share it?. 

Hello,I intend to put LIS3DH and LSM6DSV32X on same SPI bus and use different CS lines to address them separately. But when the CS is desactivated, these components activate their I2C engine, therefore leading to possible conflicts of I2C interface on the SPI bus.For LSM6DSV32X, the datasheet states that I2C can be deactivated by setting to 1 the bit I2C_I3C_DISABLE of IF_CFG register.For LIS3DH, iy is said here (https://community.st.com/t5/mems-sensors/use-lis3dh-on-the-same-spi-bus-as-an-eeprom-is-it-possible/td-p/427285) to write 0x80 on address 0x17 to desactivate I2C on LIS3DH.Question 1: this method for LIS3DH is not officially documented in the datasheet, nevertheless, is it an official and safe way to deactivate the I2C bus ?Question 2 : If I deactivate I2C on LIS3DH and LSM6DSV32X, is it a

I'm using a STEVAL-MKI109D with the IR sensor STHS34PF80 and I need to fine tune it to detect objects with low IR emissivity, but everytime I want to load the log file into the IR Algorithm Tuning, the same error appears "Failed to parse log file". I've tried modifiying different things from the log, but everytime, I get the same error. Here is an example of a log file:# STEVAL-MKI231KA (STHS34PF80)time[us],t_object[LSB],t_object_comp[LSB],t_ambient[C],t_ambient_shock[LSB],t_ambient[LSB],t_ambient_shock_flag,motion[LSB],presence[LSB],presence_flag,int_1638,-614,-614,23.470,0,2347,0,0,0,0,0638,-671,-671,23.540,0,2354,0,0,0,0,0729188,-641,-641,23.490,5,2349,0,0,0,0,01736289,-659,-659,23.440,9,2344,0,15

On platforms like LCSC and Mouser, an IMU labeled "LSM6DSVQTR" is listed separately from the LSM6DSVTR. On JLCPCB, the LSM6DSVQTR has considerably more stock than the LSM6DSVTR and is eligible for the "economic" PCBA service, unlike the LSM6DSVTR.Do these IMUs have any meaningful differences, or can they be used interchangeably? If they do have differences, are they documented anywhere?

Hello everyone,I am interfacing ADXL345 in stm32f103c8t6 by using I2C connection. I have fixed the set up on a board. I would like to know if I can identify the movement of adxl by observing the changes in x, y, and z values if there is no vibration but the board is moving smoothly, that is, to the right or left. If not, how can I predict when the adxl will go forward or backward without relying on the sensor's tilt or vibration? I just want to create a basic activity detector where the logic would be :1. If the setup does not move, the output should be zero.2. If the setup is vibrating and moving, the output should be one.3. If it is simply vibrating (and not moving in space), the output should be 0.So, basically, I want to detect actual mov

Greetings,I am bring up a new HW design with the IIS2DLPC accelerometer integrated into the design.I am trying to bring up a Linux IIO device driver for this device, and the kernel does not currently have direct support for the IIS2DLPC, however it does support the LIS2DW12, which from looking at thedatasheet for both, they appear to be SW compatible.Can I just code the device tree node to specify the LIS2DW12?accelerometer@18 {compatible = "st,lis2dw12";reg = <0x18>;status = "okay";st,drdy-int-pin = <1>;interrupt-parent = <&sysfpga>;interrupts = <SYSFPGA_INT_ACCELEROMETER>;interrupt-names = "ACCELEROMETER-INT1";};Thanks,Ken 

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 STM32

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_

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,I am trying to get the STHS34PF80 sensor working on an STM32L0 platform via I²C. My initialization sequence is as follows:Algorithm reset according to AN5867:CTRL2 (0x21) = 0x10 // FUNC_CFG_ACCESS = 1 PAGE_RW (0x11) = 0x40 // FUNC_CFG_WRITE = 1 FUNC_CFG_ADDR (0x08) = 0x2A FUNC_CFG_DATA (0x09) = 0x01 PAGE_RW (0x11) = 0x00 CTRL2 (0x21) = 0x00Interrupt configuration:CTRL3 (0x22) = 0x05AVG_TRIM:0x10 = 0x01Continuous mode:CTRL1 (0x20) = 0x15 (BDU=1, ODR=4 Hz according to datasheet)

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

Hello, I'm using (ISM330DHCXTR) accelerometer to calculate the phase difference between two axes to measure the movement of a system. configured ODR at 6.6 KHz and measured the operation frequency of the system which has a 10% error while measuring the FFT and adjusted the ODR on the math lab logic to match the operation frequency of the system but still the phase difference has a major deviation, can someone confirm what is the ODR deviation on this sensor and how to correct the same on the firmware instead of modifying on the paired application.  

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.

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&nb

Good day,I came across the "STAR1 reference design". The document is a few years old. I am trying to find components so that I can reproduce the reference design. Can someone please help me to find the component: mirrors, drivers, ST piezo mirror evaluation kit, waveguides. Thank you in advance.URL for STAR1: https://www.st.com/content/dam/ces23/pdf/laser-beam-scanning-presentation-ces-2023.pdf

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.