MEMS and sensors

Hi,I am using VL53L8CX sensor from Pololu and connected it with Nucleo-F411RE board. I am using Arduino IDE 2.3 where I have downloaded STM32duino VL53L8CX library. When I run HelloWorld_I2C example with the wire  connections as mentioned with (SPI/I2c-->GND, Lpn-->A3), I am getting the distance result. But when I do the same with the HelloWorld_SPI example with mentioned connection (SPI/I2c-->3v3, Lpn-->3v3), I am getting nothing. When I put the breaker in between, the initialization itself fails saying sensor initialization status 1. I would be a great relief if you could help me with this.Thank you

We are currently trying to run experiments with the ILPS22QS sensor. According to the datasheet, when setting the SWRESET bit in the CTRL2 register to 1, it should self-clear when the reset is finished - but this never happens. The bit stays 1, and this also effects the official driver located at https://github.com/STMicroelectronics/STMems_Standard_C_drivers/tree/master/ilps22qs_STdC - it just runs in an infinite loop, waiting for the bit to clear.I have written my own small application to verify this.We use a Raspberry Pi as the I2C host. Does this has anything to do with it, or is the datasheet not up-to-date?

Hi, I use the ISM330DLC to measure the tilting of an excavator arm (similar to an inclinometer). I have observed that some ISM330DLC accelerometer sensors exhibit misalignment in their Z-axis measurements. For example, while the X and Y axes produce values ranging from -1000 to 1000 mg, the Z-axis measurements range from -500 to 1500 mg.To compensate for this misalignment, I apply an offset variable. However, the issue is that some sensors initially show good alignment when tested in my office, but after being installed on excavators, they develop misalignment over time, similar to what I described above.My questions are:What could be causing this misalignment to appear over time?What steps can I take to prevent this from happening?Thanks

I'm trying to add an LIS2MDL (STEVAL-MKI181V1) magnetometer to my LSM6DSV32X's (STEVAL-MKI240KA) sensor hub. I can't get the LSM6DSV32X to properly identify the LIS2MDL, and I'm not sure if it's a hardware- or firmware-related problem. My current hardware configuration is:SCx on MKI240KA tied to SCL on MKI181V1SDx on MKI240KA tied to SDA on MKI181V1INT2 on MKI240KA tied to DRDY on MKI181V1Jumpers on MKI240KA shifted to SCx/SDx positionsCS on MKI181V1 tied to VddFor context I'm using Zephyr RTOS, but the initialization sequence for the LSM6DSV32X should be the same, especially since it fails right at the beginning when attempting to identify slaves. From the LA output, it looks like the LSM6DSV32X is trying to communicate with the external sensor but it can't sufficiently drive its SCx/SDx pins?

I’m using the VL53L8CH sensor with an ESP32 and developing a program in Arduino language based on Example_10_motion_indicator.c provided by ST. I successfully obtained the motion indicator output using a 4x4 map.Next, I tried switching to an 8x8 map by applying the following settings: VL53L8CH sensor(&Wire, LPn_PIN); sensor.set_resolution(VL53LMZ_RESOLUTION_8X8);sensor.motion_indicator_init(&motion_config, VL53LMZ_RESOLUTION_8X8);  However, when I checked the output, I noticed that the 1st and 2nd values, as well as the 9th and 10th values, are identical, resulting in behavior similar to a 4x4 map.Could you please advise if there are any additional settings required or if this might be related to a library issue? Any suggestions or insights would be greatly appreciated.

Hello,I am writing a firmware with nrf52832 microcontroller and I have interfaced ST's LSM6DSL module. I am facing some issues regarding power consumption of LSM6DSL module. I have used 10K resistors with sda, scl, sdO and cs pins is this correct.I am initializing my module below are the commands : using the wake up interrupt with inactivity function enabled to power down gyroscope.uint32_t app_mpu_int_enable(void){uint32_t err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_TAP_CFG1, 0xF0);if(err_code != NRF_SUCCESS) return err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_WAKE_UP_DUR, 0x00);if(err_code != NRF_SUCCESS) return err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_WAKE_UP_THS, 0x30);if(err_code != NRF_SUCCESS) return err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_MD1_CFG, 0x20);if(err_code != NRF_SUCCESS) return err_code;return NRF_SUCCESS;}uint32_t app_mpu_init(void){uint32_t err_code;uint

