MEMS and sensors

Hi,I am follow up on the query i am posted "https://community.st.com/t5/mems-sensors/integrating-the-sths34pf80-proximity-mems-sensor-using-the/td-p/823236".I am integrating the STHS34PF80 proximity MEMS sensor using the STMicroelectronics HAL from the following repository:https://github.com/STMicroelectronics/st-mems-android-linux-sensors-hal/tree/masterHowever, when I run the HAL binary, I encounter the following error:"root@imx8mp-lpddr4-evk:/st-mems-android-linux-sensors-hal/linux/build# ./stm-sensors-linuxfailed to open config file [/etc/stm-sensors-hal/config], using defaultsfound 5 IIO devices available under /sys/bus/iio/devicessths34pf80_tmotion: IIO device not supported by sensorHALsths34pf80_tobject_comp: IIO device not supported by sensorHALsths34pf80_tpresence: IIO device not supported by sensorHALsths34pf80_tambshock: IIO device not supported by sensorHALsths34pf80_tobjamb: IIO device not supported by sensorHALNo IIO sensors found!no sensors available!"As you me

Hi,I am integrating the STHS34PF80 proximity MEMS sensor using the STMicroelectronics HAL from the following repository:https://github.com/STMicroelectronics/st-mems-android-linux-sensors-hal/tree/masterHowever, when I run the HAL binary, I encounter the following error:"root@imx8mp-lpddr4-evk:/st-mems-android-linux-sensors-hal/linux/build# ./stm-sensors-linuxfailed to open config file [/etc/stm-sensors-hal/config], using defaultsfound 5 IIO devices available under /sys/bus/iio/devicessths34pf80_tmotion: IIO device not supported by sensorHALsths34pf80_tobject_comp: IIO device not supported by sensorHALsths34pf80_tpresence: IIO device not supported by sensorHALsths34pf80_tambshock: IIO device not supported by sensorHALsths34pf80_tobjamb: IIO device not supported by sensorHALNo IIO sensors found!no sensors available!"Could you please guide me on how to add support for the sths34pf80 sensor in the ST HAL or help me resolve this issue?Thank you.

Hi, I am using LSM6DSO as my I3C sensor. It works well with RSTDAA and ENTAA. But when I tried to get its PID using GETPID ccc command, it does not work.CCC commands: RSTDAA (CCC: 0x06): Previous assigned dynamic address is removed.ENTDAA (CCC: 0x07): 0x02 0x08 0x00 0x6C 0x10 0x1B 0x07 0x44 (matches the PID, BCR and DCR in the datasheet)GETPID (CCC: 0x8D): 0x03 0xFF 0xFF 0xFF 0xFF 0xFF or just 0x02GETBCR (CCC:0x8E): 0x07GETDCR (CCC:0x8F): 0x7FHere is how I connect LSM6DSO to my I3C host:I tried I2C communication (removing the INT1 connection and leave it unconnected) and I am able to query WHO_AM_I (0x0F) register using address 0x6B and get back 0x6C.Any idea why I3C is not working properly? Thanks.

Hi,  I'm struggling to monitor the debugging values on the MEMS studio. setup1. MEMS studio 2.1.1 (latest version)2. Sensor PRO Tile Box + STEVAL-MKI229A(LSM6DSO16IS)3. ST Official ispu-example GitHub, normhttps://github.com/STMicroelectronics/ispu-examples/blob/master/ism330is_lsm6dso16is/norm/output/norm.json4. ispu-examples/ism330is_lsm6dso16is/norm/output/norm.json    loading this json to the board through MEMS studio5. I can see the entire blank on the "Data Monitor" Page with checked "ISPU Output".6. Toggle the "ISPU Output" to the un-checked state, everything can back to the normal.  

I was trying to implement VL53L1 TOF sensor on VL53L1-SATEL breakout board with STM Nucleo C071RB development board using STSW IMG009 VL53L1X Ultra Lite Driver.By following the example after init, boot, setup and startRanging I called VL53L1X_CheckForDataReady(), which always returned error -13 - VL53L1_ERROR_CONTROL_INTERFACE . After extensive checking of I2C interface I figured out that this error occurs when VL53L1X_GetInterruptPolarity() is called (within checkForDataReady or independently) when ranging is active. If ranging is stopped, GetInterruptPolarity() works just fine.My solution was to write my own library of required functions that further rely on VL53L1X_api. Before start ranging, I read the Interrupt Polarity, store it locally and then use modified checkForDataReady() function, which uses stored InterruptPolarity to check if new data is available.Has anyone else noticed such behaviour?This also connects to topics:https://community.st.com/t5/

