MEMS and sensors

Hi, I am trying to merge the left and right wrist tilt configuration examples so that I have left wrist tilt on the FSM1 routing to INT1 and right tilt on the FSM2 routing to INT2 on LSM6DSV16X. I am sharing the merged config and the reference configurations being used(link). I have been trying to find an example for multi FSMs in MEMS studio but can't find any. Issue is thig config works fine for right wrist but not for left wrist. Any help in this regard would be appreciated. thanks

 Title: VL53L8CX pulls SCK line low on ESP32 – PCB or power-up issue?Hello everyone,I’m currently developing a prototype using a VL53L8CX sensor together with an ESP32 controller. On our PCB, the sensor seems to permanently pull the SCK line low. This is already the second revision of the PCB, so with fairly high confidence I can rule out a basic PCB layout or routing issue. Here are my questions: Can you spot any possible mistakes in the schematic?Do you know under which conditions the VL53L8CX might actively pull SCK low? (To me it looks like an internal IC problem)Could this be related to the power-up or reset sequence of the sensor?Do you have any general debugging tips for this kind of issue?The SCK line is connected through a TXS0108 level shifter. With a different I²C device, the TXS0108 works perfectly fine, so I’m not sure if it’s involved here — but could the TXS0108 still cause problems in this setup?On the software side, I already tried:Running an I²C scanner

HiI am using Vl53L1X to measure dark surface upto 1000 cm far.. I am using a split cover glass(specifications attached). The benefits of using the split cover is that it prevents crosstalk. But even after attaching the cover, the distance measured by the sensor decreases when the object moves away from the sensor.  Do I still need crosstalk calibration with cover glass or the cover is not ok.I have configured my sensor as follows:status = VL53L1X_SetDistanceMode(dev, 2); /* 1=short, 2=long */ status = VL53L1X_SetTimingBudgetInMs(dev, 100000); /* in ms possible values [20, 50, 100, 200, 500] */ status = VL53L1X_SetSignalThreshold(dev, 1024);//500); VL53L1X_SetROI(dev, 16, 16); // Full FoV (start here)  

Dear Community,I think I have encountered an uncommon problem. The SW_RESET bit in CTRL3 on the lsm6dsv16x does not change to 0 again. In https://www.st.com/resource/en/datasheet/lsm6dsv16x.pdf it states that after the software reset this bit is automatically cleared. Even after disconnecting the power and doing a reboot, also of the chip itself this bit wont change back to 0. I use https://github.com/STMicroelectronics/lsm6dsv16x-pid to communicate with the chip, and other things like reading who_am_i and so on work normally. But otherwise, I only get meaningless readings from the sensor. What can be done about this, especially the reset bit?Thanks and greetings

Hello ST community,I am working with LSM6DSOX and using the Machine Learning Core (MLC) configured through UNICO GUI. My goal is to use the sensor as a low-power wake-up source for my system.System overview:MCU: nRF52840 (goes to deep sleep / system OFF)Sensor: LSM6DSOXInterface: I²CInterrupt: INT1 used as hardware wake-up sourceMCU is sleeping, so no software filtering is possible before wake-upWhat I want to achieveI want the MCU to wake up ONLY when one specific gesture occurs (for example a “wave” gesture).INT1 should assert only for this one gestureINT1 should NOT trigger for:static staterandom shakeother trained gesturesnoise or motion not matching the target gestureWhat I have already doneI successfully trained multiple gestures in UNICO GUI using MLC.I can export and load the UCF correctly.INT1 triggers when any gesture is detected.I can read MLC status (Get_MLC_Status) after MCU wakes, but this does not help because:The MCU must already be awake to do software filtering.I need

Hello,I am trying to use an accelerometer LIS2DUXS12 in ultralow power mode using the FIFO with a threshold. To initialize it, I configure the registers using the driver's functions in this order:sw resetinit setfifo_mode_set (operation = LIS2DUX12_BYPASS_MODE to reset the FIFO, store = LIS2DUX12_FIFO_1X and xl_only = 1)fifo_batch_set (dec_ts = LIS2DUX12_DEC_TS_OFF and bdr_xl = LIS2DUX12_BDR_XL_ODR)fifo_mode_set (operation = LIS2DUX12_FIFO_MODE, store = LIS2DUX12_FIFO_1X and xl_only = 1)fifo_watermark_setfifo_stop_on_wtm_setpin_int2_route_setmode_setI use odr=25Hz ULP, fs = 2g.Everything works fine as long as I setstore = LIS2DUX12_FIFO_1Xand bdr_xl = LIS2DUX12_BDR_XL_ODRbut as soon as I add a divider to BDR (for example I set bdr_xl = LIS2DUX12_BDR_XL_ODR_DIV_2), the FIFO remains empty forever.Same result if I usestore = LIS2DUX12_FIFO_2X instead of store = LIS2DUX12_FIFO_1X.I read the number of elements in FIFO after a timeout with lis2dux12_fi

