MEMS and sensors

 Hi Team, We are using the VL53L4CX in QCS8550 platform.Below are queries listed below for clarification. Query 1:Load Capacitance I'm using a same I2C for 5 sensors of VL53L4CX. Is that good to connect or any load capacitance issues will occur Need to understand the max load capacitance of the sensor Query 2: Slave Address configuration As per the User manual, we can able to modify the slave address by controlling the XSHUT pin low The slave address configuration is one time process or every power cycle i need to do address configuration? Query 3 : IO Voltage level From the datasheet, IO level is mentioned either 1V8 or 2V8 I'm using the VCC of the sensor is 2V8 and rest all IOs (SCL,SDA,XSHUT,GPIO) in 1V8 level Is there any issue in this. Kindly provide the insights at the earliest.ThanksManikandan R

Hello everyone,I have an X-NUCLEO-IKS4A1 expansion board connected to the STM32F401RE Nucleo board. The LIS2DUXS12 sensor on the expansion board incorporates a Qvar sensor capable of detecting changes in electrical charge near the external electrodes connected to the device. I have a detachable STEVAL-MKE001A board connected to the 2 x Header 3pin SMD for QVAR electrode.To activate the Qvar channel I set the AH_QVAR_EN bit to 1 in the AH_QVAR_CFG register (31h) and I set the INT1_ON_RES bit to 1 in the CTRL1 register (10h) so that the INT1 and INT2 pins are used to connect the electrodes to detect the Qvar signal.The problem is that the signal I read does not vary when I touch the electrodes as it happens when the LSM6DSV16X sensor as Qvar controller.Did I skip any steps by chance? It looks like the INT1 and INT2 pins of the sensor are not connected to QVAR1 and QVAR2

Dear all,A newbie here. Any help is much appreciated. I appreciate this is an STM forum and while I am using ESP-IDF to interface with STM's lsm303, I believe the problem is caused by my incorrect configuration of the STM lsm303 sensor. Hence any guidance is much appreciated.I am using an LSM303 sensor, connected via I2C to an ESP32 and programmed via ESP-IDF to retrieve the magnetometer and accelerometer data. I was previously using an Ardunio and the the Pololu LSM303 library and everything worked with the same wiring.However, when using bare i2c in ESP-IDF, it seems like I have messed something up as the magnetometer data freezes unless I power cycle the LSM303 (rebooting the ESP32 doesn't seem to change the readings, while unplugging the VCC of the lsm303 and plugging it back in again results in new readings).Here is the code, which reads the data at 50 Hz via I2C. I have checked various sources including the stack exchange electrical engineering forum and others but I am

Hi, I'm looking at the FSM capability of this module, and I'm having a hard time finding meaningful examples. The ST examples found here seem to contain meaningless strings.  "Ac 01 80Ac 04 00Ac 05 00Ac 5F 0AAc 46 01Ac 47 00Ac 0A 00" Am I missing something here? How do I learn how to use the FSM? The AN5226 document may contain all of the information but I'm feeling a lack of how to put it together....  thanks 

Hey, I have been using the AIS2IH accelerometer senson in my TI's am652 linux based board.i found the linux iio driver for this in the github of ST. click to view the supported driver for ais2ih. Click to view the driver files (named as lis2dw12).  i copied the files (lis2dw12.h,lis2dw12_core.c,lis2dw12_spi.c,lis2dw12.i2c,lis2dw12_buffer.c,lis2dw12_embfunc.c) to my linux (drivers/iio) directory. i created Kconfig and Makefile and also defined in the devicetree and in defconfig and built an image in jenkins and the image built was success without any errors. but the module file for the ais2ih is not present in the linux board in /lib/modules/<username>/kernel/drivers/iio  inside this in accel folder i have all the driver files but the accel folder itself missing and i dont know how to make that accel folder to show up. can you give me a solution to add this driver to my linux environment board so that i can make ais2ih sensor to work. give me a complete solution asap. Th

Hi, in my application I intend to use the LSM6DSV16X in order to store accelerometer, gyroscope, SFLP and QVar data, all at the same time.I am able to get XL, G and SFLP data from the FIFO on INT1 correctly, and now I want to also record QVar data.Based off of the example provided here: https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsv16x_STdC/examples/lsm6dsv16x_qvar_read_data_polling.c , I was able to get QVar data alone by routing it to the INT2 pin, however when I also enable the FIFO, I don't receive the data ready interrupts anymore.Is there an incompatibility between these functions that I missed by reading the datasheet ? Here is the code that I am using to set up the sensor (the commented out section are the commands that prevent QVar data from getting output):int lsm6dsv16x_start_acquisition(bool enable_gbias) { lsm6dsv16x_pin_int_route_t pin1_int; lsm6dsv16x_pin_int_route_t pin2_int; lsm6dsv16x_fifo_sflp_raw_t fifo_sflp; lsm6dsv16x_

