MEMS and sensors

I have a device which uses an accelerometer (LIS2DH12) to trigger a wake up upon movement. Now I have a few samples on my hand, where this wake-up does not work. The design, configuration, interrupt, etc of the parts work (as validated by other identical builds). The parts in question, I can also bring back to "normal" operation, by turning VDD off and back on. After such a hard reboot, everything works as it should (this further confirms that the parts on hand do not have an electronic/manufacturing defect). Hence, I could in principle schedule a periodic reboot of the accelerometer, but this defeats the idea of a wake-up interrupt. Is the LIS2DH12 supposed to be rebooted on a regular interval? When the parts are in the "stuck" state, I can communicate (read/write from/to the registers) with the accelerometer. All values appear to be coherent (e.g. the WHO_AM_I, and the CTRL registers report back what I write to them). In other words, the electrical interface still works as

Hello STM32 community,I'm relatively new to STM32 development and I'm currently working with the I3G4250D Gyro Sensor on the STM32F411e-Discovery board. I've been using the stm32f411e_discovery_gyroscope.c file provided by STM32Cube to interface with the sensor.I've managed to retrieve data from the sensor using the provided code snippet:BSP_GYRO_GetXYZ(Buffer2); Xval = Buffer2[0]; Yval = Buffer2[1]; Zval = Buffer2[2]; However, the output I'm getting seems to be raw data, and I'm not quite sure how to interpret it correctly. My understanding is that these values represent the raw sensor readings, but I'm unsure how to convert them into meaningful X, Y, and Z values.Could someone please provide guidance on how to properly interpret and convert these raw values into meaningful data? Additionally, if there are any specific calibration steps or formulas that need to be applied to obtain accurate results, I would greatly appreciate any insights on that as well.Thank you in advance for

Hello,I’ve been reviewing the current consumption section (Section 7.4) of the VL53L8CH datasheet.I’m currently using the Detection Thresholds plugin, and I would like to ask:Which power mode does this correspond to?Continuous mode (Table 15)?Autonomous mode (Table 16)?When Detection Thresholds are enabled, what are the assumed internal ranging settings (e.g., frame rate or integration time)?Additionally, if we reduce the integration time to 1 ms, could you clarify:How much power savings can we expect?Would this affect detection reliability or ranging stability?Thank you for your support.

Hi, I am, working with LIS2DH12 and I want to detect some variations of Z axis.I don't need to detect accelerations just variations of its current positions over my threshold. My current configuration is the following. CTRL1 (0x20) -> 0x17CTRL2 (0x21) -> 0x00CTRL3 (0x22) -> 0x40CTRL4 (0x23) -> 0x00CTRL5 (0x24) -> 0x08CTRL6 (0x25) -> 0x00 INT1_CFG (0x30) -> 0x20INT1_THS (0x32) -> 0x30INT1_DUR (0x33) -> 0x3C   Other registers set as default. What I want is to detect Z axis variations in case it has changed its position from (typically around 60) to something around +-14. I want it only to trigger the interrupt if it keeps this way more than 60 seconds that is why I set an ODR of 1. The problem is that my accelerometer is waking up my MCU every 60 seconds even when it is flat on the table and nothing is touching it. In case I read the axis, it gives me 60 for Z. I think I have something wrong but I don't see what. Also, I just set ZH but no ZL. In case I ad

I’m trying to read the 3-component “game rotation” quaternion out of the LSM6DSV80X’s FIFO, but every time I pop a FIFO record I get three half-precision floats [x,y,z] where x is always zero and y,z look plausible. When I read the same fusion engine registers directly (not via FIFO), I get a full four-component quaternion [w,x,y,z] where x is nonzero—as expected. Ive connected the STEVAL-MKI247A to my ESP 32 via SPI with the following configuration // Define SPI pins #define CS_PIN 5 // Chip Select pin #define SCK_PIN 18 // SPI Clock pin #define INT_PIN 25 // Interrupt pin #define MOSI_PIN 23 // Master Out Slave In pin #define MISO_PIN 19 // Master In Slave Out pinWhat ive done: Enabled the SF-LP game rotation vector and timestamp in the embedded-function bank, thenConfigured FIFO streaming mode and set watermark = 1, andIn loop() I parse the data from the FIFO queue and immediately compare it with the raw register read. 1. How i enabled SF-LP FIFO batching:fifo_sf

