MEMS (sensors)

Dear SIR,In my application is to use lsm6dsr gyro values.When the set is in stationary state, sometimes the X component gyro values become large that cause wrong calculation.It happens randomly and other sets not seen the case currently.I have no idea to debug it. Any comments are welcome, thanks.initiates regs with their values as follows, reg, val   {{0x12, 0x04}, // CTRL3_C, bit IF_INC = b'1(Register add automatically incremented during a multiple byte access with a serial interface  {0x14, 0x60}, // CTRL5_C, Rounding[1:0] = b'11 = gyroscope + accelerometer  {0x16, 0x00}, // CTRL7_G, G_HM_MODE = b'0, gyroscope high-performance mode enableHP_EN_G = b'0, HPF disableHPM_G[1:0] = b'00, gyroscope digital HP filter = 16mHzOIS_ON_EN = b'0USR_OFF_ON_OUT = b'0, accelerometer user offset correction block bypassedOSI_ON = b'0

The datasheet for the LSM6DSO does not specify the tolerance of the linear acceleration sensitivity. Can you please tell me what the linear acceleration sensitivity tolerance is for this part.To be clear, I would expect to find offset and sensitivity accuracy/tolerance figures for linear acceleration and angular velocity: * LA_TyOff: Linear Acceleration offset accuracy * LA_So%: Linear Acceleration sensitivity tolerance * G_TyOff: Angular Velocity offset accuracy * G_So%: Angular Velocity sensitivity toleranceThe datasheet has three of these (LA_TyOff, G_TyOff and G_So%), but is missing LA_So%.

For the gyro the sensitivity values are stated on Table 3 of the data sheet page 21. However, with those values we would fall outside of the full range selected for the gyro. The same sensitivity is used in your sample conversion table in application notes. (both attached)For example for +/-125dps16bit signed max values, range would be 0.004375 *(+/- 32768) = +/-143.36dpsSo we are unsure how to treat the values outside of the sensor range. For example if we selected +/-125dps how to treat the values outside that range i.e. 132dps1. is the conversion table on the datasheet correct? or is the full range +/-125dps equivalent to +/-32768 li

hellowe are using LSM6DSL with full-scale acceleration range of ±2g. each one of x/y/z axis has 2 bytes output value: OUTX_L_XL (28h) + OUTX_H_XL (29h). as far as i understand, we should get 2^16=65,536 value for -2...+2g. i.e. 65,536/4=16,384 for 1g.Thus, if my device is in a steady state (does not move), i should be in -16,384 ...+16,384 range for any axis. BUT i have some devices that give out 16500 and even 17000 values.how can it be possible?thanks in advance

I followed these instructions in the LSM6DS3TR-C datasheet.Reading the WHO_AM_I register I get 6Ah.A basic SW routine which shows how to enable the pedometer functions is as follows:1. Write 20h to CTRL1_XL // Turn on the accelerometer// ODR_XL = 26 Hz, FS_XL = ±2 g2. Write 14h to CTRL10_C // Enable embedded functions and pedometer algorithm3. Write 80h to INT1_CTRL // Step detector interrupt driven to INT1 pinI move the Accelerometer and see steps accumulating.After 3 minutes of no steps, I put the main Cpu to sleep. LSM6DS3TR-C stays powered.When steps are detected by simulating steps again, the INT1 wakes up my CPU.But sending the above commands to the registers reset the pedometer steps even though ****_RST_STEP is 0.Is there a different setup to be used upon reconnecting to the device?Why are the steps getting reset using this basic setup?I reference thi

付属�?�プラスティックケース（丸型）を使�?��?��?��?��?��?��?��?開�?�る事�?��?��??�?��?�ん。開�?�方を教�?��?��??�?��?��?�。​

I am attempting to use single conversion mode to read x/y/z data.My configuration is:- CTRL_REG1: set data rate to 5Hz/ x/y Axis ultra high perf mode- CTRL_REG2: set full scale to 16 gauss- CTRL_REG3: Single-conversion mode- CTRL_REG4: Z-Axis mode - Ultra-high-performance mode- CTRL_REG5: BDU set to 1Once config registers are written as described above I use a loop:{ read status register until it returns ZYXDA (0x08). read x/y/z registers // device automatically returns to IDLE mode. Write 0x00 to CTRL_REG3 to set single conversion mode again}Once x/y/z registers are read the 1st time ZYXDA status bit never gets set to 1 again.Does this logic look correct?

Hi,I am trying MLC core examples. First time I program I can bale to debug the ISM330DHCXTR + Nucleo 401RE board successfully. If I reinitialize debug session, the debugger stuck at while loop below. do {    ism330dhcx_device_id_get(&dev_ctx, &whoamI);    HAL_Delay(500); } My Observations,I2C working perfect with 400kHzMLC core makes some way ISM330DHCXTR unstable state. After power On reset, everything works perfectly.If I run normal/Polling for accelerometer and Gyro data, works perfect.Can had same issue. Any help around this issue will be a great help.Thanks,Naveen

I would make the IoT device that detect vibration of the FAN. I will use this industrial portable blower FAN . https://www.indiamart.com/proddetail/portable-blower-fan-15055431262.htmlScenario1. To saving the energy of the device, the device goes to deep sleep when FAN is not working.2. the device is activated by interrupt from iis2dh when FAN is start to working.My question is that #01.Is it possible to generate interrupt from deep sleep when vibration detected by iis2dh?#02.for more sophisticated solution, is it more good to use microphone such as MP23AB01DH ?

For absolute orientation estimation, magnetometer serves as an important role to calibrate the angle drift.However, it seems there is no 9-axis IMU available now.(ST LSM9D... is obsolete.)However, for low-cost, consuming purpose 9 axis IMU: BNO055 for Bosch and ICM20948 for TDK.Is there any issue on integration of 9-axis IMU? Or 6-axis IMU + mag are enough for current application? ​

Hi all I am working on ABPDLNN100MG2A3 pressure sensor from honeywell which is an i2c communication, i have read the sensor data through i2c and saved it in two variable a and b the issue is how to convert the raw data to millibar, any thoughts kindly share.Thankyou

What is going on here. Do I have the right parts?

I have been using the IIS3DWB evaluation board alongside TIs CC1352P2 uC to bring up software ahead of the actual hardware arriving. The SPI bus speed is 8MHz in mode 3.The IIS3DWB is configured only sample accelerometer data on 3 axis and to store the values in the FIFO. The FIFO is configured to be in continuous mode with a FIFO watermark threshold configured to raise an interrupt when the threshold is exceeded.Below is an outline of how I have configure the IIS3DWB:-   /* We need to allow 10ms for the STIIS3DWB to come up */   HAL_TIME_sleep( STIIS3DWB_STARTUP_TIME );   /* Reset the software - this resets control registers to default condition */   stiis3dwb_software_reset();   /* Ensure Accelerometer is in powerdown mode*/   stiis3dwb_write_config_mode ( STIIS3DWB_POWER_DOWN );

Hi,I am interested in purchasing a gyroscope sensor (ASM330LHH)How can I connect the sensor to a computer? (for real time measurements)what equipment do I need?Thank you!

Well, the Unico-GUI software was working fine, and one day all of the tools (bars, plot, data, etc) started getting drawn on top of one another, and the last one (pedometer) is the one on "top" and the only one I can now select. Any idea how to fix this? I uninstalled/reinstalled and it's still doing this...Brian

After loading a new decission tree for the Machine Learning Core the behaviour of the Step count registers of the pedometer changed.I must note that none of the code changed, just the register mapping corresponding the decision tree loaded to the MLC. With the previous setup the value was correctly read, the LSM6DSOX_STEP_COUNTER_L is copied into the lower part of the variable, and LSM6DSOX_STEP_COUNTER_H on the higher part.But after the new tree was loaded, LSM6DSOX_STEP_COUNTER_L gets read on the lower part but for the higher part of the variable LSM6DSOX_STEP_COUNTER_L gets written again instead of LSM6DSOX_STEP_COUNTER_H.To fix this we had to change the code from lsm6dsox_reg.c that reads this values from the registers,Previous code without fix:int32_t lsm6dsox_number_of_steps_get(stmdev_ctx_t *ctx, uint8_t *buff) { int32_t ret;   ret = lsm6dsox_mem_bank_set(ctx, LSM6DSOX_EMBEDDED_

I have powered from LSM6DSO32 through a 3V Coin cell battery and connected with Nrf52810 using I2C.Without any coding sensor taking around 2mA and after flashing its taking 4MA.I am getting the readings correctly.Attached the schematics

I am using LSM303D to get accelerometer and magnetometer values but i keep getting ay and az axis of accelerometer values wrong. I am able to communicate with the chip because I can see the magnetometer values but something is wrong with accelerometer.I added the picture of output values. The is as follows:#include <Wire.h>//Register addresses for magnetometer#define OUT_X_L_M  0x08   #define OUT_X_H_M  0x09   #define OUT_Y_L_M  0x0A  #define OUT_Y_H_M  0x0B#define OUT_Z_L_M  0x0C#define OUT_Z_H_M  0x0D// Register addresses for accelerometer#define OUT_X_L_A  0x28   #define OUT_X_H_A  0x29   #define OUT_Y_L_A  0x2A#define OUT_Y_H_A  0x2B#define OUT_Z_L_A  0x2C

Hello ST,I am using LIS2DS12 sensor for step detection application. I read the step count register every 1 minute and reset the count value. I observe that even if the object is stationary, the step count register has a non-zero value (The value varies from 1 to 120). How can I ensure that the step count is zero when the object is stationary?Here are the initial settings used for the sensor:CTRL1_REG: 0xA0 (25Hz rate, +- 2g, Low power mode)CTRL2_REG: 0x18 (Access to pedometer advanced configuration registers, Filter enabled)STEP_COUNTER_MINTHS: 0xA8 (1.25 g)FUNC_CTRL: 0x01 (Step counter routine enable)****_DEB_REG: 0x6F (i.e Default debounce time: 1040 ms, Debounce threshold: 7 steps)After every 1 minute, these are register operations performed:Read STEP_COUNTER_LRead STEP_COUNTER_HReset step count by writing 1 to MSB of STEP_COUNTER_MINTHS.Reg

Can we use ISM303DAC for detecting vehicle's presence by sensing deflection in earth's magnetic field when vehicle (Ferromagnetic material) enter/depart parking area. Hello Team ST, Greetings ! We are looking for the presence detector sensor for our smart parking project. In this we expect magnetometer sensor to detect deflection in magnetic field and it will give interrupt whenever there is change. Rest of the time sensor will remain in sleep mode to conserve energy.Also we are looking for ultrasonic, mmWave radar for confirmation of vehicle's presence. Kindly confirm regarding ISM303DAC and suggest suitable ultrasonic, Radar modules. Best Regards, Madhav LoharGladiance Automation (India) Pvt. Ltd.WhatsApp Number :- +91-9422554303

I'm trying to use several different IMUs in the LSM6DS family (LSM6DSOX and LSM6DSO32). Both of them are exhibiting "ringing" on the three gyro axes when exposed to shock (knocking the PCB against a table). It almost looks like there's no anti-aliasing filter, but as far as I can tell, I've enabled LPF1. Any insight here? Things to check? See attached graph of gyro X data.Configuration:+/- 16G (+/- 32G on the SO32)1660 Hz+/- 2000 dpsFIFO in use, BDR 1660 Hz for both accel and gyro, continuous modeNo FIFO overflows are detected (FIFO overflow detection works, but it's not being triggered, so the firmware is keeping up)Thanks.

Hello, I'm working on a project involving voice recognition. So, I used the stm32 sensory library to complete this project and the MP23DB02MM digital MEMS PDM microphone. However, I only found one example that used STM32H747I-DISCO, so I ported it to Nulceo-F746ZG and it works fine(meaning that I could receive data and convert them to PCM and pass them to the sensory library). However, the library did not respond in any way. Because I am using an SAI peripheral, I followed the

We are trying to use lsm6dso32 accelerometer/gyroscope connected to a custom hardware (non-st) via i2c. What we want to achieve is reading measured values continuously, ideally via libiio (buffered).We are building a custom linux (kernel version 5.4) via yocto for our board and integrated this driver for lsm6dso32 support into it: github.com/torvalds/linux/tree/master/drivers/iio/imu/st_lsm6dsx.Question 1:Is the driver integrated in the kernel sources the same one, ST is providing here?github.com/STMicroelectronics/STMems_Standard_C_driversQuestion 2:If we are using the driver st_lsm6dsx from kernel sources, do we still have to apply the changes stated out here?github.com/STMicroelectronics/STMems_Linux_IIO_driversSo would we have to patch include/uapi/linux/iio/types.h to add custom events, for example, to be able to read data?Question3:Ideally, we wo

Hi,I try to use a custom board with LIS25BA.I use SAI with STMF446.What I know :MCLK = 12.288 MHzWCLK = 16kHz8 slot with 3 activeso BCLK = WCLK * (8 * 16) = 2.048 MHzWhat I can do :I2C works like a charm ;)What I can't do :Configure SAI with these values.Only MCLK is false and depends on Master Clock Divider I guess ...My actual config :  If

Hi,I used LIS2DS12 in a previous design and i appreciated the high number of embedded function, expecially the integrated step counter; unfortunately i cannot use the same accelerometer in a new design since my power supply is 3V3: is there any equivalent accelerometer having same embedded funcions?Thanks