MEMS and sensors

I am looking into the VL53L4CD TOF sensor but find the specifications on distance accuracy at 10 cm (or perhaps in range 5 - 20 cm) to be murky at best.  I need to be able to determine distance to object with accuracy of 0.02 mm (0.001 inches) at this distance and be able to determine if object has moved in or out by that amount or more.  Can this device produce that kind of accuracy? Other posts here make me think not, that all it can do is about 1 mm.Also, the ST introductory webinar mentioned higher resolution project 55H2 if I heard it right. Can you provide any insights on that? Or suggest another product that can provide the accuracy / precision that I need, please.Initially planning to use Arduino for the CPU processing.Thank you.

We have a STEVAL-MKI224V1 kit, which should be equipped with a LPS22DF. I have tried to use the static (I2C) address of the sensor, and after much time, I discovered it is (depending on the state of SDO) 0x5C/0x5D, and not 0x6B/0x6A, as stated in the datasheet.Strangely (or not) 0x5C/0x5D is the static address of the LPS22HH, but according to the GETPID command, I do have a LPS22DF.Thank you.

Hello,We have implemented the LIS3DH with a nRF52832 in I2C mode on our board, and are using the accelerometer to detect motion and vibration events. The LIS3DH internal high-pass filter and threshold detection are used to generate the INT1 interrupt.Our issue is as follows. We are observing an excess current draw of ~40uA in this state. Our evaluation has found the excess current to be associated with setting the INT1_CFG register value for interrupt generation. Attached are two charts showing 10 minute periods of idle current measurements of the whole PCBA, one with firmware built to set INT1_CFG=0x2A, the other with firmware built to set INT1_CFG=0x00, and otherwise the exact same code. The spikes in current can be ignored, those are BLE advertisement bursts. In neither case was the interrupt actually triggered.LIS3DH registers are set as below, other than the changes noted above. Register writes occur in the order indicated. I have also attached a screenshot of the circuit.CTRL0 =

Hi,I have an X-NUCLEO-53L1A2 and a NODE_F401RE.The VL53L1.exe GUI is unstable and frequently freezes, but I could at least perform most of my experimental measurements (including MultiZone Ranging 4x4).However, when using MultiZone 10x10 Ranging, the GUI constantly crashes. During calibration, the following message appears:  Is this a known issue? What could be the problem?What do I have to do to be able to use the devkit?Thank you very much for your supportRegardsStefan@John E KVAM 

We have two VL53L1X sensors side by side. Both have gilizmo cover glass and are placed 140mm from a 8.5x11 sheet of mat grey paper. Running the calibrate offset function returns 2mm for sensor one and 6mm for sensor two. Following this the Xtalk calibration function is called this returns 37333cps for sensor1 and 52562cps for sensor2. Measuring distance after calibration shows the sensors are now way off and differ 2-3 inches from each other.  My question is what could be going on to get such high values for Xtalk when we have ideal cover glass and placement?Do we want the SPAD ROI to be 16x16 when we run the calibration? currently we have it at 4x4, 200ms of timing budget, and 200ms of intermeasurement period. The sensors are in a dark room away from an external sources of IR light.  

An anonymous customer was trying to get the best possible range accuracy with a VL53L5 sensor.  His temperature range was from 25degrees C to 50 degrees. This was his plot with no temp cal.  After calibrating between the ranges he got: These plots have different temperature ranges and scales. But between 25 and 35 degrees, the top shows a drift of 10mm whereas the bottom shows a drift of 1mm.  He tells me the calibration takes a while which is a reason to skip it, but if you really need the accuracy, it's worth trying.   He did not show me what he was doing, but I'm betting it's:   /** * @brief This function is used to set a periodic temperature compensation. By * setting a repeat count different to 0 the firmware automatically runs a * temperature calibration every N frames. * default the repeat count is set to 0 * @PAram (VL53L5CX_Configuration) *p_dev : VL53L5CX configuration structure. * @PAram (uint32_t) repeat_count : Number of frames between

