MEMS (sensors)

Hello,I am developing a board with the LIS2DUXS12 accelero.During testing after assembly, I saw that there was no reaction to I2C communication. Other devices on the bus work fine, with a logic analyzer I have seen that there is indeed traffic sent to 0x18. I desoldered the component and saw that during assembly, was too little paste on the VDDIO and the SCL pin. I corrected it and resoldered the component and saw there was good contact under the microscope. I have connected the STEVAL$MKI235AA to the pins and that responds correctly.I still see the same behavior, so my first question is this:1. Are VDD and VDDIO completely isolated from each other such that VDD won't internally be connected to VDDIO in the event of a bad connection to VDDIO, the digital interface pins are in danger of being damaged?2. I also am looking for a sanity check of my schematic. I have only 1uF + 100nF on the supply as 10uF seems extremely overkill for

Is there any noise spec on VDD of LSM6DSV36S that we need to be aware of when supplying the voltage to it? I.e. concern of specific frequency of a switching regulator, ripple spec, etc. 

Hi everyone,I have set up my LIS2DW12 to recognise double taps in the Z direction, which works well with the following settings:ODR = 400 Hz (High performance mode)FS = +-2gLow Noise Mode enabledTap threshold: 0b1000 = 0.5 gLatency: 0x0F = 1200 msQuiet: 0x03 = 30 msShock: 0x02 = 40 msNow I wanted to fine-tune these parameters for my application, as some collisions that should not be detected are also being detected as double-tap events.My idea was to read the acceleration values from the output register/FIFO and send them via the UART interface of my MCU to the virtual COM port of my PC in order to recognise the characteristic waveform and derive the appropriate parameters.My questions at this point are: Which signal does the LIS2DW12 use as input for the internal double-tap detection logic, and is it possible to output the same data via the output register/FIFO? As I know fro

Good Morning,I own both a SensorTile.box and a SensorTile.Box PRO. I used the SensorTile.box to identify anomaly vibrations on a device, using the prebuilt app, with slight modifications, that performs the FFT of data coming from the accelerometer and then the FFT Compare with the reference FFT captured when no anomaly is present on the device. Now, due to some limitations of the SensorTile.box, I want to replicate it on the SensorTile.box PRO, but among the available functions offered to manipulate data, there is only FFT (DFT - Discrete Fourier Transform), but not the FFT Compare which is available on the base board. The question is: how can I recreate the app developed on SensorTile.box to operate also on the SensorTile.Box PRO? Do I need any firmware upgrade and if yes, where I can download it? It seems to me very strange a so important function is not present and I don't think it could be difficult to insert it also on this device.Could s

Hi,We currently use the LIS2DW12 in our design and have encountered an issue in some units after prolonged continuous operation (approximately 5–6 days). Specifically, the accelerometer output becomes unresponsive and remains stuck at a constant value. Attempting a soft reset does not resolve the issue.During this fault condition, all device registers remain readable, and the WHO_AM_I register continues to return the correct value (0x44). However, we observed that the BOOT bit in the CTRL2 register (0x21) remains stuck at '1', suggesting that the internal reboot process has not completed successfully. The only way to recover from this state is to complete a power cycle. Unfortunately, due to our product's design, removing the onboard battery is not feasible for end users.Could you advise on the potential root causes of this behaviour and whether any recommended solutions or workarounds do not require a physical power cycle?

Hi guys,I'm working on a new hw design and I can't find the difference between these two references.Thanks in advance,Kind regards

To my knowledge all the LSM6DSV sensors are 3rd gen sensors.And they have additional features to prior sensors like lower power consumption, high accuracy ODR, dual channel output mode, and the LSM6DSV80X/320X even have a second high g accel channel, a few more options/modes.Looking through all the industrial and automotive sensors, the feature set mostly aligns with the LSM6DSR/DSO variants. So I may have overlooked some, but in case not, when can we expect 3rd gen IMUs with longevity commitment and/or 105°C temperature range?

Using the LSM6 over SPI with the RP2040 Microcontroller for a mission-critical project (flight controller for UAVs).The SPI works well. Well in theory. In practice, 1 in every 20-100 reads returns corrupt SPI data (WHOAMI reads as 0x68/0x58). This issue is somewhat reduced when moving the sensor (worst when still) and when adding decoupling capacitors (reduces corruption dramatically).The project itself is ultra high volume (10k+ units), and we have already invested a very large amount of time and resources into testing.

