MEMS and sensors

I need to use 2 image sensors for tracking proposes, it would be nice if I could sync the two cameras.I see that provide configurable GPIOS with signals like PWM/ PULSE/ VSYNC/ START OF FRAME.Is there any application note/ reference design, on how to sync two image sensors ?  Do I need an external PWM for this? or one sensor can be master (to generate pulse) and to provide clock to Slave sensor?Also I would like to now if the two sensors can have the same clock source to sync MIPI clock.Thank you.

camera module cam-6gy-152vis with rockchip rv1106g3 boardBelow are the pin connections of the adapter board to rockchip let me know what is wrong in this like ffc cable is be have alternate connection at the ends of cable on that time if we reverse the cable first pin goes to 22nd pin vice versa.now my problem is will camera module will on with this connection or no ?Here are three things first image left side is adapter board schematic and right side rockchip ffc connection schematicbelow is image has camera module pinout which is snapped on the adapter boardUnable to detect the i2c on the rockchip and unable turn on the camera ?for more info i have attached full shematic of the both adapter board and rockchip.Thank you 

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? 

OverviewThe LSM6DSV80X represents a breakthrough in wearable technology. Its ability to measure both high- and low-acceleration ranges, combined with high energy efficiency and advanced processing capabilities, makes it an ideal choice for users who need detailed data analysis and improved performance tracking in high-impact sports and activities such as volleyball, football, tennis, boxing, and explosive jumping.This IMU provides a comprehensive solution for wearable devices, high-impact detection, and activity tracking, delivering an excellent combination of accuracy, integration, and efficiency.The LSM6DSV80X is the world’s first IMU to combine high-g acceleration measurement of up to 80 g and low-g sensing capabilities in a single package. It integrates advanced features, including edge processing and sensor fusion, to provide consistent performance and valuable data for sports-wearable tracking and high-impact detection.  The device supports edge AI capabilities, using a finite st

Hello,I tried to get the HP properly working for hours now, but I get zeros on all axes every third output.What ist wrong? I tried a lot of different setup variation buts always with similar result.When disabling FDS (HP function), there are no zeros in the data stream.In this example I shaked the sensor.##########################WHO_AM_I: 0x33LIS3DH found.--- Register-Verification ---TEMP_CFG (0x1F) = 0x00CTRL_REG1 (0x20) = 0x2FCTRL_REG2 (0x21) = 0x08CTRL_REG3 (0x22) = 0x00CTRL_REG4 (0x23) = 0x80CTRL_REG5 (0x24) = 0x00CTRL_REG6 (0x25) = 0x00REFERENCE (0x26) = 0x00FIFO_CTRL (0x2E) = 0x00INT1_CFG (0x30) = 0x00INT1_THS (0x32) = 0x00INT1_DUR (0x33) = 0x00INT2_CFG (0x34) = 0x00INT2_THS (0x36) = 0x00INT2_DUR (0x37) = 0x00CLICK_CFG (0x38) = 0x00CLICK_THS (0x3A) = 0x00TIME_LIMIT (0x3B) = 0x00TIME_LAT (0x3C) = 0x00TIME_WIN (0x3D) = 0x00ACT_THS (0x3E) = 0x00ACT_DUR (0x3F) = 0x00--- Configuration finished --- ms; X; Y; Z;INT1 56; 184; 1

In section 1.2 of DB5834Time-of-Flight (ToF) sensors software expansion for STM32Cube it is written that “The package is compatible with STM32CubeMX. It can be downloaded from and installed directly into STM32CubeMX, as described in UM1718”. I followed UM1718 but could not find “X-CUBE-53L9A1” in Tab “STMicroelectronics”. I’m using the CubeMX version 6.18.0. Also the upload of the zip-file via “From Local...” failed. The error message: “This file is eighter corrupted or not recogniced package. [...]”. How to proceed? Thanks for your help.

Dear Community,I am currently following the official MEMS Studio tutorial "Module 5 - MLC Configuration and Visualization" available on YouTube.I am using the following hardware and software setup:MEMS Studio version: 2.4.0 Board: NUCLEO-F401RE with X-NUCLEO-IKS4A1I was able to successfully complete all tutorial steps up to the Automatic Filter & Feature Selection (AFS) stage. However, whenever I click "Run" in the AFS tool, MEMS Studio displays the following error message:"Unexpected error with code 104 occurred during AFS request processing."The issue occurs consistently, even though I am following the tutorial exactly as shown in the video.Additional information:The PC has internet access. I tested both my company network and a mobile hotspot, but the error persists in both cases. No firewall events indicating blocked connections were detected. The board is correctly recognized by MEMS Studio and all previous steps work as expected.Could you please help me identify the cause of