I'm new to the STEVAL-DRONE2 kit and would like to ask: Given that the STEVAL-FCU001V2 flight control unit includes basic sensors like the IMU and barometer, can it support the integration of additional external sensors, such as GPS modules, magnetometers, optical flow, LiDAR, or ultrasonic sensors, through STM32? And are there any specific hardware or firmware considerations I should be aware of when adding these to the system?

Hi, I am having trouble with the interrupt. I manange to coummunicate via I2C and read Model ID and Type. But my problem is that i can't initiate the sensor via the VL53L1X_SensorInit() function in the Ultra Lite Driver I'm using. When I debug I see that the program gets stuck in the wait for new data from the sensor in VL53L1X_CheckForDataReady(). In this function the polarity of the interrupt is read as 0x00 and the GPIO__TIO_HV_STATUS as 0x03. Bit 0 in GPIO__TIO_HV_STATUS and the interrupt polarity must be equal for the program to interpret this as data is ready (i.e. a measurement has been made and can be read). A strange thing is that the interrupt polarity is 0x00 (active low) by default even if the manual says active high. And if I try to set the polarity to active high using the dedicated function it will still be active low. If I plug in a logic analyzer I can see that the GPIO1 (Interrupt output) from the sensor is high all the time. I then tested the sensor wi

Hello wonderfull STM community,Really enjoying the experience with MotionFX so far, really easy to implement and get working, well done ST! Even on a G0 in CM0+ mode its working well! I'm just woudring three things:What precaution(s), if any, should be taken when pausing and later resuming the RTOS task that runs MotionFX_CM0P_update()?What is the refrence point for the quatenion in 6x mode? (to be fair I have not worked much with quatenions before so that might be an uneducated question. They are quite complex after all! (pun intended)) Is it normal for data_out.rotation_6x to be near 0 (e-16) during oppration in 6 axis mode? (other values, inlcuding inputs, are changing as expected)  Note that mag is just uninitialized, the values are those of what was already in memory, I should fix that, through this is the first I've noticed it.Thanks and happy coding! 

Hi,Like the post https://community.st.com/t5/mems-sensors/anyone-have-v1-3-1-mems-studio-for-download/m-p/745081 , I search the older version v.1.4.2 of MEMS-STUDIO for documenting my project. Does anyone have the installers of this version ?Thanks,lxaiia  

Hello Developers, Hello ST-Team,unfortunately we are stuck in implementing VL53L5CX on our PIC18. We see a strange clock stretching behaviour of the sensor and problem downloading the firmware.We implemented Ultra Lite Driver 2.0.0 in an application on a Microchip PIC18F57Q43 (CURIOSITY NANO Evaluation Kit) using Example_1_ranging_basic.c from the examples folder.After the adjustments of platform.c and modification of the download routine to download the 86 KB firmware in chunks, we got the following odd behaviour:- The function  vl53l5cx_is_alive(&Dev, &isAlive); returns SUCCESS = No error!- The function vl53l5cx_init(&Dev); fails.Sending the first package of data seem to be successfull. When trying to start sending the second chunk of data the sensor refuses to communicate with the MCU by returning NACK for any further byte.Has anybody an idea why the sensor behaves like that and why the sensor stretches the clock line?Even while stretchin SCL for each byte

Hello, Is it possible to add the download links for the old versions of all your software's and resources, like it's the case on the web page of STM32CubeIDE ? In my case, I search to download the versions v1.4.1 and v.1.4.2 of MEMS-Studio for documenting my project. I asked to your support for this in the case 00239175 "How do I get an old version of MEMS-Studio ?", but your employee didn't find this. I think it is important to be able to get the older version of your resources for work on old projects and documenting the bugs and errors encountered. In my case, it's MEMS-Studio, but, in my feedback, I ask this for other of your resources which hasn't the same same system of the web page of STM32CubeIDE. Thanks for your time in the reading of my post. Best regards, lxaiia

Hi there!I'd like to use the STEVAL-CAM-M01 P-board to evaluate the VD55G0 BrightSense image sensor with the Discovery kit for the STM32N6 MCU (STM32N6570-DK). The discovery kit does have a camera connector, however, looking at the schematics it seems that the polarity of the CSI data and clock lines is swapped compared to the P-board. Everything else looks fine.Is it possible to use the P-Board with the Discovery kit without destroying either of the two? ST's marketing material (slide 33) seems to suggest it is possible but the schematics are unclear. Note that a similar question has been asked in the MCU forum, but it was suggested to ask in this forum to be sure. Also note that I'm not asking about software driver support here, only hardware compatibility.Camera connector on STM32N6 discovery kit: Connector on P-board:Thanks a lot!Michael