I have a question about the ADC sensitivity for the vAFE in the ST1VAFE3BX. Table 3 of the datasheet says that the input range is +-25mV when the gain is set to 16. With a 12-bit reading, this results in about 12 uV/LSB of resolution. However, the "AH / vAFE channel gain" row of the table lists 1311 LSB/mV, or 0.76 uV/LSB of resolution and mentions "16 bits, input referred". These values seem to conflict. Is the sensitivity 0.76 uV/LSB or 12.2 uV/LSB? This is a huge difference in sensitivity. If 0.76 uV/LSB is achievable, what settings can be used to reach it? According to the datasheet, none of the configurations appear to generate samples with more than 14 bits. In my experience working with the part, the vAFE samples are always at least 14-bits when using vAFE only mode. When enabling the low-pass filter, I see 16-bits. This also doesn't seem to match the information in the datasheets or application notes, further increasing my confusion. I w

Does the LSM6DSV support in-circuit firmware updates over SPI? If so, is there an app note that details how to do this. We are just trying to plan to support this in our new design if needed.

Hello Team,We are using the Qualcomm QCS6490 chip set running Android 13 on our custom board.As part of our project, we have integrated the LSM6DSOTR sensor, which is connected to the DSP pins via the I3C interface. Based on our discussion with the Qualcomm team, we understand that we need to update the JSON configuration files for the LSM6DSO sensor to reflect changes such as soc_id and bus_type.Although our sensor is part of the PVL, we understand that for all non-POR sensors, the OEM is expected to coordinate with the sensor vendor to obtain the following:SEE-compliant driver source codeJSON configuration file(s)Test results, including the Driver Acceptance Checklist validated with the same driver source and registry settingsTo proceed with the sensor bring-up, we kindly request the relevant JSON configuration files for the L

Hi everyone,I'm working with the LSM303AGR magnetometer using an STM32 microcontroller and trying to run the built-in self-test as described in the datasheet. However, the self-test consistently fails — the delta values (normal vs self-test mode) fall outside the expected range.GoalPerform a successful magnetometer self-test and confirm the output is within the required limits (according to the datasheet).Summary of the IssueSelf-test bit is enabled in CFG_REG_C_M (0x62) → value reads back as 0x12.Data output seems valid and updates regularly.Delta between self-test and normal readings is either too small or too large, so the test fails.Self-Test Code (Full Function)void LSM303AGR_Mag_selfTest(void){uint8_t addr = LSM303_MAG_ADR, stat

Hi ST experts, Is there any linux driver library available for LIS2DTW12? Where can I find the related information/document? Thanks.

Hello,I was wondering if it is possible to set the steval-mki109d with steval-mki245KA to standalone.I would like to test the ISM330BX what is happening when rotating. Thus I have set up a kit with a battery pack and I can start up the measurement with MEMS studio 2.0. When I just pull out the USB-C connector, I think everything will go on (LEDs keep doing the same thing as when i turned the mems on in MEMS studio). But when I reconnect to MEMS studio the ISM330BX will have to be configured again. Meaning I cannot check the final values after rotating.Is there any way to for example log all the data to a SD card without writing all the code by myself? Or any other way to read out the final value without the processor/MEMS resetting?Thanks!

Hi,do the STEVAL-MKI109V3 motherboard support STEVAL-MKI251A daughterboard or do I need the STEVAL-MKI109D Motherboard?STEVAL-MKI109V3 with FW 3.73.9 does not recognize STEVAL-MKI251A in my setup. Other daughterboards work just fine. /Ludvig

I am looking to extend battery life of the SensorTile.box PRO using sleep mode of STM32U5 and disabling the MEMS sensors. Currently I am measuring approx. 8 mA in this configuration, but I would like to reduce current into the uA range if possible.  I am running some quick tests in Arduino IDE using STM32duino libraries, but open to using Cube IDE as well:  LPS22DF.Disable();  LIS2MDL.Disable();  STTS22H.Disable();  LIS2DU12.Disable_X();   LSM6DSV16X.Disable_X();

HI, this is Ahilesh Krishna, I am using STEVAL - MKBOXPRO module for my project, I am eager to know whether this module has in bag and out bag feature in it. Which means whether this would indicate whether the laptop is inside the bag or outside the bag. 