Hi, I am following the linux-startguide-stbrightsense for the Raspberry Pi 5 (with a clean build of RPi OS Lite, where I only had to install the i2c regmap), and I have come across some problems in the tutorial. I am using two VD66GY cameras, with the entire S-board kit. Hardware connection is OK, as I get I2C communication and I can detect them both via the i2cdetect on i2c4 and i2c6.I have put both dtoverlays together, as I have both cameras plugged in (basically the same thing except changing some names for conflict reasons):  // SPDX-License-Identifier: GPL-2.0-only /dts-v1/; /plugin/; /{ compatible = "brcm,bcm2835"; fragment@0 { target-path="/"; __overlay__ { camera_clk_12M: camera_clk_12M { #clock-cells = <0>; compatible = "fixed-clock"; clock-frequency = <12000000>; }; v1v2: v1v2 { compatible = "regulator-fixed"; regulator-name = "fixed-supply-1v2"; regulator-min-microvolt = <1200000>; regulator-

  Hello ST Team, We have integrated the TOF sensor into our hardware, and we would like to clarify the following: How can we calibrate the TOF sensor? When does the calibration occur—during device power-on or reboot? What are the results of the TOF sensor calibration? Thank you for your assistance!

Hello,my team is planning to use the gyroscope of the part LSM6DSOX in a health tracking device,and one of the engineers noticed that the readings from the Gyroscope often have measurements that go beyond ±2000dps (specified in the datasheet as Full Scale).When converting raw data to dps, based on the Angular rate sensitivity, 2000dps would correspond to around 2000dps/70mdps ≈ 28,571 (raw data). But there are raw data readings higher than 28,571.The datasheet does not cover results beyond ±2000dps.Is there any validity for readings beyond ±2000dps, to the point offor example using the given Angular rate sensitivity to convert raw data output of 32767 to ≈ 2,293dps (15% beyond Full Scale)?Or could there be any distortion involved, making readings beyond 2000dps invalid? Best Regards,

I am trying to use Satel -Vl53L8 after breaking it .  I am unable to operate it , I also tried to use the same method as used by brekout board but failed . Here is the circuit I usedIs there a way I can use the brakout board , What circuit do I need to use.

HiI managed to read both accelerometer and gyroscope ISM330DLC in "polling" mode with INT1 pin with 3330 output data rate, but my goal is to reach peak data rate (6660 samples / s) so I need to use FIFO and this is where my problems start, I dont know how to set FIFO properly, results in FIFO are intertwined. Could you show me a problem in my configuration? I have some success with enabling FIFO but I have no clue how to configure it to reach my goal which is reading acc ang gyro via primary SPI with max data rate (6660 Hz) and with lowest latency (low set fifo watermark) My code   /* Header of application modules */ #include <sensors-board-app/logging.h> #include <sensors-board-app/ism.h> #include <sensors-board-app/ism330dlc.h> /* Header from CubeMX autogenerated code */ #include <main.h> #include <spi.h> #include <gpio.h> /* Constants */ /** @brief Timeout of ISM330 SPI interface */ #define ISM330_SPI_TIMEOUT_MS 100 /* Priv

HI, it seems to me that reading the LIS2MDL sensor only works correctly if I read first the X axis, then the Y axis, and finally the Z axis separately, each axis in a separate SPI transaction. My settings:- continuous measurement, output data rate set at maximum 100Hz- temperature compensation turned on- high resolution mode- low pass filter disabled, offset compensation disabled- i2c disabled, SPI 3-wire clocked 10MHz, BDU enabled- data ready interrupt on INT pin triggers enqueuing event into event queue, then main loop perform readout after some time (there are other higher priority tasks) My observations:1. Reading 8 bytes in one SPI transaction (from OUTX_L_REG 0x68 to TEMP_OUT_H_REG 0x6F) to read all data does not work at all, temperature data is broken, you need to split readout into 6 bytes of "axis data" and 2 bytes of temperature data2. In certain edge cases of my application when possible readout latency is high I have incorrect readouts of Z axis from time to time

