MEMS and sensors

I know the VD55H1 is in preview phase and might be difficult to get it from ST. Although from the you tube videos it seems it is ready to be requested. Do you know what is the status to get one sensor? And if maybe is there any design house offering a module for testing it?

Hello,Please , can i use the module STEVAL-MKI228KA (ILPS22QS) with arduino ?Thanks

Hello,I am currently working on integrating the Smart Presence Detection (SPD) library on a Raspberry Pi Pico.Using the programming guide, I have managed to run the SPD algorithm, but I cannot get the “Approach” state to be detected correctly— it switches to “Presence” almost immediately.I believe the key is to tune the parameters contained in the Params_t structure, but I have not been able to find detailed explanations for each field.Could you please let me know where I can find a complete description of every parameter in Params_t, or any document that explains their effect on the algorithm?Thank you for your support.

Hello, I am trying to use the output of the LSM6DSL (accelerometer + gyroscope) to feed an orientation filter. While the accelerometer part is easy to interpret, I am having some trouble with the gyroscope. Apologies if my question is trivial, I have not found any clear answer on the subject so I must have missed something very obvious.   The LSM6DSL returns the angular velocity of the device as a vector of 3 Euler angles, one per axis. With this sort of representation this usually means that the underlying rotation R is a composition of 3 axial rotations, either intrinsic or extrinsic, such as R = R_x * R_y * R_z or any of the permutations. The actual order of the permutation being crucial. The documentation is not 100% clear to me in what order I should apply the axial rotations to describe R. There is no textual mention of this in the Application Note but on page 2 there is a diagram showing: The axis of the accelerometer The rotation Omega_Y, Omega_P, Omega_R Where I guess t

Hi Team,I came across the LSM6DSV16BX, which seems suitable for sports earbuds. Are there any compact earbud-style development boards or hearable devices available on the market?

Hello,I am looking for MEMS accelerometer for seismic application.We need low noise, up to 100Hz bandwidth, full scale +-2g range.I consider IIS3DHHC as a candidate, which has features as below:3-axis, ±2.5 g full-scaleUltra-low noise performance: 45 µg/√Hz16-bit data outputI would like to clarify what is the effective number of bits for 16bit output?How does the Sensitivity 0.076mg/LSB relates to the noise performance?Is there any other products with lower noise?Best regards,Lhagva

Hi based on the quaternion/Sensor fusion of LSM6DSV example I developed an application where I display the direction of a cube. Everything works fine, no drift, but: when I take the device move and turn it around, then put it back in the same exact position, the drawing on the PC is not back to the same direction as when I started.What is going wrong?Thx

Hi Team,We have the two boards as mentioned below.                      The Code generated in Cube MX is for the F401RETX(which configures the MCU inside VL53L8CX)In the above diagram , the host is the F401RETX . Please confirm , if our understanding is correct. Regards,Vikaash.K.B

Hello Everyone, I am currently using the vl53lmz_uld_api  tto process data measured by the VL53L8CX sensor. I have also used the "example_12_cnh_data" to retrieve data from my sensor. However, the incoming data seems completely incorrect, and I don't know where the issue lies. When I hold my sensor 20-25 cm in front of an obstacle, I receive highly unreasonable data: Zone : 40, Status : 0, Distance : 1383 mm Zone : 41, Status : 13, Distance : 1892 mm Zone : 42, Status : 5, Distance : 1371 mm Zone : 43, Status : 5, Distance : 1367 mm Zone : 44, Status : 5, Distance : 1347 mm Zone : 45, Status : 5, Distance : 1370 mm Zone : 46, Status : 5, Distance : 2448 mm Zone : 47, Status : 9, Distance : 2262 mm Zone : 48, Status : 4, Distance : 2977 mm Zone : 49, Status : 0, Distance : 1398 mm Zone : 50, Status : 5, Distance : 1381 mm     Can someone please help me to understand what i am doing wrong  here is my main.c:  int main(void) { /* USER CODE BEGIN 1 */

