MEMS and sensors

Hi Sir, What internal adjustments have been made to cause the noise density to differ between the high-performance, normal, and low power modes of the ISM330DHCX? Filter? Gain?Thank you.

Hello,in KDE/plasma environment I can't use MEMS-studio because it doesn't show file dialogs.For example: MEMS-studio is connected to the STEVAL-MKI109V3 board, in "Advanced Features" -> "FSM" I click the "Load state machine from file“ button, but nothing happens, the file dialog does not appear.Is there any solution to allow MEMS-studio to work properly in the KDE/plasma environment?When I run MEMS-studio from the command line I get this output from the console: Searching in: "/home/senbuvis/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin" Searching in: "/home/senbuvis/STMicroelectronics/STM32CubeProgrammer/bin" Searching in: "/home/senbuvis/STMicroelectronics/STM32Cube/bin" Searching in: "/home/senbuvis/STMicroelectronics/bin" Searching in: "/opt/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin" Searching in: "/opt/STMicroelectronics/STM32CubeProgrammer/bin" Searching in: "/opt/STMicroelectronics/STM32Cube/bin" Searching in: "/opt/STMicroelectronics/bin" Searching in

What is the Shock Detection to Interrupt latency of the HSLIS331DL 3-axis digital MEMS accelerometer?I have an application where I would like to configure the device for impact detection that would drive an interrupt when sensed. I am trying to determine what the time is from when the Acceleration is sensed (based on the threshold) to when the Internal Interrupt (INT) is driven out on the pin.

What is the Impact Detection to Interrupt pin being driven latency of the HSLIS331DL 3-axis digital MEMS accelerometer?I have an application where I would like to configure the device for impact detection that would drive an interrupt when sensed. I am trying to determine what the time is from when the Acceleration is sensed (based on the threshold) to when the Internal Interrupt (INT) is driven out on the pin.

Hello,We have been working with the LIS3DH Accelerometer on an Android 11 based device. We have Integrated the corresponding Kernel drivers and the STM Android Sensor IIO HAL.As per our understanding our Android device should be able to read values from the accelerometer and rotate the screen accordingly, but this feature is not working as expected.When enabling the debug output of the Android WindowOrientationListener I saw that the code always returns a “proposedRotation=-1�? identifier, and when doing some research, I noted that this might be caused when the accelerometer has not been calibrated.I reviewed the STM Android Sensor IIO HAL, and I noted that there is a calibration_daemon which depends on a calibration tool.Could you please explain me if this calibration tool is an external APK? And provide information about how could I enable and run the calibration_daemon?Any guidance will be highly appreciated,Thanks, and best regards,Esteban V.

Hi,I'm having trouble following how to properly setup free fall detection on the LIS2DH12. I'd like to generate an interrupt when the device goes from rest to free falling for a couple feet. The duration of the fall would be approximately 200ms. I'm a bit confused by how the combination of the INT1_CFG, INT1_THS and INT1_DURATION registers affect free-fall detection. Some questions:INT1_CFG - what are the differences in high vs low interrupt enabling? If low is enabled, does it wait for the  current reading to drop below INT1_THS threshold value for INT1_DURATION? Conversely if high is enabled, does it wait for the current reading to rise above INT1_THS threshold value for INT1_DURATION?A free-fall algorithm would typically detect three states, (1) Resting (+/- 1g on one or more axis, depending on how the chip is oriented) to initial acceleration (+/- N acceleration increase on the axis, or axes, of fall direction), (2) Initial acceleration to free fall (acceleration on axis

Hello. I'm a newbie to stm32 or actually to everything.I am using VL53L0X sensor and STM32F030C8T6 MCU in stm32idecube.What I want to do is to get a good reading of the sensor data.And I want to use a timer interrupt to read the sensor data every certain period and I don't want to read any weird sensor data.So I used someone's code to read the sensor data using the VL53L0X api to check the sensor data.But this code doesn't use timer interrupt, so I modified it to set a timer and use VL53L0X_PerformSingleRangingMeasurement function in HAL_TIM_PeriodElapsedCallback function to read sensor data.This modification didn't work, so I put the VL53L0X_PerformSingleRangingMeasurement function in a while() in the main function, and the sensor data was read in just fine.Why did I not get the sensor data when I used the function that reads the sensor data from the timer interrupt, but I got the sensor data in while()? Is it possible that this sensor should not be used with a timer?(For reference, I

Hello.I have a small fan at home with STEVAL-MKI245A attached and STEVAL-MKI109V3 is near the fan as well,like you would using PROTEUS1.The fan offers 3 mechanical switches to modify the speed.Using the switches causes a stop of reading data from the sensor in MEMS Studio.I tried Linux, Windows and MacOS with STEVAL-MKI109V3 (Firmware: 3.67.1) always with a notebook detached from a power source.Sometimes under "Sensor Evaluation / Data Monitor" the message "Log data view not active at high data rate" appears, regardless which scale setting or Output Data Rate is used.Many times the Accelerometer and Gyroscope Output Data Rates are set to "Power Down" automatically,respectively register CTRL_1 and CTRL_2 are set to 0x00 and I don't know who is doing this.In this case I'm not able to write different values than 0x00.The only solution is to reset the board.I'm worried to use it in industrial environment even if it's not stable at home. 

Hi, we are using ASM330LHB. How many times we can perform self test (in static condition) for ASM330 in its lifetime? Is there any limit OR can we perform self test unlimited times? If there is any limit please mention the count.Thanks in Advance,Pavani

Hello,both of MotionFX 6X and MotionDI return the same output (rotation vector, quaternion, gravity, and linear acceleration)so what is the difference between theme, and witch one is more suitable for 6 axes fusion ?should i implement additional calibration Lib ? like MotionAC and MotionGC ?Thank you,Sincerly. 