Dear all,I am using SensorTile.box STEVAL-MKSBOX1V1 with St app.I made application with vibrometer and output to USB.but the problem when I receive this data with Python code.there is byte misaligned in x,y,z because I started to receive data after streaming.Is there any solution or another firmware to control thisBest regards 

dear all, i want to recoed acceleration date from LSM6DSOX . i made app on st app and made output rate 6666 and output stram to usb. the proplem is i use python to read date from port with serial but the bytes mismatch because the sensor starts streaming then code later and i cant control stream is there idea or solution.stream to sd isnt suitable becaues i nedd live date  best regards

We need ~50k 6-axis IMUs for an application that will experience > 2000dps yaw rate and highly dynamic motion. The spec sheets for the ISM330BX and LSM6DSV32X seem to not paint a complete picture regarding the angular zero-rate at different G_FS angular rate measurement range.We're looking for an ST engineer to make a recommendation for the highest-quality IMU with respect to angular drift and accuracy while in highly dynamic motion. We are interested in IMUs with on-board sensor fusion. Other questions:The ISM330BX seems to be better than the ISM330DHCX in several dimensions, but appears to use a different accelerometer that is not strictly better than what is found in the ISM330DHCX. Is this correct?Is there an IMU that can be classified as "strictly the best" IMU under highly dynamic motion & vibration for mobile vehicle and robotics applications?

Hi, I'm currently facing a challenge with the VD55G1 driver. I've designed my own minimal system board for the N6 and VD55G1, using MIPI CSI for communication. When attempting to drive the VD55G1, I can enter the stream mode but no data is being transmitted (the N6 interrupt is not triggered). Upon reading the stream_fsm register of the VD55G1, I noticed it remains stuck in the dark task, with the REPEAT_COUNT, CURRENT_CONTEXT, and NEXT_CONTEXT values consistently showing 0 0 1.Here is my codetestfsm means getting the value of the stream_fsm register.I would greatly appreciate your prompt assistance in resolving this issue. Thank you.

 We are currently working on integrating the LSM6DSV16X (IMU) and IIS2MDC (Magnetometer) sensors into our platform based on NXP’s i.MX8MM SoC running Android 10. As Android 10 uses the legacy HAL, we’ve followed the integration steps as per the README documentation.Below are the key configurations and issues we are encountering:Platform & Sensor InfoAndroid Version: 10 (AOSP)SoC: NXP i.MX8MMSensor Drivers: LSM6DSV16X and IIS2MDCHAL Version: 1.0 (Legacy)What We've DoneIntegrated device nodes into DTS as follows: dtsCopyEditiistmdc_magn@1e {compatible = "st,iis2mdc_magn";reg = <0x1e>;pictrl-names = "default";pinctrl-0 = <&pinctrl_st_magno>;interrupt-parent = <&gpio1>;interrupts = <14 IRQ_TYPE_EDGE_FALLING>;st,module_id = <1>;status = "okay"; };lsm6dsvx-imu@6b {compatible = "st,lsm6dsv16x";reg = <0x6b>;pictrl-names = "default";pinctrl-0 = <&pinctrl_st_acc_gyro_yo>;interrupt-parent = <&gpio1>;interrupts = <15

Hello everyone,I'm currently in the process of integrating the ISM330BX IMU to a sensor i'm developping.So far, I have been able to implement this component to my design, communicate with it and read acceleration/gyroscope data.However, the reason that made me choose this component was for its embedded sensor fusion capabilites... And this is where problems start.Enabling the sensor fusion was a pretty straighforward process thanks to the ISM330BX's documentation and examples on Github. But i find the rotations it gives very strange.I noticed a huge amount of drift on the pitch and roll axes (i didn't expect the yaw to be robust and stable without the addition of a magnetometer, which is planned). It also often take way more than the state 0.7 seconds to stabilize its rotation.Currently, my configuration is as follow :- Accelerometer and Gyroscope ODR at 480Hz- Accelerometer, Gyroscope and SFLP game vector (the rotation quaternion) ODR in FIFO at 30Hz- Accelerometer scale set at&n

We have procured STEVAL-MKI197V1 I3C device to validate I3C on the AMD platform, and we have found the slave driver support from the st website and below is the link shared for the same.https://github.com/STMicroelectronics/st-mems-android-linux-drivers-iio/tree/master When we connect the same device to the i2c controller it's getting the address as 6a but when we connect to i3c controller device is not even detectingwhen we checked the in the source code 6a address we couldn't find and tried by adding prints in the beginning of the st_lsm6dsox_i3c_probe function but didn't get the prints too can anyone help it on the issue.

