MEMS and sensors

My customer asked me to assess some ST MEMS products using a project he found on Github: https://github.com/STMicroelectronics/X-CUBE-MEMS1/tree/main/Projects/NUCLEO-L152RE/Applications/IKS01A3/FitnessActivitiesThis advised to purchase a Nucleo L152RE, a X-NUCLEO-IKS01A3, STEVAL-MKI196V1 and STEVAL-MKI224V1. I have actually ended up with a X-NUCLEO-IKS02A1 because the X-NUCLEO-IKS01A3 is obsolete and the write-up on ST web site https://www.st.com/en/development-tools/unicleo-gui.html says it can be used. I used the most recent updates to STM32CubeIDE to download and import the FitnessActivities project and compiled it okay, and installed it in the Nucleo L152RE with the X-NUCLEO-IKS02A1 plugged in.This sort of works but the Unicleo-GUI thinks that the X-NUCLEO-IKS02A1 is an X-NUCLEO-IKS01A3 and shows the wrong links to set pictorially, with nothing readable on the screen.Will this set-up work with the current set of equipment? I am interested in assessing both the optional sensors I li

LSM6DSOX is a really powerful chip for detecting events, but i also wanted to get quaternions out of it without having to do any math on raw IMU data.   So this is what i found Example  IMU driver  Register 59H - TAP_THS-6D,  You can enabled 4D/6D position.   This will trigger events from register D6D_SRC 1Dh But this just give you a general direction on where your going.  It would be more useful if i had just a quat i could grab at a given frame rate.  Is that possible?  