Hello  everyone,  I started learning programming on the STM32 ecosystem a few weeks ago, and I'm currently trying to get data from the VL53L8CX sensor using the NUCLEO-F401RE expansion boards and the vl53l8cx_api. I wrote a small program based on what I have seen in other projects, but my code doesn't work at all. While debugging, I discovered that the program jumps to the HardFault_Handler() function at this line in vl53l8cx_init().   status |= VL53L8CX_WrByte(&(p_dev->platform), 0x7fff, 0x00); Here is the essential part of my code maybe someone have any solution: #include "vl53l8cx_api.h" #include "main.h" #include "stm32f4xx_hal.h" #include <stdio.h> // Private variables --------------------------------------------------------- static VL53L8CX_Configuration tof_dev; // Sensor-Konfiguration static VL53L8CX_ResultsData results; // Ergebnis der Messung static int32_t status ; // Status für Fehlerbehandlung static void MX_VL53L8CX_SimpleRanging_Process(voi

Hello Everyone,I am currently working on a project to determine if it is possible to differentiate between a glass cup and other types of cups using VL53L8CX sensor data histograms, and also to detect the fill level. I have already collected data from the sensor using Example 12 provided in the Ultra Lite Driver, and I have written a small Python script to visualize my data.My first challenge is switching between the 4x4 histogram data format and the 8x8 format. The second challenge is interpreting the incoming bins_data to understand the differences between, for example, a ceramic cup (which is already possible using just the distance data) and an empty glass cup (using the histogram data to make a distinction, detect the edge, and determine the fill level).  Here below is my code stmIDE  Code//__________MY CODE ___________ p_dev.platform.address = 0x52; Reset_Sensor(); if (status != VL53LMZ_STATUS_OK){ printf("vl53lmz_init failed : %d\n"); return status; }

Hello all,I'm currently using the LIS2HH12 to sense the acceleration on the three axes. My aim is not to continuously read the acceleration value, but is to set a threshold for each axis and receive an interrupt when one of the thresholds is exceeded. The problem is that when I enable one of the three axes or all axes at the same time, by writing the appropriate values in the appropriate registers, an interrupt is generated even if no threshold is exceeded. This only happens when the interrupt on a particular axis is enabled for the first time, if I disable the interrupt and then re-enable it, no "false interrupt" is generated.At initialization, i set the following registers values:CTRL1 : 0x37CTRL3 : 0x88CTRL4 : 0x34FIFO_CTRL : 0xE0IG_CFG1 : 0x2AIG_DUR1 : 0x01All other writeable registers are set to 0.If I want to enable the interrupt on one or more axes, I write the LIS2HH12_REG_IG_CFG1, LIS2HH12_REG_IG_THS_X1, LIS2HH12_REG_IG_THS_Y1, LIS2HH12_REG_IG_THS_Z1 accordingly.For now, I fou

I'm trying to use the LPS27HHW in a 1 gram wildlife tracking device (water resistance required) and am wondering (a) how pick&place is supposed to pick up the sensor, and (b) how I can apply automated spray conformal coating to the board. I would have expected an option where the sensors are shipped with a small cap or film to facilitate p&p and to protect the sensor and that gets removed after assembly is complete... I'm probably missing something?

Hello, We received LIS2DH12TR bought from distributor source with full label and full lot code.Our QC team checked with measuring equipment, and we found the height is above the max 1.0mm. Is it considered normal phenomenon?   Referring to photo attached, thank you!  

I'm using the VL53L1X in the Arduino environment. During the initialization phase, I can read the device address as 0x29, and the device ID is EACC — so there's no issue with that.However, when I try to read the register VL53L1_FIRMWARE__SYSTEM_STATUS, a problem occurs — its value is not 0x01 as expected.I printed out the register value and it shows 2.Here's that section of the code: uint8_t system_status = readReg(VL53L1_FIRMWARE__SYSTEM_STATUS);SerialUSB.print("System Status: ");SerialUSB.println(system_status, HEX);  while ((readReg(VL53L1_FIRMWARE__SYSTEM_STATUS) & 0x01) == 0 ){    if (millis() - timeoutStart > 5000) {  // 延长等待时间至5秒      SerialUSB.println("Error: Boot completion timeout.");      return false;    }  }  SerialUSB.println("Boot completed successfully.");

