MEMS (sensors)

Hi, I am reading from IMP34DT05 (master receive, PDM), and I always receive 0x00 0x7F 0xFF 0xFF ...and 0xFF's, ever after, until reset of SAI (disable-enable). Playing sound into mic has no effect. In debugger, immediately upon SAI enabled, FIFO is full and underrun flag is on, before any data is read. Here is my current ioc config:And register values, just in case (WB55):Mic L/R is on GND. Mclk is 50MHz.I tried different configs with same result; frame synchro length, 8/16kHz, rising/falling edge.Where am I wrong?

Dear community,I am trying to detect metalic objects (train axles) that are passing above two LIS3MDL sensors. For this purpose I am using LIS3MDL breakout boards from PololuWhat I notice is that often, what seems randomly, the signal becomes noisy during the data gathering process.To provide an example, I have plotted the sensor's X-axis output in a graph.In the left half of the graph you can see that the signal is normal, and in the right half you can see the signal become noisy.Nothing really seems to  change in the external environment at the moment that this transition occurs. We see this in multiple datasets.Has such behavior been seen before with this sensor? If so, what could be the cause of this and can it be fixed?I will give a few details about my setup below:LIS3MDL configuration:Ultra-high performance mode155 Hz in continuous conversion mode.Scale: 4 gaussThe VVD and Vin pins on the LIS3MDL are shorted together and connected to 3.3v.There are two LIS3MDL bre

I tried running the code present in the github link -  https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dso_STdC/examples/lsm6dso_tap.cfor Tap detection. But in the logs, I'm not able to see the axis/sign, even after tapping(both single and double tap). 1) Do I need to configure Interrupt pins for this to work? as I tried polling.2) Can someone explain me the background of how tap detection is working? and how to configure the time. 

Is it possible to execute features such as pedometer, activity/inactivity detection, tilt/tap, with same configuration of ODR, Full scale? How can I include all these features in a single program?Can someone explain this please

 whenever double tap is detected, I'm getting interrupts for both single tap as well as double tap. currently both are routed to int2 pins. I tried routing single tap to INT1 and the double tap to INT2 pin, to ensure single tap doesn't operate under double tap condition. but both single and double tap interrupt is being generated.  How do I get/print only single tap and double tap? 

hello,i have few basic Question regarding accelerometer sensor.1. accelerometer data coming from imu sensor that is 2's compliment data, so should i receive this data in signed integer or unsigned integer? 2. i want to know whatever raw data is coming from this sensor resgistors of accelerometer that is mg/LSB or only g ? if it is mg/LSB then how i can covert into g (refer ±2g)?3. formula of convert g into (-180° to 0 to 180°) ?please refer below attached  code or screenshorts

Hello,I set ODR_XL target during inactivity(INACTIVITY_DUR XL_INACT_ODR_[1:0]), but when I read CTR1 ODR in inactivity mode, it doesn't change to the setting, why?

Hello,First time posting in this forum!I'm evaluting the STHS34PF80 sensor and went through these materials: Datasheet & AN5867.However, I could not find any information regarding the interpretation of the object temperature (after calculating the signed value of 16 bit (TOBJECT_L and TOBJECT_H), then divide by the sensitivity).My very first thought was that this represents the so-called absolute object temperature value, as the sensor is T-MOS based technology and its sensitivity is calibrated with a black body covering the full field of view. However, the function of f(TOBJECT_L, TOBJECT_H, SENS_DATA), doesn't give me that.Rather I have a feeling that it gives me the difference between the object temperature and the ambient temperature. I have attached an image to show you how the values changed when I have my hand approaching the sensor, to completely cover it, then get my hand off the sensor.I have tried with both the ST driver: https://github.com/STMicroelectron

We are currently using the ST LPS33HW pressure sensor in an industrial IoT application. I am aware that this product is being phased out, and we have plans to replace it with a different offering from ST. However, right now, we have 100s of these in the field and have noticed a couple anomalies.In our application, we are actually using the two LPS33HW per system to get a pressure difference between two regions in an outdoor facility. Typically, these regions are approximately the same temperature. However, with some of the cold weather recently in the US, significant temperature differences (10°C or more) have been observed, and the pressure difference between our sensors in each location show a correlated pressure shift. We would like to calibrate this out if possible.I am aware that the one point calibration exists, and we plan to implement this at some point in manufacturing. However, we're looking for solutions to post-process data from the parts already in the field.Can you provid