MLC was working and suddenly stopped working , checked all the registers related to MLC and all the writes and read were happening properly.Even tested accelerometer data in the same state and it was also working fine.My device gets powered on using coin cell battery and after draining out the power , MLC started working (power dissipation in this scenario was much high than the normal scenario)

Hello everyone,I'm using the II2SDH accelerometer and want to collect the data whenever the Data Ready Interrupt is fired. I'm using the INT1 pin for that and this is my configuration: SPI_WriteByte(CTRL_REG1, 0x9f); // Low power mode, 5.376Hz data rate, XYZ Axis enable SPI_WriteByte(CTRL_REG2, 0x00); SPI_WriteByte(CTRL_REG3, 0x10); // INT1 on data ready SPI_WriteByte(CTRL_REG4, 0x00); SPI_WriteByte(CTRL_REG5, 0x00); SPI_WriteByte(CTRL_REG6, 0x00);The INT1 pin is configured as external interrupt mode on STM32, but the interrupt won't triggered. Is there any other ways to collect the data correctly? Otherwise my FFT calculation is incorrect.Any ideas how to fix the problem will be appreciated. Thanks.

Hello, I am wondering if there is any software reset for the VL53L8CX when using the ST provided API. When I reprogram my micro using ST-LINK but do not do a hard power reset on my device the VL53L8CX init fails. I have attached an image below showing soft reset ST-LINK operation and hard reset. In UM3183 I see that a power cycling of the device is recommended for reset. Is there any ability to do this through the API?    Point in which the VL53L8CX init fails:vl53l8cx_api.c  --> _vl53l8cx_send_offset_data() status |=_vl53l8cx_poll_for_answer(p_dev, 4, 1, VL53L8CX_UI_CMD_STATUS, 0xff, 0x03);  UM3183:  

I need to configure LIS3DH to generate FIFO full interrupt in INT1 pin. Once my MCU gets the hardware interrupt, it will read entire FIFO. And the loop should continue. Can anyone help me what are the correct steps to configure and read FIFO?Regards, 

I am using an adafruit stm32f405 feather, with the hal rather than arduino. I have I2c, and CDCworking now, and would like to add audio functionality with a mems mic.The I2s pins are available pins, but the clock cannot get to a low enough speed(1MHZ) through PLL.I thought about using divided master clock output ,and jumping to external source for I2s clock, but thesepins are not available. Can I use TIM3_CH2, jumped to an SPI clock input, and read the data using that periipheral.The data sheet for the mic says it can use I2s, SPI, DFSDM, and sai.  SPI is the only one that is both present, and available. I haven't seen any examples doing similar, unlike I2s cube examples. Any advice? Many thanks in advance.

I have a LIS3MDLTR connected over I2C on an aerial system that is used as part of our GNC system.  In our most recent test we received data from the magnetometer that appears to have gotten "stuck" reporting to exact same measurement (see below).  The system was flying from minute 0 until around minute 10.I've seen this behavior in the lab as well and I have found that I can temporarily fix this by rebooting the magnetometer by writing to the REBOOT bit in CTRL_REG2.  While this does resolve the issue, it frequently re-appears (about every 2-3 power ups).  What is causing this issue and how can I avoid it?I have multiple peripherals connected to the I2C bus that continue operating correctly so it is not an issue with the I2C master.The LIS3MDLTR is configured as follows.0xFC, // CTRL_REG10x0, // CTRL_REG20x0, // CTRL_REG30x0E, // CTRL_REG40x40 // CTRL_REG5Since I'm reading from the magnetometer at a rate of 10Hz, significantly lower rate than it's 80Hz output r