How do you perform a soft reset on the VL53L4CD if XSHUT is not used?  I can't seem to find an example.  I see the VL53L4CD_ULP_SOFT_RESET or VL53L4CD_SOFT_RESET is defined, but I don't know what to write to it.Also, how do you shut the sensor down without XSHUT, is telling it to StopRanging enough?Thanks.

Hello, I have a SensorTile.Box and I am playing with the "Expert View" mode on the ST BLE Sensor Classic app. I have created a useful custom application, which combines the output of different sensors on the board and transmits them over USB. When I save this application, a json file is created into the smartphone file system. I want to share this application with another user, but when I send her the file and she puts the file into the "Files->Internal Memory->Documents->SensorTile.box folder", she is not able to see any new app in the ST BLE Sensor Classic app. The only applications that can be seen on a device are the ones created on the same device. Is there any way to enable the share of the application profiles between different devices? Thanks, Francesco

Hi I'm working with the ISM330DHCXTR sensor and would like to know how long I should wait after applying power before the device is fully operational and ready to communicate (e.g., via I²C) Thanks Uri

Hi Team, We are using ASM330LHH IMU in our project. want to know if there are any special guidelines for placement of IMU on PCB. please let me know.   Regards, Jitendra

I'm using the LSM303AGR magnetometer with an STM32L4 via I2C + HAL. The built-in self-test works fine for X and Y, but Z-axis always fails — the delta (self-test vs. normal) is out of range.   Set UpSTM32L4, I2C, HAL driversMagnetometer config: 50 Hz, continuous modeSelf-test enabled via CFG_REG_C_M (0x62) = 0x1250 samples averaged before/after self-testDelays: 200ms (pre), 500ms (post self-test)     ProblemX/Y deltas: within 100–1000 LSB range → passZ delta: often too low or too high → fail    QuestionAre 100–1000 LSB valid self-test limits for Z?Is 500ms delay enough after enabling self-test?Do I need to read output registers in burst mode for sync?Any known Z-axis issues in continuous mode?Any advice or working examples appreciated!

Hi,I'm trying to get the SPI interface with the ISM330DHCX to work but it seems that the SDO pin can't reach logic high levels.The above has SCL in blue and SDO in red.CS in blue and SDO in red.SCL in blue and SDI in red.Above is my hardware setup, vdd and vddio is hooked up to 3.3V on the Nucleo.I've been able to get this to work with I2C but haven't with SPI. Any help or advice would be appreciated

Hi everyone,I'm currently developing firmware for the VL53L1X Time-of-Flight sensor on a breakout board using STM32CubeIDE, and I’m working with the bare driver provided by ST (not the ULD). I’d like to implement the complete calibration sequence, but I’m unsure about the correct procedure and how to manage the physical steps during calibration.Based on the documentation, the recommended calibration order is:RefSPAD CalibrationCrosstalk CalibrationOffset CalibrationI have a few questions regarding the practical and programmatic steps for performing these calibrations using the bare driver functions:1. RefSPAD CalibrationShould this be performed with no target in the Field of View?What environmental conditions are ideal — e.g., should the sensor be facing open space, a dark surface, or something else?2. Crosstalk CalibrationI understand that a grey target should be placed at about 600 mm from the sensor for Full ROI crosstalk calibration.How should I structure the calibration code to pa