Hi there!I'm having issues with my LSM6DS3TR device FIFO. I am trying to read and process all values stored in the FIFO by the accelerometer every interval using I2C. I am doing this by:1) Retrieving number of unread messages in FIFO at addresses 3Ah and 3Bh.2) For every unread message:2.1) Reading the pattern in address 3Ch and 3Dh.2.2) Reading the value of the FIFO in addresses 3Eh and 3Fh.2.3) Processing and storing value retrieved from value as x, y or z axis. I assume the pattern will tell me which axis the FIFO value relates to? I am only using the accelerometer, so I assume pattern = 0 is x axis, 1 is y axis and 2 is z axis? However, the pattern seems to be corrupted when I leave the program running long enough and will no longer align with the axis; for example- sometimes it will show pattern 0 but the value will be for y or z axis, pattern 1 but the value is for the x or z... etc...Further details about the settings of the LSM6DS3TR device:- I am using only the Accelerome

STHS34PF80 code needed to access SEL_ABS bit in ALGO_CONFIG embedded register Address: 28H using Arduino NanoI would like to know how to generate the code to set SEL_ABS bit in ALGO_CONFIG embedded register using Arduino Nano Board as the micro-controller.

Hello everyone,My goal is to record audio from one MP34DT05-A microphone via SAI PROTOCOL in an STM32F446 Nucleo Board. In resume, I receive data from microphone via DMA, then I make the transformation via PDM2PCM Library and write the buffer into an SD CARD via SDIO.I'm using STM32Cube IDE and I can see that the two buffers (input SAI data and output PDM2PCM data) are always being updated with values. Also, I confirmed that all the values are written into the SD with no missing values.I tried to replicate the code from "Microphone_Streaming" Stm32 examples (also made in this video: https://www.youtube.com/watch?v=BjTj1XXpjBU. But the result is always looking like this graph below. It seems like the microphone never respond to any higher sound... My feeling is that the parameters are not correctly adjusted and I'm missing something. Unfortunately, I think all the documentation available is very weak and I'm not reaching all the knowledge and attention necessary to be sure abo

Hello all.I would like to ask how to calculate dB from a data recorded by a MEMS microphone.I currently use the MP34DT04 on the SensorTile Kit. I checked the SensorTile can record sound with the microphone, and store a wav data file in MicroSD.In the .wav file, there are chunk of data and, of course, there are sound level data. Then, I would like to calculate dB data from the sound level data. How can I calculate?If the sound level data is 16 bit, the data would be in between -32768 and 32768. Is the digit can be mapped to full scale sensitivity? The sensitivitiy means the parameter in the datasheet. In the case of the MP34DT04, the sensitivity is in the range of -26dB to 120 dB.I also wonder what the description in the page 6 of the datasheet means. It says "Duty cycle: min = 40% max = 60%". Is it related to the dB calculation?Please take care yourself first, and looking forward to the answers. Thanks in advance. Masaru

Dear forum,I try to understand the bin shape of the VL53L8CX / CH sensor calibration buffer while evaluating different sensor cover and their influence on ranging. Using the example8 file from the ULD driver the shape looks more or less always the same (as eg. shown by @John E KVAM ) for most cover glasses I used. Nevertheless doing the math with a bin size of 3.75 cm the light path must be in range of ~40 cm, which seems to me highly unlikely with a 1 mm cover glass placed in 0.5 mm distance. Moreover I realized that the calibration buffer yields 144 bins whereas I read somewhere here that there are only 128 bins for ranging.Perhaps someone can elaborate on that a little bit.Thanks!

