MEMS and sensors

Edit: I just effectively measured the cables, and they’re are 1.2m, not 50cm, I dont know where I got that number.I have been sitting on this issue for a long while, trying to fix it, so it is a long post. Please bear with me.Hardware setupThe system is based on an ESP32 WT32-ETH01 connected to two ST VL53L8CX ToF sensors (aliexpress pcb).The main hardware configuration is:* ESP32 WT32-ETH01* 2x VL53L8CX* Sensors have both NCS and SPI_I2C_N connected to GND* TCA9548A I²C multiplexer* 3.3 V supply for esp, sensors and multiplexer (Variable regulated DC power supply 1.2A max and 3.3v)* I²C SDA: GPIO 32* I²C SCL: GPIO 33* Separate LPN control for each sensor* Approximately 1.2m of multi conductor shielded cable between the controller and the sensors (also tried with ethernet cable)* No Cable shield connectedThe sensors work correctly when tested individually (with both long or short cables) and also worked together when using short cables. Also using one long cable connected to one sensor

I Can't Connect to X-Nucleo-53L5A1 board & Nucleo-L476RG in order to run the "VL53L5CX GUI Software" Firmware and driver installed properly according to the manual, but can not get it to connect.Do I have to use the STM32-F401RE board to get the software to connect? 

I have the X-NUCLEO-53L9A1 board and NUCLEO.H563ZI. I load the binary provided by ST (53L9A1_PostprocessSingle.bin) and I attach what I get in the serial terminal. I was expecting different data, like a distance value array that I could draw as bitmaps. How is this supposed to work? 

Hi,I've got an X-NUCLEO-53L9A1. The board is in volume production and the product page advertises "full system software supplied, including code examples and graphical user interface", but the only downloads on that page are hardware files (Gerber, BOM, schematic). There's no driver, no example code, no GUI, no user manual. I've searched the product page, this forum, and GitHub and found nothing.On the host side: I have a NUCLEO-N6 (N657X0), and I see UM3655 is written around the STEVAL-VL53L9 on the N657X0 — so that looks like the intended dev path. But the GUI was demoed on a NUCLEO-H563ZI. I can buy a H563ZI if that's what's actually required, but I'd rather not guess.So, plainly:- Does the 53L9A1 software package (driver + code examples) exist for download yet, and where?- Is the GUI available, and which host does it need — H563ZI, or does it run on my N6?- If any of this isn't public yet, what's the route to get it, and when does it land on the product page?I just want to get the

During the SMT process, air may get blown into the pressure port from the pick-and-place nozzle, will the sensor inside be damaged? 

I purchased  X-NUCLEO-53L9A1 with NUCLEO-H563ZI as it was recommended by ST. I just want to load the binary and see a simple ranging output value array. The binary provided didn´t work. Now it seams like they recommend  Nucleo N657X0. Could please someone clarify what board should I use so that there is a working binary provided?

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

Dear all,We are using the LIS2DW12TR on a custom PCB and have observed significant offset errors on the Z-axis, reaching up to ±20% of full scale.The sensitivity appears to be correct; however, instead of measuring the expected values of +1 g and −1 g, we obtain readings such as +1.17 g and −0.83 g. This suggests a substantial offset while the sensitivity remains largely unaffected.The X- and Y-axes do not exhibit this behavior and remain within specification.The most unusual aspect is, that the offset is not stable. It changes very slowly over time, typically over a period of several days, without any intentional modification of the hardware or software configuration.Has anyone experienced similar behavior with the LIS2DW12TR or identified possible causes such as PCB stress, assembly process effects, flux contamination, humidity, temperature exposure, or aging effects?Any recommendations for further investigation would be greatly appreciated.Best regards,Reto 

Hi, We are using the ASM330LHHTR in our design and would like clarification regarding the INT1 pin configuration. We intend to configure INT1 as an active-low interrupt with the output driver set to open-drain.However, the datasheet seems to indicate that active-low operation requires a push-pull configuration.Kindly let me know the details.Thanks