Hello everyone, i'm trying to use the vd66gy with the raspbeery Pi x64 connected on cam0 and im following all the steps of the "Linux Start Guide for ST BrightSense" but it still doesnt work. I downloaded the drivers for the camera as well as the libcam st version from this link: https://www.st.com/en/embedded-software/stsw-img503.html?dl=redirect. However i see that even for the vd66gy driver, the en.vd66gy_1.0.3.zip has all the vd56g3 files and the makefile looks like this: ifneq ($(KERNELRELEASE),) include Kbuild else KVERSION ?= `uname -r` KDIR ?= /lib/modules/${KVERSION}/build default: CONFIG_DRIVER_VD56G3=m $(MAKE) -C $(KDIR) M=$$PWD clean: CONFIG_DRIVER_VD56G3=m $(MAKE) -C $(KDIR) M=$$PWD clean endifIs this a mistake? It looks like the vd56g3 driver. You can confirm by downloading the driver from the link. As a result when i complete all the steps and launch rpicam-hello i get this: rpicam-hello [0:30:33.792539716] [3479] INFO Camera camera_manager.cpp:327 l

Hi,I want to know the exposure time of VL53L5CX per frame.I also want to know that it is possible to configure the exposure time?Best,Jsc.

I wish to connect the P-board, which has a 22-pin connector, to a Raspberry Pi that has a 15-pin camera connector (From the Raspberry Pi 1/2/3/4 series, not the 5). The datasheet for the P-board only gives a vague suggestion. Is there a specific cable that has been known to work?

Hi John, Could please confirm if the slew rate requirement of VL53L8CX is satisfied in the EVM X-NUCLEO-53L8A1?  We're considering to use TI's TLV751180330PDSQR to power up the VL53L8CX sensor. But the TLV751180330PDSQR supports 11mV/µS approx. Also, there is no graph where we can infer the O/P slew for the LDK130M33RY or LDK130M18R. 

Hello ! I am calibrating a VL53L4CD ToF sensor. Is it suggested to set a large timing budget (e.g. 200 ms) for the offset and crosstalk calibrations' distance measurement process? In the distance measurement examples, the timing budget is set to 10 ms for 'fast mode' and 200 ms for 'high accuracy mode'. If the sensor will ultimately be operating in both 'fast' and 'high accuracy' modes, is it better to perform the initial offset and crosstalk calibrations in 'high accuracy mode'? Thanks!  Brian

