MEMS (sensors)

Hello,I'm trying to understand the LIS2DE12 behaviour. First, there is no AN (Application Note), thus I used the one for LIS3DH which seems close enough.What I want is that my accelerometer wake up my stm32. This works. After that I just want to read 1 sample to know the current acc value. But the FIFO system seems a problem for me. In the doc, it says the sample I get is the oldest one in the FIFO and that if I don't read fast enough data will be overwrited.I just want to read one sample for Z-Axis when I need in my code. Do you have any idea or clue?Thanks.Best regards, Simon

..

I tried following this tutorial (https://community.st.com/s/question/0D50X0000BYnQt6/sensortilebox-not-connecting), but it looks like DfuSe is obsolete, and I should use the new STM32CubeProg tool. I couldn't seem to find any information on how to use the STM32CubeProg tool to restore to defaults. How do I use STM32CubeProg to restore to defaults?

Dear SIR,When FIFO mode is disable. And Polling mode is used.There is a bit DRDY_MASK in registerCTRL4_C(0x13), 1 : mask DRDY on pin (both XL & Gyro) until filter settling ends (XL and Gyro independently masked).It says that it mask DRDY on pin, it dos NOT raise interrupt INT1 or INT2 until filter setting ends.When polling mode is used, does it means that it mask bit XLDA and GDA to b'0 when filter is not complete(data is not ready)in STATUS_REG?Thanks,E-John 

HelloWe must replace the old LSM6DS with the new one LSM6DOX because of End of Life of the first one.Checking the results on the same jig, reveals half of the Accelerometer part of the new chip. Do you have a detailed documentation which may support with all the differences between them?What should be change (in setup or in FW) in order to have the same results between them?Thanks!

Hi,I am using the LSM6DSL, i can see that the chip marking is different for some of my chips,some have SF 951 and others have 952. Further, I am getting different sensor results from each, Does someone know what is the difference between them?Thanks

Hello,We are working on tilt feature development based on LIS2DW12 sensor.For the development of the tilt feature with the help of Wakeup interrupt and following the attached example belowSo, How to set the sensitivity value from the open to the close position? (Please refer to the below example) 

Hi, i'm using LIS2DS12 accelerometer in FIFO continuous mode connected to my MCU using the I2C interface. i'm setting the FIFO threshold to 80 samples and using the maximum ODR of 6400Hz so it takes ~12.5ms for the FIFO interrupt to read it. reading the 80 samples takes ~4ms using I2C in 1MHz speed. all data is read in one I2C transaction.examine the received data, it seems that some of the samples data is missing which fits the time it was reading the FIFO, 4ms that are 25 samples. it looks that new samples are not entering the FIFO while reading the FIFO.is the LIS2DS12 supporting filling new samples to the FIFO while reading the FIFO?is it a configuration issue?Thanks, Roei.

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, OIS disable  {0x11, 0x4c}, // CTRL2_G, ODR_G[3:0] = b'100, gyroscope ODR = 104Hz, FS[1:0]_G = b'11, +/- 2000dps  {

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 like on the Accelerometer (sensitivity 3.815mDPS)?2. if the sensitivity in the datasheet is correct, how should values outside of range be treated?Thanks for your help

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 this document for the basic setup:AN5130LSM6DS3TR-C: always-on 3D accelerometer and 3D gyroscopeThank you,Trey

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

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 );   /* Enable 3-axis mode */   stiis3dwb_write_active_axis( STIIS3DWB_3_AXIS );&nbsp

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_FUNC_BANK); if (ret == 0) { ret = lsm6dsox_read_reg(ctx, LSM6DSOX_STEP_COUNTER_L, buff, 2);