MEMS (sensors)

When I try to set the LIS2MDL's operation mode from IDLE to CONTINUOUS or SINGLE_TRIGGER mode, the register values in CFG_REG_A that I already set prior (including comp_temp_en) gets reset to default including the operation mode when I check the register after a 7ms delay. I am using functions from the lis2mdl_reg.c/h files and have read values on hardware debug mode and on the SDA line. I have checked that 3V3 does not drop out and I2C communications look expected. Does anyone have any insight into what could be causing this?

Hello, I recently integrated LSM6DSOX on a testing PCB which contains an MCU and some other peripherals. The problem is that I have been trying to reduce power consumption without success, and I thought maybe you could help me find the problem. First, the application also uses BLE, and I measure power consumption during advertising, connecting and other states. Before the LSM6DSOX, the consumption was around 45-60 uA during these states. After integrating it, the consumption rose up to ~97-140 uA, which is unexpected as I have confirmed it to be low power mode. I also confirmed that the previous code with the current board with LSM6DSOX also consumes around 45 uA, so I assume there is something wrong in the code, handling, configuration etc. Hardware details: 1. I have connected a MOSFET as a switch before the power pins of LSM6DSOX. Meaning, I set high/low the gate of the mosfet to g

How to know  MotionMC and MotionEC Library minimum Stack size Heap_Size?When I invert my compass,stm32 will reset, then i  increase Stack size Heap_Size,it run very well.

Hello, I am designing a PCB board using LSM6DSO and STM32f1xx, this PCB design will be only an experimental design for a bigger project, so I need both SPI and I2C to be available for testing (not at the same time).I'm wondering if there will be any issues regarding having both of them, espcially from the HW side, and is there any considerations or something to keep in mind when designing the PCB.Thanks! "Design schematic, typical connection for mode 1"

HiWe are testing out the lsm6dsv320x, which will be used on our new board.The low G accelerometer is working fine, however the high G looks to be reporting wrong values.If I use a simple calculation to computer the angles, the high G  is off by about 3-4 degreesThis is the formula i use to calculate the angles AccXangle = (math.atan2(ACCy,ACCz)*RAD_TO_DEG) AccYangle = (math.atan2(ACCz,ACCx)+M_PI)*RAD_TO_DEGBelow is an example of the results of both formulas when the sensor is horizontal. The last two columns are for the high G sensor.  you can see that it is different from the low G sensor. My expectation is that they should be reporting the same result.ACCX_angleACCY_angle

Hi everyone.Can someone from ST please provide information about when the STEVAL-MKI248KA will be available for testing?We are currently designing a new device that could really benefit from ISM6HG256XTR but we are tight on time and already in the integration phase, so it would be great if we could test this new product as soon as possible.  Thanks  Tiziano 

Hi team,We need thermal details (Junction to ambient temperature, Case temperature and body temperature) for the following IC's:ASM330LHHXG1TRM24M02-DWMN3TP/KPlease provide the details for the given IC's.Thanks & regards,Aravind R

I am developing firmware for the ISPU on the LSM6DSO16IS and have a question regarding communication between the host MCU and the ISPU core.My objective is to persist magnetometer calibration data. My intended workflow is:The ISPU runs the MotionMC_update function and calculates the HI_bias values.The host MCU reads these HI_bias values from the ISPU's output registers and saves them to non-volatile memory.On the next device startup, the host MCU writes the saved HI_bias&nb

Hi,  I am using LSM6DSL accelerometer sensor.I have configure it to use acc only, +-16g, @27Hz, and using FIFO.Here is the configuration I am doing:uint8_t val = 0x04; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_CTRL3_C, &val, 1); val = 0x24; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_CTRL1_XL, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_CTRL2_G, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL1, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL2, &val, 1); val = 0x09; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL3, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL4, &val, 1); val = 0x16; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL5, &val, 1); val = 0xF0; err = lsm6dsl_write_reg(p_ctx, 0x18, &val, 1); val = 0x00; err = lsm6dsl_write_reg(p_ctx, 0x19, &val, 1);