Hi,i've been posting here a few times to get a VL53L4CX to work. I've had success so far, but the latest iteration of my little PCB is really giving me troubles.When i apply power to my board (via an esp board) it stops working (the esp32 board). It feels like i've created a short, but i can't seem to measure that on the board.I do solder this myself, so there could be a short under the sensor itself (i just use a heat gun from the bottom after tinning the pads). I've done this a few times now and i'm quite sure it's not the case... so there must be an issue with my board layout/design.It would be great if somebody could review this for me?http://cyclops.nettrends.nl/stuff/tofboard.tar.gz

 Hello STM32 Community,I'm working with the LSM303AGR magnetometer/accelerometer sensor on an STM32L4 microcontroller. I'm trying to compute a tilt-compensated heading, based on the method described in ST's application note DT0058.However, I'm running into a problem: the heading value changes significantly when the sensor is tilted, even when the actual orientation toward magnetic north doesn't change. I expect the heading to stay consistent regardless of tilt, thanks to tilt compensation — but this is not happening.Below is the code I'm currently using to compute the heading:  uint8_t lsm303agr_heading_read(float* heading) {float magx_out, magy_out, magz_out;float accx_out, accy_out, accz_out;// Read sensor dataif (lsm303agr_acc_data_read(&accx_out, &accy_out, &accz_out, 10) != 0)return 1;if (lsm303agr_m_data_read(&magx_out, &magy_out, &magz_out, 10) != 0)return 1;// Normalize accelerometer readingsfloat acc_norm = sqrt(accx_out * accx_out + accy

Hi all,I need to integrate the driver for the iis2mdc magnetometer (Github: https://github.com/STMicroelectronics/stm32-iis2mdc/tree/main) into my own project for a custom board (with STM32H7A3 and i2c3).  The code from the driver requires an additional hardware driver so that the magnetometer can be read/written to. However this interface functions are not included in the driver on Github. int32_t __weak iis2mdc_read_reg( ...) and int32_t __weak iis2mdc_write_reg(stmdev_ctx_t *ctx, uint8_t reg,uint8_t *data,uint16_t len){int32_t ret;ret = ctx->write_reg(ctx->handle, reg, data, len);return ret;} Is there any sample code available, which can be simply adjusted for the specific i2c interface? or do I simply have to replace the call:ret = ctx->write_reg(ctx->handle, reg, data, len);    by  the corresponding    HAL_i2c... calls? Many thanks for any hints.BR GS    

I am guessing there is nothing that can be done about this, but I thought I'd post about it. I got the VL53L8CH because it has better bin resolution than the VL53L3CX, which I hoped to use to distinguish between objects at different ranges that are closer to one another. It is somewhat better at that, but not as much as I had hoped. The reason for this is the signal spread. The emitter's signal arrives as a peak that spreads over about 10 bins. At 3.75 cm per bin, that means a signal spreads over 37.5 cm. It's not actually as bad as that, since the signal follows a normal distribution, but it does mean that signals for objects close to one another will overlap and distinguishing objects separated by only one to three bin widths is quite difficult.Don't get me wrong, this chip is amazing, and the people at STMicroelectronics have done wonders in giving us 3.75 cm bin resolution when the signal is traveling at the speed of light. It just may be important for the applications of some peop

We've implemented an example program based on UM2220 using an lsm6dsox IMU sensor on an STM32U575 microcontroller. We're trying to use MotionFX for orientation calculation from 6 axis measurement, configured with accelerometer and gyro. The IMU sensor is configured to sample at 12.5Hz. Pitch and roll are extracted and printed to a terminalWhat we're seeing is that the output data is stable for a short period of time, however after an indeterminate period of time, pitch and roll become corrupted, spewing (seemingly) random data outWe'd really appreciate any assistance on why this may be happening! We've already tried doubling the stack size of the thread, with no luck

Hello STM32 community,I'm relatively new to STM32 development and I'm currently working with the I3G4250D Gyro Sensor on the STM32F411e-Discovery board. I've been using the stm32f411e_discovery_gyroscope.c file (BSP Drivers) provided by STM32Cube to interface with the sensor.I've managed to retrieve data from the sensor using the provided code snippet:BSP_GYRO_GetXYZ(gyro_data); X_val = gyro_data[0]; Y_val = gyro_data[1]; Z_val = gyro_data[2]; However, whenever I observe the output, the values keep varying even if the system is at rest. Also the output I'm getting seems to be raw data, and I'm not quite sure how to interpret it correctly. My understanding is that these values represent the raw sensor readings, but I'm unsure how to convert them into meaningful X, Y, and Z values.Could someone please provide guidance on how to properly interpret and convert these raw values into meaningful data? Additionally, if there are any specific calibration steps or formulas that need to be

Hi,I have a i3g4250d sensor chip on our custom board with STM32G474 MCU.I have used the below driver github.com STMicroelectronics stm32-i3g4250dfor reading the sensor chip registers through SPI interfaceI am able to read "WHO_AM_I_ADDR" register without any issue that confirms my SPI interface is fine and communicating with sensor chip but when I read XYZ values I always get the same value irrespective of sensor position.My sensor init configurations areCTRL_REG1 = 0x3FCTRL_REG4 = 0x10When I read the STATUS_REG, the first read shows 0xFF and consecutive reads always shows 0x00What could be the problem.PS: I have a Accelero meter sensor chip lsm303agr on the same board configured with I2C interface which is working properly.Thank YouPrabhu M K

Hello everyone, I am currently working with the VL53L8CX sensor to explore solutions for a specific use case. In particular, I am trying to detect glass material using the CNH (Compacted Normalized Histogram) data—more about this can be found under the topic: Artificial Intelligence Enabler .From my research, I understand that the sensor generates a total of 121 histogram bins. However, due to constraints such as memory limitations, only 18 or 24 bins can be accessed, depending on the configuration used.I started by configuring the sensor to retrieve the first 24 bins and set the subsample value to "1", so that each bin corresponds to a single zone. Then, I attempted to determine the first significant return using an interpolation algorithm I found online. According to the documentation, I multiplied the resulting value by 3.75 to obtain the actual distance.def interpolate_bin(signal_values, ambient_light_level): for i in range(len(signal_values) - 1): if signal_values[i] &