MEMS and sensors

I am working with the ST VL53L8CH sensor for research purposes. To generate a point cloud from depth measurements, I am trying to get the directional ray to each zone. I am wondering if there is a more detailed explanation of the configuration for SPAD maps in this diagram:For example, in a similar sensor, the AMS TMF882X sensor datasheet has the following information for how SPADS map to each zone:If not, is it reasonable to assume that the 16x16 zones uniformly make up the 45° x 45° square FoV, or is manual calibration with a known scene necessary?

Hello, Our teams is making a proof of concept about dead reckoning using a STM WESU board. The goal is to get pedestrian position onyl using ACC/GYR/MAG for a short period of time and small moves.First results in certains conditions are pretty good. Without any calibration/correction, we manage to get approx 3m absolute error on a 20m walk (30seconds). We expect same error on a 100m walk with good AHRS algorithm parameters and sensor calibration.We are ready to put more effort on the IMU. Do you have calibration source code/protocol for WESU sensor ? * LSM6DS3 = acc value + gyro drift* LIS3MDL = soft and hard iron calibrationWe also have other more advanced IMU, but we want to keep it simple and low cost for now and WESU allow us to be pretty fast on POC steps.Thanks a lot for your future help. Best regards. 

Hi ThereWhere I can find some source files for LSM303DLHCI see some ref.links there, but right now they pointed to non-existed pages on github :( Or I miss somethingAlso I found this link https://github.com/STMicroelectronics/stm32-lsm303dlhc but it contain some "Common/accelero.h" and I also can't find it on github :(Regards, Evgenij

Dear ST/Forum,Your attention would be much appreciated for a technical enquiry.We are using the LPS22HB pressure and temperature sensors in some electronics for an experiment that will be onboard the International Space Station (ISS) in orbit later this year. We are having great success reading the sensors generally but we have an anomaly in the data if you could please advise. Our code is communicating with your chip in one-shot mode using the chip enable line and SPI serial bus. We are powering the devices from 3.3V and the code enables the chip, waits 100mS and then begins reading.We are finding that the first pressure value and subsequent values all seem OK. However the first temperature reading is consistently 1 degree lower than all subsequent readings. This is consistent on one device and the same on all devices. Are you aware that the first temperature reading is known to be in error, or are we doing something wrong?Please see the plot file from two devices attached. You can cl

Hi, I am looking for a ToF sensor using VL53L1X.We are currently developing a ToF sensor using VL53L1X.I have a question about the sample API VL53L1X_UltraLowPower you are using.Whenever I execute VL53L1X_ULP_CheckForDataReady within VL53L1X_ULP_SensorInit(), it always TimeOut.After examining the contents a little more, it seems that the problem is caused by the difference between the values of &temp and int_pol obtained by the VL53L1X_ULP_GPIO__TIO__HV_STATUS command. (This is the location in the picture).In other words.・What does it mean to do this setting・What does the value of temp mean?・What does &temp return?I need answers to these three questions. The microcontroller in use is EFR32MG22Also, if I use VL53L1X_ULP_GPIO_HV_MUX__CTRL, 0x11 is returned and int_pol is set to 1. Please let me know if this is even the correct behavior. I would be glad to answer your questions!Best Regards.    

Hello,I am working on a project using the LIS2MDL magnetometer sensor to build a smart parking device that detects the presence of a car based on the x-axis readings exceeding an interrupt threshold.Currently, I face an issue with setting high and low thresholds for the interrupt. For example, if I set the high threshold to +30 and the low threshold to -30, and the x-axis reading is around 1400 mG, the interrupt remains consistently high. This makes it difficult to reset and detect new threshold crossings.Is it possible to dynamically adjust the thresholds based on the initial raw data reading from the x-axis? For instance, could I configure the device to read the raw x-axis value during initialization and then set the high threshold to x_axis_val + 100 and the low threshold to x_axis_val - 100?I’d appreciate any guidance or suggestions.

Hi, We are developing a product/device that is mounted on a machine/vehicle that generates vibrations when in the ON state. We need a sensor that can 1.. Detect vibration start and stop while the device is stationary, with good accuracy, to determine when the machine is ON and for how long.2. Differentiate between vibration and actual motion, meaning it should detect when the device is no longer stationary and has started moving in any direction in on condition with vibration.3. Detect motion in the OFF state, where the machine is off (no vibration), but the device itself has started moving and trigger an interrupt to alert the MCU. Note: We can measure and predefine the acceleration threshold that should be considered as vibration. Is there a sensor with an internal mechanism that can directly provide output to differentiate between vibration and motion? Thanks, Jay

Hi, I'm trying to implement the tap and double-tap function in the FSM tab. Is it possible to achieve this at an output data rate of 26 Hz? 

We are moving to VL53L4CD.Have it all coded but having a strange experience.  Simplistically we use the sensor continuously and only use GetResult to retrieve the sensor readings (e.g. not CheckforDataReady).So,  simplistically looks sorta like this using the ULD:....VL53L4CD_SensorInitVL53L4CD_SensorStartRanging()while Forever             VL53L4CD_ResultsData_t result;             VL53L4CD_Error VL53L4CD_GetResult(&result);.... This worked fine for the VL53L1X but for the VL53L4CD while all Init, StartRanging and GetResult are returning a status of 0 the reading never changes.  It gets a reasonable reading first but then just never changes.Any idea?Thanks,Will   

I am trying to run a VL53L8CX sensor at the maximum advertized speed. Originally, following the marketing for this chip, I had thought that this was possible at the full 8x8 sensor resolution, but later learned that that has a maximum speed of 15 Hz (strangely, an associate of mine was able to get it to work closer to 20 Hz, but no faster). We need to have the sensor running at 60 Hz, even if at a reduced resolution, but all examples we can find online are below that 20 Hz threshold. Does anyone have any advice for settings and configurations to bring this sensor to maximum speed? For example, beyond cutting the resolution down by 75%, do we also have to use SPI? Are there any important clock speed values that have to be set to some specific maximums?For reference, I am running the board with an ESP32 S2 Dev Module board.

static const uint8_t VL53L4CD_DEFAULT_CONFIGURATION[] = {#ifdef VL53L4CD_I2C_FAST_MODE_PLUS0x12, /* 0x2d : set bit 2 and 5 to 1 for fast plus mode (1MHz I2C),else don't touch */#else0x00, /* 0x2d : set bit 2 and 5 to 1 for fast plus mode (1MHz I2C),else don't touch */#endif0x00, /* 0x2e : bit 0 if I2C pulled up at 1.8V, else set bit 0 to 1(pull up at AVDD) */0x00, /* 0x2f : bit 0 if GPIO pulled up at 1.8V, else set bit 0 to 1(pull up at AVDD) */0x11, /* 0x30 : set bit 4 to 0 for active high interrupt and 1 for active low(bits 3:0 must be 0x1), use SetInterruptPolarity() */ Above is the default configuration for the VL53L4CD (the beginning part anyway). When I first started testing with the VL53L4CD readings were static.  Meaning,  they never changed.  The first reading was the only reading it would ever give out. However,  comparing the Configuration I had for the VL53L1X I noticed that 0x11 (interrupt above) was instead 0x01.  So,  I tried 0x01 and e

We are using the X-STM32MP-GNSS2 (with the STM32 discovery board DK2), which has ISM330DHCX IMU. The accelerometer readings seem fine from the IMU, but the gyroscope gives enormously high and varying readings even when we are stationary. See below the varying output from the gyro  root@FAFUSION:/sys/bus/iio/devices/iio:device2# ls buffer in_anglvel_x_raw sampling_frequency buffer0 in_anglvel_y_raw sampling_frequency_available current_timestamp_clock in_anglvel_z_raw scan_elements dev name subsystem in_anglvel_scale of_node uevent in_anglvel_scale_available power waiting_for_supplier root@FAFUSION:/sys/bus/iio/devices/iio:device2# cat name ism330dhcx_gyro root@FAFUSION:/sys/bus/iio/devices/iio:device2# cat sampling_frequency 833.000000 root@FAFUSION:/sys/bus/iio/devices/iio:device2# cat in_anglvel_scale 0.000152716 root@FAFUSION:/sys/bus/iio/devices/iio:device2# cat in_anglvel_x_raw in_anglvel _y_raw in_anglvel_z_raw -19111 11246 -3500 root@FAFUSION:/sys/bus/iio/devices/iio:de

Hi all!I've recently started working on a fault classification model utilizing the proteus1 board and the NEAI studio suite. I'd ideally like to set up a serial datalogger via the onboard micro USB to both obtain and display readings, alongside benchmarking models. Connecting the proteus with the datalogger flashed via FUOTA (As I don't have a STLINK V3MINIE on hand) leads to it not being recognized when trying to select a COM port to obtain readings. I'd be grateful if anyone would be kind enough to tell me if I'm missing anything, or if there are specific COM drivers for this. Thanks in advance

Hello, I'm currently working on ST1VAFE6ax sensor to read 6 axis data from accelerometer and gyrometer via SPI protocol. But sensor is not behaving as expected. it returns the value as 0. Is there any initial booting process for the sensor or is anything I have to do for the sensor initialization? Pins assigned in my controller (STM32WB series) for SPI are behaving as expected. I have verified that pins with DSO. But the Slave out pin is not returning anything. How to solve it? I'm also having the user manual for the sensor. But I cannot resolve this issue. Please suggest me any solution if you have. Thanks in advance !

We embed LIS3MDLTR on our board that we produce, because this has high sensitivity: 6842 LSB/gauss. This corresponds to 0.146 mgauss/LSB, if I convert correctly. The other products has significanltly lower sensitivity: 1.5 mgauss/LSB. What are you proposing to replace the LIS3MDLTR once it is discontinued?https://www.mouser.com/PCN/STMicroelectronics_15054_1.pdfRegards

Hi All,we tried to migrate from VL53L1CX to VL53L4CD for better precision in short range.both use ULD driver, we expect they work in similar way however it seems not.we set both to TB20 and compare power consumption in single shot case. It seems VL53L4CD takes much long time and power than VL53L1CX even TB is same.Is the observation true and why ?   

(I deleted the content by accident) I'm working on a project that uses Smart Presence Detection to control a LED strip using the X-NUCLEO-53L8A1 board. I started a blank project in STM32CubeIDE and included the X-CUBE-TOF1 bundle. I have added several other features to control the LEDs (SPI, DMA, timers, etc). I am able to get ranging data from the ToF sensor.I would like to add the Smart Presence Detection from STSW-IMG048 but I'm having a great deal of difficulty integrating the SPD code with the existing code that talks to the VL53L8. It seems that the SPD code makes extensive use of function calls to control the sensor using the VL53LMZ_ULD_API but these calls do not work in the context of my existing project - perhaps it some incompatibility in the GPIO or I2C setup but I cannot be sure. I would prefer to be able to use calls to the sensor-control functions in the X-CUBE-TOF1 package to satisfy the requirements of the SPD but it does not look possible - the TOF1 functions do

Hi, We use the calibration ST APIs.  The procedure we follow is run calibration and then reboot with the new offset. However,  is there anyway to avoid having to reboot? We would like to auto calibrate in real time without a reboot if this is at all possible with this sensor.  Additionally,  we are moving to the CD sensor and would like to know if it is perhaps also possible with the CD. Thanks, Will  

Dear ST/Forum,We are using the LPS22HBTR pressure-temperature sensor in some PCB assemblies.Due to some cleanliness requirements of the experiment, I need to be able to clean the PCB this device is attached to but due to the very fine holes in the lid to allow pressure to be measured, and your warnings in data to "not clean in solvent" etc, we are after some advice. I have purchased some liquid masking compound used in electronics assembly and propose to paint this onto the top of the device before cleaning and then peel it off after cleaning. Have you seen this done before and is it likely to cause a problem? I would prefer not to break a device trying this as replacing them on PCBs is difficult due to the geometry.The masking compound is called Techspray WonderMASK P, Peelable Solder Mask Product# 2211. Data attachedThanks in advanceDuncan

Thank you for solving my problem. Please forgive my poor English.I am using lsm6dsl sensor. When I use FIFO to read LSM6DSL, the data is correct at the beginning, but later there will be data errors. configuration :XL_ODR_208HzGY_ODR_208HzFIFO_208Hz2g, 2000dpsXL_ANA_BW_400HzLOW_NOISE_LP_ODR_DIV_100BDU EnableAfter my machine is turned on, I will run lsm6dsl_freq_reset first to ensure that my LSM6DSL is at 208Hz, but I will not turn on the FIFO. I will execute lsm6dsl_fifo_set through the serial port to turn on the FIFO. You can refer to the file I uploaded      #define PATTERN_LEN ((3 + 3 + 3) * 2) #define LSM_DATA_PACKAGE_NUM (10) void lsm6dsl_fifo_set(void) { uint8_t temp = 0xAA; lsm6dsl_int1_route_t int_1_reg; /* FIFO配置 */ //配置FIFO ODR 208Hz lsm6dsl_fifo_data_rate_set(&dev_ctx, LSM6DSL_FIFO_208Hz); //配置降采样率 为0 按照输出ODR直接存储到FIFO lsm6dsl_fifo_gy_batch_set(&dev_ctx, LSM6DSL_FIFO_GY_NO_DEC); lsm6dsl_fifo_xl_batch_set(&dev_ctx,

Are there any plans to have a video tutorial on the biosensor eval board?  (ST1VAFE3BX)? I connected it to MEMS Studio via the MKI109V3.  I'm experimenting with the "Features Demo" but it's not behaving as I expect.  Perhaps there's documentation about what I should be expecting in the MEMS Studio somewhere that I'm missing? 

I am using Mems-Studio for my FSM project. I am testing the state machine, and everything is working fine; I can see interrupts. However, in the debug tab, when debug mode is enabled, the table does not compile, and I cannot observe the program's behavior. I used LSB data as shown in the examples for unico gui  

Hi team,I am new to the STM32 Cube IDE environment and would like to interface and control the VL53L4CX Time-of-Flight sensor using an STM32F030 DEMO Board. I kindly seek your guidance and support in achieving this.Here are the details of the hardware I am working with:MCU Board: STM32F030 DEMO BOARD V1.1TOF Sensor Module: VL53L4CXI would greatly appreciate any resources, sample code, or advice you can provide to help me get started.Looking forward to your support.Thanks and regards,Anirudh

Hello,I am using the VL53L8CX sensor on an I2C bus, and it operates normally until I run the i2cdetect command. After running i2cdetect, the sensor stops working properly, and calling vl53l8cx_check_data_ready() returns a GO2 error status.Interestingly, if I have another sensor (e.g., a temperature sensor) enabled on the same I2C bus, the VL53L8CX recovers and continues working after i2cdetect. The temperature sensor is at a different address and only performs normal read operations.Why does i2cdetect disrupt VL53L8CX?Why does another sensor’s read operations seem to "fix" the issue?How can I debug and prevent this problem without adding a secondary sensor?Any insights or debugging tips would be greatly appreciated!Thanks!

Dear ST/Forum,Preamble:We are using the LPS22HBTR pressure-temperature sensor in some PCB assemblies.The data sheet indicates a pressure reading range with defined accuracy from 260 to 1260hPA/millibar and an absolute maximum overpressure value of 2MPa (20000mbar).We are using the sensor in a vacuum application, where we expect them to not be exposed to vacuum unless there is a leak in part of the assembly. From the data sheet, we have noted there is no minimum safe pressure defined but we naturally expect the pressure readings to be at least inaccurate below 260mbar as it falls outside of the range quoted as "accurate". However we note that readings are given that seem at least sensible down to about 1mbar and then when the pressure goes lower, the sensors starts to read 4096.159874325 or similar, with the digits to the right still decreasing. Lower still and 4096 changes to 4095. We have not continued to note the readings at these low pressures.Temperature readings seem unaffected by