MEMS and sensors

Hi!I have set up and connected a LSM6DSV16X via I2C to my raspberry pi, its on bus 10, address 0x6a. The sensor seems to have been detected via an I2C dump but the identifier (which should be 0x70) is stuck at 0x00 and I'm not sure why. azlan@argo:~ $ i2cdetect -y 100 1 2 3 4 5 6 7 8 9 a b c d e f00: -- -- -- -- -- -- -- --10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --40: -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- --50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --60: -- -- -- -- -- -- -- -- -- -- 6a -- -- -- -- --70: -- -- -- -- -- -- -- --azlan@argo:~ $ i2cdump -f 6 0x6a0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef00: 48 05 3d 3a 20 13 5e 9d 03 44 93 e2 80 13 00 00 H?=: ?^??D????..10: 00 00 00 08 39 ff ff ff ff ff ff ff ff ff ff ff ...?9...........20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

Hi,I am trying to capture data from the IIS3DWB sensor at its maximum rate and save it into a buffer of length 8192 (due to internal RAM limitations). I'm using SPI with DMA to interface with the sensor. However, I'm not able to capture the data correctly — the X-axis shows incorrect values, while the Y and Z axes remain constant. I tested with another sensor, but the issue persists. The FIFO is configured to stream mode. I haven't detected any buffer overflows. I'm attaching the code and a CSV file for reference. SETTINGS: SPI clock-8MHz, iis3dwb stores data in FIFO in continuous mode with 26.67k ODR , 3-axis mode is used, timestamp batch to FIFO is on, BDU is on, 16G range mode is on, IRQ pin -not connected, using polling mode. can anyone give me solution. Thanks 

Hi ,We need a clarification in the register values of LSM6DSL for configuring g values. Is this the correct values or is it a printing mistake where 16g is given as 01 ,should'nt this value be allocated to 4g .It would be appreciated if you can kindly clarify at the earliest.Thanking youRegardsGouri.k

Hi,I am trying to use the LIS2DU12TR's low address that is 0x18 but I keep on encountering issues with not able to read WHO_AM_I and the accelerometer does not work. Can anyone please help me with this?Also, does it support 100kHz I2C bus?Thanks.

Problem SummaryI'm experiencing challenges with MotionFX library for azimuth rotation detection using the ISM330DHCX sensor. While MotionDI works well for altitude detection, MotionFX shows inconsistent behavior for azimuth (rotational) measurements.I have done a test where I have collected samples over the entire weekend (about 65 hours). I am aware of the difficulties in detecting rotational movement using only accelerometer and gyroscope, however, the issues below do not seem to stem from this, but rather with issues in the MotionFX library or parameters.Hardware SetupSensor: ISM330DHCX (accelerometer + gyroscope)Orientation: WDS mounting (X-West, Y-Down, Z-South)Sample Rate: 104HzApplication: Rotational motion detection system that detects motion over longer periods in time. (No real time updates needed)Current ConfigurationMotionDI Parameters (working well for altitude):mdi.move_thresh_g = 0.25f; mdi.cal_type = 1; mdi.acc_thr_g = 0.01f; mdi.gyro_thr_dps = 0.01f; mdi.max_gyro_dps =

 Hello everyone,I am using I2C to communicate between an STM32F411 Discovery Board and the on-board LSM303AGR sensor. I have already configured it for a 400Hz ODR, normal power mode, and am reading temperature values (around 25°C to 27°C).However, I am stuck on how to soft-reset the entire sensor. I tried to SET bit 5 in CFG_REG_A_MAG and adding a small delay, but this does not reset the values I configured in other registers. Those settings remain the same, no matter how many times I try to SET the reset bit.The registers only reset when I unplug and plug the power back in.Please help me.Thank you very much.bool LSM303AGR_softReset(const LSM303AGR_t* lsm303agrStruct){ uint8_t regVal = 0; if(!readMag(lsm303agrStruct, LSM303AGR_CFG_REG_A_MAG, &regVal)) return false; //Extract the current status bit-field and assign it to regVal /* Start to assign and write regVal to CFG_REG_A to start FULL CHIP RESET */ regVal |= (SET << REG_A_SOFT_RST_Pos); if(!writeMag(lsm303agrSt

Hi, I was trying to make the sensor sense slow rotation.I read the datasheet and I guess if I set HPM to work as normal mode, and High-pass filter for interrupt 1so CTRL_REG2 should have 0x81,Then I should read the REFERENCE (0x26) register, (according to the thread in here https://community.st.com/t5/mems-sensors/lis2dh12-measure-conversion/td-p/420708) My question is, is it even doable ? Can I sense slow rotations until it reaches some point ?Thanks in advance 

The Ultra Light Driver (STSW-IMG023) init function vl53l5cx_init() fails in this section :/* Get offset NVM data and store them into the offset buffer */   status |= WrMulti(&(p_dev->platform), 0x2fd8,   (uint8_t*)VL53L5CX_GET_NVM_CMD, sizeof(VL53L5CX_GET_NVM_CMD));   status |= _vl53l5cx_poll_for_answer(p_dev, 4, 0,   VL53L5CX_UI_CMD_STATUS, 0xff, 2);The sensor does not answer with '2' as expected by _vl53l5cx_poll_for_answer. (The senosr answers '0')This results in a failed initialization.How can this be fixed?

Thank you for your continued support.From your responses, I have made the following initialization procedure for ASM330LHH.POWER ONCTRL3_C <- 0x42(BDU,IF_INC)CTRL1_XL <- 0x9C(3333Hz,8G)CTRL2_G <- 0x92(3333Hz,125dps)INT1_CTRL <- 0x01(Accelerometer data-ready interrupt)Read STATUS_REG every 0.5ms to check if TDA is 1.Some units do not set TDA to 1. This is a problem.Is the ASM330LHH initialization procedure correct?Do I need to wait, etc.?

Hi,I am developing an application using the accelerometer LIS2DH12 and a STM32L451. It works perfect but I get some kind of issues when temperature is low. I used a thermal chamber to perform this test and it seems very repetible.If the accelerometer is set in low power mode and disabled at the beginning, what I do is:1) Initialize I2C HAL interface.1) Configure the accelerometer. (ODR 10, PW normal, FS 2G)2) Enable X, Y, Z axis3) Wait for 100 ms4) Read XYZ flag (Register 0x27) until it says values are updated. 100ms between retries.5) Set BDU to 1 in register CTRL 4.6) Read 6 registers XL, XH, YL, YH, ZL, ZH. I haven't been able to read 6 at once. It always fails or returns 0 for all the axis.7) Set BDU to 0 in register CTRL 4.8) Wait for 1 second, and go to number 1.In case the temperature is over 7ºC, I always get good results. Once the temperature drops 7ºC, I always get value for X axis and 0 for Y and Z axis. The pcb is not moving at all.After the temperature stops decreasing at

