MEMS (sensors)

In application note TN1571 "Reference design based on the ST1VAFE6AX and ST1VAFE3BX biosensors..." Table 2 mentions that ST1VAFE3BX has a selectable 50/60Hz notch filter. However, there's no further reference to this filter or how to enable it in the datasheet.Is this an error in TN1571, or something I'm missing.Thank you.  

Hello,I have the LIS2HH12 chip in two separate boards, same board, same firmware.  These devices have been working well, producing X,Y,Z data.  Until today, that is, after a firmware update.This device is the only thing on the I2C bus, 100KHz, 5.1K pullups, 3.3V, connected to an ESP32 S3.  Waveforms on the oscilloscope look clean.The CTRL1 register gets 0x3F and CTRL4 register gets 0x04 which I believe should provide initial functionality.WHOAMI returns 0x41, but STATUS returns 0x00 and all six OUT_ registers return 0, as illustrated below.I have a feeling I've overlooked something really simple.  I've read both datasheet and appnote, and looked through this community for hits on the LIS2HH12.  Thanks for any thoughts or ideas.

Hi,I would like to know what is the stop band attenuation of LPF1 and LPF2 for the sensors ISM330DLC & IIS2DLPC. Thank you!

AN5296Application noteASM330LHH: automotive inertial module digital 3-axis accelerometer and digital 3-axis gyroscope3 Operating modes”To guarantee proper power-off of the device, it is recommended to maintain the duration of the VDD line to GND for at least 100μs."About the statement:If the power is turned on before reaching the GND level, what will be the effect?

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

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 STMicroelectroni

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_EN

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 guys,I am using the STEVAL-MKPRO BOX, i want to use MLC with this box. For that i tried to log data(Accelerometer data) with BLE Sensor application. The data is stored inside the micro SD . I connected the SD card to my computer and saw that  it was a .dat file. I tried to convert it into a format which is compatible with ST Mems studio with stdatalog_to_unico.py in the stdatalog-pysdk but it is not working  .I also tried using the nb_stdatalog_converters.ipynb under how_to_notebooks section but literally only the cell with conversion to unico was not working, all the other cells were working. What can i do ?Thank you in advance

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)

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_rout

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, &amp

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

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