Hello,Could you please confirm that in LSM6DS, as in ASM330, as in ISM330, the low pass gyroscope filtering LPF2 cannot be bypassed and is only driven by ODR_G (no "enable" flag is available for this filtering stage) ?  Furthermore, the block diagrams in the corresponding datasheets suggest that a single ADC (ADC1) is used to digitize the three axes of the gyroscope. Could you please confirm that digitization is indeed multiplexed in these products ?Thank you by advance for your help.

Hello,I wish to test the IMU LSM6DSV, using STEVAL MKI239A and STEVAL-MKI109V3 Motherboard. In the past I've used Unico-GUI, where I could save to file not only inertial sensors' readings, but also temperature. Moving to MEMS Studio, I can no longer find a checkbox to select recording temperature values as well.Is there a hidden setting that allows that? I did find one can fix the temperature units in the GUI. that hints there might be an ability to read such data.Shmulik

Hi, I have STEVAL MKI109D, on it I mounted STEVAL MKI250KA. I would say if I could use QVAR Swipe Electrode mounted on STEVAL MKI250KA for reading Qvar signal. It is possible?

Hi, I have the STEVAL-MKI109D board, on which I mounted the STEVAL-MKI250KA. I would like to implement the free-fall example on the FSM, using data from the ST1VAFE3BX biosensor, using only MEMS Studio. Is it possible to do this without writing firmware solution? If so, how should I proceed? Thanks.  

I’m working with a LIS2MDL magnetometer sensor connected to an STM32F407VTG6 microcontroller running FreeRTOS. The sensor communicates over the SPI3 interface, and is configured to operate in SPI Mode 0 (CPOL=0, CPHA=0). The chip select (CS) pin is initialized to HIGH at startup using STM32CubeIDE.I’ve also attached the wiring diagram and SPI configuration settings from STM32CubeIDE for reference.In my FreeRTOS task, I enable SPI 4-wire mode, and I’m able to read the WHO_AM_I register successfully—it returns 0x40, confirming that SPI communication over SPI3 is working correctly.However, the DRDY (Data Ready) flag never goes high, so the sensor doesn't indicate that data is available. When I bypass the DRDY check and try reading the magnetic field values directly, I get invalid data:X = -1, Y = -1, Z = -1.This makes me think there may be an issue with the sensor configuration or the data reading process, but I haven’t been able to identify the

Hello everyone,I am using the LIS2MDL sensor in a parking project, where it operates via interrupt using a threshold value of 60. Initially, the sensor is calibrated with hard-iron correction and is able to detect interrupts properly. However, when a car approaches the sensor, the magnetic field, in all axis, changes significantly, causing the interrupt threshold to be exceeded.I want to recalibrate the sensor using hard-iron correction so that the X, Y, and Z axis readings return as close as possible to zero. This would allow the sensor to detect another interrupt after the car moves away. The problem is that the hard-iron correction function does not seem to work properly on its own. I’ve only been able to make it work by reinitializing the sensor and then applying the hard-iron calibration. I know this isn't the proper method, but I haven't found a better solution.Do you have any suggestions on how to handle this more effectively?I forgot to mention tha

Hi, I have an evaluation board STEVAL-MKI168V1 with the sensor IIS2DH. I was hoping to plug it into the DIL24 connector of the SensorTile.Box PRO and be able to see the sensor's output using the MEMS Studio. This does not seem to be the case. Can somebody provide me some guidance on how to access the sensor data using the SensorTile Box? Currently I am running the firmware FP-SNS-Datalog2 v 3.0.0. I saw that the Git repository https://github.com/STMicroelectronics/fp-sns-datalog2 includes drivers for the the sensor IIS2DH, so it looks like it should be possible to access the sensor somehow.  Thanks,Michal 

Hello, I am using the LIS2MDL development kit. I have two questions. When I measure with two development kits in the same environment, I get different values.Both are 5 cm away from each other and there is no factor that will disrupt the magnetic field around either of them.What could be the reason for this? When I bring a magnet closer to any of the development kits without changing its position and move it away, I get different measurements than the first values ​​it measured.For example:x: 500 y: 100 z: 800After moving the magnet closer and further away:x: 200 y: -200 z: 450When I reset the card nothing changes. It still reads the bad value. The position of the development kit does not change and I guarantee that the magnet is far enough a