HiIs it possible to configure the interrupt function for free-fall with normal XYZ polled operation, or is it better to use the interrupt in low power mode and performing the free-fall via normal XYZ programmatically in normal operation?Thanks! 

Hi ST Support,A few datasheets for the BrightSense series, eg. um3224, show an option under CFG: Streaming readout mode control which is not precisely described in the documentation."-0x06: = XY binning x2"How does this differ from "-0x01: = digital binning x2"?The documentation says that digital binning is vertical+horizontal."Digital binning digitally combines every two pixels in horizontal and vertical directions to create the pixel output.This solution averages the pixel photoshot noise and improves the SNR without impacting the frame rate."Thank you!

Regarding the statement in the ASM330LHH datasheet “Embedded compensation for high stability over temperature”, does this mean that each output is temperature compensated? Does the compensation value correspond to the memory contents loaded when the BOOT bit is set? What output behavior is expected if this read/boot operation fails? 

When I try to set the LIS2MDL's operation mode from IDLE to CONTINUOUS or SINGLE_TRIGGER mode, the register values in CFG_REG_A that I already set prior (including comp_temp_en) gets reset to default including the operation mode when I check the register after a 7ms delay. I am using functions from the lis2mdl_reg.c/h files and have read values on hardware debug mode and on the SDA line. I have checked that 3V3 does not drop out and I2C communications look expected. Does anyone have any insight into what could be causing this?

Hello, I am working on a project using an AVR64DB32 MCU and the VL53L1 time-of-flight sensor over I2C.I downloaded the official API from ST (STSW-IMG007) and adapted vl53l1_platform.c to my environment.Since my I2C communication library is written in C++, I converted it into vl53l1_platform.cpp. I also wrote a simple distance measurement test program (main.cpp).My custom I2C driver (I2cDriver.cpp) is already used in other projects and seems reliable, so I assume the issue is not primarily there. I have attached these files for reference. The issue: Inside the while loop, I repeatedly call VL53L1_WaitMeasurementDataReady. If successful, I call VL53L1_GetRangingMeasurementData and then VL53L1_ClearInterruptAndStartMeasurement. In this case, I blink an LED once. If it fails with VL53L1_ERROR_TIME_OUT, I blink the LED twice. For any other error, I blink three times. After each loop iteration, whether success or failure, I wait one second before retrying. When running the program, I

Hi, I use 2 VL53L1 Sensoren via I2C for measuring distance. At first I used a raspberry pi and the provided API and it seems to work properly and all fine. Since I need to reduce my power consumption I migrated my Code to an atmega644 and therfore I use Atmel Studio for developing Code.Using this Controller I observe some strange behavior. Using the default setting, it takes around 30 seconds for a measurement to provide data, the interrupt show the same time frame. If I start a measurement immediately (continuous mode) it again takes ~30 seconds. If I start waiting 10 seconds delayed it takes around 20 seconds. So it seems the interrupt show measurment time is 30seconds. I tried to configure it, as well as time budget to 200ms. I also set long range mode explicitly and preset mode to autonomously.What i saw is the same behavior but with about 19 seconds not 30. So i started debugging and comparing. The lib seems to read some values from the Sensor at start up. Thes

