MEMS and sensors

Hello Guys,  currently, im trying to get the VL53L0X to work with my MSP430 Controller but my biggest problem is the communication with the Device. Ive copied the Software from Artful Bytes and changed it to match my board. Here is the Link: https://www.artfulbytes.com/mcu-i2c-driver   Ive tried to write a simple byte to the Sensor but all it does is pulling SCL and SDA down right after transmitting the last digit (write). It doesnt even give an ACK and it willbe pulled down until i cut the power supply. Writing Byte Ive also tried to read a byte from the Sensor and strangly it seems work. All i did was to write a simple code to read right from the VL53L0x. There was no init for the Sensor but it didnt pull the line down. Reading Byte I need help with my Sensor. Do i have to write some data to an other Slave-address before writing to 0x29?    Sincerely EddyK

Hello,Please the pressure sensor LPS22DF is it recommanded for a new design ?Thank you

Hello, I am having trouble with the VL53L4CX Sensor for my Capstone Design Project. My group created our own breakout board for the sensor, and I was able to get it up and running with the VL53L4CX_SimpleRanging project provided by ST.However, I am having trouble figuring out the setup for our own project. Here's my steps to get to my problem:I create a new project with Board Selector, NUCLEO-U575ZI-Q.I click Software Packs, and Select the dropdown for X-CUBE-TOF1.I select VL53L4CX under the Board Part Ranging dropdown.I setup a GPIO pin on the Nucleo for XSHUT, see below.  I setup I2C2 with Fast Mode, and connect the VL53L4CX breakout board to the Nucleo Board (SCL to SCL, SDA to SDA, XSHUT to GPIO, AVDD to 3.3V, IOVDD to 3.3V, GND to GND). I also setup UART1 for terminal debugging.In Middleware and Software Packs, I choose X-CUBE-TOF1, and choose the GPIO for VL53L4CX _XSHUT and I2C2 for VL53L4CX BUS IO driver.Then, I setup the code as below:   This

Issue with Wrist Tilt Direction Detection on LSM6DS3TR-CHardware & Software Details:- Sensor: LSM6DS3TR-C- Platform: Arduino- Interface: I2CProblem Statement:We are working on detecting wrist tilt using the LSM6DS3TR-C sensor. While the tilt detection interrupt (`wrist_tilt_ia`) is triggering correctly, the tilt direction values (`wrist_tilt_ia.xpos`, `wrist_tilt_ia.xneg`, etc.) always remain zero, regardless of the actual movement.Configuration Steps Taken:Sensor Initialization:Verified sensor presence using lsm6ds3tr_c_device_id_get().Performed a software reset using lsm6ds3tr_c_reset_set().Enabled Block Data Update (BDU) to ensure data consistency.Sensor Configuration:Set accelerometer output data rate to 26Hz (lsm6ds3tr_c_xl_data_rate_set()).Set gyroscope output data rate to 26Hz (lsm6ds3tr_c_gy_data_rate_set()).Configured accelerometer full scale to ±2g and gyroscope to ±2000 dps.Wrist Tilt Detection Setup:Enabled wrist tilt detection (lsm6ds3tr_c_wrist_tilt_sens_set()).Config

Hello there,  Are there any examples on how to use the inactivity feature of the lsm6dsv16x?I checked the github and I only see for waking up, but not the other way around. My goal is to set a device to sleep once there is no motion from imu. meaning, once the imu has no motion, it sets an interrupt like hey there is no motion going on, go to sleep/off mode. Then once there is motion, I want the imu to fire a interrupt telling device, here wake up. Is it possible to use one Interrupt pin for both cases or do I need to use both?

I am using steval mkbox-pro with FP-SNS-DATALOG2 to get acceleration from the subway train.How can i remove the gravity effect in measurements from the LSM6DSV16X accelerometer? 

Hello,I'm trying to calibrate the gyroscope of LSM6DSO MEMS but I don't really understand what describe the quality parameter in the MGT_state_t structure. I didn't find any information about it in the datasheet. Could you explain it to me ?I succeeded few times to calibrate the gyroscope but sometimes even with the quality close to 0 (1e-8) the bias are not good at all. Is there a procedure to follow to achieve the gyroscope temperature calibration ? And when the bias are better, there is always an offset. How can I resolve it ?

Hi, I'm trying to use the LPS28DFW in one shot mode and there seems to be a discrepancy between the devices functionality and the application note.From an5758 section 3.2 - one shot mode: "One-shot mode has to be executed while the device is in power-down mode by setting the ONESHOT bit (default value 0) in CTRL_REG2(@11h) to 1. When this happens, a single data acquisition is executed and read data are made available in the output registers. Once the acquisition is completed and the output registers updated, the device automatically enters again power-down mode and the ONE_SHOT bit is self-cleared (to 0)"Based on this I set CTRL_REG1 to 0x03 (power down mode, 32 sample average) and CTRL_REG2 to 0x41 (4096 full scale, one shot enabled). I then poll the value of CTRL_REG2 to wait for the one shot bit to be self-cleared to indicate the acquisition is complete and read out the sample.However the first reading of CTRL_REG2 is 0x40 (one shot bit cleared), even with almost no delay. This mean

