MEMS and sensors

It appears that the longest spi operation that could be used to access the LSM6DSV (and related parts) would read a single fifo entry (7 bytes) and it is not possible to read all the available fifo entries in a single dma operation.  Am I missing something? Geoffrey

Hi, ST Community, I am working with an lis2mdl on a STEVAL-MKI217V1 board and I used lis2mdl_hard_iron.c this Application and I was able to get data_raw_magnetic and magnetic_mG I want API to get the Angle of Rotation of the sensor  

Hello,I am testing LSM6DSO and LSM6DSO32 on Zephyr.As these 2 sensors are pin compatible, I prepared 2 identical boards, one is mounted with LSM6DSO and LSM6DSO32 on another. (The sensors are connected to MCU through SPI interface.)My purpose is that I can use one single Zephyr image to drive the IMU sensor no matter which one of these 2 sensors is mounted on board.It looks promising because one lsm6dso.c driver is provided in Zephyr, and this driver defined DT_DRV_COMPAT for LSM6DSO32. And Zephyr's official document also confirmed this compatible as well.So I use the default sample/sensor/lsm6dso app for a simple testing.The sample can be built and run for the board with LSM6DSO. The output from the uart console looks making sense.But I encountered some problems when configure the dts file for the board with LSM6DSO32.At first I config the dts file like this:

Hi, I am looking for the burn-in specifications for a MEMS accelerometer device/sensor. Could you please help me with this information? Thank you

Hi Team, do ST offer a high-g accelerometer, similar to the LSM6DSV320X on the STEVAL-MKI251A, that supports over 400g with integrated free-fall detection?

I am using the STEVAL-MKI238A kit with the LIS2DUX12 chip. This is connected to an NRF52840DK and interfaced using Zephyr's lis2dux12 driver. The eval kit is connected to the SPI3 device using its default settings. I am running an SPI clock of 1Mhz and the VDD and VDIO pins are supplied 1.85V+GND from a shared power supply with the nrf52840dk. The Zephyr lis2dux12 driver is hard coded to use SPI mode 3, so CPOL+CPHA.The lis2dux12 driver fails its INIT sequence by mismatch of the WHO_AM_I readback. The device seemingly returns 0x0C.I have connected a logic analyzer to the pins of the eval kit shows this sequence:- 0x01 is written to register 0x3E to wake the device up from sleep- Once the CS signal is disabled, 50ms passes before the next CS enable to allow the sensor to wake up- A read request is made to register 0x8F (bit 7 read + 0x0F)- The clock idles for 48.5µs before pulsing for the response- The sensor effectively pulses 00

I notice there is now a github repo with FSM examples; very useful!However, in comparing what I have been successfully using, for example, for shake detection on the LSM6DSV (or LSM6DSV80X) where 30 lines are written to page 0x7A: _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0xC0 | 0x20 | 0x02); // write to CONFIG_A (three thresholds, two masks, two short timers) _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to CONFIG_B _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x1E); // write to SIZE (30 byte program) _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to SETTINGS _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to RESET POINTER _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x00); // write to PROGRAM POINTER _i2c_bus->writeByte(i2cAddress, LSM6DSV80X_PAGE_VALUE, 0x66); // write to THRESH1 LSB _i2c_bus-

Hi everyone,I am a beginner working with the VL53L1X sensor on an STM32F103C8T6 using the STSW-IMG009 (Ultra Lite Driver). I am trying to implement a calibration routine, but I am encountering two specific compilation errors inside my VL53L1X_calibration.c file:The errors:1. 'VL53L1X_ERROR_TIMEOUT' undeclared (first use in this function); did you mean 'HAL_DMA_ERROR_TIMEOUT'?2. implicit declaration of function 'VL53L1_WaitMs' [-Wimplicit-function-declaration]I have checked the driver files but cannot find their declarations.I have not changed any of the driver files. Am I missing something? Any help is appreciated. Thank you!

I'm stuck at trying to make motion_fx call MotionFX_LoadMagCalFromNVM and MotionFX_SaveMagCalInNVM - a problem which is mentioned already in link1 and link2 but to which actually there is no working solution (the rest of the motion_fx seems to work without any issue). I implemented the functions as below, but already when compiling, they get optimised out and end up being discarded - hence the motion_fx library never calls them, in contrary to what UM2220 suggests. My code does actively call MotionFX_MagCal_init(MFX_MAGCAL_SAMPLE_PERIOD_MS, 1); and MotionFX_MagCal_init(MFX_MAGCAL_SAMPLE_PERIOD_MS, 0); which as per UM2220 should trigger the call of the NV