Hello,I would like to evaluate  IIS2MDC mounted on MKI185V1 evaluation board using MEMS Studio. in the “Save to File” section I can choose Timestamp, Magnetometer, Magnetometer [LSB}, and Interrupt 1, but not Temperature, although the device has an internal temperature sensor. my setup:STEVAL-MKI185V1 on STEVAL-MKI109V3, FW: 3.79.1. MEMS Studio ver. 2.4.0 on Windows 11.Please advise,Shmulik

Hello, we are planning to use LSM6DSO in Mode 1, but PCB is fixed and pins 10 and 11 are connected to GND. This conflicts with LSM6DSO datasheet but I was wondering if it is still OK to connect them to GND. Can you clarify on this?

If I want to use tof to achieve gesture recognition, which can recognize all dynamic sliding and static classification: palm clenching, OK, digital gesture waving, static hovering, and can recognize the key points of the hand, which products should I choose

Hi  ,   he system operates in timing mode with lower limit detection at 1.1-second intervals and a measurement duration of 33 ms; the status code is read to verify accuracy, though misjudgments may occur—for instance, when no object is present, measured values may fall below the lower limit, requiring correction. Parameters: long-distance reference Spad count = 7; aperture Spads = 1; HV settings = 32; Phase calibration = 1; Offset micrometer = 7000 (for 100 mm); myXTalk compensation rate (Mega CPS) = 66 (for 600 mm).Why is the refSpadCount value obtained by our school less than 10?Increasing the measurement time reduces the likelihood of misjudgment, as I use a battery-powered device and cannot extend the measurement duration.

Please support to update how LPS27HHW pressure sensor can detect the fall of a human being.

Hi, I am evaluating VL53L8CX and couldn’t find anything in the data sheet about a programmable FOV. I require a FOV of 2-3degrees. Does this sensor support a programmable FOV to that size?Thanks,BH

Hi,I am using the NBP8FD4ST1 pressure sensor with the S32K146 microcontroller. The CS_B/WAKE-UP pin of the sensor is connected to a GPIO pin on the microcontroller.The logic analyzer signal mapping is as follows:D0 → SCLK D1 → CS_B D3 → READY D5 → MISO D7 → MOSIDuring the communication sequence, when I pull the CS_B pin low to request SPI communication, the READY pin is asserted as expected. After READY goes high, I send the SPIOPS register read command (0x00E1). However, the sensor always returns 0x0000 on MISO. As a result, the firmware validation fails, and the CS_B pin is subsequently driven high to terminate the transaction.Could you please help me understand whether my SPI communication sequence is correct or if I am missing any required step, such as the wake-up sequence, dummy transfer, or SPIOPS handling described in the datasheet?I have also attached the logic analyzer screenshots for reference.Thank you in advance for your support.Best regards,Pratyusha.  

Hi, I'm seeing a consistent issue where every sensor connected via I²C (as far as I can tell) produces 0 bytes of streamed data over USB:HTS221 (temperature + humidity) LPS22HH (pressure + temperature) STTS751 (temperature) IIS2MDC (magnetometer)At the same time, all SPI-based sensors stream normally:IIS3DWB IIS2DH ISM330DHCX (accelerometer + gyroscope)Both microphones also work correctly.Execution details:Board: STEVAL-STWINKT1BFirmware package: FP-SNS-DATALOG1 v1.5.1 (Utilities/HSDPython_SDK included)Host SDK: HSDPython_SDK (st_hsdatalog 3.0.1, st_dtdl_gui 2.1.0, st_pnpl 2.1.0), Python 3.10, Windows 10Connection: USB (WinUSB), using hsdatalog_cli.pyResult (consistent across multiple runs and after a full USB power-cycle of the board):Name                  Length----                  ------AcquisitionInfo.json     226DeviceConfig.json      28090HTS221_HUM.dat             0HTS221_TEMP.dat            0IIS2DH_ACC.dat         76608IIS2MDC_MAG.dat            0IIS3DWB_ACC.dat      1542000IM

9 axis gyroscope mems sensor available?

Hi,I am developing an object detection system using the sensor, integrated inside the inner wall of a toilet bowl to detect falling waste. I am experiencing persistent "Low Confidence" issues, and I am looking for expert advice on whether this is an inherent physical limitation or a configuration issue.Current Setup & Environment: Environment: Actual toilet bowl (highly reflective curved ceramic surfaces). Hardware Integration: The sensor is mounted behind a cover glass, and an active NIR/Visible fill light is installed inside the bowl to assist a separate camera system. Configuration: VL53L7CX_RANGING_MODE_AUTONOMOUS @ 60Hz. The Phenomenon: Static/Idle State: Even in this real-world environment (with cover glass and fill light), the sensor produces some "Low Confidence" data points even when nothing is happening. Dynamic Event (Object Drop): When an object is dropped, the frequency of "Low Confidence" reports increases significantly, often rendering the detection logic unrel

