MEMS and sensors

Hello,Could you provide the bias instability of ISM330DLC and LSM6DSV I could not find them in their datasheet ?Thank you by advance for your help

In the datasheet at page 13, the sensitivity is of 2096 LSB/hPa instead of 2048.

The measurement data of LIS2MDL was read in the application. Both the Y and Z axes were normal, and their data changed with the position. However, the data of the X axis was abnormal, and its value was the same as TEMP_OUT. Moreover, it was not related to the position. As shown in the screenshot below.                                 Chip settings: CFG_REG_A = 0X80Dear friends, could you please help me figure out what the problem is? Thank you!

Hello Community,I am currently developing a medical device and am utilizing the LSM6DSOX IMU sensor for user activity tracking. My goal is to implement functionality that can accurately track activities such as running, walking, and being steady.To achieve this, I’ve started by working with the MLC (Machine Learning Core) example provided in the ST GitHub repository. However, despite my efforts, we are not getting any output from the implementation.Could anyone provide guidance or suggestions on the following:Steps for implementing user activity tracking with the LSM6DSOX IMU sensor, specifically for activities like running, walking, and being steady.Common pitfalls or challenges that might cause issues like not getting output.Any best practices or recommendations for improving activity classification accuracy.I’d appreciate any advice or tips to help move forward with this project. Looking forward to your suggestions!  

Hardware environment: STM32F405 chip and VL53L5CX-SATEL module;Software environment: Based on the STSW-IMG023 sample code, the code is ported to KEIL5 for use;Problem description: After completing the sensor initialization (ranging frequency 10hz, ranging continuous mode), use polling to read data, call the vl53l5cx_check_data_ready function to read the sensor data: 0x00, 0x03, 0x01, 0x0D, these four values ​​are considered data not ready after judgment.I want to know what these four values ​​mean? I checked the documents I know (DS13754, um2884, etc.) and did not find the relevant register description.Why does this happen, and how should I debug?Thank you!

I am using the VL53L4CD sensor with a nucleo board by using the API provided by ST.By using the xshut pin and the API, I can change the device address.But as soon as I shut down the power or reset the sensor through xshut, its address comes back to the default one.Am I doing something wrong?If not, is there any way to save the new address in non-volatile way?   

Hello, it's code correct for  testing WHO_I_AM? LED doesn't work  #define LIS3DH_CS_LOW() HAL_GPIO_WritePin(GPIOE, GPIO_PIN_3, GPIO_PIN_RESET) #define LIS3DH_CS_HIGH() HAL_GPIO_WritePin(GPIOE, GPIO_PIN_3, GPIO_PIN_SET) #define LIS3DH_WHO_AM_I_REG 0x0F #define LIS3DH_READ_CMD 0x80 uint8_t LIS3DH_ReadWhoAmI(void) { uint8_t txData = LIS3DH_WHO_AM_I_REG | LIS3DH_READ_CMD; uint8_t rxData = 0; LIS3DH_CS_LOW(); HAL_SPI_Transmit(&hspi1, &txData, 1, HAL_MAX_DELAY); HAL_SPI_Receive(&hspi1, &rxData, 2, HAL_MAX_DELAY); LIS3DH_CS_HIGH(); if (rxData == 0x33) { HAL_GPIO_WritePin(GPIOD, GPIO_PIN_12, GPIO_PIN_SET); } return rxData; }  

Hello,I use the STEVAL-MKI209V1K with the IIS2ILCX sensor. I am trying to get the IIS2ILCX communicating with a second IIS2ILCX via sensor hub. The master sensor is connected to my MCU via SPI. Please find my „schematic“ and the configuration code below.My problem is, that I cannot observe any I2C communication between the sensors. My oscilloscope just shows 3.4 V for each SCL and SDA. What could be wrong?I would greatly appreciate any suggestions. Additional information: i want to read the slaves data triggered by DRDY-Interrupt to get synchronized data of both sensors.accelerometer_write_register(accel, ACCEL_IIS2ILCX_REG_ADDR_FUNC_CFG_ACCESS, 0x00); accelerometer_write_register(accel, ACCEL_IIS2ILCX_REG_ADDR_FIFO_CTRL1, 0x7F); accelerometer_write_register(accel, ACCEL_IIS2ILCX_REG_ADDR_FIFO_CTRL2, 0x00); accelerometer_write_register(accel, ACCEL_IIS2ILCX_REG_ADDR_FIFO_CTRL3, 0x07); accelerometer_write_register(accel, ACCEL_IIS2ILCX_REG_ADDR_FIFO_CTRL4, 0x01); accelerometer_writ