I want to operate the VL53L5CX to accomplish gesture recognition operations using an ARM Cortex-M4F microcontroller chip. So can libGesturesMZ_m4.a be used with Cortex-M4F?I am trying to port the en.STSW-IMG035_F401 project to an ARM Cortex-M4F controller chip and the HT_set_square_resolution() function returns -5 at runtime.Operation flow: lmz_platform_init -> vl53lmz_init -> gesture_library_init_configure(Err -5, HT_set_square_resolution() failed).

Hello!I recently designed a custom PCB with an LSM6DS3TR-C IMU. However, it doesn't seem like it responds to I2C and I wonder if anyone could take a quick look at the schematic I have for it to see if I've done a misstake. VCC in the schematic is 3.3V.Help appreciated :)

Hi! I am trying to use motion detection data from VL53L8CX sensor. Where can I find deeper explanation of results data and configuration structure than is it in datasheets.RESULTSstruct{uint32_t global_indicator_1;uint32_t global_indicator_2;uint8_t status;uint8_t nb_of_detected_aggregates;uint8_t nb_of_aggregates;uint8_t spare;uint32_t motion[32];} motion_indicator;   CONFIGp_motion_config->ref_bin_offset = 13633;p_motion_config->detection_threshold = 2883584;p_motion_config->extra_noise_sigma = 7; //default 0p_motion_config->null_den_clip_value = 0;p_motion_config->mem_update_mode = 6;p_motion_config->mem_update_choice = 2;p_motion_config->sum_span = 4;p_motion_config->feature_length = 9;p_motion_config->nb_of_aggregates = 32; //default 16p_motion_config->nb_of_temporal_accumulations = 32; //default 16p_motion_config->min_nb_for_global_detection = 1;p_motion_config->global_indicator_format_1 = 8;p_motion_config->global_indica

Long story short, I'm trying to use the MLC algorithm from the BLEMLC sample for SensorTile.Box Pro. However, I can't seem to read any output from the MLC. The MLC is working fine in the BLEMLC sample, but when I try it in my own file, it does not work. I've tried modifying the BLESensorsPnPL file with the MLC, and it still does not work.

I have the STEVAL-56G3MAI1 evaluation kit for the VD56G3 image sensor and the STEVAL-EVK-U0I1 to connect and take snapshots from the sensor.  I have been looking into script generation and register setting and I would like to set the exposure time to be a known duration in microseconds.  I referenced UM2602 titled "How to integrate and configure the VD56G3, VD66GY, and VD16GZ devices from a hardware and software perspective", which contains all the register configuration information for this sensor.  Section 14.7.2 of UM2602 is for configuring the manual exposure and it talks about a register called "MANUAL_COARSE_EXPOSURE".  The description of the "MANUAL_COARSE_EXPOSURE" register is "Integration time is controlled by the MANUAL_COARSE_EXPOSURE register. The value is expressed in line equivalent".  The manual also states that the value is a 16-bit unsigned integer. However, there is no information in the manual for how to configure this value to set the manual