I configured both the accelerometer's and gyroscope's odr in asm330lhh to 6.667kHz, and used a FPGA to sample the acceleration and angular velocity as quickly as possible. The spi read start from 0x1E to 0x2F, which include both the ready bits and motion data. All the data sampled was sent out via uart at a frequency of 1kHz. Then i found the odr of accelerometer was quite slower than 6kHz, i don't know whether it's normal.The photo below is the record, tempCnt, gyroCnt and acclCnt represent the sum of the ready bit(get from 0x1E register) of temperature, gyroscope and accelerometer respectively in 1 millisecond. The attachment is the configuration code of asm330, is the configuration right? Or i missed any other details?

Hello To receive various Interrupt events how INT1 and INT2 Pins of LSM6ds3tr need to be connected with Microcontroller ?My assumption is INT1 and INT2 pins need to be connected with microcontroller GPIO pins and GPIO pins has to be configured to catch IMU Interrupt events. Please Support whether this assumption is correct or not.

I want to download other versions of STSW-IMG019 software, how can I download it?At present, the official website can only download the final version

Hi, I'm trying to get the VL6180 Time-of-Flight (ToF) proximity sensor working with the SAM E54 Xplained Pro evaluation kit. Hardware Setup: Board: SAM E54 Xplained Pro Sensor: ST VL6180 ToF Module IDE: MPLAB X v6.10 (Linux x64) Connection: I2C + GPIO Current Status: SERCOM3 is connected to SDA on PA2 and SDL on PA23 The external interrupt (GPIO 1) is connected on PB08 GPIO 0 is connected on PB09 Using the VL6180X API (v2.3.1) Goal: Get the VL6180 working via I2C Operate the sensor in interrupt mode to read sensor data I attempted to use the VL6180X API (v2.3.1), but it needs to be ported to the SAM E54. I'm struggling to understand: Which parts of the API need modification for the SAM E54? How to correctly implement I2C communication with the VL6180 using the API? How to configure and handle interrupt-based operation on the SAM E54? Are there any example projects or resources that could help with this setup? Any help or guidance would be greatly a

Hello all,I have a question regarding the MEMS audio sensor MP23DB01HP. I managed to read out the Soundlevel of the sensor. But I don't know how to interpret this value. My question is, how can I convert the soundlevel to obtain a corresponding value in dB? Is the datasheet needed for that conversion?Thank you in advance for your replies

I want to recognise small movements with small acceleration.Which mode is best suited?Is it better to have a high sampling rate or a lower one?which filters?where do the large peaks (incorrect values) come from?But I can already recognise the acceleration and braking

HiWe are currently working on a project using the nRF5340 MCU with Zephyr, and the interface between the MCU and LSM6DSOX is set up using the I2C protocol.We are able to successfully get data related to step count, accelerometer, gyroscope data, tilt, tiltpan, single/double tap. We are trying to evaulate the Activity recognition feature.As part of the project, we are trying to implement the MLC (Machine Learning Core) for detecting activity states such as idle, walk, or run. We came across example application on GitHubhttps://github.com/STMicroelectronics/STMems_Machine_Learning_Core/tree/master/application_examples/lsm6dsox/Activity%20recognition%20for%20wristhttps://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsox_STdC/examples/lsm6dsox_activity.cBased on above links, we integrated the lsm6dsox_activity.c and lsm6dsox_reg.c files into our application firmware, as these files have necessary dependencies

With LSM303AGR to achieve the electronic compass function now 0-360 degrees can be obtained normally, has increased the calibration function; Why the uneven distribution 

Hi,My company uses the ASM330LHH for dead-reckoning applications and we are trying to improve the performace of the gyro with our own calibration of rotation sensitivity. After calibration, we want the gyro sensitivity accuracy to be 0.1 % or better over -20 to 70 C. I know this may not be easy or feasible, but we still want to get as close as possible. Our current calibration procedure uses an Ideal Aerosmith rate table that we try to set to 100 dps +/- 0.01 %, but we're running into a ton of issues getting an accurate enough speed. I'm hoping someone can help show us a better way!Right now, our rate table often misses the set rate by much more than 0.01 % or the rate will oscillate around the set point by much more than 0.01 %. We have tried using the rotation rate readout of the rate table, but that is showing its own set of difficulties. Is this what folks normally do for high-accuracy sensitivity calibration? Or is an ultra-high accuracy gyro normally used as reference for th

Hi,We're using the lsm6dsv's SFLP algorithm to calculate IMU rotation. Recently however we noticed that the resulting rotation has big gaps at around the 180degree mark. We believe this is because of the half float precision, specifically because there aren't a lot of representable values near 1. See below image for our calculated accuracy results which match the actual results we're seeing:  

I am using a python script to update the One Point Calibaration register 1Ah, 1Bh. I put values in but the resultant reading of the normal pressure registers in 28h, 29h, 2Ah are way off. Does anyone have a script that might show exactly how it is done. The script can be in about any computer langauge.Are there any tricks to get this to work?