Hello,I am trying to get my STM32WB5MM module to talk to VL53L7CH. I have working BLE project (compiles no warnings, no error and works-advertises as beacon). Now I added files from STSW-IMG043, according to doc file in the package.I also modified the platform.c file, with I2C functions (used the ones from F401 example, just changed the I2C handle to the one I use "hi2c3").After trying to compile, I receive some weird errors in log that I haven't dealt with before, so some help would be appreciated. From what I could extract, there are some "wrong" definitions in file "vl53lmz_buffers.h" (haven't modified that file at all). Log output:   11:14:34 **** Incremental Build of configuration Debug for project XXXXX **** make -j16 all arm-none-eabi-gcc -o "FPulse.elf" @"objects.list" -mcpu=cortex-m4 -T"C:\Users\klemen.skorjanc\Documents\CubeIDE_workspace\FPulse\STM32WB5MMGHX_FLASH.ld" --specs=nosys.specs -Wl,-Map="FPulse.map" -Wl,--gc-sections -static --spe

Hello,How is the INTERNAL_FREQ_FINE register set in the ISM330?Is it factory calibrated or is there on board logic that allows it change with age/temp/etc.?Thank you,Brandon M

Hello!I took two attemps and recorded measurements in steady state (2 and 3 hours) that i want share.Config:G/XL FS: default ODR 104HzSensor data polled at rate ~ 90HzSome standby/wakeup stuff:TAP_CFG0 (56h) = b0101.0001TAP_CFG2 (57h) = b1000.0000WAKE_UP_DUR (5Ch) = b0100.0000WAKE_UP_THS (5Bh) = b0000.0001MD1_CFG (5Eh) = b0010.0000Can the bias drift be explained somehow?Many thanks

Hi.I am working on evaluation with STEVAL-MKI210V2K. I use Unico to get sensor data, however what I really want is post-fusion data. Looking at other forum questions, it seems like Unico gives a "fusion" option on the left vertical tab. I don't have it (as well as the QVar option).Is it because the product I am using does not have this feature in the HW/FW level?Or am I missing something? Thanks.  

Hi,     We are use openWRT and  ism330dhcx and LIS2MDLTR  on board.  The ko driver   has been created and  insert into kernel . When read data from  /sys/devices/platform/i2c_gpio@0/i2c-0/0-006a/iio:device2/in_accel_XXXX,   We has found the Z value is random ( device dosn't move ).   it cause our heading value calculation  is not stable.   Any suggestion ?BR, arprip  Here is the log============check imu ko module =0ST imu & mag40 ko already loadedST ISM330DHCX (G sensor):accel x_raw= 804, x_scal=0.001196411accel y_raw= -18, y_scal=0.001196411accel z_raw=32764, z_scal=0.001196411check imu ko module =0ST imu & mag40 ko already loadedST ISM330DHCX (G sensor):accel x_raw= 278, x_scal=0.001196411accel y_raw= -16, y_scal=0.001196411accel z_raw= 8070, z_scal=0.001196411check imu ko module =0ST imu & mag40 ko already loadedST ISM330DHCX (G sensor):accel x_raw= 159, x_scal=0

Hi everyone! I am using LSM6DS3 in a very simple setup: For the debugging purposes I am only using accelerometer, ODR is set at 416Hz, fifo is enabled in continuous mode and set at the same freq, no decimation. Only XL data is set to be stored in fifo. I am reading data from fifo every second while buffer is constantly being filled. In random intervals the data I am reading gets corrupt in different ways: One axis data is simply missing (even reading the pattern confirms that there is an entry missing)Value from one axis is read out at another axis (pattern) (e.g. if device is standing still on the table, and normal reading is 10,10,-990, one of the readings can be -990,10,-990 or 10,10,10, while pattern values are always 0,1 and 2. Sometimes it even happens that the pattern is an invalid value (>2). I have tried reading values in a numerous ways (reading fifo_status 1,2,3,4 and then fifo L and fifo H) and all possible combination of those. I have also tried reading whole fifo in a

We are developing product with VL53L8CH integrated. Now I have to developed simple firmware that will extract data and control it and for that I need datasheet with registers description. After searching for over an hour, I cant find any datasheet, user manual or application note on this topic.