MEMS and sensors

Hello, I am using VL53L9CX with adapted drivers for ESP32 / Arduino environment. I am able to read values and play with the settings but I am a bit worried with the precision I get. I run the sensor in precision mode, 4ms exposure time. My bench is indoor. Sensor facing the ground ( 1 m ish, wood) or the roof (1.6m ish, white ceiling). Resolution is 8 x 6 (Binning 12). I have radial to perpendicular conversion enabled so I am expecting to see all distances being equal +/- precision across the cells of the frame (excluding corner cells maybe). According to table 34: Precision for “ambient mode 24x20” profile from the sensor datasheet: (results are better for 24*20 then they are for 54*42, so I assume it is the same or better for 8*6 compared to 24*20)I am expecting less than 0.8 mm difference between the values but instead I get 50 mm - 100 mm or more of difference. So I was wondering, is there some specific settings to enable to achieve such precision / accuracy ? PCB is of my own (not

I am looking for the STEVAL-VL53L9 evaluation board for vl53l9cx, but it is out of stock at all distributors I checked.could you please let me know the expected availability / ETA, where i can buy it or, if there is any similar alternative board with same specs.

Hello, I was wondering where can I find the Pick n place file to create the dev board. on the official site there is the BOM and the gerber files, but without the pick N place I can’t actually assemble it.Thanks for the helpRoman

Hello Team,I am using the STM32N657x0-Q Nucleo board with the STEVAL-66GYMAI1 (VD66GY) camera board connected via FFC. Both CN8 and CN10 are connected to the PC, and I am viewing the camera stream through UVC.I tested the official precompiled HEX files from: X-CUBE-N6 Camera Capture STM32N6 Getting Started Object Detection In all cases, the image is heavily blurred. Objects appear relatively clear only at approximately 1–2 cm from the lens, while anything beyond that distance becomes significantly out of focus.I attempted to adjust the M12 lens focus across its full rotation range, but no noticeable improvement was observed. The same behavior occurs with multiple example projects and unmodified hardware.Could you please advise which of the following areas is most relevant to investigate? Camera board compatibility with STM32N657x0-Q Sensor/lens configuration in the example firmware Lens focus or alignment issue Defective lens or hardware issue Recommended reference project/co

Section 2.5 of UM3656 says "For a complete description of the library capabilities, refer to the vl53l9-transform-c documentation." The X-CUBE-53L9A1 v1.0.0 package ships Documentation/ media-object/transform-c.chm and media-c.chm, but those document the generic transform framework they do not contain any mention of VL53L9, binning or resolution.In vl53l9-transform-c, _retrieve_output_size() accepts only raw frame sizes 14842 (54x42) and 3844 (24x20); the stream capability tables likewise list only those two resolutions. Calling the pipeline at other binnings is rejected, so 18x14, 12x10, 8x6 and 4x4 produce raw data with no calibrated depth.The underlying algorithms appear resolution-generic — vl53l9_algo_extract() takes frame width/height, crop offsets and binning as parameters, the calibration offset map is bicubic-resized to arbitrary width/height, and the radial-to-perpendicular map is computed per width/height/binning.Questions:Is support for the other binnings planned, or delibe

Hello,I would like to test the VL53L9CX using the GUI interface compatible with the X-NUCLEO-53L9A1 board. This software appears to be the STSW-IMG052. The ST webpage for this software returns a 404 error. Were there issues with using this software that led to the download being suspended, or is it simply a broken link on ST's servers?Thanks for your answers,Christophe

Hello,I understand that ToF sensors inherently have limited performance under daylight conditions. However, I would like to know which ST ToF sensor family currently offers the best performance in daylight, regardless of whether it is a single-point or multi-zone sensor.The VL53L9 series looks very promising for our application, but unfortunately, its cost is above our target budget. Therefore, I am looking for a more cost-effective alternative that still provides good performance under daylight conditions.A wider FOV would be preferable for our application.Would it be reasonable to select a sensor based primarily on its maximum specified detection range? If so, the VL53L1 series seems to be a good candidate. However, I am not sure whether the maximum specified range is the best parameter to use when comparing sensors for real-world daylight performance.I also assume that a wider FOV reduces the number of photons received per unit area, which could potentially reduce the sensor's perfo

Good afternoon, We are currently working on the development of a board intended for use in explosive areas. For the design calculations, could you please confirm the junction-to-ambient thermal resistance (θJA) of the LSM6DSV80XTR? In the Datasheet it is not avaliable.

I'm testing the VL53L9CX sensor with the X-NUCLEO-53L9A1 board. I'm conducting my tests with the Nucleo H561ZI board and the X-CUBE-53L9A1.zip software stack.The sensor works correctly indoors. However, outdoors, when moving from shade to full sun, the sensor malfunctions.The software returns the error: VL53L9_ERROR_INVALID_STATE. why?In the datasheet, this isn’t a description of all registers? So I cannot clear this error without resetting the device!Can have a complet datasheet of the product?

Wondering if VL53L9CX generates per-pixel histograms?It looks like there is no relevant information either in the datasheets or the released firmware. Many thanks,Z

In Section 5.1 of datasheet for VL53L9CX, it says “Refer to the postprocessing technical note (TN1596) for more details of the data formatting, processing, andfilter functions.”But I cant seem to find the TN1596 document. I am looking for information on the distortion correction on the raw depth output.

Did anyone have issue with freezing LPS22DFsensor?Have it connected using 4 wire SPI at 3.3 and 3.3  Volts. It successfully starts and reads temperature and air pressure once and than stays at the same value with no updates until I reset power on it. I can still read the Who_Am_I register which returns the correct valie (zeroed every time after it is read, so no doubt it reads every time) but the Air pressure and Temperature registers not updating. I use NoFIFO setting and sensor updating once per second. What I may be doing wrong?I do not use burst mode for reading and read individual bytes separately (not sure why but burst reading does not work for me)Using MikroC compiler.and PIC18F25K83 MCU

Hello ST Expert,We have been experiencing a number of shorts and opens on the IIS2DLPC and suspect issues with our solder mask layer. We have tried opening the solder mask under the component and have tried leaving the solder mask under the component, please see images below.  We have experienced shorts and opens using both of these methods. Could you please provide the recommended solder mask layer for this component? Thanks, Sam 

When testing the gyroscope of this product (LSM6DSV80X) we noticed that the noise density on each gyro axis is different with z being the lowest. This was observed on the dev-board (STEVALSMKI109DA) both in high performance and HAODR modes. The ratio between x and z is particularly noteworthy. Is there an explanation for this? The datasheet only reports one noise density so I am assuming that all axis should be the same. The same characteristics has been found on two different units. N.B.: Plain implies high performance. Rn is the noise density 

Hi, STNow for my STEVAL-MKI225A Board which contains LPS28DFW Barometer sensor I Used the application “read_data_polling.c” which is running on “NUCLEO-F401RE Board” to test the sensor with the default example configurations which are:md.odr = LPS28DFW_4Hz;md.avg = LPS28DFW_16_AVG;md.lpf = LPS28DFW_LPF_ODR_DIV_4;md.fs = LPS28DFW_1260hPa;and I noticed that when I’m getting the data in the while loop, It works correctly only with I2C Standard Mode (100KHz) and it stucks with fast mode.but the main problem is when I’m adding delay or another code execution to the while loop, It also stucks and doesn’t work unless I removed the delay or the code added. 

We encountered an issue with the MPXM2053GS sensors: several units showed no output after SMT assembly. Decap analysis revealed that the die in the failed parts was damaged. We would like to understand whether this was caused by mechanical mishandling or other factors, and what measures can be taken to prevent recurrence. 

We visually inspected the surface of the die of MPXM2053GS, which was covered by gel. We found some of them were not intact. there were holes and cracks on the gel. Although the electrical tests were passed but we are concerned about the long term reliability. Could someone advise if this is a normal phenomenon caused by the packaging process？ 

Hi,I'm measuring the power consumption of the LIS2DUXS12 for FSM, MLC, and the step counter with or without Smart Power mode (SMART_POWER_EN bit in CTRL1). The current reduction matches my expectations (e.g. ~13.3 µA down to ~8.2 µA with 1 FSM program running). AN5909 describes the mechanism as dynamically scaling the supply current of the embedded function hardware blocks between "operating level" and "lower non-operating level".My question: Is there any trade-off to enabling Smart Power mode besides the current savings? For example:Any added latency? Any impact on accuracy? Any recommended ODR for Smart Power? Any settling time when switching between operating and non-operating levels?I couldn't find this addressed in the AN5909 or the datasheet, and I haven't found any existing thread relating to this. Any clarification would be appreciated.Thanks!

Does anybody know what the marking KCY547C means? Is it normal that there are several markings in one reel? 

We are looking for a more details on STDES-ESP01 product and product which does cuffless BP measurement as discussed in this video. 

Hi,I am evaluating the LSM6DSV16X for a project that requires gyroscope Angular Random Walk (ARW) and In-Run Bias Stability specifications. I understand these AVAR (Allan Variance) parameters are not tested at production level and therefore not included in the datasheet.However, I noticed that ST has previously shared characterization data for related parts under the same request:- LSM6DSR: https://community.st.com/mems-sensors-48/what-is-the-bias-in-run-stability-instability-of-the-lsm6dsr-gyros-and-accelerometers-41777- LSM6DSV16BX: https://community.st.com/t5/mems-sensors/bias-instability-and-random-walk-of-lsm6dsv16bx-and-ism330dlc/td-p/574922 Could someone from ST please share the equivalent characterization results for the LSM6DSV16X (gyroscope, and accelerometer if available)? Specifically, if possible, could you provide the full Allan Deviation plot (σ(τ) vs. averaging time τ) rather than just the extracted ARW / bias instability numbers — we need to see the noise floor and cor

Hello, I would like to use a magnetometer to develop a small system that can discern the presence of a certain object with a magnet mounted on top of it. For this reason I got a X-NUCLEO-IKS5A1 as a starting point.From my understanding the faster approach was to connect the NUCLEO board NUCLEO-F401RE (which I already had) to the aforementioned X-NUCLEO board with the software MEMS-Studio.So I followed the procedure explained here:  and applied it to the “new” X-NUCLEO -IKS5A1 board (instead of the IKS4A1 described in the video).I’ve successfully programmed the board with the supplied firmware (STMicroelectronics/MEMS Studio/firmware/mems-studio/x-nucleo-iks5a1/nucleo-f401re/DataLogExtended.bin, Interface MASS STORAGE, Device_ NODE_F401RE).But when I try to connect the board it says:And I cannot go further with the procedure.Is there something wrong with my procedure? Any idea of the issue?If not, how can I start using this board? Starting from an STM32CubeMX project?Thank you for your

HelloI have a NUCLEO-U545RE-Q + IKS4A1 board, I want to connect with MEMS Studio 2.4.1 via tutorial The main problem that I cannot find the DataLogExtended code for any board and my NUCLEO-U545RE-Q isn’t compality with orther binary firmwareQuestion: How can I connect with MEMS Studio by DataLogExtended firmware with my hardware NUCLEO-U545RE-Q + IKS4A1

Hi there!I'd like to use the STEVAL-CAM-M01 P-board to evaluate the VD55G0 BrightSense image sensor with the Discovery kit for the STM32N6 MCU (STM32N6570-DK). The discovery kit does have a camera connector, however, looking at the schematics it seems that the polarity of the CSI data and clock lines is swapped compared to the P-board. Everything else looks fine.Is it possible to use the P-Board with the Discovery kit without destroying either of the two? ST's marketing material (slide 33) seems to suggest it is possible but the schematics are unclear. Note that a similar question has been asked in the MCU forum, but it was suggested to ask in this forum to be sure. Also note that I'm not asking about software driver support here, only hardware compatibility.Camera connector on STM32N6 discovery kit: Connector on P-board:Thanks a lot!Michael

Dear STMicroelectronics Community,I am performing a thermal analysis for the following component:MPN: LSM6DSOXTRPackage: LGA-14L, 2.5 mm × 3.0 mmCould you please provide the following thermal parameters for this exact MPN and package?Junction-to-Ambient Thermal Resistance, RθJA (°C/W) Maximum Junction Temperature, Tj(max) (°C)Please also provide the PCB/test conditions associated with the RθJA value, if available.If RθJA or Tj (max) is specified in a separate package thermal document, application note, or internal technical document that can be shared with customers, please provide the relevant document/reference.Thank you.Best regards,Bajas.