I need to implement the  clock wise motion using the sensor like LIS3DH accelerometer with i2c protocol. Using NUCLEO-L031K6 Board. I don't know how to implement . If you have any reference. Please share it.    Thank you.

Hi,I see the following markings on IIS2DLPC.1) Dot - to identify the correct orientation of sensor2) 2D code - could be for traceability3 a letter "T"What does this letter "T" mean?Thank you!

Hi, I am using the VD66GY image sensor on the STEVAL-56G3MAI board. It is connected to an Allwinner S3 with an ISP. This is my v4l2 pipeline:media-ctl --set-v4l2 '"vd56g3 0-0010":0[fmt:SGRBG10_1X10/1120x1360]' media-ctl --set-v4l2 '"sun6i-mipi-csi2":0[fmt:SGRBG10_1X10/1120x1360]' media-ctl --set-v4l2 '"sun6i-csi-bridge":0[fmt:SGRBG10_1X10/1120x1360]' media-ctl --set-v4l2 '"sun6i-isp-proc":0[fmt:SGRBG10_1X10/1120x1360]' v4l2-ctl -d /dev/video1 --set-fmt-video=width=1120,height=1360,pixelformat=NV12 v4l2-ctl -d /dev/v4l-subdev3 -c vertical_blanking=2977 # set 30 Hz update rate The image I receive is too green. When I use the colorbar test pattern (v4l2-ctl -d /dev/v4l-subdev3 -c test_pattern=2) I see all colors correctly indicating that the issue is not originating from the ISP. When I set horizontal or vertical flip, the image changes to pink, if both are active it is too green again. When I change the format to 480x640, which uses binning, the image is pink. W

Hi All,   I am working on a design that has been working for years. Now we wanted to design a revision of the PCB with the LSM6DS3TR but sadly it became obsolete and I can't find it back on the website of ST.Could the LSM6DS3TR-C be a Drop-In-Replacement for this part or another type? Thanks in advance & kind regards,

Hi guys!From the last week I am trying to connect my TOF sensor with the STM32, but the I2C Communication has not been started. I have tried to use I2C Scanner to scan the address of the   VL53L7CX SATEL breakout board but was not even able to gets its address back. I also tried changing the VL53L7CX SATEL breakout board but it was also not very useful.  I have tried using both the STM32 Cube Ide software package that they provide for the TOF Sensosrs and the STM32duino VL53L7CX Library but was unsuccessful in making them work.Can anyone let me know if I am making any mistakes or if my approach is wrong in any way!Thank you in advance!

I am having STEVAL-STWINKT1 to be interfaced on USB channel for ST MEMS PC application.I have flashed DATALOG2_Release.bin in eval kit.I can get the ST MEMS PC Application showing the vibration sensor analysis graph. See attached.However, the issue I am facing is when the ST Eval board is moved from the desk to up in the air (only 1 cm). The firmware is hung, and the USB connection is lost. Can you suggest what is wrong with the firwmare?Also, if possible, I would like to connect the kit BLE channel with the ST MEMS application but it does not connect even then on MEMS applicaiton. Can you suggest if I need to use a different firmware? Or something else?

Hello ST Team,I am curious to know how LSM6DSV32X Accelerometers sensor communication takes place.So, basically what I am trying to understand here is when Master assigns some dynamic address to LSM6DSV32X Accelerometers sensor, then where exactly the sensor stores it?Do we have any sensor register for the same? Thanks & regards,Sourav

Dear STMicroelectronics team,I would like to suggest including references in your documentation—such as datasheets, application notes, or user manuals—for the VL53L family of time-of-flight range sensors regarding the use of retroreflective surfaces as a technique to enhance signal return levels in feasible applications.In my experience across multiple VL53L-series devices, even small retroreflective tapes can greatly improve signal strength and extend the usable range, often surpassing performance obtained with standard Lambertian white targets. These retroreflectors significantly improve accuracy and reduce noise, especially at longer distances, where standard targets often yield weaker and noisier returns.Unfortunately, many users and reviewers are unaware of this option, possibly due to the current documentation emphasizing only white diffuse targets as the ideal case. This can lead to underestimating the sensor’s true potential and, in some cases, favoring less suitable alternativ

I'm having an issue with a breakout board housing a VL53L1X sensor where, between the breakout board and MCU, the only connections are power, gnd, sda and scl through a PCA9617ADPJ I2C buffer. I've set it up for continuous ranging at about 200ms timing budget and is usually accurate for my purpose of just detecting if something is within about 1-2 meters. I have my codes set up so if the sensor status returns 255 VL53L1_RANGESTATUS_NONE, the code will attempt to reinitialize the sensor for re-connection.  However, sometimes it will randomly enter this state when plugged in normally. While I'm still yet to figure out WHY it enters this state, my big issue is that once it reports VL53L1_RANGESTATUS_NONE and reinitializes, the ranging accuracy is hopelessly screwed up, where hovering a target about 4cm in front of the sensor reports a maxed out distance value of 8043mm, and linearly scales from there as an object gets closer. The absolute worst part about this is that a physical rese