I am trying to get the raw data (with timestamp included) from a few IIO devices (hardware sensors, such as accelerometer, gyroscope, magnetometer and barometer) mounted on a linux platform and with the ST drivers. I was able to get the data for the accelerometer and for the gyroscope using the libiio library within a C++ code or using sysfs commands (enabling the buffer). However, for the magnetometer and for the barometer it seems (I'm not expert in this field) this procedure doesn't work. In particular, with the magnetometer (device2), I am able to get the data but not the timestamp (that remains 0).root@dab:/sys/devices/platform/soc@0/soc@0:bus@30800000/30a50000.i2c/i2c-3/3-001e/iio:device2/buffer# hexdump -C /dev/iio:\device200000000  85 01 20 00 34 fe 00 00  00 00 00 00 00 00 00 00  |.. .4...........|00000010  87 01 24 00 31 fe 00 00  00 00 00 00 00 00 00 00  |..$.1...........| I've noticed, from the iio_info commands th

Unico Version: 9.17.2.10FW: V3.60.7HW: MKI109V3 + MKI238AOS: Win10Hi,Can someone explain how the X/Y/Z axis on Unico are related to the OUT_X/Y/Z_H/L register readouts from the LIS2DUX12? On first glance, it looked like X-axis is not getting updated at all (I've tried with two MKI238A units, same results), but after looking closer at the register readout, it seemed like Y = OUT_X, Z = OUT_Y, and I have no idea where X came from or where OUT_Z went. What I see on the plots - no movement on X-axis, no matter how much I shook it.Controls are set to "Easy Configuration"Register settings and readouts.Comparing OUT_X/Y/Z registers and what Unico displays. X_OUT was 0xFCB0 = -848, which was close to 'Y', and Y_OUT was 0xF190 = -3696, which was close to 'Z'. I couldn't tell where the "X=13" came from, and it never moved. 

Hi all, We have integrated an LIS2MDL magnetometer into our custom PCB. We have recently been running some tests on the boards, and are collection raw data from the sensor via the I2C line. In our testing, we have found that different boards appear to be outputting different raw values in what should be the same conditions. What we have done is taken the raw data from the devices, calculated the magnitude ( sqrt(mag_x^2 + mag_y^2 + mag_z^2) ) which provides the following pieces of information. All devices are placed in the exact same location in the exact same orientation when the data is recorded. Values are in LSBs, where 1LSB = 1.5 mG: DeviceX DirectionY DirectionZ Direction Magnitude# 1-3-15358163# 2126-218454519# 3132-315211404# 4262-376325561 We have been testing the devices with various paramagnetic and ferromagnetic materials, so I'm wondering if there was some sort of bias introduced that I am unaware of. Regardless, I am looking for some explanation a

I have this MEMS sensor on a custom board to detect landscape or portrait mode of my device.The problem is that it doesn't generate an interrupt.- 4D mode should be sufficient.- Range 2g- Tested different ODR settings. My current code is now:     void tilt_init(void) { dev_ctx.write_reg = platform_write; dev_ctx.read_reg = platform_read; dev_ctx.handle = &SENSOR_BUS; lis2de12_boot_set(&dev_ctx, PROPERTY_ENABLE); lis2de12_pin_sdo_sa0_mode_set(&dev_ctx, LIS2DE12_PULL_UP_DISCONNECT); lis2de12_high_pass_mode_set(&dev_ctx, LIS2DE12_NORMAL); lis2de12_device_id_get(&dev_ctx, &whoamI); /*Set Output Data Rate */ lis2de12_data_rate_set(&dev_ctx, LIS2DE12_ODR_400Hz ); /*Set full scale */ lis2de12_full_scale_set(&dev_ctx, LIS2DE12_2g); /* Enable Block Data Update */ lis2de12_block_data_update_set(&dev_ctx, PROPERTY_ENABLE); /*Configure power mode */ //lis2de12_power_mode_set(&dev_ctx, IIS2DLPC_CONT_LOW_PWR

i am using i2c1 and uart2 to show any values i have created program but i am not getting any values from accelerometer. can you tell me any one, solution of this problem I2C_HandleTypeDef hi2c1; UART_HandleTypeDef huart2; /* USER CODE BEGIN PV */#define LIS3DH_ADDR 0x19// I2C address of LIS3DH accelerometer  /* USER CODE END PV */  /* Private function prototypes -----------------------------------------------*/void SystemClock_Config(void);static void MX_GPIO_Init(void);static void MX_I2C1_Init(void);static void MX_USART2_UART_Init(void);/* USER CODE BEGIN PFP */ /* USER CODE END PFP */ /* Private user code ---------------------------------------------------------*//* USER CODE BEGIN 0 */ void accelerometer_read_data(uint8_t reg, uint8_t* data, uint16_t size) {   HAL_I2C_Master_Transmit(&hi2c1, LIS3DH_ADDR, &reg, 1, HAL_MAX_DELAY);HAL_I2C_Master_Receive(&hi2c1, LIS3DH_ADDR, data, size, HAL_MAX_DELAY);} /* USER

Anybody know where I can get the data sheet for MEMS AR products and how can I purchase it?Thank you.

I have the Sparkfun version of the LSM6DSV16X. I used it with the Arduino IDE and everything works easily. I migrated that LSM6DSV16X board to using a Nordic nrf5340dk. There doesn't seem to be a working library for the LSM6DSV16X, but that is ok as I would like to control it directly over I2C.I am able to read WHO_AM_I = 0x70. I am also able to read LSM6DSV16X registers that have default values.What I can't do is read any values from "output" registers that should hold Accel and Gyro data. I imagine it's because I don't have the configuration bits set correctly as anything I read comes back 0x00.I2C, IMU's, LSM6DSV16X, and the nrf5340 are fairly new to me, can you help me with steps to take to set the LSM6DSV16X up manually so that I can get the same Accel/Gyro output I was getting from the Arduino library? This is the general idea of how I expected it would work. I believe that I am supposed to read registers 0x22-0x2D? Any advice would be appreciated.  i2c_b

I have used the LIS3LV02DQ before but it is no longer being made. A new circuit has the IIS328DQ but I can not get it to work as the did. I can successfully get the WHO_AM_I to return and set/read the control registers so I know the SPI is working fine. All I want to do is continuously read the X, Y, and Z values after a Data Ready interrupt.My code first does a WHO_AM_I, then sets the config registers with CTRL_REG1 = h20 (Normal mode, 50hz, xyz off). Then I read all the registers and print to a terminal, then turn on xzy, read INT1_SRC to clear any interupt 1, then wait for Data Ready. Data ready never happens.What am I doing wrong? How can I make it work just like a LIS3LV02DQ? Here is what is printed to the termial:WHO AM I - 32REG h20 = 20REG h21 = 00REG h22 = 82REG h23 = 80REG h24 = 03REG h25 = 00REG h26 = 00REG h27 = 00REG h28 = 10REG h29 = 01REG h2A = C0REG h2B = 01REG h2C = 10REG h2D = 3EREG h2E = 00REG h2F = 00REG h30 = 00REG h31 = 00REG h32 = 00REG h33 = 01REG h34 = 00R

Does ST offer any IP67 microphones with analog output?

I'm trying to figure out if a latched interrupt affects the INT pin signal. I'm working with Arduino. The datasheet says the following on page 44:AOI-6D = ‘11’ is direction recognition. An interrupt is generated when the orientation isinside a known zone. The interrupt signal remains while the orientation is inside the zone.I understand that latched interrupt makes the IA bit on INTx_SRC stay HIGH until i read the register.But when I enable LIR, this doesn't seem to be true.Before configuring everything, I reset all the registers to default value. I configured INT1 without LIR and INT2 with it to check the difference.I put a LED on each INT pin.Here's the configuration code:write_reg(LIS_ADD, CTRL_REG1, 0x97); // 0x97: 1344 Hz, enable XYZwrite_reg(LIS_ADD, CTRL_REG2, 0x00); // 0x00: HP offwrite_reg(LIS_ADD, CTRL_REG3, 0x40); // 0x40: IA1 on INT1write_reg(LIS_ADD, CTRL_REG4, 0x30); // 0x30: 16gwrite_reg(LIS_ADD, CTRL_REG5, 0x02); // 0x08: LIR_INT1, 0x02: LIR_INT2write_reg

While I’m using ASM330LHH the gyroscope’s data jump to unusual value just once sometimes . The data rate is 10hz 

Hi all, I'm trying to move Finite State Machine config from devkit using Unico GUI to final application. I've prepared movement wakeup example from FSM datasheet in Unico, which is working totally fine on devkit, it could even detect knocking in desk.static const uint8_t lsm6dso32_prg_wakeup[] = { 0x50, 0x40, 0x12, 0x20, 0x0C, 0x0D, 0x00, 0x38, // threshold (1.00) 0xAE, 0x23, // hyst (0.03) 0x02, //mask A 0x02, //temp mask A 0x41, 0x75, 0x10, 0x10, 0x22, 0x00 };I've tried to replicate example from here: https://community.st.com/t5/mems-sensors/dear-st-community-i-am-currently-trying-to-setup-a-finite-state/td-p/77183Overall, it doesn't seem to be working, code below gives me infinite interrupts on INT1. So far I discovered on devkit, it happens when fsm is correctly enabled but there is issue in fsm program. It also happens when I comment lsm6dso32_ln_pg_write.ImuError imuInit(void) { uint8_t id; HAL_StatusTypeDef err = HAL_OK; // Set the IMU's reset bit and wait fo

Posted on June 12, 2017 at 11:07Hi,I have inserted the accelerometer in a custom board.Is is connected via I2C to a microcontroller, Vdd and Vdd_IO both connected to 3V3.In my application the micro controller awakes when the acceleration on all the axis is grater than a predetermined threshold.The configuration works fine and also the data read have sense but the INT1 pin remains low.Following the registers configuration:&sharpdefine IIS2DH_CTRL_REG1_DATA         ((BYTE)0x47)  // ODR = 50Hz, Normal Mode, X + Y + Z axis all enabled&sharpdefine IIS2DH_CTRL_REG2_DATA ((BYTE)0x00) // filter disabled&sharpdefine IIS2DH_CTRL_REG3_DATA ((BYTE)0x40) // I1_AOI1; AOI1 interrupt on INT1&sharpdefine IIS2DH_CTRL_REG4_DATA ((BYTE)0x30) // FS = +/- 16g, No High Resolution&sharpdefine IIS2DH_CTRL_REG5_DATA ((BYTE)0x08) // Latch Interrupt request on INT1_SRC&sharpdefine IIS2DH_CTRL_REG6_DATA ((BYTE)0x00) // INT pins active high&sharpdefine IIS2DH_IN

Hi everyone,   First of all, I use a STWINBX1 board, which include a MCU and several sensors. I try to get the magnetic field by reading the output of the magnetometer (IIS2MDC), but the output value seems false. Please note that : - I checked the PIN configuration on STM32 CubeIDE, and the PINs are well configured. - I use HAL library to configure the chipset (IIS2MDC), and to use I2C protocol. - I tested 2 differents methods of reading the output using I2C functions from HAL (HAL_I2C_Mem_Read and HAL_I2C_Master_Receive). Both method return me the same output, which is even more confusing for me. - I have two differents boards of the same models that give me the same errors in the output. - The slave address (of the Magnetometer) is 0011110b. I have two variable for read and write the slave, which are :         uint16_t IIS2MDCTR_ADDR_VAR_R = 0x3D; // 00111101b uint16_t IIS2MDCTR_ADDR_VAR_W = 0x3C; // 00111100b          I store th

..

Hi,we are using the LSM6DSO in Fifo mode and with the double tap feature. Our firmware configures the Sensor Frontend to give an interrupt at fifo_th on INT1 and for double_tap on INT2. Therefore, we explicitly disabled the INT2_on_INT1 bit inside the CTRL4_C register.But still we see the the INT2 interrupts on the INT1 line. (See plot)We always reset the sensor to default. So I guess it seems something is not correctly configured.Here is the code for configuring the sensor:  // configure for the first time ret_code_t err; // Get ID err = lsm6dso_device_id_get(whoamI); if (whoamI[0] != LSM6DSO_ID){ APP_ERROR_CHECK(NRF_ERROR_NOT_SUPPORTED); } // Do reset uint8_t res; err = lsm6dso_reset_set(PROPERTY_ENABLE); do { lsm6dso_reset_get(&res); } while (res); // Disable INT2_on_INT1 to avoid wrong Interrupts lsm6dso_ctrl4_c_t ctrl4_c = {0}; ctrl4_c.i2c_disable = PROPERTY_ENABLE; ctrl4_c.int2_on_int1 = PROPERTY_DISABLE; writeReg(LSM6DSO_CTRL4_C, (uint8_t *)&ct