I am currently working with the VL6180X proximity sensor and would like to inquire about its long-term performance characteristics:      1. What is the expected Light/Luminous Depreciation time frame for the VL6180X's VCSEL source? Could you                provide any data regarding its lumen maintenance curve or L70/L50 specifications?     2.How does Light/Luminous Depreciation affect the sensor's performance over time?        Specifically:                 1. Does it primarily manifest as a reduction in return signal rate?                 2. Are there any observable changes in measurement accuracy?                 3. What are the typical indicators that Light/Luminous Depreciation has occurred?      3. Are there any recommended compensation strategi

I’m using a VL53L5CXV0DH/1 sensor in my current setup (see pictures). The goal is to detect a ball rolling between the sensor and the background. The red box is about 12cm apart.The settings is 4x4 for speed, i also noticed that 60 is not the highest scan frequency in code : status = vl53l5cx_set_ranging_frequency_hz(&dev,60);if i set 120 this works too, while scanning seems to be lot faster and just as accurate, why is 60 defined as maximum in the datasheet?However (even at 60), I often see target_status = 255 for 3-4 pads, without the ball passing and wonder why this happens. When this occurs, the distance information is apparently correct but the datasheets states that the distance readings become unreliable, and I want to ensure I get the most accurate and dependable measurements.When the ball passes i see 255 in even more status records.What could be causing this issue?Additionally, I’d appreciate any advice on settings or adjustments to improve detection, especially

I need to calibrate a VL53L4CX and have been reading UM2923. The functions described do not seem to bear any obvious relationship to the functions in the STM32Cube middleware which was generated for my project, which I find confusing. I it is not clear which functions I should be calling in order to satisfy the flow charts in UM2923. I have found essentially no other useful information about this device or its specific set of registers. I'm usually a huge fan of ST devices and documentation... The first sticking point is how to properly understand what to do with calibration settings. Am I supposed to store them in my own flash somewhere? That seems to be implied by UM2923. I can do this, but imagined the device would have its own NVM storage on board, since it is calibrated in the factory anyway. Is this the case? I thought so because the wrapper function VL53L4A2_RANGING_SENSOR_OffsetCalibration() ends by writing a data structure over the I2C interface from a function called VL53LX_s

I BOUGHT STEVAL- MKBOX PRO AND AM THINKING OF USING IT.I have a wireless function, but please tell me the status of technical conformity approval for use in Japan.There was no conformity mark on the package.

Hello,I'm designing a custom board with a LIS2DW12 accelerometer for motion detection. I want to use INT1 to send a signal to the MCU when it detects movement, which should wake up the whole system. The accel supports both i2c & SPI communication but I intend to use SPI. I would like to verify how I plan to make my connection between the accelerometer and MCU. Please refer to the images below.Note: VBAT is sourced from a 3V CR 2032 coin cellQ1) I'm aware that the datasheet mentions that to enable SPI communication, the CS pin must be set to logic '0' as seen in the image below. Is it okay if I directly connect the CS of the accel to a GPIO pin on the MCU through ACCEL_CS or should I add a pulldown resistor on the ACEEL_CS connection? Q2) The datasheet mentions using 100 nF (C6) ceramic and 10 µF (C5) aluminum decoupling capacitors for pin 9 (VDD). Is it okay if I use a 10 µF ceramic capacitor instead. I'm constrained for both real estate and budget on this project?Q3) Are

1- Is there a permanent memory in LSM6DSOX for machine learning? In other words, does the ".ucf" file that we load in case of power off or reset become permanent?2- Can we load the ".ucf" file without using "STEVAL-MKI109V3"?3- Can we load the ".ucf" file using I2C communication? Thank You.    

Hi,I am working on a custom ISPU code for LSM6DSO16IS and I want to generate interrupts on INT1 and INT2. I checked all the examples in x-cube-ispu/Ispu/ism330is_lsm6dso16is at main · STMicroelectronics/x-cube-ispu generates an interrupt only on INT1.Is it possible to generate interrupts on INT1 and INT2 at the same time? Thanks a lot :)Chen

