MEMS (sensors)

I need to configure LIS3DH to generate FIFO full interrupt in INT1 pin. Once my MCU gets the hardware interrupt, it will read entire FIFO. And the loop should continue. Can anyone help me what are the correct steps to configure and read FIFO?Regards, 

I am using an adafruit stm32f405 feather, with the hal rather than arduino. I have I2c, and CDCworking now, and would like to add audio functionality with a mems mic.The I2s pins are available pins, but the clock cannot get to a low enough speed(1MHZ) through PLL.I thought about using divided master clock output ,and jumping to external source for I2s clock, but thesepins are not available. Can I use TIM3_CH2, jumped to an SPI clock input, and read the data using that periipheral.The data sheet for the mic says it can use I2s, SPI, DFSDM, and sai.  SPI is the only one that is both present, and available. I haven't seen any examples doing similar, unlike I2s cube examples. Any advice? Many thanks in advance.

I have a LIS3MDLTR connected over I2C on an aerial system that is used as part of our GNC system.  In our most recent test we received data from the magnetometer that appears to have gotten "stuck" reporting to exact same measurement (see below).  The system was flying from minute 0 until around minute 10.I've seen this behavior in the lab as well and I have found that I can temporarily fix this by rebooting the magnetometer by writing to the REBOOT bit in CTRL_REG2.  While this does resolve the issue, it frequently re-appears (about every 2-3 power ups).  What is causing this issue and how can I avoid it?I have multiple peripherals connected to the I2C bus that continue operating correctly so it is not an issue with the I2C master.The LIS3MDLTR is configured as follows.0xFC, // CTRL_REG10x0, // CTRL_REG20x0, // CTRL_REG30x0E, // CTRL_REG40x40 // CTRL_REG5Since I'm reading from the magnetometer at a rate of 10Hz, significantly lower rate than it's 80Hz output r

Hello,How is the INTERNAL_FREQ_FINE register set in the ISM330?Is it factory calibrated or is there on board logic that allows it change with age/temp/etc.?Thank you,Brandon M

Hello!I took two attemps and recorded measurements in steady state (2 and 3 hours) that i want share.Config:G/XL FS: default ODR 104HzSensor data polled at rate ~ 90HzSome standby/wakeup stuff:TAP_CFG0 (56h) = b0101.0001TAP_CFG2 (57h) = b1000.0000WAKE_UP_DUR (5Ch) = b0100.0000WAKE_UP_THS (5Bh) = b0000.0001MD1_CFG (5Eh) = b0010.0000Can the bias drift be explained somehow?Many thanks

Hi.I am working on evaluation with STEVAL-MKI210V2K. I use Unico to get sensor data, however what I really want is post-fusion data. Looking at other forum questions, it seems like Unico gives a "fusion" option on the left vertical tab. I don't have it (as well as the QVar option).Is it because the product I am using does not have this feature in the HW/FW level?Or am I missing something? Thanks.  