Hi everyone,So I'm trying to get the VL53L8CX ToF lidar working in ZephyrRTOS running on a NRF9151 chip. I'm using the VL53L8CX ULD driver version 2.0.1. The VL53L8CX is connected to the NRF9151 using i2c with the address 0x52, however when I call the vl53l8cx_is_alive() function from the driver i only see the messages being sent over i2c and getting a NAK. The i2c setup itself is confirmed to be working given that other devices use the same bus and are working as intended (we have tested with just the VL53L8CX connected as well with no difference in behaviour). We are using a custom pcb and the lpn pin is connected to 1.8v IOVDD with a 47k resistor and the system is powered with 3v AVDD. The VL53L8CX relevant circuitry for our custom pcb looks like this:With pull-up resistors for the i2c lines.The vl53l8cx_is_alive() function is called right at the beginning of main, but we have tried to add a delay before calling to give the system time to get fully powered up without effect.As

I discovered a strange phenomenon:After I powered on the VL53L4CD, I called the interfaces:The interfaces such as VL53L4CD_SensorInit, VL53L4CD_SetRangeTiming, VL53L4CD_SetDetectionThresholds, and VL53L4CD_SetSignalThreshold complete the initialization operation.Then call the VL53L4CD_ClearInterrupt and VL53L4CD_StartRanging interfaces to start the measurement. At this time, interrupts can be received normally, and the interrupt pin can rise and fall normally.At this point, I call the VL53L4CD_StopRanging interface to stop the measurement. At this time, tthe interrupt pin is at a high level.At this point, I put the device aside without operating it for about two or three days.I recalled VL53L4CD_ClearInterrupt and VL53L4CD_StartRanging, and immediately received an interrupt. At this time, I called the VL53L4CD_GetResult and VL53L4CD_ClearInterrupt  interface to read the result and found that the value of range_status was 2.Subsequently, the interrupt pin remained at a low level. I

Hello everyone,I am currently working with the VL53L8CH sensor, and it's impressive what can be achieved with it. However, I would like to know if there is any way to reduce, modify, or adjust the sensor's field of view while maintaining its resolution (8x8).Then, in certain specific use cases, I would like to increase the resolution, though I believe 64 (8x8) is the maximum. If increasing the resolution isn't possible, is there perhaps another way to reduce the field of view to focus on a smaller area while preserving accuracy?

Hello ST team,I’m currently developing on the STEVAL-PROTEUS1 platform and encountered an issue when transitioning from the application firmware to the bootloader.Specifically, after executing a jump from the application to the bootloader (located at 0x08000000), the bootloader hangs during CPU2 initialization. It gets stuck at the following function call:SHCI_C2_BLE_Init(&ble_init_cmd_packet);This only occurs when jumping from the application. When powering on the board directly into the bootloader, everything works as expected, and BLE initialization succeeds.I have ensured that:CPU2 is not held in reset by the application before the jump.The jump procedure clears necessary registers (SCB->VTOR, stack pointer, etc.).Despite this, SHCI_C2_BLE_Init() does not return or proceed further.Has anyone experienced similar behavior on the STEVAL-PROTEUS1 or other STM32WB-based boards? Are there additional steps required to properly re-initialize CPU2 when switching from application to b

I use some VL53L3CX with Arduino (in C++) with PWFusion_VL53L3C.h library.In some situation I need to disable multi-target detection.How can I do this ?ANDWhere I can find a detailed documentation about VL53L3CX api ?ANDCan I use a different library on Arduino ?Thank youMax   

Good morning, I am programming a SensorTile using the STEVAL-STLKT01V1 expansion kit, and when I flash the program to the device, I encounter the following error:Break at address "0x8000270" with no debug information available, or outside of program code.

For a medical device that use NIR light we are using the VL53L4CX as range detector. We found that the TOF sensor light interfere with our NIR lighting system. In order to perform some simulations we would like to have some more details about the light irradiance from the sensor VCSEL. From datasheet we found only few data related to the wavelength. Is it possible to have some more detailed applicaiton notes and/or datasheet related to the VCSEL of the TOF. BR  

We found a problem with VL53L1CB, After VL53L1_GetMeasurementDataReady returns 0, VL53L1_GetMultiRangingData returns VL53L1_ERROR_ZONE_GPH_ID_CHECK_FAIL. What causes this problem?Thank anyone for a little help