MEMS (sensors)

Hi, I am working on the LIS2DH12,  I have a problem to the appearance of acceleration data.  I'm using full scale of +/- 2g and ODR of 400Hz.  When the resolution is either 10-bit or 12-bit, only even number acceleration data is read(all x/y/z axis).  The acceleration data is generally correct(but only even number).  When resolution of 8-bit is selected, now both even and odd number acceleration data can be read.  It shows the same appearance for ODR from 1Hz to 400Hz.

Hello,I have a requirement to log the data from evaluation board STEVAL-STWINBX1 to cloud. I have created Azure IOT hub and while initiating the cloud logging from the app i was unable to successfully connect to the created IOT Device created in azure even though the connection string was pasted correctly. the application ST BLE Sensor classic automatically disconnects from the sensor once the cloud logging is enabled. do i need to install the SD card and log the data from card to cloud ? I got struck at this point, is there any specific firmware to be loaded, for now I'm just testing with the basic firmware that provides data from all the sensors to the app

Hi,ASM330LHH datasheet states that "compensation for high stability over temperature" are embedded in the device. Could you provide more information about the correction algorithms applied ?In particular, when we measure the bias at 0°/s of the ASM330LHH in a temperature chamber, we get strange non-linear behaviors that we suppose to be a consequence of these algorithms. For instance, in the following figure (filtered bias at 0°/s depending on temperature) some "steps" can be observed. Could you provide a description of the corrections applied / the reason of this behavior ? It would make the device more predictable for us.Furthermore, is there a way to disable these corrections ?Thank you a in advance.  

I am looking for information about iNemoEngine sensors in the latest STMicroelectronics HAL for Android.I successfully integrated the STMicroelectronics HAL framework into Android 11. I am using the LSM6DSOTR gyroscope/accelerometer and the LIS3MDLTR magnetometer. These sensors are correctly detected and can be accessed from an Android application. However, the STMicroelectronics HAL also creates iNemoEngine sensors, which do not return any values.The previous STMems_Android_Sensor_HAL_IIO framework used several proprietary STM libraries, including SENSOR_FUSION, GEOMAG_FUSION, GBIAS, MAGCALIB, and ACC_CALIB, to generate the game_rotation_vector, orientation, and rotation_vector sensors. Are these libraries still required for the latest STMicroelectronics HAL framework? What is needed to gain access to these libraries?What is required to make the fusion sensors work in the latest STMems_Android_Sensor_HAL_IIO?