Hi,     We are use openWRT and  ism330dhcx and LIS2MDLTR  on board.  The ko driver   has been created and  insert into kernel . When read data from  /sys/devices/platform/i2c_gpio@0/i2c-0/0-006a/iio:device2/in_accel_XXXX,   We has found the Z value is random ( device dosn't move ).   it cause our heading value calculation  is not stable.   Any suggestion ?BR, arprip  Here is the log============check imu ko module =0ST imu & mag40 ko already loadedST ISM330DHCX (G sensor):accel x_raw= 804, x_scal=0.001196411accel y_raw= -18, y_scal=0.001196411accel z_raw=32764, z_scal=0.001196411check imu ko module =0ST imu & mag40 ko already loadedST ISM330DHCX (G sensor):accel x_raw= 278, x_scal=0.001196411accel y_raw= -16, y_scal=0.001196411accel z_raw= 8070, z_scal=0.001196411check imu ko module =0ST imu & mag40 ko already loadedST ISM330DHCX (G sensor):accel x_raw= 159, x_scal=0

Hi everyone! I am using LSM6DS3 in a very simple setup: For the debugging purposes I am only using accelerometer, ODR is set at 416Hz, fifo is enabled in continuous mode and set at the same freq, no decimation. Only XL data is set to be stored in fifo. I am reading data from fifo every second while buffer is constantly being filled. In random intervals the data I am reading gets corrupt in different ways: One axis data is simply missing (even reading the pattern confirms that there is an entry missing)Value from one axis is read out at another axis (pattern) (e.g. if device is standing still on the table, and normal reading is 10,10,-990, one of the readings can be -990,10,-990 or 10,10,10, while pattern values are always 0,1 and 2. Sometimes it even happens that the pattern is an invalid value (>2). I have tried reading values in a numerous ways (reading fifo_status 1,2,3,4 and then fifo L and fifo H) and all possible combination of those. I have also tried reading whole fifo in a

Hi,  I'm trying to get the FIFO working on the LSM6DSOX on a custom board with a silicon labs microcontroller, communicating both through SPI. I have checked the application note at https://www.st.com/resource/en/application_note/an5272-lsm6dsox-alwayson-3axis-accelerometer-and-3axis-gyroscope-stmicroelectronics.pdf and followed the example code at https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsox_STdC/examples/lsm6dsox_fifo.c, but no success, so I'm wondering if I'm missing something or it's a hardware problem.  I'm able to read the device id and communicate normaly with the IMU through SPI, retrieving acc and gyro readings without issues. This is my code for enabling the FIFO:  lsm6dsox_reset_set(&imu_dev, PROPERTY_ENABLE); uint8_t rst; do { lsm6dsox_reset_get(&imu_dev, &rst); } while (rst); /* Disable I3C interface */ lsm6dsox_i3c_disable_set(&imu_dev, LSM6DSOX_I3C_DISABL

I am trying to read the data of the accelerometer and gyroscope of the LSM6DSV16B with an FPGA. I build a 4 wire SPI-Interface. I am able to write data to the chip and the chip is capable to give data out. But sometimes the output of the chip gets driven for a fraction of the clock cycle. This creates the spikes which you can see in the picture. Nothing other than the chip is driving the dataline. The FPGA is configured as an input and just reads the high or low state at the rising edge of the clock. As you can see in the screenshot sometimes I get a voltage spike an the data out line, sometimes the pin gets driven normally from falling edge to falling edge. Is this behavior normal or expected? Or is something wrong with the chip. I used the STEVAL-MKI241KA development board. The issue arises one the square board aswell as the earphone board.

Hi!I've configured an ISM330DHCX in CubeIDE with the X-CUBE-MEMS package. The code was generated, however, I have absolutely no idea how to initialize and use the sensor in my main.c code. So far I've managed to make following observations:There is a ISM330DHCX_RegisterBusIO function. It needs a ISM330DHCX_Object_t pointer and ISM330DHCX_IO_t. When I tried to create and fill ISM330DHCX_IO_t values by hand, I've noticed, that I can't find any function, that suits the WriteReg and ReadReg fields. ISM330DHCX_WriteReg_Func and ISM330DHCX_ReadReg_Func seem to be written with I2C in mind, requiring address and register value, while BSP_SPI2_Send and BSP_SPI2_Recv, generated in custom_bus.h file along other files to support the MEMS module, seem incompatible with the needed type. There is a ISM330DHCX_Init() function, but i'm not sure it can be called before calling RegisterBusIO, which leaves me with the previous problem.So how do I initialize the MEMS for 4-wire SPI bus, and why isn't this

Hi,We are trying to evaluate Sensortile.box (STEVAL-MKSBOX1V1). I downloaded the apk from the ST Website for android app and installed it.I followed the steps mentioned in UM2580. When I tried to connect the device to app. It was asking for firmware upgrade. I did the firmware upgrade. It completed. Later. I again connected to the device and using the play button, I uploaded the PEDOMETER APP. App was uploaded successfully.Step Counting is happening in the app. However, When I try to upload the Human activity Recognition app, it displays Timeout error (See attached image).I have gone through the previous posts with similar reported issues. Using STLINK, I erased the flash and loaded the BLEFOTA_BL_1.0.0.bin. (After loading this .bin file, device name changed to stboot. I was unable to upload any apps like pedometer etc.I am also observing that the device becomes unresponsive after few minutes and is not discoverable from the app. Request you to suggest how to resolve the time

Hello,I am working on water ingress application experiment, and I want to know how to evaluate different pressure sensors to figure out which one is best for me? Since this application involves water, I think a water proof option would be good. But what are some basic tests I can perform to evaluate the different pressure sensor's performance? I apologize for the (hopefully) very basic question, I am new to using pressure sensors.RegardsAlex

I use the official lsm6ds3tr-c-pid driver,Here is the code I initialized:  u8 who_amI = 0; lsm6ds3tr_c_device_id_get(&dev_ctx, &who_amI); if (who_amI != LSM6DS3TR_C_ID) { printf("lsm6ds3tr_c_device_id_get err,%d,%d", who_amI, LSM6DS3TR_C_ID); } printf("LSM6DS3TR id:%x\n", who_amI); lsm6ds3tr_c_reset_set(&dev_ctx, PROPERTY_ENABLE); do { lsm6ds3tr_c_reset_get(&dev_ctx, &rst); } while (rst); /* Enable Block Data Update */ lsm6ds3tr_c_block_data_update_set(&dev_ctx, PROPERTY_ENABLE); /* Set full scale */ lsm6ds3tr_c_xl_full_scale_set(&dev_ctx, LSM6DS3TR_C_2g); lsm6ds3tr_c_gy_full_scale_set(&dev_ctx, LSM6DS3TR_C_250dps); lsm6ds3tr_c_int_notification_set(&dev_ctx, LSM6DS3TR_C_INT_PULSED); lsm6ds3tr_c_pin_mode_set(&dev_ctx, LSM6DS3TR_C_PUSH_PULL); lsm6ds3tr_c_pin_polarity_set(&dev_ctx, LSM6DS3TR_C_ACTIVE_HIGH); lsm6ds3tr_c_int1_route_t int1_route = {0}; int1_route.int1_drdy_xl = PROPERTY_ENABLE; int1_route.int1_drdy_g = PROPERTY_ENA

I'm working through the "Getting started with the X-CUBE-ISPU software package for STM32Cube" tutorial and trying the ISPU_Logging example.NULCEO F411RE -> X-NUCLEO IKS02A1 -> STEVAL-MKI229AA (LSM6DSO16IS)(This is also my first time using the Cube IDE so not sure where things are as its a different layout to the tutorial now)I've set up the hardware pin outs & configured the software components for the appropriate sensors, generated the code, built & downloaded onto the board. The IDE says this was all successful...File download completeTime elapsed during download operation: 00:00:01.175Verifying ...Download verified successfully  I open up the Unicleo-GUI and am met with the following... So far so good, the board & its sensors have been recognized and that's the same sensors I added in the software component sectionI click apply & ...  What am I missing here? I've stepped through the document a few times now but cant for the life of me find w

I am working with the X-NUCLEO-IKS4A1 expansion board and NUCLEO-F401RE.I’ve successfully programmed and run the examples provided by MEMS Studio and those in the STMems_Finite_State_Machine/application_examples/lsm6dsv16x repository. Additionally, I’ve used .ucf files and AlgoBuilder to generate C programs.But I have no idea how to program my own FSM from scratch. I have read some of AN5882 but I am not sure if that is the right way to learn about FSMs. Are there any tutorials I am missing?How do I implement my own FSM from scratch based on my own requirements and application? I would like pointers to some good tutorials with examples which explain how to program the FSM.

Hi ST technical support，Our product need to pass Certification, this certification requires thermal resistance of LIS2DW12TR, LGA-12 package, Certification body required write “thermal resistance” into datasheet or provide formal test report of thermal resistance. Otherwise, it will not be recognized. Could you please provide LIS2DW12TR’s datasheet with “thermal resistance”, or provide the test report of thermal resistance? Thank you very much. Best wishes,Susan

Hello, I am currently working on a project concerning the degradation of a rotary machine overtime. To detect this degradation, we want to study vibration using the IIS3DWB accelerometer which is on the STWINKT1B. Till now, I am taking 30 seconds of data "manually" every 2 days by using the ST BLE Sensor app. With those data I am checking the evolution of the spectrum to try to find a pattern.I was wondering if it is possible to make the acquisition process automatic and if yes how.For now, I am using the firmware FP-SNS-DATALOG2_Datalog2. I have very little knowledge in firmware programming so if you can use a simple language in your answer I would really appreciate it :) 

I recently began working on an driver software for a magnetometer application, which is intended to support both the LSM303 (the LSM303DLHC, to be exact), and the HMC5883L from Honeywell.And I didn't fail to notice that both devices have identical I2C addresses and identical values for the identification register values (IRA, IRB and IRC).My question would be, is this intentional ?Not that it is of utmost importance to me, I found another way to distinguish between both. The HMC5883 has no accelerometer part, and when I can write into a RW accelerometer config register and read the same value back, I deal with a LSM303, else with a HMC5883.

Hi everyone,We are using the STEVAL-STWINKT1B board as a reference for the study of condition monitoring applications.In particular, we have always used the board with the default firmware. For the configuration and acquisition of data on the SD card, the STBLESensor application was used (https://www.st.com/en/embedded-software/stblesensor.html)Instead, for reading and converting data, we used the FP-SNS-DATALOG1 function package (https://www.st.com/en/embedded-software/fp-sns-datalog1.html). In the specific case of microphones (both digital and analog: IMP34DT05 and IMP23ABSU), it is not possible to configure a different amplitude/volume by STBLESensor app; it happens that when the sensor is too close to the process to be monitored, the values ​​go into saturation (clipping). In order to modify these microphone parameters, is it necessary to modify the firmware or are there different firmware versions that already do this? Thanks in advanceBest regards

I am working on ism330dlc to find gyroscope x, y, and z values. I am getting x, y, and z values. I am also getting variable x, y, and z values when the board is maintained constant. I wrote registers are 0x1204,0x1160,0x1060,0X22,0X23,0X24,0X25,0X26, and 0X27. Pleas

Hi all,We got odd issue with LSM6DSO32 IMU on our device. After like 6-10 hours of working it begins to not response correctly and it stays until completely power replug. Our code tries do reinitiate IMU when it happens, but within that "frezze" state it reads chip id as 0x00 using lsm6dso32_device_id_get (which we're using to determine which chip is on board) instead of 0x6C.We're using latest libraries from https://github.com/STMicroelectronics/lsm6dso32-pid Whole init sequence:imuSoftReset(); imuErr = imuReadID(&imuID); if(imuErr != imuOk){ return GRAVITY_VECTOR_INIT_ERROR; } imuErr = imuInit(imuID); if(imuErr != imuOk){ return GRAVITY_VECTOR_INIT_ERROR; } ------------------------------ void imuSoftReset(void) { uint8_t resetValue = 1; // Set the IMU's software reset bit and wait for it to clear after a reset // Note: didn't use LSM6DSV32X's reset set function because that function also sets a new global reset bit not present in LSM6DSO32. Reset later if identif

Hi, stNow I've found some new problems.​Sometimes the value read from who AMI register will be 0x48. After finding this problem, I suspect that the connecting wire is unstable. After replacing the DuPont wire, the value read back to normal (0x6b). I want to ask what is the reason for this strange phenomenon.In addition, I found that the accelerometer data rate can only be set at 833hz or below. If the accelerometer data rate is set above 1667hz (1667hz,3333hz,6667hz), the value read from the register is still the previous value, that is, the data setting above 1667hz always fails. By the way, there is no such phenomenon in the setting of gyroscope.​So I updated the driver file to the version of 5 days ago (ism330dhcx: fixed examples # 107) in Git library.A step was added to the driver calling routine of this version(ism330dhcx_device_conf_set), but this step didn't seem to succeed.After execution, I also read the value of this register(ism330dhcx_device_conf_get(&dev

I just bought the latest SensorTileBox (STEVAL-MKSBOX1V1), can I add RTC to the Level function? I need timestamps added to the accelerometer output. Level Function is missing in the available functions under Custom Apps.

 We want to use iio buffers to read accelerometer data. I tried the following, but it did not work. root@FAFUSION:/sys/bus/iio/devices/iio:device2# ls buffer current_timestamp_clock events in_accel_scale_available in_accel_y_raw mount_matrix of_node sampling_frequency scan_elements uevent buffer0 dev in_accel_scale in_accel_x_raw in_accel_z_raw name power sampling_frequency_available subsystem waiting_for_supplier root@FAFUSION:/sys/bus/iio/devices/iio:device2# cat name ism330dhcx_accel root@FAFUSION:/sys/bus/iio/devices/iio:device2# root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_x_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_y_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_z_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > buffer0/in_accel_x_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > buffer0/in_accel_y_en root@FAFUSION:/sys/bu