MEMS and sensors

Hi,I read the LSM6DSV on the STEVAL SMKI239AA using a Raspberry Pi Pico running Circuit Python. The CTRL1 register is set to 0x07 (240 Hz ODR, high performance). My output is converted to m/s^2 and looks like that when I move the sensor board slowly:Xacc: -8.6479 | Yacc: -1.3192 | Zacc: 5.5958 | sum: 10.38456 Xacc: -8.6479 | Yacc: -1.3120 | Zacc: 5.6042 | sum: 10.38817 Xacc: -9.1219 | Yacc: -2.3511 | Zacc: 6.3375 | sum: 11.35342 [snip]Xacc: -6.9216 | Yacc: -5.3630 | Zacc: 6.2219 | sum: 10.74166 Xacc: -9.1081 | Yacc: -6.2662 | Zacc: 6.7229 | sum: 12.93914 Xacc: -10.0293 | Yacc: -5.9400 | Zacc: 8.0236 | sum: 14.15091 Xacc: -6.5439 | Yacc: -4.0893 | Zacc: 9.1746 | sum: 11.98826 Xacc: -7.0288 | Yacc: -3.8098 | Zacc: 9.6672 | sum: 12.54482 Xacc: -7.5543 | Yacc: -3.9289 | Zacc: 10.4986 | sum: 13.51752 [snip]Xacc: -5.1715 | Yacc: 5.1571 | Zacc: 14.4975 | sum: 16.23320 Xacc: -4.8076 | Yacc: 4.4610 | Zacc: 15.3564 | sum: 16.69827 Xacc: -3.3956 | Yacc: 3.4147 | Zacc: 17.1664 | sum: 17.82908 Xacc

Hello friends;I aim to develop FreeRTOS STM32 based flight control card software. First of all, I am trying to read data from my LIS2DH12 and LIS3MDL sensors in separate tasks and see them on my serial screen at usart1 921600 baudrate for debug purposes. However, I encounter a few problems. I present my project file in the attachment and I will explain the problems I encounter in detail below. Thank you in advance for your interest.These are ;1-) When I run the UART in normal mode, I can only read data from LIS2DH12.LIS3MDL only ends with a not found sensor 0xFF warning at startup, but the data flow of LIS2DH12 continues.2-)When I run the UART with DMA and semaphore, I can only read LIS3MDL data. This time I cannot see the LIS2DH12 sensor data on my serial screen.3-) However, sometimes the sensors sometimes interrupt the serial screen data flow, as if the sensor is locked and becomes inactive, but every time I reset the stm32, 10-20 data comes and goes back. After a few reset attempts,

I am trying to work with the VL53L5CX Tof sensor. The following calls succeed.VL53L5CX_InitVL53L5CX_ReadIDVL53L5CX_Start However, the following call fails:     VL53L5CX_Result_t pResult;    VL53L5CX_ProfileConfig_t _profile;    _profile.RangingProfile = VL53L5CX_PROFILE_8x8_CONTINUOUS;    _profile.TimingBudget = 200;    _profile.Frequency = 1;    _profile.EnableAmbient = 1;    _profile.EnableSignal = 1;    auto status = VL53L5CX_ConfigProfile(&vl53l5cx_obj, &_profile);Especially, when the driver tries to set the resolution, the calls fails. Any idea why is it so?