When setting high pass filter mode to HPM=01, the values in the reference registers (3Ah-3Fh) need different scaling compared to the data output registers (28h-2Dh). I am following the algorithm specified on p.18 of AN4662 using the following C code:void accel_set_reference(void){ int16_t xyz[3]; lis2hh12_acceleration_raw_get(accel1, xyz); // extra dummy read lis2hh12_acceleration_raw_get(accel1, xyz); xyz[0] /= 8; xyz[1] /= 8; xyz[2] /= 8; lis2hh12_xl_filter_reference_set(accel1, xyz); lis2hh12_xl_filter_hp_bandwidth_set(accel1, LIS2HH12_HP_ODR_DIV_50_REF_MD); lis2hh12_xl_filter_out_path_set(accel1, LIS2HH12_FILT_HP);}For some reason, I need to divide the raw acceleration values by 8 before setting them as the reference values.  Observe the graphs of acceleration data I obtain (the step change occurs when this function is called). First, without scaling down by 8:Now when scaling down by 8:Why is this scaling necessary? It is not documented anywhere (as far

Hello Team, We are using a custom board based on QCS8550 processor with LE r90 release. This release has lsm6dsv driver available as part of the ssc framework of the qualcomm. Our custom board includes two LSM6DSVTR IMU sensors which are interfaced over SSC (sensor core based) I2Cs and we are able to get the data through see_workhorse (i.e. qualcomm's userspace utility for sensors) Use Case Requirements: There is a requirement from client regarding sampling the data from IMU sensors on the edge of the reference signal which needs to be provided on the INT2 pin of the LSM6DSVTR sensors. Same reference signal also work as sync signal for the camera as well. so we can consider like sampling the data of IMU and capturing the frame over camera should be somewhat simultaneously. Current Status:In the current driver implementation located at:source/adsp_proc/ssc_drivers/lsm6dsvFrom the driver code analysis, we observed that data is currently being received using a FIFO-based mechanism.Additio

Product https://www.st.com/en/mems-and-sensors/lsm6dsox.htmlAbout the below datasheet description, I want to confirm exact I2C Fast mode Plus timing. Should this SETDASA/ENTDAA follow all timing parameters as I2C Fm+? For NXP I3C, it’s not hard to set a suitable baud rate for this, but it’s impossible to meet all timing for a ENTDAA operation. Can ST I3C IP run ENTDAA with I2C timing to meet your sensor product?  

Hello,I am using the STWIN.box with the DATALOG2 firmware and would like to acquire data based on an external trigger signal from a speed sensor.My speed sensor provides an open-collector output, which is connected through appropriate signal conditioning to the STWIN.box.I would like to know:What is the recommended way to use an external GPIO as a trigger source in DATALOG2? Can a GPIO interrupt (EXTI) be used to start data acquisition or mark events in the recorded data? Are there existing examples in DATALOG2 that use external trigger inputs? Which GPIO pins are available for this purpose on the STWIN.box? For an open-collector speed sensor output, should I use an internal pull-up or an external pull-up resistor?My goal is to trigger or synchronize vibration measurements with the rotational speed signal.Thank you.

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

Hi ST community,Below is what I have setup for the sensorhub interface between LSM6DSO and H3LIS331DL Goal: Read H3LIS331DL WHO_AM_I (0x0F → expect 0x32) via LSM6DSO Mode 2 sensor hub (MCU ↔ LSM on main I²C; H3LIS on SCX/SDX).SetupH3LIS: CS→VDD (I²C), SA0→GND (addr 0x18), SCL/SDA→LSM SCX/SDX Hub: 1 slave, MASTER_CONFIG = 0x4C (WRITE_ONCE | SHUB_PU_EN | MASTER_ON), SLV0 read of 0x0F Trigger: internal (XL ODR ~104 Hz, START_CONFIG = 0) — not using INT2 / H3LIS_DRDY for this Readback from SENSOR_HUB_1 with embedded-page access (SHUB_REG_ACCESS=1)What we seeLSM6DSO itself is OK (WHO = 0x6C) After arming the hub: STATUS_MASTER ends as 0x09 → ENDOP=1, SLAVE0_NACK=1 SENSOR_HUB_1 = 0x00 (expected 0x32) Scope on SCX/SDX: lines go from low → high when hub pull-ups enable, then stay high — no visible I²C clock/data bursts Same result after resoldering / swapping H3LIS; also tried addr 0x19Question: With Mode 2 + internal XL trigger, why would we get SENSOR_HUB_1 =0x00 . It seems that the sensorhu

Hi,I am using the VL53L7CX in an object detection system.Today, I found that the sensor does not detect black objects well. It can only detect a black object at a very short distance, approximately 10 cm.Is this the expected behavior?If so, what is the maximum detection distance of the VL53L8CX for a black object?My application requires the sensor to reliably detect a black object at a distance of about 50 cm.Is there any way to improve the detection performance for black objects, such as changing the configuration or tuning any parameters?Thank you.

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

Dear All,I have a query regarding VL53L4CX voltage requirements. The data sheet mentions the typical voltage for AVDD is 2.8 and for IOVDD is 1.8V/2.8VThere is no separate IOVDD pin for VL53L4CX isn't it. So the I2C lines work with 1.8V MCU voltage also with AVDD and AVDDVCSEL at 3.3V? Thank you,Ravi

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

Hey there,I have made a working implementation of the VL53L9 tof lidar sensor for linux.You can find it here:https://github.com/jonferran/vl53l9cx-pi-lidar Jon

I made a linux kernel driver for VL53L9 with ~ 10 FPS.Tested on Radxa Dragon Q6A with STEVAL-VL53L9https://github.com/momoisgoodforhealth/st-vl53l9-i2c-kernel-driver

Hello ST Team,Good morning!I am currently working on integrating the VL53L9 sensor with the STM32N6570-DK development board. I have successfully obtained the STSW-IMG053 software package, which is designed for the STEVAL-VL53L9 evaluation board using the MIPI CSI interface.However, my target hardware configuration is different. My objective is to use the following setup:Software Package: STSW-IMG053 Host Board: STM32N6570-DK Sensor Board: X-NUCLEO-53L9A1 Communication Interface: I3CI would like to port the STSW-IMG053 software package to support the X-NUCLEO-53L9A1 evaluation board while retaining the STM32N6570-DK as the host platform.I would appreciate your guidance on the following points:Is there an official procedure or application note describing how to port STSW-IMG053 from the STEVAL-VL53L9 (MIPI CSI) platform to the X-NUCLEO-53L9A1 (I3C) platform? Are there any reference projects, example applications, or software packages available for the STM32N6570-DK with the X-NUCLEO-53L9

**VL53L8CX ranging stops after a few frames (2-4 typical, up to 28 seen once) clean status, no error on three independently-built boards****Setup:** Custom board, VL53L8CX (I2C mode) + STM32G0B1KBU6 host MCU, ULD driver, 4x4 resolution, 10Hz continuous ranging mode, 30ms integration time. **Symptom:** `vl53l8cx_init()` and `vl53l8cx_start_ranging()` both succeed. Ranging produces good frames (plausible per-zone status/distance data) for a small number of frames usually 2-4, occasionally more (saw 28 once) then `check_data_ready()` starts returning `VL53L8CX_STATUS_OK` with `data_ready` staying false indefinitely. No error code in the common case. I2C bus itself stays healthy throughout (clean ACKs on every transaction, confirmed via logic analyzer).**One-off exception:** on a single occurrence, `check_data_ready()` returned `0x84` instead of `0x00`. I found the earlier thread here (linking below) where a `0x81`/`0xC5`/`0xCA`-style status was identified as a GO2 (internal MCU) error. I

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.

I'm trying to start working with Evaluation board based on VL53L9CX Time of Flight sensorIn I2C, I'm having a problem with identifying the component addressI find address 55 and not 29The connection looks like thisGND to GNDSDA to SDASCL to SCLXSHOUT to 3V33V3 to 3V3I removed resistor 25 for internal clockAccording to the datasheets, it seems that 55 is the EEPROM ID