Hello ST Community,I am currently working on integrating the LSM6DSV16X accelerometer with an STM32H7 series MCU over I²C. Our main goal is to detect the tilt angle of the system. Hardware SetupMCU: STM32H7Sensor: LSM6DSV16X (mounted on a custom board)Interface: I²CSA0 Pin: Pulled high → I²C address = 0x6BPower Supply: 3.3 VPull-ups: 4.7 kΩ on SDA and SCL linesI²C Speed: Tested at both 100 kHz and 400 kHz The setup is straightforward — the sensor is connected to the STM32H7’s I²C1 bus, and it can be successfully detected using an I²C scanner. I’m using the official STMicroelectronics driver from this repository:https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsv16x_STdC/examples/lsm6dsv16x_self_test.c  However, I’m facing an unusual issue during normal operation. Issue DescriptionWhen I try to read the WHO_AM_I register using the official LSM6DSV16X driver, I get inconsistent results. Case 1 – Normal Run (no breakp

hello , i am using lsmds0 sensor with nxp board below is the section of my code int main(void) { /* Write your code here */ Clock_Ip_StatusType clockStatus; clockStatus = Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); Siul2_Port_Ip_Init(NUM_OF_CONFIGURED_PINS0, g_pin_mux_InitConfigArr0); Siul2_Dio_Ip_WritePin(MEMS_CS_DRIVE_ENABLE_PORT ,MEMS_CS_DRIVE_ENABLE_PIN,1); i2c_int(); //i2c_scan_bus(); i2c_bustest(); // I2C_ManualBusRecovery(); dev_ctx.write_reg = accelero_write;//assigning read and write pointers to ST driver context dev_ctx.read_reg = accelero_read; dev_ctx.handle = NULL; uint8_t who_am_i = 0; uint8_t ctrl1; int16_t raw_accel_data[3];// variable to store raw 16 bit accelerometer value volatile float acceleration_mg[3];// converted acceleration in milli-g lsm6dso_status_reg_t reg_status; // structure store the register flags lsm6dso_device_id_get(&dev_ctx, &who_am_i); lsm6dso_reset_set(&dev_ctx, PROPERTY_ENABLE);// starting resetting process uint8_t rst; uint

I have a question regarding the absolute maximum ratings of the ASM330LHH.In the datasheet, the Vin rating lists “(including CS, SCL/SPC, SDA/SDI/SDO, SDO/SA0)”.Does this voltage range also include any overshoot and undershoot on these pins?Additionally, if overshoot or undershoot exceeds the absolute maximum ratings,what potential issues could occur (e.g., malfunction, degradation, or damage to internal circuitry)? 

I connected STEVAL-MKI236A and STEVAL-MKI109D and confirmed that the IMU information comes from Mems studio and Unico.My final goal is that this IMU value is output in serial communication.I want to read the output IMU 6-axis information through python and match it to ros2 topic.Please teach me the way.Thank you. Have a nice day

I could successfully operate the X- NUCLEO IKS4A1 in the MEMS Studio with the default sensor selection on the board. However, when I tried to select the LSM6DSV, which is connected on the DIL24 socket of the  X-NUCLEO IKS4A1 board, for the accelerometer and gyroscope sensor configuration in MEMS Studio, I get the following error window: The WHO AM I register value does not match the device selected I also connect two jumpers between 9-10 for the headers J4 and J5 on the X-NUCLEO IKS4A1 board and removed the two jumpers between 11-12 for the header J4 and J5. Do you have some recommendation, what I miss here?Many thanks in advance. Best regardsChristian

Hello,I am testing the LIS2MDL magnetometer in single-shot mode with offset cancellation enabled, according to the datasheet (DS12144 - Rev 6, page 22). The documentation states that in single-shot mode both bits OFF_CANC and OFF_CANC_ONE_SHOT in register CFG_REG_B must be set to 1.However, when these bits are both set (CFG_REG_B) and a single measurement is triggered by writing md = 01b in CFG_REG_A the measurement never completes — the ZYXDA flag in STATUS_REG remains 0 permanently.If only OFF_CANC_ONE_SHOT=1 is set, the measurement finishes normally and ZYXDA is asserted, but the output values look identical to normal single-shot measurements (no visible offset compensation effect).Test conditions:4WSPIBDU=1verified data readout sequence (reading all 6 output bytes resets ZYXDA properly)communication via SPI verified by WHO_AM_I = 0x40It appears that combining OFF_CANC=1 and OFF_CANC_ONE_SHOT=1 prevents the internal FSM from completing a single measurement.Questions:Is this a k

Could you please let me know at what point we can confirm that the ASM330LHH has successfully started up at the hardware level?If the WHO_AM_I register returns the expected response, can we consider that the device has initialized correctly?Additionally, after enabling the sensors via CTRL1_XL and CTRL2_G, is it possible to verify proper startup by checking whether the value of STATUS_REG changes?In a situation where the STATUS_REG value sometimes changes and sometimes does not, is it appropriate to judge that “no change” indicates the hardware has not successfully started?Thank you very much for your guidance.

Dear Sir,Our project using LSM6DSO IMU to detect the position, the sensor temperature is very high after power on and Initialization, it's over 80 degree, I think it's abnormal, I attach the sch, can you give some suggestions, thanks a lot.

Would you please share with us some sample performance test results of LSM6DSV family, like Allan Variance graphics, VRE, misalignment, etc?

I want to read the FIFO of IIS2ICLX, but I found that INT1 only triggers once when the power is first turned on. This is my initialization code. Is there anything wrong with this initialization?I triggered the interrupt through the rising edge. Once the interrupt occurred, an event would be sent. I measured the level of the interrupt pin, and it remained constant.iis2iclx_xl_full_scale_set(&dev_ctx, IIS2ICLX_500mg); /* Configure filtering chain(No aux interface) * Accelerometer - LPF1 + LPF2 path */ iis2iclx_xl_hp_path_on_out_set(&dev_ctx, IIS2ICLX_LP_ODR_DIV_10); iis2iclx_xl_filter_lp2_set(&dev_ctx, PROPERTY_ENABLE); iis2iclx_fifo_xl_batch_set(&dev_ctx, IIS2ICLX_XL_BATCHED_AT_104Hz); iis2iclx_xl_data_rate_set(&dev_ctx, IIS2ICLX_XL_ODR_104Hz); s_sample_rate = 104.0f; iis2iclx_fifo_watermark_set(&dev_ctx, 112); iis2iclx_fifo_mode_set(&dev_ctx, IIS2ICLX_FIFO_MODE); iis2iclx_pin_int1_route_t int1_route; int1_route.int1_ctrl.int1_fifo_th = 1; int1_route.int1_ct

Hi,I am evaluating sths34pf80 but unfortuantely I am not able to make it work. I am referiing to the code in the github https://github.com/STMicroelectronics/STMems_Standard_C_drivers/tree/master/sths34pf80_STdCThe below code is from example sths34pf80_tmos_presence_detection.  /* Wait sensor boot time */ platform_delay(BOOT_TIME); /* Check device ID */ sths34pf80_device_id_get(&dev_ctx, &whoami); if (whoami != STHS34PF80_ID) while (1); /* Set averages (AVG_TAMB = 8, AVG_TMOS = 32) */ sths34pf80_avg_tobject_num_set(&dev_ctx, STHS34PF80_AVG_TMOS_32); sths34pf80_avg_tambient_num_set(&dev_ctx, STHS34PF80_AVG_T_8); /* read filters */ sths34pf80_lpf_m_bandwidth_get(&dev_ctx, &lpf_m); sths34pf80_lpf_p_bandwidth_get(&dev_ctx, &lpf_p); sths34pf80_lpf_p_m_bandwidth_get(&dev_ctx, &lpf_p_m); sths34pf80_lpf_a_t_bandwidth_get(&dev_ctx, &lpf_a_t); snprintf((char *)tx_buffer, sizeof(tx_buffer), "lpf_m: %02d, lpf_p:

Hello,I am using the LSM6DSV in a very simple configuration.  I am finding that it does not power down properly after I have powered it up.  In normal operation I power it up by writing a value of 0x01 to address 0x10 (turns on accelerometor at 1.875Hz) and writing a value of 0x02 to address 0x11 (turns on gyroscope at 7.5Hz).  Then after taking some readings I power it down by writing a value of 0x0 to address 0x10 and a value of 0x0 to address 0x11. After I power it down I find that it still draws ~650uA of current.Other than reading the conversion results at address 0x22-0x2D, the writes to addresses 0x10 and 0x11 are the only ones I do.I have run a couple of experiments:1. I omitted the writes to 0x10 and 0x11 when powering up and find that the power draw stays at or below a few uA.  This demonstrates to me that the power draw is coming from a mode the LSM6DSV is in rather than my MCU or other circuitry.2. I explicitly wrote power down/disable values to the othe

Hi,I am working on a project to read the magnetic field with the IIS2MDCTR chip. Actually, I am replacing a read switch with this accelerometer. I use the IIS2MDCSensor Arduino library. After testing with the magnet, I set the threshold to 10000. Enabled the interrupt on all axes in pulsed mode and routed it to the INT pin to get my microcontroller. (STM32U385VGT6) interrupted. When I close the magnet from the z-direction, I get the interrupt. But when I bring it closure from an angle, it does not change the pin status. I tried printing the ODR register values. I saw one, two, or three register values go beyond the 10000 threshold. But I do not get the interrupt. But when I move from the z direction, I am getting the interrupt even when only one axis exceeds the threshold. Can somebody explain the situation and advise me to understand this behaviour? 

My LSM6DSVD component and a spring-driven mechanical button are mounted on the same circuit board, approximately 5cm apart. I have secured the circuit board to a table to ensure it does not rotate at all. When I press and quickly release the button, the gyroscope's measurement output spikes to as high as 4 rad/s. As shown in the graph below.

Hello,I am using an LSM6DSV16X with an external sensor on Unico-GUI. I want to train a decision that uses both the internal and external sensors as inputs for the MLC. I am trying to save data from the internal sensors as well as the external sensors, but I do not find the option to include the external sensors in the "Load/Save" in Unico-GUI, even when the LSM6DSV16X is actively reading data from the external sensor through Unico-GUI's "Sensor Hub Registers" tab. How do I use Unico-GUI to save external sensor data, and if it isn't possible, how would I include external sensor data in the training for the MLC. Thank you,Abdurrahman Farag

Hi,I need an accelerometer sensor that generates an interrupt on the acceleration, Let's say that the acceleration always is 9.8, it'll just generates an interrupt on 11 for example.Because all the sensor that I've tested just generates a specific interrupt on a threshold on either x, y, or z values. Which I don't really care about as much as the overall acceleration.Thanks in advance

failed functional test at step: "BARO_3_READ_ALT_VAR, BARO_4_RE:FAIL". LPS25HBTR Date Code 2314, Any reported issues with this date code?

Posted on March 18, 2017 at 11:51Hi all,I am attempting to build a microphone array out of digital MEMS microphones and I am trying to determine if I can achieve a reasonable system on an STM32F7 microcontroller. Ideally I would like to capture the output of 8 or more MEMS microphones synchronously with a filtered and downsampled output of 100Hz - 10kHz and12 bit resolution. I would like to transmit the data to a PC for processing in an algorithm I have developed. I am aware of the DFSDM peripheral however it seems that it is only capable of working with 4 elements synchronously or with 8 elements multiplexed between the 4 filter inputs. My other inclination is to attempt to read the microphone data signals via GPIO using the DMA controller and perform the downsampling and filtering operation on the PC. Is this a viable option or is it difficult to perform without enough storage space on the microcontroller (As the output of one microphone is now being stored as a 1Mbit/s stream). Fro

We are using the LSM6DSV80X sensor in our battery-powered device for an industrial application. However, we could not find the thermal resistance from junction to ambient (θJA) specified in the datasheet. Could you kindly provide this information to support our thermal design calculations?

I’m building a small wearable logger: ESP32 sleeps most of the time, wakes on LSM6DSOX step-detector, logs, then goes back to sleep. Looking for settings that work in practice:ODR/FS and step-detector config that avoids vibration false wakesINT wiring to an RTC-capable GPIO (pull-up value?), latched vs pulsed INTFIFO vs direct interrupt; simple debounce in firmwareRe-init after deep-sleep (soft reset, clear INT, reprogram registers)Typical deep-sleep current numbers with the IMU powered vs fully offConcrete numbers welcome (thresholds, durations, current, wake frequency). Thanks!

Dear ST Mems,Customer Shenzhen Vtech uses IIS3DWB for water pipe vibration detection, using the official routine SPI polarization detection. The data read varies greatly.Revise as follows:1: Communicate with R&D team to conduct self inspection first, pass the self inspection, and then poll. However, there is still a lack of contact, fixed placement, and large deviation in the sampling process.2: Modify the range. Switch from the initial+-2g to+-4g, without contact, with fixed placement and large variation deviation during the sampling process.3: Using a DC stabilized power supply to ensure stable power supply for IIS3DWB, the issue has not been resolved.The following are pictures of product placement and logo information for sampling. May I ask where specific modifications can be made to address the issue of significant numerical variations during the sampling process. Thank you!