MEMS and sensors

Hi ST team,I'm developing the device which is using VL6180. Sometimes ToF(VL6180) is not recognized the object. And sometimes it is not recognized first and then becomes recognized again. But I don't know why this happened. I'm trying to find the reason but kept failing.My question's are..1. Could this phenomenon(1. not recognized 2. not recognized first and then becomes recognized again) occur when repeatedly recognizing a very short distance (<10mm) due to drift? According to the datasheet, drift is affected by temperature and voltage. But there is no mention about repeated recognizing. That's why I'm asking.2. Or is there something suspicious that could be causing this phenomenon?- In terms of hardware, software, and mechanical aspects Thank you

Hi all,We got odd issue with LSM6DSO32 IMU on our device. After like 6-10 hours of working it begins to not response correctly and it stays until completely power replug. Our code tries do reinitiate IMU when it happens, but within that "frezze" state it reads chip id as 0x00 using lsm6dso32_device_id_get (which we're using to determine which chip is on board) instead of 0x6C.We're using latest libraries from https://github.com/STMicroelectronics/lsm6dso32-pid Whole init sequence:imuSoftReset(); imuErr = imuReadID(&imuID); if(imuErr != imuOk){ return GRAVITY_VECTOR_INIT_ERROR; } imuErr = imuInit(imuID); if(imuErr != imuOk){ return GRAVITY_VECTOR_INIT_ERROR; } ------------------------------ void imuSoftReset(void) { uint8_t resetValue = 1; // Set the IMU's software reset bit and wait for it to clear after a reset // Note: didn't use LSM6DSV32X's reset set function because that function also sets a new global reset bit not present in LSM6DSO32. Reset later if identif

Hi, stNow I've found some new problems.​Sometimes the value read from who AMI register will be 0x48. After finding this problem, I suspect that the connecting wire is unstable. After replacing the DuPont wire, the value read back to normal (0x6b). I want to ask what is the reason for this strange phenomenon.In addition, I found that the accelerometer data rate can only be set at 833hz or below. If the accelerometer data rate is set above 1667hz (1667hz,3333hz,6667hz), the value read from the register is still the previous value, that is, the data setting above 1667hz always fails. By the way, there is no such phenomenon in the setting of gyroscope.​So I updated the driver file to the version of 5 days ago (ism330dhcx: fixed examples # 107) in Git library.A step was added to the driver calling routine of this version(ism330dhcx_device_conf_set), but this step didn't seem to succeed.After execution, I also read the value of this register(ism330dhcx_device_conf_get(&dev

Hello,I am trying to use the VL53L7CX on a robotic project with the provided driver, but it fails at Init.The sensor is detected as alive ("isAlive" is true), the I2C speed is set to 1Mhz (even if I tried lower speeds as well), and it fails exacly at this line of the Init function:status |= _vl53l7cx_poll_for_answer(p_dev, 4, 0, VL53L7CX_UI_CMD_STATUS, 0xff, 2);The status byte is 0 just before that and it goes to 66 (MCU failure) just after the above line.And if I put 2 instead of 4 in the second argument, it doesn't fail at this line, but 2 lines after:status |= _vl53l7cx_send_offset_data(p_dev, VL53L7CX_RESOLUTION_4X4); For info, when I don't stop the init after these errors (forcing the following lines to be executed), I am able to "see" (with a smartphone camera) the infrared light from the sensor when starting ranging in my ranging function, but without any result, nothing detected. Does it mean that at least the firmware is downloaded?Any help would be apreciated!Thanks.

I am using the VL53L8CX sensor to measure distances, and I am getting correct values. After some time, the data starts to be sometimes incorrect, while slowly increasing the ratio of incorrect vs correct, until eventually all of the readings are incorrect.I've noticed that the time it takes for the data to start being incorrect is linearly related to the ranging frequency.The resolution I am using is 4x4.When using ranging frequency = 5, it takes 4 minutes for the first incorrect data.When using ranging frequency = 10, it takes 2 minutes for the first incorrect data.When using ranging frequency = 20, it takes 1 minute for the first incorrect data. When using ranging frequency = 60, it takes 20 seconds for the first incorrect data. Regarding the "correctness" of the data - the sensor is roughly 200 mm from the surface, and the readings I get at the beginning are as follows:Zone 0: ambient/spad = 2 | nb_spads_enable = 5632 | signal/spad = 1394 | distance_mm = 210 | range_s

I just bought the latest SensorTileBox (STEVAL-MKSBOX1V1), can I add RTC to the Level function? I need timestamps added to the accelerometer output. Level Function is missing in the available functions under Custom Apps.

 We want to use iio buffers to read accelerometer data. I tried the following, but it did not work. root@FAFUSION:/sys/bus/iio/devices/iio:device2# ls buffer current_timestamp_clock events in_accel_scale_available in_accel_y_raw mount_matrix of_node sampling_frequency scan_elements uevent buffer0 dev in_accel_scale in_accel_x_raw in_accel_z_raw name power sampling_frequency_available subsystem waiting_for_supplier root@FAFUSION:/sys/bus/iio/devices/iio:device2# cat name ism330dhcx_accel root@FAFUSION:/sys/bus/iio/devices/iio:device2# root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_x_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_y_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > scan_elements/in_accel_z_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > buffer0/in_accel_x_en root@FAFUSION:/sys/bus/iio/devices/iio:device2# echo 1 > buffer0/in_accel_y_en root@FAFUSION:/sys/bu

Hi All,My name is Stefano, and I developed firmware for an embedded sensor that integrates the LIS2DW12 MEMS accelerometer. We encountered the following issue:At the end of the firmware development, we tested the current consumption across many of our new sensors, and the results were as expected;The new firmware was then put into production;After a few months, we noticed that some sensors had a lower-than-expected battery level, despite their typical lifespan;We retrieved those sensors from the field for analysis;Upon analysis, we discovered that the issue was due to abnormal current consumption by the sensor, with an average current (Iavg) of approximately 300 mA instead of the expected 7 mA;The sensor's current consumption returned to the normal range when the firmware powered off the accelerometer;After extensive investigation, we determined that his abnormal consumption is due to the resin potting phase, Main resin infos are follows: shore A hardenss of 74-80,Dielectric

I am reaching out regarding an issue I am experiencing while reading register values from the ISM330DLC sensor using a Python script over SPI. Specifically, I am encountering incorrect data when accessing certain registers.For example, when reading the WHO_AM_I register (0x0F), I receive a value of 0x7F instead of the expected 0x6A. This discrepancy suggests there may be an issue with the communication setup or the sensor response.Here is a brief outline of my setup and process:Hardware:Raspberry Pi 5 connected to the ISM330DLC via SPI.Correct wiring verified (VDD, GND, SCL, SDA, CS).Software:Python with spidev library for SPI communication.SPI mode set to Mode 0 (CPOL=0, CPHA=0).SPI clock speed: 1 MHz.Code Snippet:import spidev spi = spidev.SpiDev() spi.open(0, 0) spi.max_speed_hz = 1000000 spi.mode = 0 # Reading WHO_AM_I register reg = 0x80 | 0x0F # Set MSB for read operation response = spi.xfer2([reg, 0x00]) print(f"Response: {response}") Despite these checks, the returned v

Hello ST Forum,I am currently working on a project that aims to help surfers analyse their surfing sessions. The goal is to use a LSM6DSV16BX attached to a surfboard, using the IMU to analyse the board's movement, and one of the QVar channel to detect whether the board is put in water.I was wondering about how to use the second QVar channel. In particular I was wondering if it could be used to detect the presence of the surfer on the board without contact.In the August 2022 revision of AN5755, the document states that using a single electrode is recommended for presence detection, especially in cases where powerline noise is weak, which seems to be my use case. However, the surfer and his/her surfboard will be immerged in seawater. Do you know if it is possible to detect human presence in these conditions ?Additionnaly, since QVar channels seem designed to be used differentially, do you know if I can use one channel to detect if the device is in water, and the other channel to detect a

I need the thermal resistance Junction to Ambient for LIS2DH12, LGA-12 package. 

..

Hi. I have both the ST1VAFE3BX and the X-NUCLEO-IKS4A1 and I'm trying to read data from the biosensors using MEMS-studio, but I don't see how to get MEMS-studio to recognize the biosensors.  The documentation for the biosensors has instructions for working with the ProfiMEMS tool (a different motherboard).  In that documentation, it shows that there are biosensors. The docs for the ST1VAFE3BX also indicate that it will work with the IKS4A1 but it's not obvious to me how to make MEMS-studio "see" the biosensors as a data source.any help would be appreicated.TIA.-Rich 

I’ve been using the "vl53l8cx" sensor to measure distances through I2C, and I noticed that when I measure distances (between 10cm and 50cm), the values reported by the sensor are consistently half of the actual distance. For example, when the actual distance is 100mm, the sensor reports around 50mm, and similarly for other distances.I used the example code ST provided.I set 8*8 resolution and 15Hz frequency.I think problem occurs here. I got "target status : 6"  Could you please explain the reason for this issue and how to fix it?  

We are designing an STHS34PF80 into an occupancy sensor and the plan is to have an HDPE window to protect it.  To test the response in the actual product we purchased 1/16" (1.5mm) HDPE sheet and put it over the sensor.  The fresnel lens with the dev kit was removed.  Surprisingly the Tpresence triggers when the sheet is over the sensor, and so the device doesn't seem to be seeing through the HDPE sheet.My first thought is that the HDPE is doped or just wrong somehow but I thought I'd ask if anybody else has seen something like this.Thank you.

Currently I'm using some of the vl53l5cx api functions along with some custom code. I plan to have multiple ToFs used and noted, via o-scope, that the initialization function vl53l5cx_init (looks to be blocking code?? correct me if I'm wrong) takes about 2.5 seconds to complete (at 400Kbps I2C) to configure a single ToF. This means with the current initialization it would take more than 10 seconds alone for initialization to complete. Unfortunately, I am working in constraints that prevent me from accessing the watchdog to circumvent the issue. Are you aware of any ways of overcoming this? I wasn't sure of the initialization sequence was one that could be split.

Hi I have an application inquiry...'m looking into remote mounting a ToF sensor (i.e. VL53L4EDV0DH/1) in order to observe the environmental limitations of the sensor in a more difficult envorment...are there any guidelines or application history for this kind of optical adaptation?  (not as straightforward as a simple cover glass)   thanks, Jason

Hi all, I am currently working with the STEVAL-PROTEUS1 Board, which incorporates the STM32WB5MMG module and the IIS3DWB high-bandwidth accelerometer sensor, interfaced via SPI_1. According to the IIS3DWB sensor datasheet, it supports a clock frequency of up to 10MHz and an Output Data Rate (ODR) of 26667Hz (37 microseconds). My objective is to collect sensor data at an ODR of 26667Hz. Here are the steps I have taken so far: Configured the core to 20MHz. Configured SPI_1 to 10MHz. Configured the sensor to generate an ODR interrupt, which is successfully triggering every 37 microseconds. The issue arises when collecting data (6 bytes) from the sensor, which is taking 125 microseconds using HAL functions in blocking mode. Ideally, this should not be the case. I have also tried using non-blocking mode (DMA), but it is taking more time (175 microseconds). Could anyone help me understand if the HAL function is supposed to take 125 microseconds, and why DMA is taking more time than the blo

Hi,I recently bought a SensorTile(STEVAL-STLKT01) and I want to modify the default project for my own usage case.Based on the information I found, I downloaded the source code from https://www.st.com/en/embedded-software/fp-sns-allmems1.html (Github source) and then I opened the project "STM32L476JG-SensorTile" with CubeIDE Version: 1.17.0 and then I tried to build this project without any modifications.The first problem I encountered is that the defined variable "STM32L4xx" seems not exist so I have to add it manually into the path and symbol property:However, I encountered another problem that the header file "STC3115_Battery_Conf.h" is not exist:I am completely stuck at this point since I cannot find it anywhere even in the Github....Can someone guide me how to build this project and download it to the SensorTile platform?Thank you!BR,Mike 

Hello,for a new project we are avalutaing the use of an iNEMO inertial module in conjunction with the motion fx library with the goal of doing position estimation with dead reckoning.My doubt is about the library, since we are forced to use a thrid party MCU (an ARM M4), can I import the library on any ARM M0/M4/M7 mcu? Or does it target ONLY st devices?Thank you,Davide

Hello,I searched the forum and found out a topic regarding the sensing technology of LIS3MDL sensor. The topic mentioned that LIS3MDL is a TMR sensor, however no support documents are included to further investigate the integrated circuit of the sensor.Moreover, I found several studies/papers claiming the LIS3MDL is an AMR sensor.My question is: Is there any official document available regarding the underlying sensing circuit and phenomenon the LIS3MDL sensor is using?Thank you for your time and support.

To begin, I am using the vl53l8cx breakout board from Pololu with a Nucleo-F446RE and PlatformIO. I have been having trouble getting the VL53L8CX to start ranging using the SPI2 interface. I get successful responses from the `_is_alive()` and `_init()` methods, but find that I get an error status of 1 from the call to `vl53l8cx_dci_read_data()` within the `_start_ranging()` method. Subsequently, a few lines down, `_start_ranging()` errors out with VL53L8CX_STATUS_ERROR.I tried following @RJRP 's solution here, but it didn't solve my problem.I have jumper wires from the Nucleo-F446RE to a breadboard. The wires are possibly too long, ~12cm in length.For clarity, the lines in question:/* Read ui range data content and compare if data size is the correct one */// This gives status = 1status |= vl53l8cx_dci_read_data(p_dev, (uint8_t*)p_dev->temp_buffer, 0x5440, 12);// This gives status = 255(void)memcpy(&tmp, &(p_dev->temp_buffer[0x8]), sizeof(tmp));if(tmp != p_dev->data_re

Hello,can anyone tell me what I am doing wrong?For example, I can't get app_mems.c (eCompass) to debug.The debugger does not stop when I set a breakpoint on subsequent function calls because, for whatever reason, the “SensorReadRequest” always has the value 0.:RTC_Handler(&msg_dat);Accelero_Sensor_Handler(&msg_dat);Gyro_Sensor_Handler(&msg_dat);Magneto_Sensor_Handler(&msg_dat);Humidity_Sensor_Handler(&msg_dat);Temperature_Sensor_Handler(&msg_dat);Pressure_Sensor_Handler(&msg_dat); I also need direct access to the variable “heading”. 

We have an issue with LSM6DSM and LSM6DSV. Sometimes they start consuming abnormally high current of 2.5 mA, which is about 200 times more than normal. Most reliably this can be reproduced when their SPI clock input pin 13 is driven by a week 47k pull-up / pull-down resistor.It seems that LSM6D becomes unstable and begins to oscillate. This happens when LSM6D is in any operation mode: in a full shutdown mode just after cold start, in a low power mode, any SPI speed, I2C disabled, etc.The reason why we drive SPI clock input by a week 47k pull down resistor is that LSM6D suppose to wake up the STM32L496RGT6 MCU from the shutdown mode. In the shutdown mode, the STM32L496RGT6 has only a week pull up/down option to drive its pins. But the voltage on the LSM6D SPI clock input pin 13 is about 7 mV and hence is well below the required logical 0 level. Documentation does not mention clock driver impednce and neither SPI nor I2C standards require low impedance input drivers.We found a tempo

I am trying to use the DATALOG1_V1.1.0\Utilities\Python_SDKWhen I call the script hsdatalog_data_export I get an error: "No module named 'click'What to do to make these scrpits work? Pyhton is V3.7.8