Hello, I'm having trouble interacting with the SensorTile Box Pro through the BlueST protocol. I've used the ST BLE sensor app to set the device to stream compass data, I used the included example and did not change anything. In the app, I can receive compass data without a problem with its included visualiser. I then used the Lightblue app to receive the same data, and it worked without a problem. I used the BlueST datasheet to figure out which characteristic held the compass data, and subscribing to receive notifications worked immediately.The next step is where I seem to be blocked, I want to receive this data with an esp32 dev board. I used a xiao esp32c3 with the included bluetooth library. I wrote a very basic script that connects to the sensortile and subscribes to the characteristic. Connecting and finding the characteristic work without a problem, but I cannot get it to receive data at all. My arduino script is attached as a .c (the forum doesn't like .ino) for reference

Hi all,About 25% of the LSM6DSOX sensors in the field have a non-functional pedometer. The step count is showing as zero. A power-on reset or software reset does not resolve the issue. We rely on the step count provided by the pedometer module, but it is consistently reading zero. The wake-up interrupt is working correctly, but the step count interrupt and direct reading from the step count register both return zero. Please assist in addressing this issue. This is very critical as we are replacing a lot of devices because of this. Thanks,Vishnu Pradeep

Hi,  I am reading datasheet of LSM9DS1, and a little conccerned about the following part:  Especially about the text: "When a FIFO threshold interrupt occurs, the first data has been overwritten and theFIFO stops collecting data from the input channels."Why first data have to be overwritten? It looks more naturel not to be overwritten in FIFO mode. Thank you in advance.

Hello,I'm working on a project where I use the LSM6DSRX. I have noticed that the Gyro has a strange behavior, reporting peaks on the X axis while the device is solid static. The peaks may be correlated to the temperature change but it's not clear yet. I did run a test, on ambient temperature range +5C to +30 with two end-devices (DUT1 & DUT2) and one of the two reported the peaks on X axis at around 33C (internal temperature) while the other not. Is this something you have ever experienced or reported by any user? Since now all of my experiments shows that it is device related and not system related. I have replaced the LSM on some of the faulty and the issue seams to have been resolved. I have taken X-ray scans to verify that the soldering is acceptable and it is. Following raw data as read from the sensors Gyro from 3 different devices. You may see the noise coming after a few minutes with a duration of around 50-60 minutes The samples are taken every second. The noise is al

I am currently implementing a series of  vl53l4cd sensors into a project. These work really well and I am able to address these individually on one shared i2c line. These sensors are working perfectly fine on this shared line when measured independently but when an object is blocking both sensors, the readings speed up and the readings of both sensors becomes much less accurate and noisy. Is there a specific approach to reading sensor data from both sensors simultaneously? As a test I did move one of these sensors onto another i2c line, and the issue continued. I originally thought it was congestion on the i2c line but it clearly isn't and may be the way I am getting the distance data from both sensors. I am using the Arduino library - https://github.com/stm32duino/VL53L4CD/ I have attached a video which should hopefully show what I am seeing. The yellow line is one sensor and blue is the other.  Thanks  

Posted on February 15, 2017 at 16:29Hello,I have an EVALSTPM34 board.I am trying to access the board via the UART using the 'STPM3x Evaluation Software' v3.1.0.0J7 has 3.3v supply attached. J2 has TTL-232R-3V3 cable attached.PC recognizes the TTL-232R-3V3  as COM5.J3 jumper is removed.SW1 has all SWs in ON position.I start up the STPM3x Evaluation Software.Options > Interface = USRT, COM5, 9600I press 'Open' and get success.Options > Configuration > Application tab = EVAL-STPM34I press 'Apply' and get a pop-up dialog box that says:Read buffer lenght insufficient.   < Yes, 'length' is mis-spelled.The operation has timed out.Has anyone had a similar experience?Is there a newer version of the 'STPM3x Evaluation Software' ?Rob ParsonsSchneider ElectricKnightdale NC USA

I have a VL53L8CX time of flight sensor connected via I2C on a custom board. The Board has other devices that can talk on I2C no problem. now i cant see the i2c address of the ToF device. from my understanding everything seems to be fine and in accordance with the datasheet. However there are two things that might be not correct and i want to make sure that my assumptions are not wrong. about the LPn pin (A2) in the datasheet this is written:Enables communication. Drive this pin to logic 0to disable I²C communication when the device isin low-power mode. Drive this pin to logic 1 toenable I²C communication in low-power mode.This pin is typically used when you need tochange the I²C address in multidevice systems. Ifit is not used, or if interfacing via the SPI,connect to IOVDD with a 47 kΩ pullup resistor I dont plan to use the low power i2c mode. so i connected it to IOVDD via a 47kohm resistor. Was this correct? the other thing i am not sure about are

Hello, I have been working on a project using the H3LISD331Dl accelerometer set at +-400g and the STM32U585OI MCU. I wish to capture the high G shocks that occur during drop testing. I have completed my project and I am just wondering how accurate the results I am getting are. I secured my PCB inside an enclosure and did drops from various different heights focused on different axis. I attached .csv files for 3ft and 6ft drops focused onto the Z-axis. I plotted the data I got in excel and the increase in g's seem to correlate with the increase in drop height. Is there any way to guarantee the accuracy of the values I am recording? 

Hi:I am trying to use en.STSW-IMG037 (VL53L7CX_GUI_v2.2.29009) software to evaluate the VL53L7CX ToF sensor. I implemented firmware on the NUCLEO-H755ZI-Q board with VL53L7CX sensor from Pololu based on the firmware example in the "en.X-CUBE-TOF1\Projects\NUCLEO-F401RE\Examples\CUSTOM\VL53L7CX_SimpleRanging. I initialized the UART with 460800 baud and sensor is dumping the data on a terminal software. The next step, I would like to use the GUI software installed in the en.STSW-IMG037 to evaluate the sensor. I launched the software, and it detect the ST-LINK. However, the "Connect" button is still graded out. Do you have any guideline how to format the serial data? Can I use the software with the board other than NUCLEO-F401RE and NUCLEO-L476RG boards?Please let me know if anyone has success on the software. Thanks! 

Hii,       I am writing to seek support regarding an issue I am facing with the VL53L4CX Time-of-Flight sensor. In my current setup, I’m consistently encountering incorrect distance measurements beyond 2 meters, where the sensor tends to report values that are approximately 75-85 cm more than the actual distance.Details of the Issue:Setup: Indoor environment, with stable power supply, targeting a white sheet-covered wall.Timing Budget: Set to the maximum value of 200ms.Observations: While the sensor occasionally reports the correct distance, more often than not, the values are incorrect, with a significant error margin of 75-85 cm. The status returned is also zero, indicating no error according to the API.Steps Already Taken:Environmental Factors: The sensor is used indoors with no direct sunlight or ambient IR interference.Cross-talk Compensation: Using cross-talk compensation function provided in driver.Field of View Adjustments: Limited any possible interference

Hello,We have been using multiple VL53L3CX sensors for some time but only using one zone. Now, we want to use all four of them but we are running into some issues: Specifically, we can only read one zone while the rest all return status 255. In addition to this, only one object is found which makes sense considering the status. But, as said before, we need to use all the zones. The issue that we have is very similar to this thread but sadly it was not solved. So, is there any procedure, configuration or calibration that we need to do before attempting to use the rest of the zones?Our setup consist of an Arduino Due connected to the sensor and we do the following to initialize it:  (void)VL53LX_WaitDeviceBooted(&dev); (void)VL53LX_DataInit(&dev); (void)VL53LX_SetDeviceAddress(&dev, address); Then, to get the measurements the following is done: ToFLateralStartNext(&ToFLat2_t); ToFGetLateralMeasurement(&ToFLat2_t, 2); Where void ToFLateralSta

Hey! If I well understood the component IIS328DQTR will be at least "NRND" in 2025. The IIS3DHHC seems to be a good substitute but it doesn't have all the interrupt features of the IIS328DQTR. Can you confirm the lifetime of the IIS328DQTR? Do you have a 3-axis digital accelerometer with the feature: "The device may be configured to generate an interrupt signal through inertial wakeup events, or by the position of the device itself."Kind regardsCharles D 

Hello ST Community,I am currently working with the STHS34PF80 thermal presence sensor and utilizing the TMOS10-12030 lens to increase the field of view (FOV) to 120 degrees. However, I am encountering several issues that I hope you can assist me with:Limited FOV: Despite using the TMOS10-12030 lens, the FOV is still limited to around 25 degrees instead of the expected 120 degrees.Unstable Presence Detection: The sensor’s presence detection appears unstable, with limited detection range and frequent false positive detections and   negative detection (can't detect humans in front of him with in 1meter range) .Given these challenges, could you please provide any recommended configuration settings or adjustments to the sensor or lens setup that would help improve:Field of view (achieving the full 120 degrees)Detection stability and rangeReduction of false detectionsAny guidance or documentation you can provide to help resolve these issues would be greatly appreciated.Thank you fo

Hello STM Community,I am working with the STHS34PF80 presence detection sensor on an STM32WB55 development board, and I've encountered an unexpected issue with its detection behavior.Problem Description:When an object like plastic or paper passes in front of the sensor, it does not detect the object's presence, which I understand could be due to these materials not emitting enough infrared radiation. However, the problem occurs after the object is removed. Once the object is no longer in front of the sensor and there is no one around, the sensor unexpectedly detects a "presence."Observations:The sensor detects human presence accurately.The false presence detection only happens after an object (plastic, paper, etc.) is moved away.There are no obvious environmental changes (such as temperature shifts or airflow) when the false presence is detected.The object itself does not seem to be detected at all while in front of the sensor.Question:Has anyone experienced similar behavior with the S