Hi all,I recently purchased an STM32H723VGT6 breakout board [https://github.com/WeActStudio/WeActStudio.MiniSTM32H723] (not a NUCLEO) and a VL53L5CX sensor breakout from Pololu [https://www.pololu.com/product/3417], and, as I'm a beginner and struggling to navigate all the literature as it relates to STM32, I was wondering if anyone here could give me a step-by-step guide on what documents I need to read in order to set up this custom hardware before I design a similar setup myself with an STM32H523 instead of an STM32H723.I've already went through the user manual, quite a few YouTube videos, and some more stuff, and I'm confused, since I can't seem to find documents on working with X-CUBE-TOF1 and custom hardware.The main issue I have is the fact that I only want just that two pin I2C connection between the MCU and the sensor and nothing else due to the space constraints of my upcoming custom design [PB10 = SCL, PB11 = SDA]. Therefore, I have done the same in the prototype with the of

Helloin the data sheet of LPS22HH the absolute accuracy is  ±0.5 in which range of pressure ? ( 800 hPa to 1100 hPa) ? because i tested some samples in 0.3 bar and 0.5 bar, there big difference between the mesure of LPS22HH and reference (exactly values).Thanks

I want to use the motionfx library in the x cube mems1 package for my flight control card and ahrs project, my aim is to obtain roll pitch and yaw values with sensor fusion, but I have not come across an example code for using motionfx. Can anyone help?

Hello,in the datasheet of LPS22HBTR the absolute pressure accuracy is between 0. and 1 mBar in the range of 0°C and 65°C .Please have more information about the absolute pressure accuracy in negative temperature ? because i will use it betwen -20°C and 0°Cthanks 

I have asm330lhh acceleration and gyro sensor. I have a problem with communication with spi, when I try my other mems sensors (lis3mdl, lis2dh12) with the same connection line, I get the correct whoiam code, while with the asm330llh sensor I sometimes get random values or 0xff.

Hello,Can you please explain how the high pass filter work? Can it be disabled?I don't quite understand the difference between the two modes "Normal" and "Reference" (AN5881, 5.1.1 and 5.1.2), is the high pass filter always active, so the sensor does not measure DC values? However chapter 3.1 states "The sensor can measure DC accelerations" The Reference register where does it apply? Just for the Z axis? It is only 1 value, and we are measuring 3 axes. P.S. I also don't understand Figure 7, Y seems to be the acceleration, X the time but what is the vertical dotted line? Why the acceleration suddenly drops to zero?Thanks,Marco 

Dear ST Team,As the title of this article suggests, I have encountered an issue where the standby power consumption of the ST original VL53L1X-SATEL far exceeds the value stated in the datasheet. The first image below shows the power consumption data, and the second image is the power consumption description of the device from the datasheet.In my attempts, I have not made any hardware modifications to the VL53L1X-SATEL nor used an MCU to communicate or write to the registers of VL53L1X. I connected XSDN_I to the power GND to enter the hardware shutdown mode, with an input voltage of 2.8V. According to the power consumption parameters in the second image, I am puzzled because the value is much higher than what is stated in the datasheet.Additionally, I noticed that the VL53L1X-SATEL has a voltage regulator and level-shifting chip. I shorted R21 to bypass the power consumption of the voltage regulator module, but the power consumption was still over a hundred microamps, which does not al

HelloI ordered 10 samples of the LPS22HH pressure sensor evaluation board (STEVAL-MKI192V1). Upon receipt, I noticed that each board was packaged in a cardboard box but without an anti-static bag.I then began taking measurements by varying the pressure inside a test chamber. Out of the 10 samples, only 5 function correctly and measure the expected pressure, while the remaining 5 consistently read only 1 bar.Could this be due to the high sensitivity of the board and the sensor itself, or could it be a delivery issue? I find this particularly concerning as I ordered from three different distributors and encountered the same issue. This leads me to wonder if the sensor is particularly fragile. Could you provide any insights on this? thanks

Hi,I am developing an application with the LIS2DW12 accelerometer where it is reconfigured depending on which state the application is in. In one state, the accelerometer should detect when it is stationary/in motion and trigger pulsed interrupts on INT2. In another state, the accelerometer should wake up the system upon movement by triggering a latched interrupt on INT1. The only way I have managed to get this functionality is by, when the accelerometer is being reconfigured for wakeup, setting INT2_ON_INT1 in CTRL7. Without this setting, INT1 does not react to movement at all. I figure there must be a way to get INT1 to fire without having to route INT2 to it, so what am I missing?I have tried following the wakeup example without success.These are all the register contents after reconfiguring for wakeup, with INT2_ON_INT1 set:LIS2DW12_OUT_T_L = 0x70 LIS2DW12_OUT_T_H = 0xfb LIS2DW12_WHO_AM_I = 0x44 LIS2DW12_CTRL1 = 0x60 LIS2DW12_CTRL2 = 0x0c LIS2DW12_CTRL3 = 0x10 LIS2DW

I am looking for an overview over the different models in the LSM6 family. On the product selection page there are smaller differences in noise and current consumption, but I guess there are larger differences between those models.I found the following sub-families:LSM6DSVLSM6DSRLSM6DSOLSM6DSLLSM6DSTWhat are the main differences between those models? In addition there are different "suffixes" denoting specific features, including the following:"32": Max. Acceleration Range is +/-32g instead of +/-16"X": Machine Learning Core included"P": ?"IS": ?Best regards,Johannes

Dear forum,I'm actually working on LIS3DH module and I'm facing some issues according power consumption.The board on which this module is mounted is the RAK2270 Sticker (schematics in attached files).The module is driven by a STM32WLE5JCI6 and put in stop mode 2 with analog input for SCL and SDA lines.I've also send the command to set the SDO_PU_DISC bit because pull-up is disconnected to SDO/SA0 pin.First wrong behavior is the current consumption in Power-Down mode.According AN3308 p.13 the device has to enter automatically in this mode after power-up and boot procedure (5ms)But in this mode it still reacts and consumes power when there are activity like several shocks next to the module (see power-down_behavior.png).As we can see on the screenshot, I can get correct value (around 2-3uA) but only during a short period after a shock (272ms on the example).Then after this delay, the module consumes energy and reaches an average of 100uA.After that even when I setup the Low-Power mode 8b

 I am currently working with the LSM6DSLTR IMU sensor, interfacing it with an ESP32-S3-WROOM-1-N8R2 using the I2C protocol. However, I have encountered an issue where one of the accelerometer axes is not providing any data.Issue Observed:The sensor initializes correctly, and two axes provide valid acceleration values.However, one axis does not provide any readings or returns a constant value.The gyroscope readings appear normal.I have verified the I2C connections, sensor power supply, and tested multiple units, but the issue persists.

 Hi, I trying to using VL53L5CX with my jetson nano.Once I want to using it with arduino uno, but uno is not possibly for using with it.So I trying to connected directly it on my jetson. I'm trying to followingVL53L5CX_Linux manual that downloaded from here.https://www.st.com/en/embedded-software/stsw-img025.html But for 3.2, I get some trouble. When I copied driver 2.0.0 folder on my jetsonand following the procedure(well, just simply use make as in manual)it shows such error like this ./menu.c: In function ‘main’:./menu.c:87:3: error: ignoring return value of ‘scanf’, declared with attribute warn_unused_result [-Werror=unused-result]87 | scanf("%s", choice);| ^~~~~~~~~~~~~~~~~~~cc1: all warnings being treated as errors Well, I'm very new with using jetson nano. So I'm not sure what's the problem.Maybe my jetson nano has some problems, that can't detect i2c connection with otherslike this lidar sensor or arduino board,this can be a problem? I'm really apprecia

The sensor IMU is LSM6DSL model, the magnetometer is LIS3MDL model, and the motionfx library is used for attitude calculation, and the heading angle is inaccurate.I checked the value of the geomagnetometer and it is normal, but the heading angle is abnormal: for example, the sensor points to due north, the X axis of the geomagnetometer is 40uT, the Y axis is 0uT, but the heading angle is 300 degrees. After slightly vibrating the sensor to change the values ​​of the accelerometer and the gyroscope, the heading angle stabilizes to 270 degrees. I don’t understand why the magnetic field input is normal but the heading angle output is abnormal?After consulting the information, I learned that after changing the inclination angle, the fusion algorithm will dynamically adjust the projection of the gravity vector through the accelerometer and gyroscope, forcing the geomagnetic data to re-participate in the calculation, covering the wrong horizontal compensation, and correcting the heading angle

I use a VL53L3 with the STSW-IMG033 Ultra Low Power API. I use the settings in the settings mentioned in AN5769 "Using the VL53L3CX under ultralow-power mode" for maximum detection under daylight: Full ROIMacro period 200Signal limit 1500Sigma limit 60Valid distance 400mmUsing interrupt mode: generate only an interrupt when these criteria are met I need reliable detection of a human standing in front of the sensor at max 400mm. Without any cover, the sensor functions just right. WIth a cover glass (I used the cover glass shipped with the VL53L3 Nucleo addon) I get strange results.The reason I used this cover glass for this test is that it is shipped by ST to use with their reference design. Upto about 200 mm the measurement is quite reliable. When the object distance is increased, the measured distance starts to decrease. Becasue of this I get "valid measurement" interrupts upto 1200mm. With another cover, the measurement can be 400mm at a distance of about 200mm so

I’m running MEMS Studio 1.4.2 on Win 10, 64 bit latest version. And trying three different Nucleo boards:Nucleo-C031C6Nucleo-64-STM32L476Nucleo-64-STM32F303MEMS Studio will not recognize any of these three Nucleo boards, with or without the MEMS inertial  and environmental expansion board plugged in - X-Nucleo-IKS01A3. I have also tried plugging a DIL24 adapter into the expansion board - no effect.Any suggestions on what I’m missing?

I am operating a LSM6DSL with a LIS3MDL in sensor hub mode, where the DRDY pin from the LIS3MDL is connected to the INT2 pin of the LSM6DSL. Basically, it works. However, there is a problem during initialization.In order to configure the LIS3MDL, the I2C master interface of the LSM6DSL requires a trigger signal. As long as the LIS3MDL is not in continuous mode, this trigger can only come from the accelerometer. This means that in the MASTER_CONFIG register, START_CONFIG is set to 0. This allows me to switch the LIS3MDL to continuous mode using the appropriate commands but configures the INT2 at the same time as an output.However, when the LIS3MDL starts controlling the DRDY signal, there is a short circuit between the INT2 and DRDY pins because DRDY is also an output. In this case, around 70 mA flows through the pin, which can't be good. Only when START_CONFIG is set to 1 the INT2 pin is switched to an input.I haven’t found any solution to this issue. I would like to configure the INT2

Dear Team,We are integrating lsm303AGR accelerometer and magnetometer sensors on NXP's imx8 Android 10 platform.https://github.com/STMicroelectronics/st-mems-android-linux-sensors-hal for HALhttps://github.com/STMicroelectronics/st-mems-android-linux-drivers-iio for linux 5.4 kerneldevice registers as iio:device0 and iio:device1 x,y,z raw value we can see in cat sysfs files.HAL finds 2 IIO devices but furtherthere is lack of implementation of loading bias and save bias functions in legacy because of this the sensors app is not able to  read the sensor data values . apps says there are 2 sensors from stm accel and magn but data is not able to read.it is going into un-calibrated type. kindly help us in fixing the issue.

Hello ST Friends,Here we are using H3LIS331DL in our product, using SPI interface. Below is the schematic. and related code is below.    /* Check device ID */ static uint8_t whoamI, tData; whoamI = 0; h3lis331dl_device_id_get(&dev_ctx_xl, &whoamI); user_printf("\r\nh3lis331dl whoamI: 0x%x\r\n", whoamI); //REG1 tData = 0x27; //0010 0111 nrf_H3LIS331DL_write_reg(H3LIS331DL_CTRL_REG1, &tData, 1); //REG2 tData = 0x00; //0000 0000 nrf_H3LIS331DL_write_reg(H3LIS331DL_CTRL_REG2, &tData, 1); //REG3 tData = 0x92; //1001 0010 nrf_H3LIS331DL_write_reg(H3LIS331DL_CTRL_REG3, &tData, 1); //REG4 tData = 0x80; //1000 0000 nrf_H3LIS331DL_write_reg(H3LIS331DL_CTRL_REG4, &tData, 1); nrf_H3LIS331DL_read_reg(H3LIS331DL_CTRL_REG1, &tData, 1); user_printf("REG1: 0x%x\r\n", tData); nrf_H3LIS331DL_read_reg(H3LIS331DL_CTRL_REG2, &tData, 1); user_printf("REG2: 0x%x\r\n", tData); nrf_H3LI

HiI purchased the TSL2591 product and used it on the STM32 board.I am reading the datasheet and creating the code.I initialized the first writable registers to 0x00.I then looked at the datasheet and gave the control register a value of 0xB0.The configuration uses 0xD3 in the enable register, 0x00 in the control register, and 0x09 in the persist register.I read the PID and ID registers and got a 4 digit number.After that, I read the thresholds 0x14 and 0x15 (the value of 5 came out).The lower and upper bytes of CH0 and CH1 have been read (CH0 is 21, CH1 is 18).The two values did not change with illumination.I have an interrupt in the datasheet and I do not know how to handle it.Then I got a question, Is the INT pin in the product a pin for an external interrupt?I think I do not have much use for the INT in the datasheet.Could you help me?What is ALS? ALS interrupt is also required.In the status register, the sixth bit says that the device should be specified when it encounters an inter

I  am writing my own library in C++ to operate the LSM6DSO and when the sensor is at rest it reads 0.5 G on the z-axis, I've tried the code with 2 ICs, one in an Adafruit breakout board, and another one in an old PCB that had the sensor soldered one and both got the same error, so I believe that the issue might be in the code, but I can't identify where is the problem. Btw, I am using the dev kit NUH7AZIQ$ATZ3A140012 (STM32H7A3ZIT6Q). Also, when i turn the sensor 90 deg the 0.5g moves to the other axis, and regardless of the range scale I choose, the readings adjust themselves so that it still gives the 0.5 G after applying the conversion factor .The first line shows the reading from the CTRL1_XL register and breaks it down into the configurations in that register (which in this picture is set up to +-2G range and sampling of Hz)the second lines show the reading from the OUTZ_L_A (2Ch) and OUTZ_H_A (2Dh) registers, then it combines that into the raw data and multiply by the s

I am making a simple inclinometer using IIS2DLPC. The 'Zero-g offset change vs. temperature' of IIS2DLPC is specified as a maximum of ±1mg/℃, but some of the boards I made have reached 2.93mg/℃.Some have relatively good values ​​of 0.3-0.4mg/℃, while others have values ​​of 0.8-1.6mg/℃, so the characteristics vary.2.93mg/℃ is the worst value evaluated.Since most of the units can be measured cleanly, I think that it is not a problem with the circuit board, but some external factor is at work. Please let me know if there are any possible factors.Note that the measurements are taken only on the printed circuit board, without being assembled into a case.