I am using a VL53L0 ToF sensor.If an interrupt occurs, repeat the measurement using the "VL53L0X_GetRangingMeasurementData" function and the VL53L0X_ClearInterruptMask function.Normally, it operates, but the sensor outputs data that seems to be looking in the air due to unknown causes such as static electricity.From the IR camera, there is no light in ToF.Two functions, VL53L0X_GetRangingMeasurementData and VL53L0X_ClearInterruptMask, do not return errors.When I initialized the phenomenon after checking it, the sensor operated normally.I'm wondering if there's any data I can check because the data is similar to what I'm seeing in the air about the above phenomenon.

raw ID and is_alive() work Hello,I am using a Chinese VL53L8CX module from AliExpress, not the official ST evaluation board. I want to stress that in the first sentence because this may be important: this is a Chinese AliExpress breakout, not the original ST hardware. The same module works on my setup over I2C, but I am trying to bring it up over SPI on an ESP32-S3 and I am stuck at a very specific point.What already works:- The same sensor/module works over I2C on this board.- In SPI mode I can repeatedly read the hardware ID correctly: `dev=0xF0`, `rev=0x0C`.- `vl53l8cx_is_alive()` often returns `status=0, alive=1`.What fails:- `vl53l8cx_init()` never completes successfully.- The failure happens around the software reboot / boot polling stage.My hardware/software context:- ESP32-S3- custom firmware using Arduino + ESP-IDF SPI path- Chinese AliExpress VL53L8CX module- `SPI_I2C_N` fo

In the getting started guide there is a programmable audio buzzer names SPK1 but I can't find reference of it anywhere, where I can enable it in the .ioc file and how to interact with it? Please could someone advise me on this.

