MEMS (sensors)

I have configured the activity/inactivity function, but I only get the interrupt raised on inactivity, not on activity. Is this function supposed to be able to alert me to both activity and inactivity? Or is it just inactivity that raises the interrupt?

Hello Everyone!!!I am using ISM303DAC in my project E-Compass, I am facing an issue regarding hard iron calibration. in datasheet it is mentioned that we have do hard iron calibration using external processor  and has to store those values in the internal registers of sensor.  here i don't know how to do the hard iron compensation can anyone please let me know the procedure/steps to do the hard iron calibration if any example is available with you please provide me.Thank you,regards,ANIL.

Hi, I am using MKI239A and MKI109V3 with LSM6DSV (IMU). Knowing the full scale of accelerometer and gyroscope, I still need resolution information to calculate the exact readings. I did not find relevant resolution info on data sheet... Could you please provide some information? thanks for your help! @Federica Bossi 

Hello, I am using STM32H745 to setup and communicate with LIS2DS12 accelerometer via SPI 4-wires. I am trying to setup the accelerometer and I started with reading the WHO_AM_I register. It's default value is (43h) and I changed the value of the first bit to '1' so that my STM32 can read the value. The SPI communication is setup as follows: With the read and write fucntions set like this: HAL_StatusTypeDef spi_write_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret; uint8_t address = regAddr & 0x7F; uint8_t sendData[2] = {address, *pData}; //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 0); ret = HAL_SPI_Transmit(&hspi2, sendData, 2, 20); //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 1); return ret; } HAL_StatusTypeDef spi_read_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret = 0x01; uint8_t address = regAddr | 0x80; // Set the Read/Write bit to 1 for read operation uint8_t sendData[2]= {address,0}; uint8_t receiveData[2] = {

Hello I I'm using the -> GitHub - STMicroelectronics/STMems_Standard_C_drivers, for presence and motion detect with a NUCLEO-F401RE directly connected with STEVAL-MKI231KA, i can read the sensor ID and setup the other paramethers, but my question is related to wakeup_thread, i to setup an external interrupt connected to INT1 from the board sensor to toogle this variable? without this i think that i will not start to read the sensor properly. the example is: https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/sths34pf80_STdC/examples/sths34pf80_tmos_presence_detection.c   /* handle event in a "thread" alike code */            if (wakeup_thread) {              wakeup_thread = 0;              motion = 0;              presence = 0;

Hello,I want to enter the decimal part of a number in to filed "Float" (Advanced Features -> FSM -> Converter).The Decimal Separator in the Regional Settings of the system I use (KDE/plasma) is a comma.It seems that the "Float" field only accepts a decimal point as decimal separator, but I cannot enter the decimal point character in this field: after pressing "." key nothing appears in this field.I can enter the "," character as decimal separator, but after conversion I get the wrong result in the field "Float16".Am I missing a some option in MEMS-studio settings to solve this problem?Additional info: if the "Float" field already contains a decimal point, I can enter "." character, but if the field was initially empty, then I can't enter "." character.P.S. I remember I had the same problem on Windows and in the previous version of MEMS-studio. MEMS-studio v1.3.0My system: Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6

Hello, I am using STM32H745 to setup and communicate with LIS2DW12 accelerometer via SPI 4-wires. I am trying to setup the accelerometer and I started with reading the WHO_AM_I register. It's default value is (43h) and I changed the value of the first bit to '1' so that my STM32 can read the value. The SPI communication is setup as follows: With the read and write fucntions set like this:     HAL_StatusTypeDef spi_write_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret; uint8_t address = regAddr & 0x7F; uint8_t sendData[2] = {address, *pData}; //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 0); ret = HAL_SPI_Transmit(&hspi2, sendData, 2, 20); //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 1); return ret; } HAL_StatusTypeDef spi_read_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret = 0x01; uint8_t address = regAddr | 0x80; // Set the Read/Write bit to 1 for read operation uint8_t sendData[2]= {address,0}; ui

Hi, i'm trying to enable the tilt feature in an LSM6DSO on INT1 or INT2 but isn´t been possible until now. I´ve read the datasheet and used the example as template but for some reason the interrupt is not working. Looks like the embedded functions are not being activated correctly.  These are the registers that I'm using to configure it. First hex is the register direction and the second one is the value to write.   ConfigRegisters(IMU,0x01,0x80);ConfigRegisters(IMU,0x04,0x10);ConfigRegisters(IMU,0x0A,0x10);ConfigRegisters(IMU,0x17,0x80); //RW registerConfigRegisters(IMU,0x01,0x00);ConfigRegisters(IMU,0x5E,0x02); Am i missing some register to configure?  Thanks,