Greeting, this is my first ever post on the forum so i hope the topic can be interesting to others.I was working with the ISM330 gyro, reading the datasheet and i noticed that the gyro rate sensitivity seems to be a bit off. Here is what they mention in the datasheet, when i look at the angular rate sensitivy (let assume we have put a full scale range of 2000 dps) the typical value here is 70 mdps/LSB with the tolerance of +-2%. This value doesnt seem to map all the 16 bit signed integer because if you do the math with 70 mdps/LSB the full scale range is actually 2293 dps not 2000 dps, that's like 14% deviation. I don't really know if its intended like this but it's obviously strange, i have worked on many other gyros previously, let say for example mpu6500 or mpu6050 and they don't seem to have this mismatch issue.I have looked up the issue and found a blog post of a japanese that also experience this frustration with the ISM330 (

I am working with LIS2DW12 configuring the INT1 for the activity/inactivity interrupt. With the below configurations (as provided in the datasheet), 1. Write 50h in CTRL1 // Turn on the accelerometer // ODR = 200 Hz, FS = ±2 g2. Write 42h in WAKE_UP_DUR // Set duration for inactivity detection // Set duration for wake-up detection3. Write 42h in WAKE_UP_THS // Set activity/inactivity threshold // Enable activity/inactivity detection4. Write 20h in CTRL4_INT1_PAD_CTRL // Activity (wake-up) interrupt driven to INT1 pin5. Write 20h in CTRL7 // Enable interruptsAs expected the interrupt is triggered as an when there is an activity (movement).I want the interrupt to be triggered when the activity is prolonged for 5 secs. I tried playing around with the CTRL1 & WAKE_UP_DUR settings. But results are not as expect. Kindly advice.

We bought the LSM6DSOX and installed into our equipment since 2021, please help to evaluate whether we need calibrate it. Are there any conditions that the sensor must be calibrated? Please show us the detailed steps for calibrating the sensor. Since the output acceleration information is very important for our application, could you 1) give us some reliability data from customer market (especially in Aviation Industry, we called FMEA: Failure Modes and Effects Analysis); 2) show us some basic principles for generating the acceleration data. From spec and application note of LSM6DSOX, we found it can support motion/stationary recognition, please show us more detail information with the reliability of this recognition and how to implement this function during practice. Are there any limitations or key points for installation of this sensor?

Hi, I am trying to confiure my FSM on LSM6DSV320X chip following the instructions from AN6291LSM6DSV320X: finite state machine document. But in the document on page 52 line 18 it says: Write 41h to register 02h // PAGE_SEL = 4. But there is no description about "page 4". I would be really thankful to be helped with this issue. I look forward to hearing from you. Thanks and regardsY@TDK @Andrew Neil 

I am using an LIS2DH12 sensor with an esp8266 via I2C. It is the only sensor on I2C. I have a process loop that repeats every 200ms. During this loop, it is recording some other pin inputs and analog inputs, and sending the data to another esp8266 via serial. With the LIS sensor commented out, the maximum loop time is 5ms.With the LIS sensor reading active, and reading it every 200ms, the maximum loop time including the LIS reading varies from 10ms-45ms. So the LIS reading is taking between 5-40ms. My question: There is a strange pattern over the span of 1.6 seconds. Consistently the loop time progresses 45-41-36-31-26-21-16-11ms, only to repeat again 45-41-36-31-26-21-16-11ms.What is causing this pattern? Is the sensor itself doing something in this 1.6 second time period?Thanks!

Hello,I am developing a dynamometer to measure the load placed upon it. To do this, I have designed a spring so that a 1 kg load compresses it by 1 mm. Therefore, I need a sensor capable of detecting the spring's displacement with 1 mm precision.My question is: can I achieve this 1 mm precision by using magnetometer sensor? My idea is to place a magnet on the moving base of the dynamometer and create a calibration curve to correlate the change in the magnetic field with a 1 mm displacement. I need to be able to measure in 5 kg increments, which should correspond to a 1 mm 

Hi,Recently we bought & recived components (MPN LIS2DH12TR) from distributor (Mxxxxx) are over two years old date code, which exceeds the threshold for our internal testing policy.As you know, there's a potential risk of pad oxidation affecting solderability over time.For our validation process, we conduct solderability tests on:Active components that have exceeded 2 years of storage. (Apply to this component) Passive components that have exceeded 5 years of storage.Does STMicroelectronics has any official statement confirming that the shelf life of these LCA leadless pads ? We would want to confirm the product recived direct from distributor (Mxxxxx) which more then xx period are still useable or not direct into our production. Best regards,Mr. WengSupplier Quality Engineering