Hello STMicro Community,I am working with the LIS2DH12 accelerometer, STEVAL-MKI109V3 and MEMS Studio environment. My application is the measurement of vibration on rotating equipment.A vibration signal of 118Hz is being applied to the board and using ODR=400Hz, Scale +/-4g.I am noticing a significant difference in magnitude measurements when switching the filter bit on vs off (FDS). See attached image of the time series data yellow (Z-axis) where:- with FDS=0 I see -500 to -1500 for ~1000mg range- with FDS=1 I see -800 to +800 for ~1600mg rangeI DO expect to see gravity getting removed but NOT an increase in the magnitude. Is there an explanation for this?-Edwin 

Hi Community,I’m just finishing off development of a product containing VL53L4CD and need to start to think about approvals etc. ready for product launch. The product as a whole relies on human interaction, so users will be physically close to the product and therefore the beam.Judging by the datasheet for the part, there is no need to perform any testing for eye safety, relying instead on ST’s own certified testing, provided that we use the device in accordance with the datasheet (which of course we do) and there’s no attempt to focus the beam (which there isn’t). This will all be wrapped up in a detailed technical file, along with ST's certs.The artwork on the product carries the Class 1 laser radiation logo and in the instructions the customer is warned never to attempt to focus the beam, nor to stare into it.Is this sufficient due diligence, or have other developers done more and if so, what?TIA.

Hello,I have a PCB with two microphones (IM66D132HV01) with an STM32U575RGT6 (64pin) micro.Both microphones are connected (L+R) to a single input {PC0, PC2} = {MDF1_SDI4, MDF1_CCK1}Firstly I cannot find any example code that produces output samples in the MDF1_Filter3->DFLTDR,  MDF1_Filter4->DFLTDR data registers -- they are always zero.I can get the MCU to produce a clock signal and I can see a data bit stream coming to the MCU, from the microphones.       As I was a bit stuck, I resorted to using CubeMX to hopefully get some working code --- however -- with CubeMX the common clock was no longer visible.I also notcied that if I set up MDF1_F3, and MDF1_F4, that  I cannot tell CUBEMX that actually I only need the 'MDF1_SDI4' input since the two filters share the same MDF1_SDI4 bus (one outputs on low clock, the other on high).Also,  I'm looking for some sample code that can give me interrupts for each of the left and right samples, as

I just like to configure the ISM330DHCX for vibration measurement. Is that an example or a sample code(using its C driver ) of it somewhere. Please give me a pointer. Thanks.

Hello, I was told by the services to check out the forum for guidance.I am working on a project that requires surface reconstruction using non-optical based solutions. I was thinking of attaching a motion sensor module to track the handheld scanner which will be moving along the surface, and then using the obtained sensor data to plot the point cloud in 3D.Is this a feasible idea using the motion sensors for accurate tracking & reconstruction? If so, what are the recommended products (something like LSM6DSV)? How is the development experience using MEMS-Studio? Thank you!

Hi Guys. I am just trying to receive data from sensors accommodated on STEVAL-BCN002V1B (Blue Tile board) using application  "BLESensorDemoCentral" running on STEVAL-IDB008V2  board.I am able to detect all services that are advertised by Blue Tile board using "BLESensorDemoCentral" application running on STEVAL-IDB008V2 board, which are "ServW2ST", "ConsoleW2ST" and "ConfigW2ST" services.But I am still unable to find characteristics of all the three services described above. Q1 : What changes ( Master context object ?, gatt callbacks ? ) shall be done on side of "BLESensorDemoCentral" application running on STEVAL-IDB008V2  to get all characteristics of all services  that are received from  by Blue Tile board  (STEVAL-BCN002V1B)?Q2. Does somewhere exist a code, that I could use as clue ?Thanks for Your hints.  PQ.

 I am currently trying to control a VL53L8CX sensor via SPI communication from the microcontroller mounted on a Crazyflie drone.However, inside vl53l8cx_check_data_ready(), the values in temp_buffer became as follows. Indices [0] to [2] look correct, but at temp_buffer[3], the condition  ((p_dev->temp_buffer[3] & (uint8_t)0x10) == (uint8_t)0x10)evaluates to false.What exactly is this comparison checking?When temp_buffer[3] returns an incorrect value like this, which specific part of the communication or control process is likely failing?temp_buffer[0]: 0x0temp_buffer[1]: 0x5temp_buffer[2]: 0xC5temp_buffer[3]: 0xC1

Hello, I have a Sensor Tile Box Pro and I have a question about the accelerometer. Why, if it is still, does it show movement on the axes depending on the position of the Box Pro with an offset of 1000?

Hi, I'm supporting a legacy product which uses this older sensor, VL6180X.Where could I find the API source code for download? It seems that all links for "STSW-IMG003", "STSW-IMG011" etc. which are listed in the docs have been erased from the site. Could someone provide a working link to the latest API version, or perhaps just attach the .zip here for posterity?Thanks in advance!