I am using the kernel driver for accelerometer i need to find the accurate step count.Below are the reading for accelerometer from the driver from sysfs parameters and how can i find the step count,root@antler_xedge:/sys/bus/iio/devices/iio:device2#lscurrent_timestamp_clock dev events in_accel_scale in_accel_scale_available in_accel_x_raw in_accel_y_raw in_accel_z_raw mount_matrix name of_node power sampling_frequency sampling_frequency_available subsystem ueventroot@antler_xedge:/sys/bus/iio/devices/iio:device2#cat namelsm6dsl_accelroot@antler_xedge:/sys/bus/iio/devices/iio:device2#cat incat: in: No such file or directoryroot@antler_xedge:/sys/bus/iio/devices/iio:device2#cat in_accel_scale0.000598205root@antler_xedge:/sys/bus/iio/devices/iio:device2#cat in_accel_scale_available0.000598205 0.001196411 0.002392822 0.004785645root@antler_xedge:/sys/bus/iio/devices/iio:device2#cat in_accel_x_raw207root@antler_xedge:/sys/bus/iio/devices/iio:device2#cat in_accel_y_raw-16486root@antler_xedge

Dear All,We are using the IIS3DWB MEMS accelerometer in one of our products and have encountered an issue with a single unit that we would like your input on. Issue description:On this specific device, the X-axis always reports the maximum negative value (−32768 in 2’s complement), regardless of the selected full-scale range or output data rate. The Y and Z axes function correctly. The issue persists across power cycles and register resets and started after using it for 6-8 months. We have verified the following:• The offset registers are set to 0.• No filters or self-test modes are enabled.• The axis is properly enabled.• The unit was removed from its casing to exclude mechanical stress.• This appears to be a one-off issue; all other units from the same batch are functioning normally. We would appreciate your insights on what might cause this axis-specific saturation behavior and whether there are diagnostic procedures or failure analysis options you recommend. Kin

Hi,I saw in the datasheet of ISM330DLC that the sensitivity of accelerometer and gyrsocope can deviate at a maximum of 3%. What would be the typical deviation of the senitivity of accelerometer and gyroscope?Thank you!

Edit by ST Moderator: This post has been translated from Chinese to comply with the ST Community Terms and Conditions (§10.2). LSM303AGRTR  The chip is used to calibrate the orientation of the compass, but it is very easy to be interfered with and has the following two problems 1 Calibration is very difficult to calibrate, you need to shake the sensor many times 2. After calibration is done it is very susceptible to interference, resulting in inaccurate compass data Below is the circuit diagram, if you have a mature circuit please send me to see if there are other solutions to the problem.  

I am using the STSW-IMG501 software v1.1.1 with the STEVAL-EVK-U0I connected to a STEVAL-56G3MAI (the S-board evaluation module for the VD56G3).  In the EVK software, I am using the built-in script generation tool to upload different register configuration sets and test them.  However, I find that uploading the following script will cause the SW to fail to read a frame sequence:$SCRIPT SetBank(0x20); WriteAutoIncrement(0x0220, 0x00, 0x1b, 0xb7, 0x00); //SENSOR_SETTINGS.EXT_CLOCK = 12000000 WriteAutoIncrement(0x0224, 0x02); //SENSOR_SETTINGS.CLK_PLL_PREDIV = 2 WriteAutoIncrement(0x0226, 0x86); //SENSOR_SETTINGS.CLK_SYS_PLL_MULT = 134 WriteAutoIncrement(0x0227, 0x05); //SENSOR_SETTINGS.VT_CLK_DIV = 5 WriteAutoIncrement(0x0300, 0xd4, 0x04); //STREAM_STATICS.LINE_LENGTH = 1236 WriteAutoIncrement(0x0304, 0x00, 0x00); //STREAM_STATICS.X_START = 0 WriteAutoIncrement(0x0306, 0x63, 0x04); //STREAM_STATICS.X_END = 1124 WriteAutoIncrement(0x030a, 0x08); //STREAM_STATICS.FORMAT_CTRL

Tools/Software/etc:SensorTile.box PRO with DATALOG2_Release firmwareSTBLE Sensor app (to trigger data collection)hsdatalog_to_unico.pyMEMS Studio v1.4.1Ubuntu Linux 24.04I watched a handful of webinars and read through tutorials related to the LSM6DSV16X's machine learning core. Most of these covered the basics, but only the basics (as in, they only show the most barebones demonstration with a single sample of a single simple movement). When attempting to generate a decision tree on my own using custom data, I ran into several problems.First, I collected 4 samples of a basic jab motion and labeled the data "strike" and "retract" for each. Everything worked up to the point where I generated the decision tree and got a confidence value of 0%. Then, I attempted to simplify the data and only use one sample of one movement (just the strike component). At this point, I began to see the error below when running the AFS tool. I collected new samples, this time a simpler and slower bicep c