I want to read acc data by fifo, but int1 can't work. I think there might be something wrong with my setup, but I can't figure out where the problem lies. This is my code. /* Wait sensor boot time */ platform_delay(BOOT_TIME); /* Check device ID */ whoamI = 0; iis2iclx_device_id_get(&dev_ctx, &whoamI); if ( whoamI != IIS2ICLX_ID ) while (1); /*manage here device not found */ /* Restore default configuration */ iis2iclx_reset_set(&dev_ctx, PROPERTY_ENABLE); do { iis2iclx_reset_get(&dev_ctx, &rst); } while (rst); /* Set full scale */ iis2iclx_xl_full_scale_set(&dev_ctx, IIS2ICLX_2g); /* Configure filtering chain(No aux interface) * Accelerometer - LPF1 + LPF2 path */ iis2iclx_xl_hp_path_on_out_set(&dev_ctx, IIS2ICLX_LP_ODR_DIV_100); iis2iclx_xl_filter_lp2_set(&dev_ctx, PROPERTY_ENABLE); // iis2iclx_fifo_virtual_sens_odr_chg_set(&dev_ctx, PROPERTY_ENABLE); iis2

How can I save the magnetometer calibration offset in ISPU, if  lsm6dso16is is connected to a stm32l4.

I am trying to connect the custom board to the mems studio to measure the euler angles and to explore the mems studio? is it possible to connect the custom board?

Hello,I am developing a dynamometer to measure the load placed upon it. To do this, I have designed a spring so that a 1 kg load compresses it by 1 mm. Therefore, I need a sensor capable of detecting the spring's displacement with 1 mm precision.My question is: can I achieve this 1 mm precision by using an STM LIS3MDL sensor? My idea is to place a magnet on the moving base of the dynamometer and create a calibration curve to correlate the change in the magnetic field with a 1 mm displacement. I need to be able to measure in 5 kg increments, which should correspond to a 1 mm displacement for each step.

Hi,We are using the LSM6DSO in our project to find the euler angles.we are new to this motionfx in stm32. please tell us from where we have to start to find the euler angles.Do we need to add any of the files in the stm32?please tell us from the beginning.

We sincerely appreciate your continued support. We have been able to resolve many questions.In the CTRL1_XL register of the ASM330LHH, when setting ODR_XL[3:0] from 0000 (OFF) to 0011 (52Hz) and then to 1001 (3333Hz), does ODR_XL[3:0] need to be set back to 0000 (OFF) once ?

A new sensor has been recently launched on st.com, embedded in existing pressure and iNemo sensors: an electrostatic sensor that can be used for human presence and motion detection, touch detection, and user interface (UI) applicationsQvar stands for electric charge (= Q) variation (= var). It is an electrical potential sensing channel able to measure the quasi-electrostatic potential changes. ILPS22QS and LSM6DSV16X sensors allow to connect an analog input and convert it to a digital signal for embedded processing. In addition, the embedded Qvar channel can be enabled for sensing in applications such

Hi,I’m working with the LSM6DSL sensor and I’d like to know if it’s possible to use both the Low-Pass Filter (LPF) and High-Pass Filter (HPF) at the same time in the accelerometer. If so, could someone explain how to configure it?Thanks!

Dear ST,I am working with the STHS34PF80 PIR sensor on an i.MX8MP platform, using the upstream-style IIO driver (st_sths34pf80). I am attempting to run the sensor in continuous mode (buffered streaming), but iio_readdev always times out with no samples delivered.echo 1 > /sys/bus/iio/devices/iio:device3/algo_resetecho 4 > /sys/bus/iio/devices/iio:device3/lpfecho 200 > /sys/bus/iio/devices/iio:device3/thresholdecho 50 > /sys/bus/iio/devices/iio:device3/hysteresisecho 4 > /sys/bus/iio/devices/iio:device3/sampling_frequencyecho 0 > /sys/bus/iio/devices/iio:device3/events/in_temp0_thresh_rising_en# Enable scan elementsecho 1 > /sys/bus/iio/devices/iio:device3/scan_elements/in_proximity_object_enecho 1 > /sys/bus/iio/devices/iio:device3/scan_elements/in_timestamp_enecho 1 > /sys/bus/iio/devices/iio:device3/scan_elements/in_temp_x_en# Enable