SummaryOur eventual product will use the LSM6DSV320X but right now, all we have is an LSM6DSV80X chip on the STEVAL-MK1247A breakout board. The products are close enough that I can test on the 80X. I am currently trying to implement the burst read feature of the chip. I am having two main problems when doing the burst read:1. After some time, I am getting tags in the FIFO for parts of the sensor I have not enabled (e.g. I get a temperature tag despite not having enabled temperature batching)2. For some reason, my INT1 pin is triggering even though the FIFO watermark is not met. PlatformBoard: Nordic nrf52840-dkOS: Zephyr RTOS (nRF Connect SDK v3.2.0)Sensor: LSM6DSV80X on the STEVAL-MK1247A -- SPI Clock at 8 MHz BackgroundIn Section 9.8 of AN6119 it describes how to retrieve data from the FIFO and there are two methods provided:1. Read the FIFO_STATUS1 and FIFO_STATUS2 registers to check how many words are stored in the FIFO.This information is contained in the DIFF_FIFO_[8:0]

What is the marking on the bottom side of these sensors i.e. VL53L1X and VL53L1? for eg. on the bottom of VL53L1X it is written VL53LIB...so what is the marking for VL53L sensor. Basically I want to know how can I distuingh between these 2 sensors as both of these sensors returns the same model and module id.

Hi, I designed a special board that includes the LSM6DSO32 sensor. I want to get step count data, for testing I am using ESP32-CAM with LSM6DSO32 via I2C. I have followed the basic routine mentioned in application notes. I can get only garbage value. I will attached sample code for reference. Can you check and help me step by step what to do? First code give step count 0 always. For second code I attached screenshot. Please look into it and tell if anything need to change.     #include <Wire.h> // LSM6DSO32 I2C address #define LSM6DSO32_ADDR 0x6B // Register addresses #define FUNC_CFG_ACCESS 0x01 #define PAGE_RW 0x17 //0x02 #define PAGE_SEL 0x02 //0x03 #define PAGE_ADDR 0x08 //0x04 #define PAGE_VALUE 0x09 //0x05 #define EMB_FUNC_EN_A 0x04 #define EMB_FUNC_EN_B 0x05 #define EMB_FUNC_INT1 0x0A #define MD1_CFG 0x5E #define CTRL1_XL 0x10 #define WHO_AM_I 0x0F #define STEP_COUNTER_L 0x62 #define STEP_COUNTER_H 0x63 #define EMB_FUNC_SRC 0x64 #define PEDO_CMD_REG 0x83 v

Good day,I came across the "STAR1 reference design". The document is a few years old. I am trying to find components so that I can reproduce the reference design. Can someone please help me to find the component: mirrors, drivers, ST piezo mirror evaluation kit, waveguides. Thank you in advance.URL for STAR1: https://www.st.com/content/dam/ces23/pdf/laser-beam-scanning-presentation-ces-2023.pdf

The microcontroller acquires data via SPI communication with the accelerometer. What is the risk if the data update timing of the accelerometer and the data acquisition timing of the microcontroller overlap?

We are operating ASM330LHH with ODR set at 3333Hz, but the actual measured output is about 3570Hz.This is not stated in the specifications, but is this within the range of the specifications?

HiI have been messing around with VL53L4CD for the last few months, and I recently realized that my readings differ significantly, depending on the target color/texture.Here is my setup: The sensor is set on its side, and directly in front of it, at the 20cm mark, I place a few different gray-level cardboard boxes, ranging from black to white, mostly gloss-textured.The sensor readings vary by about 10mm (222 shortest, 233 longest) depending on the box.Performing offset calibration helps to have an accurate reading on a gray target, but the error persists for other colors.I have tried performing cross-talk calibration, although I don't have a cover glass for this test, but that doesn't seem to help either.My question is - do we have to know the target reflectivity in advance and calibrate for it? Am I wrong to expect more consistent readings against various targets?Thanks!

 Dear sirs. I'm connecting an ISM330DHCX with an IIS2MDC and I need to know if the connections scheme is okay to operate in MODE 2Then I need to know if pullups are needed for i2c bus coming from SCx and SDx, and if pulldowns are required for INT lines as in the provided schematic.I'm based on the ISM330DHCX and IIS2MDC datasheets and X-NUCLEO-IKS02A1 board manualThe routing jumpers are there just in case we need to route one magnetometer to tha main I2C bus Thanks in advanceIgnacio

Hello,My goal is to test the IBI functionality of my custom I3C master driver using the LSM6DSOX sensor. For this test, I need the Linux I3C slave driver for LSM6DSOX with IBI support. The file linux/driver/iio/imu/st_lsm6dx/st_lsm6dsx_core.c does not contain any IBI-related code, such as i3c_device_request_ibi. If anyone has an example or code for using IBI with I3C in a Linux environment, could you please share it?. 

Hi,I'm working on a people counting system using the VL53L1X in multi-zone mode with a single sensor. It works well in general, but I'm seeing accuracy issues when people wear black or dark clothing—likely due to low reflectivity.I’d appreciate some guidance:Would the VL53L5CX provide better detection for dark clothing?Does it handle low-reflectivity surfaces more reliably?Or would it be better to use multiple VL53L1X sensors?Any other sensor recommendations for more reliable people detection?Thanks in advance!Basil