I have a VL53L4CD that I’m trying to use as a binary signal for detecting whether or not an object is within a specified range. In the default case with no detection thresholds set, GPIO1 is driven low when data is ready as expected, and I can continuously receive data from the sensor by reading when GPIO1 is low and then clearing the interrupt. I set the timing budget to 20 ms, and the intermeasurement time to 50 ms, as was done in the ULD example code (VL53L4CD_ULD_V2.2.3/Examples/Example_6_detection_thresholds.c) . As soon as I add the same call that the example code makes:  VL53L4CD_SetDetectionThresholds((Dev_t)dev_add, 100, 300, 3); At the end of my initialization sequence, GPIO1 no longer pulls down, nor does VL53L4CD_CheckForDataReady(TOF, &ready) signal ready. This is expected behavior outside of 100-300 mm, but I can force read the device regardless of ready status and see measurements within this window that are constantly updating. Is there another step in this process

Hello,I have a couple of devices using LPS28DFW pressure sensors.The sensors are configured as follows:INTERRUPT_CFG = 0x00, THS_P_L = 0x00, THS_P_H = 0x00, IF_CTRL = 0x00, CTRL_REG1 = 0x3C, CTRL_REG2 = 0x00, CTRL_REG3 = 0x01, CTRL_REG4 = 0x02, FIFO_CTRL = 0x02, FIFO_WTM = 0x64,All other registers are left at their default values.Usually they work fine, filling the FIFO with new data and generating an interrupt every second. However, I occasionally encounter an issue where the sensors appear to stop filling the FIFO for a period of time. The duration of this stall is not consistent, it can range from a few seconds to a permanent lock-up. During this locked state, I can still successfully read the temperature, and reading back the configuration registers confirms they are set as expected. After a power cycle and reconfiguration, everything returns to working correctly.Have you ever experienced this issue? Do you have any idea what might be causing it?

Hi,     When there is no object in front of the VL53L0x, all corrections have been made, but the following test data still appears. Why are the data so high?        

It will be great if you can provide I2C address change options as in many other devices on the market. There are some unused pins, why not use them to select different I2C addresses. Or if like in VL53L8CX have MISO+NCS not used in I2C mode. One may connect this pins to VCC/GND/SCL/SDA by 47k. So you have the option to preselect the address.it may be a hardware change in base device logic and so not solving any current problems, but useful for future devices.regardsChris

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

Hi everyone,I have been testing this sensor for my application using ESP32 based board and I found that the readings/values of ambient and nb target do not co-relate or give any context to the values of reflect, signal, spad and sigma.Based on my data I found that#1 Sigma - is the most reliable feature to filter noise#2 SPAD - is the most reliable feature to see/spot highly reflective zones#3 Reflect/Signal - gives more reliable data (context) around the reflective spots - usually complementaryBut#4 Ambient - shows the reflective spots but not all the time and not complement other features, does it signify something else? more of environment? It does change based on the object color - white is high and black is low - indoors.#5 nb_target - what does it even show/mean/signify? this is the most ambiguous feature. There is a option to choose up to 4, does that mean 4 signal are sent per zone? and its filtered based on the best if I choose 1? Are all the data/values of other features selec

HI,      It appears that the LSM6DSO32X has a higher shock/acceleration rating when compared to the automotive rated ASM330 IMU modules. 20’000g rating for the LSM6DSO32X and a 3’000g rating for the ASM330 modules.  Am I reading that right? The automotive modules have a lower shock rating than the consumer module?  thanks   

Hi,NUCLEO-F401RE + X-NUCLEO-IKS02A1, MEMS Studio v2.4.0. Flashed DataLogFusion (Applications\IKS02A1\DataLogFusion), connects fine (X-NUCLEO-IKS02A1, FW: 12.1.0), but I only get "Library Evaluation" (Data Table, Charts, Sensor Fusion...). No "Quick Setup" / "Sensor Evaluation" anywhere, including under Advanced Features. DataLogTerminal gives "Board not identified."An older tutorial (MEMS Studio v1.3.0) shows a "Sensor Evaluation" section with Quick Setup, Registers Map, FSM, MLC, Qvar — raw register access, not fusion output.Question: Which X-CUBE-MEMS1 firmware (if any) enables "Sensor Evaluation"/"Quick Setup" for this board combo? Is it firmware-specific or was it removed in MEMS Studio v2.x?Thanks!