Hi, I’m working with the IIS3DWB accelerometer to acquire single-axis data (Z-axis) using the following setup:Full Scale: ±16gSPI Mode 3 at 10 MHzTarget ODR: 26,667 HzI have attempted different methods to read the Z-axis data. First, I tried reading the Z-axis high (0x2D) and low (0x2C) registers using a timer with auto-increment. I also tried using 1AX_TO_3REGOUT mode and reading all 6 registers (0x28 to 0x2D) using a timer with auto-increment.I then configured the sensor with the following register settings:write_register(IIS3DWB_CTRL1_XL, 0x00); // Power Downwrite_register(IIS3DWB_CTRL6_C, 0x03); // Single Axis Mode (Z-Axis)write_register(IIS3DWB_CTRL1_XL, 0xA4); // Power On, Full Scale 16g, 26.667 kHz ODR write_register(IIS3DWB_CTRL3_C, 0x44); // BDU and Auto Increment Enabled write_register(IIS3DWB_CTRL8_XL, 0xF4); // High-pass and Low-pass Filterswrite_register(IIS3DWB_CTRL4_C, 0x01); // 6 Consecutive Single Axis Valueswrite_register(IIS3DWB_CTRL5_C, 0x20); // Wraparound Rounding

Hello awsome peaple of the ST fourms,I've been writing a program on the MB1551-U585AI1-D01 STM32U5 dev board, after getting DMA working and writing some AzureRTOS aware platform functions for the MEMS sensors on the board I have been very successful in communicating with both the ISM330DHCX (IMU) and IIS2MDCTR (Magnetometer).However, I have a single issuse that has just popped up that has me puzzeld. During setup of the ISM330DHCX I first check the WHO_AM_I to make sure the sensor is present and talking, I then attempt to software reset it.  // Initialize IMU stmdev_ctx_t imu_dev_ctx; imu_dev_ctx.write_reg = imu_platform_write; imu_dev_ctx.read_reg = imu_platform_read; imu_dev_ctx.handle = NULL; uint8_t whoamI, rst; ism330dhcx_device_id_get(&imu_dev_ctx, &whoamI); if (whoamI != ISM330DHCX_ID) { //TODO: Handle device not found tx_thread_suspend(&imu_thread_ptr); } // Reset the device // The bellow is me testing how the device behaves after the r

Hello community, I am an electronics engineer at the CNRS in Montpellier (France). I am currently working with the IIS3DWB vibration sensor When I use the LFP2 low-pass filter, the action of gravity is added to the measurements. I use the following data registers:- CTRL1_XL- CTRL3_XL- CTRL8_XL This result is as unexpected as it is disconcerting.Has anyone ever encountered this type of problem?Thanks in advance to anyone who can help me. Olivier Maudens    

Hello all,I am working with the LSM6DSV16X and trying to determine whether the Sensor Fusion Low Power (SFLP) algorithm processes raw or filtered accelerometer and gyroscope data. Specifically, can I adjust filtering settings (e.g., LPF2 bandwidth) before the data is used by SFLP?What I Have ReviewedI’ve checked both the LSM6DSV16X datasheet and Application Note AN5763, but I haven’t found a clear answer.The Sensor Fusion section only says it generates "the following data based on the accelerometer and gyroscope data processing," but doesn't specify which accelerometer and gyroscope data it uses.Figure 3 in AN5763 (Accelerometer filtering chain - UI path) outlines filtering stages but does not show where SFLP takes its input.SFLP writes its output to FIFO, but it’s unclear if it takes its input before or after filtering.I understand that SFLP ODR must be ≤ sensor ODR, but does it depend on filtering settings as well?What I Need to ConfirmDoes SFLP process raw or filtered sensor data? I

@SimonePradolini Hi Simone,Can I get a 64 Bit version of libhs_datalog.so for Raspberry Pi 5 of the X-CUBE-MEMSMIC1 expansion software package please?Or the source code to compile it?Unfortunately DATALOG_V1.5.1 just provides a 32 Bit version libhs_datalog_rpi3b.so for Raspberry Pi 3B only.This would be awesome. Best regardsJoerg

I have bought a MKI-165V1 to test LPS25HBTR,but I find that the pressure value is decreasing for a long time ,from 1014.117 to 1002.970 in an hour.It is not stable,the next is my initial code,what is the reason for ituint8_t data = 0x90;HAL_I2C_Mem_Write(&hi2c4, 0xB8, 0x20 , I2C_MEMADD_SIZE_8BIT, &data, 1, HAL_MAX_DELAY);HAL_Delay(10);data = 0x00;HAL_I2C_Mem_Write(&hi2c4, 0xB8, 0x21 , I2C_MEMADD_SIZE_8BIT, &data, 1, HAL_MAX_DELAY);// HAL_Delay(10);// HAL_I2C_Mem_Write(&hi2c4, 0xB8, 0x22 , I2C_MEMADD_SIZE_8BIT, pData, Size, 0xFF);HAL_Delay(10);HAL_I2C_Mem_Write(&hi2c4, 0xB8, 0x23 , I2C_MEMADD_SIZE_8BIT, &data, 1, HAL_MAX_DELAY);HAL_Delay(10);