I am trying to implement Time-of-Flight data acquisition using an STM32F405 microcontroller running FreeRTOS, with the MCU and the VL53L8CX communicating via SPI. However, the vl53l8cx_check_data_ready() function keeps failing, and I have been trying to track down the root cause.Here is what I have verified so far:After loading the firmware to the VL53L8CX and starting it, I confirmed that the sensor is emitting infrared light (observed using a camera).I checked the status return values from the API functions, and no errors were reported.There were no issues with the 3.3 V power supply, and no temporary voltage drops were observed during sensor reboot.I probed the INT pin with an oscilloscope to check if the VL53L8CX is outputting an interrupt signal at the interval set by vl53l8cx_set_ranging_frequency_hz. However, no interrupt signal was observed.For comparison, I tested a bare-metal (

Hi, ST Community, I am working with an LSM6DSOX on a custom board, using an ESP32S3 with the Arduino framework, and I'm unable to get the Machine Learning Core (MLC) to run.The problem is that the output register MLC0_SRC (0x70) always reads 0x00. I am also monitoring the is_mlc_ok status bit in the EMB_FUNC_STATUS register (0x15), and it never gets set to 1. Basic communication (reading WHO_AM_I and raw accelerometer data) works perfectly.I am not using a library and am writing directly to the registers. My initialization sequence is as follows:Software Reset: Write 0x01 to CTRL3_C (0x12).Wait: A 100ms delay to ensure the reset is complete.Enable Embedded Functions Access: Write 0x80 to FUNC_CFG_ACCESS (0x01).Load UCF Data: Write the entire .ucf file (288 bytes) byte-by-byte by

I connected the VD55G1 promodule on the LS-CAM-I3C and connected it to the NUCLEO-H563ZI.The Display X-NUCLEO-GFX02Z1 is also connected.This is exactly the same configuration from the README.md.I get always an error in "ret = platform_i3c_assign_dynamic_address(p_dev->p_ctx);" (Line 82 display_qvga_streaming_i3C.c) I3C ErrorAccording to https://www.

The sensor box pro is a neat device.  If I use the CLI Example program and the USB cable, I can get 8000 data points per second, if I use a traditional C# program I get 8 data points per second.  The CLI yields dat files, which can be read with a simple C# program, although why you would mix 6 and 4 data groups is beyond my skill set to understand, but it is easier to use than Python and MEMS Set.   And it is easier to do the byte data in C#.  (It took less time to write this program than I spent trying to get Python to work.)CLI Example makes me type enter to start.  I have many ST.COM accelerometers all over the world and I am not going to type enter to start, but the main.cpp and main.h and the cmake lists file will not compile in CMAKE or Visual Studio.  So I cannot fix the challenging feature. Could we get VS SLNX file and the C++ code for this program as part of the SLNX so it is easy to take out the enter state

Greetings - I would like to request consideration for a Latched INT option similar to that of the STHS34PF80 sensor (Register: CTRL3 22h). I typically utilize the VL53 with Min/Max threshold values and would like the option to have the INT signal latched when the object is within threshold values.Thank you for the consideration,Terry

Is there a way to change the Horizontal front and backporch?   This is a addon to this question* https://community.st.com/t5/imaging-sensors/vd56g3-camera-change-the-frame-start-and-frame-end/m-p/888134#M6406@Jean_Poire 

I am using the VL53L7CX to measure a black object. When the object is placed at a distance beyond 200 mm, the readings become very unstable and a large number of erroneous points appear. Additionally, when a highly reflective object enters the sensor’s field of view, the points that were previously showing valid data for the black object also start returning errors. Once I remove the highly reflective object, those points recover and start reporting correctly again. In the error state, the affected points return no data at all — it seems as if the sensor does not detect any object. However, the black object is still present in the scene. The only change is the removal of the white object, which causes the sensor data to change significantly. Has anyone encountered a similar issue? Could this be related to crosstalk, or are there specific configuration settings recommended for black targets at longer distances? Any adv

I have an application where I run the VL53L1X in lite ranging mode and short distance mode with a timing budget of 10 ms (100 Hz) as described in AN5263.I recently noticed that on at least one unit (and probably more) the VL53L1X reports a spurious distance reading of 0 mm with no errors even though the sensor is pointing into an empty space and there are no objects within the 1.3 meter range of short distance mode.  This spurious reading happens about 10 times per minute, and the rest of the readings are regular expected errors.I am not using the API (STSW-007) directly, but have implemented code that does the equivalent thing.Here are some VL53L1X register values from these spurious readings:The lower 5 bits of the VL53L1X result__rang

We are designing a lens cover to be used with VL53L9CX. Can you share any more data on the FoV of the time of flight sensor? The attached data sheet on the part page is for a different sensor "VL53L7CX" is there a data sheet for the "...9CX" version? In "Description of the fields of view of STMicroelectronics' Time-of-Flight sensors" Sections 3.2 & 3.3 reference exclusion cones which are given in a product data sheet. Could you please share this file? Also, 3.3 references keep-out cones which can be shared by contacting support. Any additional information would be helpful to ensure our lens does not interfere with the required FoV. Thank you!

I have questions regarding estimated_reflectance and range_sigma in VL53L5 and L8The reflectance: how is it calculated? Is it R=signal_rate_per_spads*depth^2/K? the number_of sapds_enabled seems a useless parameter for a user? Can we know this calibrated constant K?The ambient_light has nothing to do with the R calculation?For these multi zone TOF, if we place a flat target in front of TOF, it shall give the same R. ST’ already does the internal compensation for the depth and for the angle of incidence. Right??  I can not find this kind of info in ST’s doc. Can only guess. If it has, please point out the Docs sourceThe range_sigma: for L5, if the resolution is 4 x 4, the readout is zero. I can read out  this parameter if it is 8 x8What is the default sigma_threshold for distance in L5? Is it the same for resolution  8x8 and 4 x4? Also, when I change this threshold, it is unclear if this threshold, e.g.,100mm shall multip

I'm using the library here: https://github.com/stm32duino/VL53L1, and it seems to stop measuring around 3.2-3.5 meters. I may be wrong, but think that means that it is not using the histogram? I set it to long distance ranging mode.Here is my code:bool Sensor::ConfigureSensor(TOF &tofSensor) { Log.noticeln("Configuring [%s]", tofSensor.name); if (tofSensor.sensor_object == nullptr) { Log.fatal("No TOF sensor object initialized."); return false; } VL53L1_Error status; status = tofSensor.sensor_object->InitSensor(tofSensor.address); delay(10); if (status != VL53L1_ERROR_NONE) { Log.fatal("Failed to initialize %s. Status: %d. Halting.", tofSensor.name, status); while (1){;} return false; } Log.noticeln("%s address set to 0x%x", tofSensor.name, tofSensor.address); sta

Hello, I am using this sensor for a project where it is mounted on a cane to detect overhanging objects that could hit visually impaired people. This works fine indoors, but outdoors, when the ambient light is around or greater than 10k Lux—and keeping in mind the sensor is pointed upwards and hit directly by sunlight—it only catches obstacles when they are very close. I am currently using a 4x4 resolution with continuous ranging at 30Hz. My question is: is there a way to increase its efficiency? By efficiency, I mean increasing the detection distance through hardware, structural, or software solutions.

 Dear all,I am struggling with getting a good SFLP result, that does not drift too much and does not appear jittery. I went trough most of the posts here but I am still not able to get good results (approx. factor 10 higher drift then according to the data sheet). in one of the posts I found the explanation about the chain of the SPFL:  that was the one im ent: For now, you have the answers: SFLP (as MLC/FSM and other embedded functions) take its input from LPF1 in the accelerometer chain, and from LPF2 in the gyroscope chain; their setting will therefore impact SFLP. Higher ODR leads to a more accurate gyroscope integration, but sensor RMS noise will also be higher. Gyroscope saturation should be avoided, accelerometer saturation matters less. Lower full scale will inc