I am putting together a water level sensor based on the vl53l4ed. The device will be in an outdoors setting with wild swings in environmental conditions. I am having hard time to design a cover / cover glass system for the TOF sensor. I have now concluded that it would be best to purchase a pre-made cover glass assembly for this sensor.  I expect accumulation of dust and other contaminants on the cover glass over time so I would prefer a zero calibration option with individual emitter and receiver covers separated by a divider. Are there commercial cover glass options available for the vl53l4ed model? I found a few options on the ST website but none for the vl53l4ed. Also, are there vendors in the USA who carry these cover glasses? If available, the vendor has to be NDAA-compliant. Thanks

..

HI,Could somebody tell me how to configure and access VL53L1 histogram data in detail.Thank you

Hello, Apologies in advance for the length of this post. I am looking for some advice as I am working on getting a cpp based callback for the VL53L4CD sensor, to do this I have written a file which should perform all the same setup as the driver provided however I am encountering a strange error that I cannot understand.Link to Github with Code, please see: real_time_drivers/VL53L4CD/VL53L4CD_LinuxDriver_V2.3.2/user/uld-driver for all relevant codeWhen I run my own file first, it sets the sensor to always return a status of two even if I then run the example executable (menu) provided as part of the the driver example this also returns a status of two.  HOWEVER, if I run these in the other order the sensor range is printed perfectly by my own program. This status will remain the same for any executable ran after the first and will be overwritten.  I have tried to find a conditional statement that might cause this however I have been unsuccessful in doing s

Greetings - what are the recommended maximum current ratings for the INT pin in either Push-Pull or Open-Drain? And FWIW, I was really surprised NOT to find this published in the datasheet...TIA,-Terry

I recently purchased a VL53L7CX and VL53L8CX, so I wanted to test the Motion Indicator functionality for each zone to show if the targets moved and how they moved via SPD of the software by STM except that there, when two people present themselves in front of the sensor, we only see one personHow to do it?

Hi Team,  Could you please share the detailed function of INT and SYNC in VL53L8CXV0GC/1?  We would probably use one sensor or two. If case of one sensor SYNC input doesn't add any value to the design. If two sensor used they'll probably share the proximity data(Just confirms if the object present or not) will it a have significance there.    Regards,  Mukesh

Maybe someone can help me. I bought five TOF050C-VL6180X time-of-flight (TOF) sensors, which also work with the Adafruit_VL6180X library, but they behave completely differently:Two:At a distance of 30 mm, the script shows: 0 mmAt a distance of less than 30 mm, the script shows: VL6180X_ERROR_RAWUFLOW "Raw reading underflow"One:At a distance of 20 mm, the script shows: 0 mmAt a distance of less than 20 mm, the script shows: VL6180X_ERROR_RAWUFLOW "Raw reading underflow"The other two: The script shows approximately the correct distance, and you can also Get unlimited close without triggering the "raw reading underflow."However, for my project, I need four sensors that are calibrated approximately the same. What can I do? Does anyone have any ideas?

Recently, I started a post about drift in the static level measurement using the VL53L4CX. I received some directions to continue the investigation, which I followed. I tested the performance by toggling the XSHUT pin as suggested, but it didn’t work. So, I proceeded with testing the drift using the ESP's temperature readings and found some interesting results.Using a fully black plastic bucket with around 10 mm of water, I observed that the drift occurred at two specific times: 8 AM and 6 PM. These times coincide with when the air conditioner turns on and off at the company where I work.The drift is perfectly parallel to the ESP’s temperature variation.I believe the sensor isn’t operating within the correct range during these temperature fluctuations, or it’s not applying the proper correction for them.I’d like to ask: Is there any way to make the correction more accurate, or even fully disable the temperature correction so I can calibrate it locally?I'm creating this new post because

Hello, I’m working on a project where I have a Nucleo F401RE connected to a 53L8A1 expansion board. I’m able to get the histogram plot with the ToF sensor on the expansion board but am wondering if I will still be able to get it if I use an external trigger with a VL53L8 ToF sensor attached to the expansion board. If anyone knows if this is possible or has done it before, input would be greatly appreciated.P.S. I am also using STM’s custom project, CUSTOM/VL53L8CX_SimpleRanging and I am using the histogram functionality with Example_12_cnh_data.c from their VL53LMZ_ULD folder. Thank you!