MEMS (sensors)

I tried to get XL and gyro data by data-ready interrupt mode,​1. Configuartion registers sequence and values are as follows Use Bypass mode, XL data-ready rounted to INT1; gyro data-ready rounted to INT22. In ISR1 reads the STATUS_REG, if XLDA bit is set, read XL data3. In ISR2 reads the STATUS_REG, if GDA bit is set, read gyro datais that correct to get XL and gyro by data-ready interrupt mode?My questions areIf read STATUS_REG on ISR, the INTx will keep on high, only do a XL read or gyro read from LSM6DSR, the INTx pin change to low?If I put the read XL and read gyro on background while(1), it is likely to cause the INTx pin high and system hangsOnly read XL and gyro inside ISR can keep system stable​​setup sequence​read back reg = 0x12, val = 0x 4read back reg = 0x14, val = 0x60read back reg = 0x16, val = 0x 0read back reg = 0x a, val = 0x 0read ba

Hi! I'm using the VL6180X with several libraries for a specific application. However, I have noticed that most of them configure some registers that are not detailed in the manufacturer's datasheet. Therefore, I would like to know what these registers refer to within the sensor and their functionality, in order to fully understand its operation. The registers in question are the following. write8bit(0x0207, 0x01); write8bit(0x0208, 0x01); write8bit(0x0096, 0x00); write8bit(0x0097, 0xfd); write8bit(0x00e3, 0x00); write8bit(0x00e4, 0x04); write8bit(0x00e5, 0x02); write8bit(0x00e6, 0x01); write8bit(0x00e7, 0x03); write8bit(0x00f5, 0x02); write8bit(0x00d9, 0x05); write8bit(0x00db, 0xce); write8bit(0x00dc, 0x03); write8bit(0x00dd, 0xf8); write8bit(0x009f, 0x00); write8bit(0x00a3, 0x3c); write8bit(0x00b7, 0x00); write8bit(0x00bb, 0x3c); write8bit(0x00b2, 0x0

Dear Sir,In datasheet, it says that Angular rate zero-rate level is +/- 1dps,does it means that when the chip soldered on PCB and in flat stationary state, the expected value is +/- 1dps or close to +/- 15 counts for +/-2000dps scale?What is the min and max G_TyOff? Not found in datasheet.Thanks.

I'm currently investigating mechanisms for synchronization of disparate IIS3DWB units in a given system. The current thought is that signal alignment between two disparate IIS3DWB units can be achieved without a traditional SYNC signal by aligning to a common "flag" or indicator time base. In the context of our system, we can use the XLDA or FIFO_WTM_IA flag. The XLDA or FIFO_WTM_IA flag will go high when there is either data ready to be consumed, or when a watermark has been hit once data has filled the FIFO enough. Assuming that the time for the processor to consume the accelerometer buffer over SPI is deterministic and consistent, we only need to ensure, then, that the time propagation between data coming in and a flag being risen high is deterministic and fixed. We also want to ensure that the time between the flag being risen and the routed output INT signal going high is also deterministic and fixed. Is there a timing diagram that shows exactly on which clock pul

We got from two different suppliers some LSM6DSOXTR and we expect to get 0x6C as fixed value in register 0x0F. ON the contrary we got 0x68 that looks to be the ID code of the oldest and obsolete LSM6D0. Is that possible? Is possible that I got wrong chips from the distributors? Is 0x68 actually the ID of the oldest LSM6DS0? Thanks!

I'm using lis2dw12 accelerometer, while using INT1 pin to route interrupts, it's working good, how ever when I route it to INT2 pin, it doesnt work, the configuration I set:in ctrl reg 5: I set INT2_DRDY to 1 in ctrl reg 7: INT2_ON_INT1 to 1, INTERRUPTS _ENABLE to 1are there any configuration/conflict with other configuration?Thanks

Dear Sir\MadamI have been using steval-mki190v1 (LIS2DTW12 IC), Trying to communicate through I2C with STM32F103RCT6  microcontroller in LIS2DTW12 IC by default how does it act SPI or I2C. Let me know how to configure the I2C pin configuration of LIS2DTW12 communication with the STM32F103RCT6 microcontroller.   Best regards,Gagan GowdaEmbedded Engineer

Hello,I'm trying to set up the two interrupts on the LSM6DSOX, INT1 and INT2 to indicate Single and Double Tap events, respectively.I'm able to make both events trigger their respective interrupt, but would like them to be completely separate.I think I need to implement a delay on the Single Tap, to ensure it doesn't operate under double tap condition - it currently operates twice for a double tap!Is there a way I can do this inside the LSM6DSO, or must I differentiate the interrupts in my microcontroller?  WriteRegister( LSM6DSOX_CTRL1_XL, B01100000 ); //Set ODR to 417Hz? WriteRegister( LSM6DSOX_CTRL4_C, B00100000 ); //Enable Tap on X,Y,Z WriteRegister( LSM6DSOX_TAP_CFG0, B00001110 ); //Enable Tap on X,Y,Z WriteRegister( LSM6DSOX_TAP_CFG1, B00001000 ); //Set X Threshold WriteRegister( LSM6DSOX_TAP_CFG2, B10001000 ); //Set Y Threshold + Enable Interrupts WriteRegister( LSM6DSOX_TAP_THS_6D, B10001000 ); //

Hi everybody and thanks in advance for the support.I have a ST SensorTile and I'm starting with the DataLog project to output data through USB port. I have correctly integrated MotionFX libraries and they seem to run, except there are just a bit of problems.What are the right units for time in MotionFX_propagate and MotionFX_update (param eml_deltatime). It seems it has to be expressed in seconds but in some samples you use a 20 constant defined. For instance: 20ms are 0.02f?What is the param eml_q_update in MotionFX_update? Should I put a float of something or it should remain NULL as stated in example/doc?What is the correct sequence for magnetometer calibration?MotionFX_MagCal_init at start (using sampleTime expressed in milliseconds?)MotionFX_MagCal_run in the loop, before the MotionFX_propagate/_update and until the MFX_MAGCALGOOD is reached?Can the MotionFX_MagCal_run be called every loop independentl

Good afternoon,I would like to use the Sensor tile on which is running the en.fp-sns-allmems1 fw to directly record sensor measurements on the SD card. The idea is to power on the sensor tile, then dobletapping on the sensor tile to start recording directly on the SD card; once I dobletapping on the sensor tile, it stops recording on SD. In a nutshel, I want en.fp-sns-allmems1 to work like en.stsw-stlkt01 on the sensor tile without interacting with the BLE app, because I am interested in having quaternions recorded in csv and en.stsw-stlkt01 does not support quaternions. Should I try to (a) adapt en.fp-sns-allmems1 to do as I said above or should I try to include a library for computing and recording quaternions in en.stsw-stlkt01? If it is better to do (b) what library do you suggest ? Since I am new to programming at these level could you provide me some hints and examples, please ?

I am working on a project which has 2 board revisions A and B.(A was the old revision and B is new). Board A has the accelerometer chip lsm6dso and board B has the accelerometer chip ism330dlc. The driver used is drivers/iio/imu/st_lsm6dsx/. If I use the compatible string in dts as compatible   = "st,ism330dlc" and only the accelerometer in REV B is working and not in board A. But if I add compatible   = "st,lsm6dso", the accelerometer in board A is only working and not in board B. What changes can I make in the dts or in the driver so that the same driver can be compatible with both boards and the accelerometer is working on both boards?

On the BL47E-IOT01A2 there are two mems microphones (MP34DT01) both connected to DFSDM1_DATIN2. I'm trying to extract the data from just one of those boards and convert it to PCM using a DFSDM filter. I've configured DFSDM Channel 2 to connect to PDM/SPI and trigger on the rising edge, and filter 0 I've configured in one-shot mode, connected to DMA, with an oversampling value of 154, and an integral oversampling value of 3. The internal SPI clock on the board is configured to 1/4 the system clock which is 80MHz, thus the SPI clock should be 20MHz. The code to capture the audio is here:void HAL_DFSDM_FilterRegConvCpltCallback(DFSDM_Filter_HandleTypeDef *hdfsdm_filter) { micAudioBuf[micAudioBufIdx] = micRecSample << 8; micAudioBufIdx++; if (micAudioBufIdx >= AUDIO_LEN) { micAudioBufIdx = 0; audioFilterCplt = TRUE; } else { micReset(hdfsdm_filter); } }   void micReset(DFSDM_Filter_HandleTypeDef *hdfsdm_filter) { HAL_DFSDM_FilterRegularSt

Hello, ST engineers. I am working with a general purpose IMU for a tilt sensor application. I am observing some drift on the sensor while the device is off. I have heard that all IMU's can drift a bit, but I was under the impression that it would happen over a longer period of time. Do you have any specifications or testing data regarding the drift of this IMU over time? I am observing an offset drift of up to 3mg on some units just overnight. The readings are taken near 0g, but not exactly due to zero-g offset in device. The sensor is temperature calibrated, and the offset drift is measured near the same room temperature to minimize the effect of temperature related drift.I would also appreciate anyone else who has input regarding if you think this magnitude of drift is reasonable and expected for this sensor?Thank you,Russell

Hello. I am using a LIS2DH board (STEVAL-MKI135V1). I use the STEVAL-MKI109V3 board and the UNICO-GUI app to configure the LIS2DH board. I configure it for Wake-Up system for X axis. So, I change the register for only enable the axis x and it works ok. I get the interrupt in INT1 not only in the UNICO app but also in a cable connected to INT1. But if I just disconnect the LIS2DH of the STEVAL-MKI109V3 and then connect Vdd and Vddio to 3.3V and GND to GND and INT1 to our device.... we do not get any interrupt, always just 0V. It seems that after configure the sensor, if we take out the power, it lose the configuration. Even written the registers with the UNICO app.Anyone know how can we solved this? We do not have a I2C or SPI to connect the sensor, we just need to get the interrupts.Thanks for your help and best regards,Javier

Reset does not work.

Facing some problems with the ST BLE Sensor App. Whenever I try to connect the device to cloud (Azure) it shows connection error ( in both android and IOS Phones).The SensorTile.Box I´m using is STEVAL – STLCR01V1

I connected the ASM330LHHX(STM sensor featuring a 3-axis digital accelerometer and a 3-axis digital gyroscope) and INA228(one of the TI sensors measuring the current and voltage) via the I2C interface. What's more, I want to read the data from the ASM330LHHX registers(e.g. Sensor hub registers) which are for external sensors. However, I have noticed that the data stored in the INA228 registers is in the format of 16 bits or more, whereas the registers in the ASM330LHHX for the external sensor only have 8 bits of storage space.So is there any solutions that can help me to slove the problem?Thank you very much!

Hi,At Application Note 5027: "Interfacing PDM digital microphones using STM32 MCUs and MPUs" it described how to connect PDM microphone to SPI I/F of STM32. My question is:at SPI I/F clock is active only when there is SPI transaction, how can I cause the SPI clock to be active constantly?ThanksAaharon

Hi,I'm trying to use LSM6DSO32X to detect a short (<5ms) event isolated by at least 100ms from other events (before and after). It's on the Y axis and with a threshold of 500mg. I'm not having any luck setting up a single TAP event or by using FSM. Any advice would be appreciated.

Hi,I configured the AIS3624DQTR sensor by using standard driver given by ST on GitHub, I am able to set all parameter correctly but when I am trying to read X,Y and Z axis. It is returning same value on all axis and value is not changing by moving sensor.I configured the sensor by using poling example code: whoamI = 0; ais3624dq_device_id_get(&dev_ctx, &whoamI);   if ( whoamI != AIS3624DQ_ID ) while (1); /*manage here device not found */   /* Enable Block Data Update */ ais3624dq_block_data_update_set(&dev_ctx, PROPERTY_ENABLE); /* Set full scale */ ais3624dq_full_scale_set(&dev_ctx, AIS3624DQ_6g); /* Configure filtering chain */ ais3624dq_hp_path_set(&dev_ctx, AIS3624DQ_HP_DISABLE); //ais3624dq_hp_path_set(&dev_ctx, AIS3624DQ_HP_ON_OUT); //ais3624dq_hp_reset_get(&dev_ctx); /* Set Output Data Rate */ ais3624dq_data_rate_set(&dev_ctx, AIS3624DQ_ODR_5Hz); am I missing any step in config

I am using LIS2DTW12 MEMS,1. I configured this sensor in continuous mode.2. Set the FIFO threshold to 16 samples.3. Selected ODR register value is 100.4 Selected Low power 1 mode.Expected:Periodic interrupt from FIFO must happen every 160ms. But I am getting FIFO interrupt at ~158.4ms.Could you please explain the cause of this time drift and how to fix it?Note: our operating temperature range is -5 to 60 degrees C.

I have an LPS22DF sensor connected via I3C. I can enable I3C in-band-interrupts (IBIs), and see the IBIs occur on data-ready events.I see the IBIs have a 5-byte data payload, but I can't find any definition of the data in this payload. Is this described somewhere? Is the PEC byte present?

Refer to the RoHS pack 22 Final report, RoHS exemptions 7(a) and 7(c)-I are possible to be expired on July 1, 2024. Could you please advise if STMicroelectronics has any plan to remove exemptions for the below parts? LD1117DT33TRSM15T100CASTPS8H100G-TRLPS25HBTRThanks,Yingxin Yao

I'm working with the LIS2DH accelerometer and I'm trying to obtain acceleration data at a rate of 100 Hz. However, I've noticed that the accelerometer interrupts have a frequency of 99 Hz. Also this frequency changes if I use another accelerometer of the same model.I'm curious to know what kind of clock the accelerometer is using and what error is causing this discrepancy in the sampling frequency. What percentage of error in frequency is expected?Any help or insights would be greatly appreciated. Thank you!

Hello I want to connect to the STEVAL-MKI208V1K via STEVAL-MKIGIBV2 (conected those both togheter) , with Nucleo-F401RE. I conected pins as it is shown belowF401RE-> MKIGIBV2MOSI (PB3 -> SDAMISO -> SDOSCK -> SCLPWM/D6 -> CS3v3 -> VDDGND- >GNDI want to use SPI 4 wire interface but immediately after connecting nucleo to the PC I lost conection to the board and led LD1 starts blinking red. Do I need to connect some other pins as well with a board? Do I need to use some pull up resistors to the pins?