MEMS (sensors)

I know that CTRL3_C, IF_INC defaults to auto-increment of register address.I am trying to stream accel/gyro register data from the device by sending a SPI read command to register OUTX_L_G. The SPI controller is configured to read 12-bytes. The register data is returned as expected.If I configure the SPI controller to read 512 bytes instead of 12 bytes the device still only returns the first 12 bytes and all 0's after that.Why is no register data returned after the 12 bytes of gyro/accel data?My intention is to somehow stream gyro/accel data using one SPI read command.

Hello Support Team,I am working on the LIS2DW12 Sensor with Wake-up feature.Issue :Getting Zero on ALL_INT_SRC (3Bh) read while Falling interrupt occurred.Description :Configuration : Operation :Why does Falling Edge interrupt show Interrupt status as Zero?Request :Can you please give a reason why the falling edge interrupt st

In I2C mode for the IIS3DWB device the datasheet says it only support single axis mode because I2C is too slow to get the data. I want to use I2C mode to configure either wake up or activity thresholds for all 3 axis and then configure the interrupts to tell me those thresholds were exceeded. I don't need the data. So the question are In I2C mode:Are all the axes still active?Can I access all the registers in I2C mode to configure the thresholds for all axes of the device for the interrupts?Can I effectively get two thresholds for each axis if I use one set of thresholds for wake up configured on INT1 pin and another set of thresholds for activity configured on INT2 pin?Regards,Jeff Lee