私はB-L475E-IOT01A2(開発ボード)が手元にあります。B-L475E-IOT01A2に含まれている以下のセンサーを使ってデータを取得をしたいと思っています。相対湿度と温度の静電容量式デジタルセンサー (HTS221)高性能3軸磁力計（LIS3MDL）3D加速度計と3Dジャイロスコープ（LSM6DSL） これらのセンサーからデータを取得するサンプルプログラムが欲しいです。最終的にはここで取得したデータをNANOEDGE AI STUDIOで使用する予定です。Translated by ST community team I have the B-L475E-IOT01A2 (development board). I would like to acquire data using the following sensors included in the B-L475E-IOT01A2: Relative humidity and temperature capacitive digital sensor (HTS221) High-performance 3-axis magnetometer (LIS3MDL) 3D accelerometer and 3D gyroscope (LSM6DSL) I would like a sample program to acquire data from these sensors. I plan to eventually use the data acquired here in NANOEDGE AI STUDIO.

I am looking at the LSM6DSV16X MLC examples in the MLC Git Repo.I am confused by some of the register settings. For example, in lsm6dsv16x_six_d_position.h  const ucf_line_t lsm6dsv16x_six_d_position[] = { {.address = 0x10, .data = 0x00,}, {.address = 0x11, .data = 0x00,}, {.address = 0x01, .data = 0x80,}, // many lines deleted {.address = 0x02, .data = 0x31,}, {.address = 0x08, .data = 0x8E,}, // PAGE_ADDRESS: Address 0x8E not in the data sheet  I cannot find the address (0x8E) in the data sheet. I'm obviously missing something in my understanding.Any insights, guidance would be appreciated

Hello everyone, I have an ASM330LHH mounted on my selfmade board with stm32f405. The ASM330LHH works well except for the data sent by the gyroscope over the Z axis. This data is not stable at all. It wobbels very badly, quickly and with long intervals. The data around the X and Y axes is fine. How can I make the angle measurement around the Z axis stable?Hint: i use this library for configuring and getting the data out of the sensor: https://github.com/STMicroelectronics/asm330lhh-pidThank you very muchZain

Posted on February 19, 2018 at 17:42Hi all,I've tried several time to get in contact with the ST Online Support (http://www.st.com/content/st_com/en/support/online-support.html  and then the Submit Request button)  but every time I've experienced an error into an unknow 'Serena Business Manager Log In ' it give me all time Invalid User ID or Password (note I've did the login to the ST support page with success).I've no idea how to get in contact with the support team then I'm writting here, sorry if this may be not the right place to do that.just to know if others have same trouble or not.Thanks in advance.Best RegardsFabio

I'm interested in integrating multiple ST IMU(6 or 9 axis) sensors to my project. However, all IMUs will be connected in serial to simplify electrical circuit design so each IMU should has its own I2C address. Pls recommend several ST IMUs either 6 or 9 axis so I can test and connect them only by I2C bus. THX!

Hi everyone,I know there are 25 and 35 degree detection angles of VL53L3. I am aware that this situation is a mechanical situation. But I want to make a timing gate and find people's speeds. We have submitted our product to reliability and validity tests, but the detection situation at 25 and 35 degree angles prevents us from getting this reliability and validity tests. We want it to detect when the target is right in front of (linear detection) the sensor. Is there a software solution for this?  

Hello again!I've been trying to measure water level using the VL53L1 sensor and reading forum posts on it, and I've gathered that RefSPAD calibration isn't really recommended anymore.From my research on the topic, I know that water reflects only 2% of perpendicular incident light, with the rest getting transmitted and also that the transmitted rays will be fully absorbed at a minimum water level of 10cm.I was wondering if doing the RefSPAD calibration utilizing the VL53L1 (with a cover glass) leveled parallel to a water suface from a body deep enough to absorb all transmitted laser could end up improving the sensor's results by giving more weight to SPADs more likely to detect those perfectly reflected photons.Thanks in advance!