EDIT [Solution]: The register 0x0014 needs to be set to 0x04. (I put more details in the reply but it has been marked as spam for some reason). I am in process of interfacing an Attiny85 (not Arduino) with a VL6180X board (with I2C level shifter built-in).I wrote my own I2C master interface (USI) and I am able to successfully to get the VL6180X work in a single shot mode (after many hours of struggle).I spent a lot of time wild geese chasing due to VL6180X "pretending" to respond correctly to some of the register read/writes but not being able to actually read the actual distance until I moved the whole thing to battery power (adding additional capacitors to 2.8V or 3.3V supplies didn't help).One thing that lead me astray was the fact that I never bothered to check the actual contents of the 0x0062 register after setting the 0x0018 register, as I was following somewhat scarce documentation and polling the 0x004f register for a ready bit set (as per the application note): &nbs

I just wanted to check the validity of an old post from 2022.The VL53L8CX, like other TOF devices returns a 8x8 grid of distances.The distances are tuned, so if a flat surface for example a wall is directly in front of the sensor (sensor is facing the wall with no offset or rotation) at a distance of 1 metre. Then all the 8x8 Zones will report a distance of 1 metre (assuming no floor, ceiling etc..., so there are no other reflections etc...). The measured distances are in fact larger for angles offset from zero, but they compensated for the requirements of the mobile phone manufacturers etc... Is this still true. Link to post:-Solved: VL53L5CX Distances Don't Match Theory - What am I ... - STMicroelectronics Community

Hello,we use STHS34PF80 sensor as little animals detector (FOV ~ 20cm) and we have problem with false motion detection on outside. When we have sunny day the sensor goes crazy and output random MOT_FLAG signals. We have try to change LPF_P_M and LPF_M filters but without success. Also we try to change motion threshold and motion hysteresis also without success.Is any solution for this problem?Thanks in advanceAdam Socha

I am looking to purchase an evaluation board for the VL53L8CH in order to take advantage of the CNH data for potential use in AI models.The below expansion board web page has the below text (Link below) Time-of-Flight expansion board based on the VL53L8 series for STM32 Nucleo:VL53L8CX Low-power high-performance 8x8 multizone ToF sensorVL53L8CH Artificial intelligence enabler, high performance 8x8 multizone ToF sensorI already have a VL53L8CX, which lacks the CNH data. The info on the web page has both part numbers, however I think only the VL53L8CH has the functionality I require.X-NUCLEO-53L8A1 - Time-of-Flight expansion board based on the VL53L8 series for STM32 Nucleo - STMicroelectronics This is just the expansion board. I guess the main board could be the following board.This page has the main board and expansion board. P-NUCLEO-53L8A1 - STM32 Nucleo pack with X-NUCLEO-53L8A1 expansion board and NUCLEO-F401RE development board - STMicroelectronics&nb

Hello,I've been working with a SATEL-VL53L8 sensor for a while. For this I've used the L4RZI board and now i moved into the nRF52 board for more tests.I've been having trouble trying to implement this. I've tried to use the VL53L0 configuration, (CONFIG_VL53L0X_PROXIMITY_THRESHOLD    and   CONFIG_VL53L0X).This because i did not find any configuration for the VL53L8 available (besides the one available in the GitHub for the ST32duino (https://github.com/stm32duino/VL53L8CX)).I've tried examples for the L0, and the L8, including using the one available in GitHub. Is there any CONFIG for the VL53L8 that can be used for this board (nRF52 DK)?   (I've checked examples between nordic-ST regarding the L1 and L0)

I have a big issue with the STEVAL MKSBOX1V1. I was making some attempts to work with the Vibration Monitoring Example (made up of "Training" and "Compare" sub-processes). After having successfully run the example on the firmware preloaded on the SensorTile.box, I made some changes to the examples in order to stream data over Bluetooth, so I uploaded a custom firmware. Af this the SensorTile proposed to me to upgrade to firmware 3.4.9, so I accepted it and the new firmware was correctly uploaded. I noticed however that the example didn't work correctly anymore, since the "switch lamp" that should be light-on only when an anomaly vibration was detected, was always lighted on after the firmware upgrade. So I checked the possibility to swap to previous firmware version, but no possibility was provided within the app and on the ST site, associated to the  STEVAL MKSBOX1V1, I found only one firmware with description "SensorTile.box firmware OTA function restore". In the details "T

does MEMS studio support STEVAL-STWIN KT1B board ; cause according to the UM (https://www.st.com/resource/en/user_manual/um3233-getting-started-with-memsstudio-stmicroelectronics.pdf) only STEVAL-STWIN KT1 Hardware compatible (not with full/reduced sensor evaluation) just for algobuilder functionality.

I am designing to mount LPS25HB on the board.Communication is I2C.Please help me with the connection of Pin 7 (INT_DRDY).Is this pin an open pad? Or does it need to be connected to GND?

I have 4 LIS2DW12TR accelerometers connected to an Seeed Studio ESP-32 S3. The accelerometers get extremely hot when they're connected to 3.3V. They are not recognised with an I2C scan.The accelerometers are connected to 2 pairs of SDA/SCL pins. Each accelerometer has the same layout, save the SAO pin which sets the I2C address.They each have an LED connected to show that the accelerometers are on.They're connected as follows: The LEDs don't turn on but the accelerometers get extremely hot.Thing's I've tried so far:Did a continuity test with a multimeter (and very fine needles) - all the routes are connected as the schematics show, none are shorted.Removed R9 - the accelerometer became even hotter.Added a 27kΩ resistor to limit current to 100uA (data sheet asks for 90uA). I chose 27kΩ by measuring resistance between the 3.3V power route and the ground plane - it was 11kΩ. `27kΩ ≈ (3.3V/90uA) - 11kΩ`I'm not sure what else can be causing the over heating, or what i'm missing here. This

Hello everyone,I'm working on implementing the Kalman Filter algorithm for sensor fusion from the MotionFX library using the ISM330DHCX MEMS sensor. My setup consists of the STM320G71RB board and the IKS02A1 expansion board. I'm trying to get the pitch and roll angles mainly, but the problem is, when the sensor is static, the pitch and roll angles exhibit drifting over time. In addition, when I look at the raw data from the gyro and accelertometer along all three axes, I don't see any drifting, only consistent fluctuations. This is what i'm currently doing using the motion_fx_cm0p.c library:  -MotionFX init-Gyro calibration enabled-6x fusion enabled and 9x fusion disabled- sensor setup at 12.5 Hz data rate for both Acc and Gy, scale set to 2g and 125 dps, slope filter for Acc set to ODR/100, and LPF enabled for Acc.- data acquisition from Acc and Gy in g and dps respectively.- applying the MotionFX_CM0P_update() function to get rotation angles.  I also have tried co

Hallo ST Community, Which Part Marking has H3LIS331DL ? Thanks RegardsBadis

STEVAL-C34KAT1 Vibrometer eval board came today and I see it came with 32 pin expansion flex cable (STEVAlL-FLTCB01).   On one end, I plug it to this eval board.  On the other, what do I plug it to?  None of my ST eval boards have such connection.   I need some kind of (beak out) adapter to connect to pins on  board.  What adapter do I need please to connect this to pins?

Hello Everyone!!!I am using ISM303DAC Mems sensor for my project ie., E-Compass.I have used MotionMC and MotionEC libraries to get the heading value i my compass is getting calibrated by MotionMC and after that i am sending those calibrated values to MotionEC library and receiving heading values but there i have found that Angle is drifting about 0.1 -  0.9 deg. Is it possible to compensate this drift i have taken reading for 15 min in a particular place & observed that there is a standard deviation of around 0.5degCan anyone please suggest how to compensate this drift.Thank you!!!regards,ANIL.

Hello Everyone!I am working on a project Ecompass using controllers STM32F401CBU6 and mems sensor ISM303DAC. can able to read raw values of both accelerometer data and magnetometer data properly and after reading the magnetometer data i am parsing magnetometer data to MotionMC library for calibration purpose but after calling MotionMC_GetCalParams function output is always showing asHI_Bias = {0, 0, 0},SF_Matrix = {{1, 0, 0}, {0, 1, 0}, {0, 0, 1}},CalQuality = MMC_CALQSTATUSUNKNOWNi have used systick as timestamp and and also cross verified with heap and stack, rotating the sensor in 3D space 8 direction everting tried but nothing got work..... got stuck at this point.could anyone please let me know what might be the problem.Thank you!!!ANIL.  

Hello everyone,I just received my X-Nucleo-53L7A1 board and I'm trying to get it working with my Nucleo-F429ZI. In CubeMX,I've selected my board and the appropriate software pack. For the pin configuration, I followed the example provided for the Nucleo-F401RE.The code generates without any errors or warnings, but when I check my serial terminal, I see the following error:VL53L7A1_RANGING_SENSOR_Init failedCheck you're using ONLY the center device soldered on the shield, NO satellite shall be connected !I can't figure out where the problem is coming from. If anyone could offer some help, I would greatly appreciate it!

Hello,We are using the VL53L1 sensor in autonomous mode to range data, mostly indoors but sometimes outdoor.Following the Table 3 in UM2133, we use the short distance mode in order to have better ambient light immunity when outdoors.However, in the AN5573, Table 6, it says that the outdoor capability in autonomous mode drops to a max distance of 200mm, but our targets are often in the 60cm-100cm range.Is the sensor not usable in autonomous mode at all for our application outside ?Please share any insights, experiences or recommendations regarding the VL53L1's autonomous mode ranging performance in outdoor/ambient light scenarios.

Hello,For a predictive maintenance project on an STwinkT1B board. I am using an iis3dwb vibration sensor.When retrieving the data provided by the sensor, one of the obtained values is saturated close to 65535, which is close to 16 bits.I am using the FIFO_continues mode and registers 0x78 to 0x7E to read the FIFO.To summarize:data_buffer[j] = raw_buffer[i] << 8 | raw_buffer[i+1];with j ranging from 1 to 3 and i ranging from 0 to 7. Please advicesRegardsRapha

I have used the VL53LCX Linux driver to operate the ToF sensor on the IMX8M Nano board, and the Linux driver is functioning correctly. However, I am encountering issues with implementing gesture recognition functionality. I have used the gesture recognition static library M7 Version, which cross-compiled successfully, but the gesture recognition is not working properly. Could you provide the appropriate .a file for the Linux architecture?

Hi all,         What is the part to part variation of ST VL6180 ToF sensor? During testing, we keep the sensor at a distance of 50mm from a retro reflector tape. In a batch of 50 sensors, the readout was from ~ 37 mm to  ~51 mm (expected readout is 50).We made a larger batch of 1800 boards and ~130 boards had a readout from 25 mm to 60 mm (expected readout is 50) . We have used the below settings as per the datasheet.  # Recommended settings from datasheetself.writeI2C(0x0207, 0x01)self.writeI2C(0x0208, 0x01)self.writeI2C(0x0096, 0x00)self.writeI2C(0x0097, 0xfd)self.writeI2C(0x00e3, 0x01) #VL6180_WriteByte(0x00e3, 0x00); (seen this in ST forum)self.writeI2C(0x00e4, 0x03) #VL6180_WriteByte(0x00e4, 0x04); (seen this in ST forum)self.writeI2C(0x00e5, 0x02)self.writeI2C(0x00e6, 0x01)self.writeI2C(0x00e7, 0x03)self.writeI2C(0x00f5, 0x02)self.writeI2C(0x00d9, 0x05)self.writeI2C(0x00db, 0xce)self.writeI2C(0x00dc, 0x03)self.writeI2C(0x00dd, 0xf

Hi allI have successfully implemented a single vl53l0x sensor, but wish to add more. I found the "AN4846 Application note Using multiple VL53L0X in a single design" documentation:https://www.st.com/content/ccc/resource/technical/document/application_note/group0/0e/0a/96/1b/82/19/4f/c2/DM00280486/files/DM00280486.pdf/jcr:content/translations/en.DM00280486.pdfUnder "VL53L0X API management" it specifies:In vl53L0x_platform.h API file set VL53L0x_SINGLE_DEVICE_DRIVER macro to 0 so that API implementation will be automatically adapted to a multi-device context.But I cannot find anything called "VL53L0x_SINGLE_DEVICE_DRIVER" in the vl53L0x_platform.h file.Where can I find it? Or has the files updated without the documentation being updated? If so should this step just be skipped?

Hi, I need some clarification about digital high-pass filter in LSM6DSO since the datasheet and application note for LSM6DSO seem to lack explanation about certain features of it (or I just didn't get it).1. In on page 20 of AN5192 (refer to the image below) showing a table of accelerometer bandwidth selection in mode 1/2/3, it has a list of max overall settling time (samples to be discarded). Does this max overall settling time referring to only the initial period of time when the HP_SLOPE_XL_EN bit is set to 1 and the accelerometer starts producing data or is it referring to the periods from time to time when there are abrupt changes in the accelerometer reading?2. On the same page I mentioned in question 1, it briefly talks about fast settling mode but it doesn't really talk about how fast it shortens the settling time of the low-pass/high-pass filter of LSM6DSO. How fast does the fast-settling mode do the job for either filters? Is there any specific specification about it?3.

Hi,I am using AIS2IH.I  can see in terminal   window of my computerthat registers of  data and temperature are zero's.   0 0 0  ...My program use the setup: ais2ih_cs_mode_set(&dev_ctx, AIS2IH_PULL_UP_DISCONNECT);ais2ih_i2c_interface_set(&dev_ctx, AIS2IH_I2C_DISABLE);ais2ih_spi_mode_set(&dev_ctx, AIS2IH_SPI_4_WIRE);ais2ih_reset_set(&dev_ctx, PROPERTY_ENABLE);platform_delay(0x00333333);ais2ih_reset_get(&dev_ctx, &rst);platform_delay(0x00333333);ais2ih_reset_get(&dev_ctx, &rst);platform_delay(0x00333333);ais2ih_cs_mode_set(&dev_ctx, AIS2IH_PULL_UP_DISCONNECT);ais2ih_i2c_interface_set(&dev_ctx, AIS2IH_I2C_DISABLE);ais2ih_spi_mode_set(&dev_ctx, AIS2IH_SPI_4_WIRE);/* Set full scale */ais2ih_full_scale_set(&dev_ctx, AIS2IH_2g);/* Set Output Data Rate */ais2ih_data_rate_set(&dev_ctx, AIS2IH_XL_ODR_400Hz);ais2ih_filter_path_set(&dev_ctx, AIS2IH_LPF_ON_OUT);ais2ih_filter_bandwidth_set(&dev_ctx, A

Can I use the STHS34PF80 outdoors?This is because ToF sensors cannot be used outdoors.