Hello, I have a FUNDAMENTAL question: TOF VL53 series  sensors report a depth map. Is the depth the "Euclidean distance from the origin (0, 0, 0) to the point (X,Y,Z)" ? or is the orthogonal distance from the camera chip plane to the measured point along the optical axis?? if we use, x y, z  ( z is the sensor chip surface normal direction, i.e., the optical axis) to represent the measured point, the first case is depth^2= x^2+y^2+z^2, The second case is depth=z.Anyone can give me a concrete proved answer? Many Thanks to you in advance!!

Hello, I recently integrated LSM6DSOX on a testing PCB which contains an MCU and some other peripherals. The problem is that I have been trying to reduce power consumption without success, and I thought maybe you could help me find the problem. First, the application also uses BLE, and I measure power consumption during advertising, connecting and other states. Before the LSM6DSOX, the consumption was around 45-60 uA during these states. After integrating it, the consumption rose up to ~97-140 uA, which is unexpected as I have confirmed it to be low power mode. I also confirmed that the previous code with the current board with LSM6DSOX also consumes around 45 uA, so I assume there is something wrong in the code, handling, configuration etc. Hardware details: 1. I have connected a MOSFET as a switch before the power pins of LSM6DSOX. Meaning, I set high/low the gate of the mosfet to give power to VDD and VDDIO pins. I thought this was something t

How to know  MotionMC and MotionEC Library minimum Stack size Heap_Size?When I invert my compass,stm32 will reset, then i  increase Stack size Heap_Size,it run very well.

Hello, I am designing a PCB board using LSM6DSO and STM32f1xx, this PCB design will be only an experimental design for a bigger project, so I need both SPI and I2C to be available for testing (not at the same time).I'm wondering if there will be any issues regarding having both of them, espcially from the HW side, and is there any considerations or something to keep in mind when designing the PCB.Thanks! "Design schematic, typical connection for mode 1"

HiWe are testing out the lsm6dsv320x, which will be used on our new board.The low G accelerometer is working fine, however the high G looks to be reporting wrong values.If I use a simple calculation to computer the angles, the high G  is off by about 3-4 degreesThis is the formula i use to calculate the angles AccXangle = (math.atan2(ACCy,ACCz)*RAD_TO_DEG) AccYangle = (math.atan2(ACCz,ACCx)+M_PI)*RAD_TO_DEGBelow is an example of the results of both formulas when the sensor is horizontal. The last two columns are for the high G sensor.  you can see that it is different from the low G sensor. My expectation is that they should be reporting the same result.ACCX_angleACCY_angle ACCX_HG_angleACCY_HG_angle-0.06-0.20 -4.44-4.6200.03-0.17 -3.67-4.1200.03-0.23 -3.84-3.610-0.03-0.17 -3.61-4.240-0.03-0.17 -2.91-5.1300.03-0.20 -3.50-4.2400.00-0.20 -4.47-3.0800.00-0.20 -3.05-5.6800.03-0.20 -4.15-4.380-0.03-0.20 -3.71-3.250-0.03-

Hi everyone.Can someone from ST please provide information about when the STEVAL-MKI248KA will be available for testing?We are currently designing a new device that could really benefit from ISM6HG256XTR but we are tight on time and already in the integration phase, so it would be great if we could test this new product as soon as possible.  Thanks  Tiziano 

Hi team,We need thermal details (Junction to ambient temperature, Case temperature and body temperature) for the following IC's:ASM330LHHXG1TRM24M02-DWMN3TP/KPlease provide the details for the given IC's.Thanks & regards,Aravind R

I am developing firmware for the ISPU on the LSM6DSO16IS and have a question regarding communication between the host MCU and the ISPU core.My objective is to persist magnetometer calibration data. My intended workflow is:The ISPU runs the MotionMC_update function and calculates the HI_bias values.The host MCU reads these HI_bias values from the ISPU's output registers and saves them to non-volatile memory.On the next device startup, the host MCU writes the saved HI_bias values into the ISPU_DUMMY_CFG registers, intending for the ISPU to use them as initial calibration data.I have successfully implemented step 3. I can write to the ISPU_DUMMY_CFG_1 register from my external STM32 host using the lsm6dso16is_ispu_write_dummy_cfg() function, and I can verify the write was successful by reading it back from the host with lsm6dso16is_ispu_read_dummy_cfg().The problem occurs when the ISPU firmware itself tries to read

Hi,  I am using LSM6DSL accelerometer sensor.I have configure it to use acc only, +-16g, @27Hz, and using FIFO.Here is the configuration I am doing:uint8_t val = 0x04; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_CTRL3_C, &val, 1); val = 0x24; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_CTRL1_XL, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_CTRL2_G, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL1, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL2, &val, 1); val = 0x09; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL3, &val, 1); val = 0x0; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL4, &val, 1); val = 0x16; err = lsm6dsl_write_reg(p_ctx, LSM6DSL_FIFO_CTRL5, &val, 1); val = 0xF0; err = lsm6dsl_write_reg(p_ctx, 0x18, &val, 1); val = 0x00; err = lsm6dsl_write_reg(p_ctx, 0x19, &val, 1); After that I am reading the fifo level: ret = lsm6dsl_read_reg(ctx, LS