Hi,I'm using ULD to get measurements from VL53L1X. My case need to get 9 ROI - divided FoV into 3x3. When I run such measurement procedure it with 2x2 = 4 RoI - It's okay. But when I get 3x3 RoI in a similar way I get measurements such as max u16_t = 65535 and my first 3 from 9 RoI center (which I get using VL53L1X_GetROICenter) oscillates around some point.My measurement procedure is like:/*run on 3 sensors*/    status = VL53L1X_GetROICenter(sensorAddr, &roiCenter);    status = VL53L1X_StartRanging(sensorAddr);/* ........ */        while (!allSensorsMeasReady)         {            VL53L1X_CheckForDataReady(VL53L1X_I2C_ADDR_1, &dataReady[0]);   &nb

We are using the FIFO compression feature of the LSM6DSO32 which is working well for us if we use it standalone at 833 Hz. When we add the 4 FSM's that handle our motion recognition we start seeing duplicate tags in the compressed output implying that data has been dropped.In AN5473 it says the FIFO compression will work up to 833 Hz in section 8.10. There is no mention of a dependency on FSM's that I have been able to find - Can someone confirm that this is indeed our issue and the only paths forward are to:Decrease the datarate to the compressed FIFOStop using FSM's and get compressed FIFO data at 833 HzHandle compression of the sensor data on a host processorAre there any other options we could pursue?Thanks

I have been looking for Linux drivers for the LSM6DS33 "iNEMO inertial module:always-on 3D accelerometer and 3D gyroscope", but have not had any luck. If anyone knows about any such repos or even references, it would be greatly appreciated.Thanks!

サンプルアプリをIAR�?�カスタマイズ�?��?�使�?��?��?��?��?�。アプリ�?�android�?�サンプルアプリを使�?��?��?��?��?�。注�?点�?��?�を教�?��?��??�?��?��?�。

here is my circuit for the LSM9DS1i used the code from sparkfun breakout moduel to test the board. i can get the data from their board, but not my board.

In my project, I used the LIS3DH chip. Most of the time the processor sleeps.The processor wakes up on time and on exceeding the shock threshold.In case of awakening on shock threshold, I need to read the data from the FIFO buffer (32 measurements) that were before the wake-up signaland a series of measurements (600-32) after waking up.How could I do this?Now I am reading the measurements while waiting for the ZYXDA register ready bit STATUS_REG(27h) set. FIFO always enabled in Stream mode.But this metod may not work when reading the FIFO part of the measurements. Should I change the read algorithm when reading data from FIFO?I think this is the algorithm:1. Read FIFO 32 measurements on wakeup by observing the EMPTY bit of the FIFO_SRC_REG(2Fh) register2. Disable FIFO by resetting FIFO_EN register CTRL_REG5(24h)3. Read 600 - 32 measurements waiting for ZYXDA bit STATUS_REG(27h)

Hello,I'm using a LIS2DTW12, here the configuration :ODR 400HzFIFO threshold on INT2 push pull interrupt. Threshold 16Continuous mode All seems to work correctly but sometimes I have an incorrect interrupt. The INT2 signal is yellow, the purple is a GPIO of my micro toggled when there is an ISR rising edge on INT2 is detected. The picture (1) show an unusual toggle (on the micro ISR) and on the code I read first 16 samples from the FIFO and then after a second interrupt just 6 samples (no overrun flag). In the other picture 2 and 3 the zoom of the problem, the yellow signal goes down for some uS then it goes up again so the micro see a new fifo threshold interrupt. Now why the INT2 goes down and the up again even if the FIFO hasn't reach the threshold ?

LSM6DS3TR is currently used on our production PCBAs. The sensor has been working for us for the past few years now. But once in a while it freezes and does not supply readings. Specifically it cannot sense taps. When we short the 3.3V and GND line it unfreezes and normal operation continues. There is no known way as to how to recreate the problem. I do know the the SPI interface that is used to communicate with this sensor is functional as I can use it to communicate with other components. Is there a reason as to why it freezes up? How can I stop this sensor from freezing up? Is there a way I can unfreeze it from the firmware such as a reset or a reboot?Thank You

I need to connect four LSM9DS1 on a common SPI bus. (I2C won't work here---resources are not available on the host microcontroller.)I'm having a hard time getting the following from the datasheets, and hoping maybe someone with experience with these chips can give me some pointers: In 4 wire SPI mode, do SDO_M and SDO_A/G assume a tristate/high-impedance state when their respective chip selects are not asserted? In 3 wire SPI mode, does SDA/SDI/SDO become tri-state/high-impedance when a chip select is not asserted? Is there any way to avoid needing both chip selects, and somehow tie these together for each chip, selecting whether you are talking to the A/G or Magnetometer via a register setting? Thanks!Tyler

I have both these devices on the same I2C bus and am trying to calculate the maximum pullup resistance.Thanks!

Hi Sir/Ma'am,I am using accelerometer LIS3DH for drop test.I disabled two of axis's x, y and enabled z axis with CTRL_REG1 (20h) .Threshold 40, ODR 100, Range 2g.I had varied range from 2g to 16 g.Even when I dropped from 25 cm and 50 cm height I am not getting any interrupt but when I tilt it in Z->y axis or Z-> -y axis I see interrupt.Kindly help!!Thanks and Regards,

Hi,I am using nordic MCU to operate LSM303AGR magnetometer device. My goal is to get a Z-axis interrupt upon crossing the pre-calibrated threshold.The i2c write and reads are working fine.INT bit of register 64h (INT_SOURCE_REG_M) is responding when getting a magnet nearby (when polling this register), yet the interrupt pin stays low all the time (verified with a logic analyzer).MCU pin is configured as input without pullup.The following register writes are being performed by the firmware:1. Write 00h in CFG_REG_A_M // Turn on the magnetometer // ODR = 10 Hz 2. Write 40h in CFG_REG_C_M // Interrupt driven on INT_MAG/DRDY pin 3. Write 80h in INT_THS_L_REG_M // Set a threshold equal to 128 (expressed in LSB)   Write 00h in INT_THS_H_REG_M 4. Write E7h in INT_CTRL_REG_M // Enable a latched active-high interrupt on

Hey guys we are using the HAL Uart at 9600 Baud between our Bluetooth Board and Motion Sensor. We are using the DMA in non circular Buffer mode and then we have an actual Circular Buffer the Data goes into after the DMA. We are noticing randomly the Uart Rx freezes but everything else including Uart tx keeps working. We are re-initializing the DMA After call back. This is the initialization.HAL_UARTEx_ReceiveToIdle_DMA(&huart2, dmaModemRxBuf, DMA_RX_BUF_SIZE);This is our Call Back.void HAL_UARTEx_RxEventCallback(UART_HandleTypeDef *huart, uint16_t Size){ if(huart->Instance == USART2){ for(int i = 0; i < Size; i++){ modemCircBufPush(&modemRxBuffer,dmaModemRxBuf[i]); } //use circ push the data into ring buffer HAL_UARTEx_ReceiveToIdle_DMA(&huart2, dmaModemRxBuf, DMA_RX_BUF_SIZE); // __HAL_DMA_DISABLE_IT(&hdma_usart2_rx,DMA_IT_HT); }else if(

I have some questions regarding loading machine learning core configurations, specifically onto the lsm6dsox chip but it should be the same across devices. I have generated .ucf and .h files. I've confirmed that the .ucf file works fine when loaded with Unico GUI, with decision tree outputs correctly updating. However, when trying to implement in standard c drivers, it does not work. I poll the accelerometer and also am sure that it is working correctly. Gyro isn't used for my decision trees. I'm loading my configurations in the same way as shown in the standard c driver examples:``` for (int i=0; i<(sizeof(mlc_configuration) / sizeof(ucf_line_t)); i++){        lsm6dsox_write_reg(&dev_ctx, mlc_configuration[i].address,                            (uint8_t *) &mlc_configuration[i].data, 1); 

Hi there fellas, i got me two Steval-Stwincsv1 and i'm now using the HSDataLog. Everything works perfectly when only one of the sensors is plugged on to the Computer. When i plug the second one and start it, one of them start, and ONLY ONE. It seems like that, i cannot choose which one of them am i triggering. My question is: How am I supposed to choose the sensor which i want the data from, because i cannot seem to be able to choose COM port or do something with the .json config files?

Hi Everyone,I am using STEVAL-MKI182V2 IMU sensor and can able to get the Euler angles of Yaw=360 degrees , Pitch= +- 180 degrees and Roll=+-90 degrees, now i want to get the Roll with range of +- 60 deg how can i get that range, please suggest me.Thank you.

If the ISM330DLC is connected to two separate dedicated SPI buses (i.e. no other SPI slaves on the bus) can the CS and OCS_Aux pins be connected to ground or do they have to be controlled by their respective SPI masters?

hello.I am using LSM6DSM to collect acceleration and gyro data.Data is being collected at 52Hz using FIFO, but the actual data collected is about 51.2Hz.It is probably caused by the LSM6DSM internal clock being inaccurate. Is there a way to correct this?For reference, my MCU's clock is set very accurately to the external clock.I need help. thank you

When trying to run MLC.ibynb in the MLC repo (STMems_Machine_Learning_Core/MLC.ipynb at master · STMicroelectronics/STMems_Machine_Learning_Core (github.com)), there is error thrown from the with call stack:generateDecisionTree > printTree > formatTree > genNextLineIndexif (getNodeNum(line) == int(num))ValueError: invalid literal for int() with base 10: ''Clearly the line being passed in is empty. Does this result from there being empty lines in the ARFF files generated by the Unico API? Any help is appreciated.

I made a sensor module with IIS3DWB to measure vibration of motors in temperature test machine.The operational temperature was -20~ 100 ℃. But some sensor modules went dead in less than three month continuously. The module had no response in SPI. I suspected the disconnection of wires at first. When I measured resistance values between wires, nothing unusual was detected. So I did CT scan, but I haven't found any defects in terms of wiring and soldering. (I compared with a good module.) I strongly doubt damages inside the MEMS circuit. but checking by myself looks impossible I really want to know the reason why the problem happened and get some advices on the failure analysis. Or it might be wrong the way that I made the module. I put sensor PCB inside aluminum housing and filled epoxy resin (Araldite). Is there anyone who has experience in similar situation here?

We are considering using an array (>2) of LPS22CH devices on a single I2C bus, and intend to use SA0 as (in effect) a Chip Select. We would like to know whether SA0 is polled (a) once at startup or (b) on every Start condition [we need (b)]. DT0132 and AN5589 don't seem to discuss this, and the verbiage in the datasheet [DS13022 rev 2, Sec 7.2.1] is ambiguous, referring only to "two" devices.In a previous version of this system, we used the LPS22HB (which has the same datasheet verbiage), and I was able to determine experimentally that it polls SA0 on every Start condition [(b) above]. Now the stakes are higher and we're hoping to get an authoritative answer.