Hello,I'm currently working with the ICM-20602 IMU sensor and the LSM6DSV16X IMU sensor in an STM32-based project using STM32CubeIDE for stm32f446re. I've successfully interfaced with the ICM-20602 sensor and am able to read the WHO_AM_I register after ensuring that the sensor is out of sleep mode by configuring the POWER MANAGEMENT 1 register. Here is the relevant code I used for the ICM-20602 sensor: /* Function to read a register from the ICM-20602 via SPI */uint8_t spi_read_register(uint8_t reg_addr) {uint8_t tx_buf[2] = { reg_addr | 0x80, 0 }; // MSB set for read operationuint8_t rx_buf[2] = { 0, 0 }; HAL_GPIO_WritePin(GPIOD, GPIO_PIN_2, GPIO_PIN_RESET); // Set CS lowHAL_SPI_TransmitReceive(&hspi3, tx_buf, rx_buf, 2, HAL_MAX_DELAY);HAL_GPIO_WritePin(GPIOD, GPIO_PIN_2, GPIO_PIN_SET); // Set CS highreturn rx_buf[1];} /* Function to write to a register over SPI */void spi_write_register(uint8_t reg_addr, uint8_t value) {uint8_t tx_buf[2] = { reg_addr & 0x7

Hello! I didn't find Driver of MPL115A2 for STM32, I tried to create a simple oneI'm not able to get dynamic data from the sensor.I connected it as below:VDD > STM32 3.3VGND > STM32 GNDSCL > PB8SDA > PB9HSR > not connectedSDWN > not connectedThis is the code i'm trying    // MPL115A2 registers with bit shifts for I2C communication #define MPL115A2_REG_PRESSURE_MSB 0x00 // Padc_MSB #define MPL115A2_REG_PRESSURE_LSB 0x01 // Padc_LSB #define MPL115A2_REG_TEMP_MSB 0x02 // Tadc_MSB #define MPL115A2_REG_TEMP_LSB 0x03 // Tadc_LSB #define MPL115A2_REG_A0_MSB 0x04 // a0_MSB #define MPL115A2_REG_A0_LSB 0x05 // a0_LSB #define MPL115A2_REG_B1_MSB 0x06 // b1_MSB #define MPL115A2_REG_B1_LSB 0x07 // b1_LSB #define MPL115A2_REG_B2_MSB 0x08 // b2_MSB #define MPL115A2_REG_B2_LSB 0x09 // b2_LSB #define MPL115A2_REG_C12_MSB 0x0A // c12_MSB #define MPL115A2_REG_C12_LSB 0x0B // c12_LSB #define MPL115A2_REG_CONVERT 0x12 // CONVERT // Perform a memory read to read

Hi everyone!!!i am working on motionEC library and there i have observed that it need sensor orientation. can anyone explain me what exactly is this orientation meaning and how it effects the library??reagards,regards,ANIL.

HELLO,Can someone tell me the time accuracy of the output rate of II3DHHC?ThanksTakenari otawa

I am using LSM6DSOX with Unico Gui, how can i plot external data in Unico Gui? Is that possible? The data is in the attachement

I DEVELOP A  STEP COUNTER USING lis2dux12 CHIP.I WANT TO KNOW I HOW I SETUP INTERRUPT IN STEP COUNTER

Hello. We know that lis3mdl is temperature sensitive, i.e. there is a scale shift. From what we have read, this cannot be compensated for with software ( Or maybe it's possible? ). Therefore, can this be prevented physically, e.g. by using some thermal paste? The idea is to prevent lis3mdl from heating up too much. Our operating temperature range is 10-35 degrees Celsius. Thanks.

Hi Team, We purchased the LIS2DW12TR MEMS sensor and we found there is a QR code + T marking on the body of the IC. In the datasheet, there is no mention of body marking. Please confirm that this is the correct part we purchased.Thanks,Abishek

Hi, I am considering IMUs from ST and ADI - ADIS16505. I found that ADI provide their IMUs with "in-run bias stability" and "angular random walk", but ST does not. I also checkout the community about this, and ST only test IMUs in characterization. I find LSM6DSR characterization can be shared. I am looking at the LSM6DSV16BX IMUs characterization for the two parameters. Could you please provide that for my final decision? Thank you very much

Hello everyone, I'm looking for an application note (similar to AN5063 but for the LPS27HHTW sensor) to get an idea of the mechanical integration and any necessary tolerances. Additionally, I wanted to ask the community if anyone has installed two sensors on the same side of the board and what the mechanical implications are in this case.

I use LIS2DS12 This is my init function   void LIS2DS12_Init(void) { uint8_t ctrl_1 = 0x72; //0111 for 6.4kHz ODR [7:4], 00 for 2g [3:2], 1 for high frequency available[1], 0 for BDU not activated [0] uint8_t ctrl_2; // [6] for soft_reset, [1] for disable I2C, [0] for 4 wires SPI HAL_StatusTypeDef ret; ret = spi_read_LIS2DS12(CTRL2_ADDR, &ctrl_2); ctrl_2 |= 0x42; // [6] for soft_reset, [1] = 1 for disable I2C, [0] = 0 for 4 wires SPI ret = spi_write_LIS2DS12(CTRL2_ADDR, &ctrl_2); //reset the accelerometer ret = spi_write_LIS2DS12(CTRL1_ADDR, &ctrl_1); //set the accelerometer to measurement mode spi_read_LIS2DS12(CTRL1_ADDR, &ctrl_1); spi_read_LIS2DS12(CTRL2_ADDR, &ctrl_2); }   with read and write :    HAL_StatusTypeDef spi_write_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret; uint8_t address = regAddr & 0x7F; uint8_t sendData[2] = {address, *pData}; HAL_GPIO_WritePin(G

Hello,I am working with the LSM6DSV16X IMU sensor and interfacing it using SPI mode 3 on an STM32 microcontroller(STM32F446RE) with STM32CubeIDE. My SPI configuration is set with CPOL = High and CPHA = 2nd edge, and I have set the baud rate prescaler to 4, resulting in a baud rate of 10 MBits/s.Before reading the WHO_AM_I register, I configure certain registers as follows:if (spi_write_register(CTRL3_REG, 0x45) != SUCCESS) return ERROR;if (spi_write_register(FUNC_CFG_ACCESS_REG, 0x00) != SUCCESS) return ERROR;However, when I attempt to read the WHO_AM_I register, I consistently receive 0x80 instead of the expected 0x70.Here is a summary of my setup and the issue:SPI mode: Mode 3 (CPOL = High, CPHA = 2nd edge)Baud rate: 10 MBits/s (prescaler = 4)Initial register configurations:CTRL3_REG = 0x05FUNC_CFG_ACCESS_REG = 0x00Could anyone suggest potential reasons for this discrepancy or any troubleshooting steps I should take?Thank you!      

Dear ST technical support.Please can you advise the pin configuration and bus timing (period between active devices) to allow me to connect three of your LPS22HB pressure sensors in parallel on the same SPI bus?The CS pin is used to enable the SPI function on one device but it is not clear if the other SPI pins can be common with other devices.Thanks and regardsDuncan

Posted on June 05, 2017 at 20:31Hi,We're using LIS3MDL to detect changes in the earth magnetic field due to various metallic objects flowing in the sensor proximity. So, we are not interested in the correctness of the absolute values in order to properly detect the magnitude of the field or the North direction, we only need to compare the magnitude of the field between consecutive measurements. That being said, I don't see any reason to calibrate the readings.The problem we are facing is that for unknown reason, the readings (mostly on Z axis, but I've seen also for Y) on some of our sensors are sometimes evolve from initial 'right after boot & install', normal values to really unexpected and different values. The external conditions are the same, the magnetic field is the normal earth field.Please have a look on this table, it's basically a log with recordings (x1, y1, z1 is the first measurement, x2, y2, z2 - second measurement, typically after two minutes):Id  &n

We embed lis3mdl on our board that we produce, most of them are perfect, unfortunately there are single pieces where the magnetic north is wrong, the heading is wrong by up to 60-100 degrees. What could be the reason ? Regards. 

As you can see, I was doing a test where I tried setting the gyroscope and accelerometer to power down mode and gave it a 10ms delay, which I called time 1, while I again turned the gyroscope on The accelerometer is set to high-performance mode, and a 70ms delay is given to the data again. This time is called time 2. After exiting, I start reading the data. At this time, the data is read normally after leaving this code, but between time 1 and time After the time of 2 is changed (only the time becomes shorter), the read data will have data errors for a long time. I would like to ask you for some advice. At the same time, time 1 and time 2 are 300us and 70ms respectively in the manual. Want to know why there is such a big discrepancy? Below is my code. Thanks，  

Hello, I am trying to interface a TI MCU with three LSM6DSV16X sensors using SPI communication on the same bus. My setup consists of 3 chip select lines with a 10 kΩ pull-up resistor (on all sensor boards), POCI (MISO) with a single 10 kΩ pull-up resistor (on 1 sensor board), PICO (MOSI) and the CLOCK line with nothing, with a long distance shown on the schematic (attached file). All sensors are powered with 3.3V. I am facing an issue that I can't solve. This setup seems to be unreliable, as I can't consistently read all three chips correctly. My flow is as follows:Configure MCU to communicate in SPI mode 3 with 1MHz frequencyGlobal reset of the device (writing 0x04 to FUNC_CFG_ACCESS)Wait 100ms (more than the application note, for some reason 30ms doesn't work every time)Read the WHO_AM_I register For some reason, most of the time I can read 0x70 on two chips, but the third one shows different behaviors. The most frequent responses I get are 0x00, 0x60, or som