we are using this LSM6DSL sensor for our smart ring device. and we also implement step counter which is inside of this IC to calculate step for user, while he wears the smart ring on his finger.I'd like to know if there is any performance difference between watch and Ring in terms of step counter. Or I'd like to know if there is any case of Ring usage of this IC.

Hi,  I am looking at the LSM6DSO device, and I am unclear what the "USR_OFF_ON_WU" bit does in the "WAKE_UP_THS " register. Does this bit: Drive the Wake-Up function with offset corrected accelerometer data? 0 means not offset corrected, 1 means offset corrected?What does this have to do with High-Pass Filtered Data? Does this bit actually set whether Lowpass or Highpass information is used to drive the Wakeup Function?  Can someone please provide clarity? thanks

Hi,    I'm looking through the LSM6DSO32X datasheet, and I'm having a hard time finding out information about certain register data bits. For instance, register "WAKE_UP_THS" (0x5b) has 6 bits labelled "WK_THS[5:0]". Are these bit signed or unsigned? I assume they are unsigned, but I would appreciate confirmation.  thanks 

In the 53L5A1 Board Support Package (BSP) for the VL53L5A1 Multi-Sensor Ranging module, setting the target order (e.g., VL53L5CX_TARGET_ORDER_STRONGEST or VL53L5CX_TARGET_ORDER_CLOSEST) doesn't seem to be directly exposed through the existing BSP functions.The vl53l5cx_set_target_order() function in the vl53l5cx_api.h (from the VL53L5CX API) uses a different configuration structure (VL53L5CX_Configuration) compared to the structure used in the 53L5A1 BSP.Is there any guidance, documentation, or example code available on how to create a wrapper function to bridge these APIs and control the target order and detection thresholds for each individual ToF sensor within the multi-sensor ranging module?

Dear all,I'm working on a product where we use 850 nm LEDs with a typical spectrum like shown below:Since we emit quite some light (10's of Watts in short, ms bursts) with our device in a narrow cone (about the same FOV as the ST sensors), I'm wondering if this could potentially cause interference when reading the distance values. I remember seeing some picture that showed the acceptance window of the incoming sensor but I can't find it any more. Thanks for your help in this, Best, Tom

My team is looking at what performance data ST has on file for the ASM330LHB. Specifically ​random walk and bias stability performance of accelerometers and gyros over the entire operating temperature range (-40C to 105C).

good morning. i am actually trying to load on my an sd card my data of the sensor tile.box. Unfortunately, I only get blank tables with only the top written. I uploaded a configuration to make it and then uploaded as seen on those photos. am I missing anything?i have also a question on those parts of the application, I do not know what they are made for and they are only in this program:  

I am trying to use VL53l8cx with STM32F407VGT6 to find depth . I have previously worked with VL53l5cx and VL53l1cx  and was comfortab;e with both of these .  I am unable to use this sensor at all as everytime a hard fault arises . I have been able to use it on Arduino but wasnt able to use it with any st controller or dev board.  The link to the projects is below: https://drive.google.com/drive/folders/1tsidyGcB8i_SaHW2IKRrtKeJuAWvVb6X?usp=drive_link https://drive.google.com/drive/folders/17VWmdfnXCuZRXwIgr5QM44ov2SjAzd09?usp=drive_link This is where the hardfault occurs : 

Hello,I need help with the STEVAL-MKI223V1K and STEVAL-MKI109V3.I get a message from the Software MEMS Studio: The sensor has not been recognizedThe WHO_AM_register value does not match the device selected.Any help will be appreciated.Thanks. 

WE have got the Library from ST for nordic Cortex M33 Processor after signing the agreement, and tried to use it for the integration: Sensors used are LSM6DSOX and LIS2MDL.the NCS zephyr uses -mfloat-abi=hardOn using the Library The MotionFX_CM33F_wc32_ot_hard.a It gets  compiled but in debug it gives error when the deice connects the Bluetooth."MFX empty_attitude   file motionFX.c"What may be the issue here? RegardsVivek 

Hi,i know that there are already a few posts on this topic, and i know the VL53L8CX has the same table as the VL53L5CX. But i just wanted to know, if anyboy could post the calculations for the LookUp-Table?Thanks!

Are the SATEL-VL53L4CD breakout boards pre-soldered, which can be connected using female jumper wires?

HelloI need to trigger an action whenever a small object (aprox 1 cm diameter) is at a fixed distance (around 10 cm) of the sensor.Using VL53L0X the readings I get are very much affected by the background, for example if the object is in range and the background (1 m behind) changes from dark to white, the reading  changes to indicates a much larger distance.What can be done to improve this behavior? Absolute accuracy is not important, but repeteability is.

Dear Sir or Madam,what is the absolute minimum measurement distance of VD55H1 3D iToF sensor die?Could you provide a (detailed) datasheet and application notes? Currently, there is only a data brief. Best regardsLukas Bath

Hi,  I was reading @John E KVAM excellent post on Time of flight sensor glass:https://community.st.com/t5/mems-and-sensors/time-of-flight-cover-glass/ta-p/49259and this documentationhttps://www.st.com/content/ccc/resource/technical/document/application_note/group0/9d/93/be/33/13/be/46/19/DM00326504/files/DM00326504.pdf/jcr:content/translations/en.DM00326504.pdf And was just wondering, how important is the IR coating:Our application will have a large sheet of glass, shared by a display (see image for reference) And it would be cost prohibitive to IR coat the whole glass. For reference the glass will be ~ 1.1 mm thick. Is this likely to cause problems?