MEMS and sensors

Hi,everyone.I measured the power consumption of LIS2MDLTR on the same board in power-down mode.and found that the LIS2MDL chip on STEVAL-MKI217V1(from mouser) consumes less power than the LIS2MDL purchased separately from mouser.We have some question and need your help.​ What is the power consumption LIS2MDL in power-down mode ？  Why do the parameter differ between LIS2MDL chip on STEVAL-MKI217V1 and LIS2MDL purchased separately？

Hi!We are working on product that needs to count people on the range of 3-4 meters. We designed dev.board for sths34pf80 and tetsted it with UNICO-GUI. The max range that we are getting is around two meters and therefore it looks that we need to use additional lens to extend the range.  I found one of your documentation " New industrial sensors:anomaly detection and presence" where you have descibed it working together with a lens. So we bought the same lens IML-0687 and tested it, but we are not reproduce the same results. With a lens the range is even less than without it. I played with different settings, but no success. There also should be document  AN5983, that describes the work with lens, but looks like its not created yet. Have you got any suggestions for us, to get it work?   

I am using the above 2 EVAL boards from ST. I am trying to get the video pipeline going to the point that I do receive the images in memory and the appropriate frame based interrupts are triggered to verify. I have tooled my code for minimal application and it fails. I have started with ST provided x-cube-n6-ai-h264-usb-uvc reference and am using the STM32Cube_FW_N6_V1.3.0 SDK provided. I am using the STMCubeIDE for development.From the terse documentation/information it seems that the 2 EVALs procured should be compatible. However, as mentioned in the other post: https://community.st.com/t5/stm32-mcus-boards-and-hardware/stm32n6-fpc-camera/m-p/755889 , I have found the hard way that the sensor MIPI lane polarities are flipped. i.e. Dx_P and Dx_N from the sensor to the Nucleo Eval.Q1. I have looked through the documentation and have no indication of the MIPI PHY being able to be configured to flip the polarities on the signals. Is this true?Anyways, I have managed to fli

Hi,It seems that some of my measurements (in a green jojo tank) are resulting in a `VL53L4CX_RANGESTATUS_OUTOFBOUNDS_FAIL` error.The measurement itself seems to still be correct as the tank is empty, and the result is around 1800mm.I check the documentation and i don't really see an explanation for this error. It says things are 'out of bounds' but does that simply mean there's not enough reflection?I've taken this sensor because it would do up to 4m, so i'm wondering what i'm doing wrong :) 

I am using VL53L4CX with VL53L4CD ULD driver v2.2.2, due to an I2C issue on my side the VL53L4CD_RdWord fails and the number_of_spad variable is set to 0. The divide by zero happen at the very end of VL53L4CD_GetResult.I checked the function in ULD v2.2.3 and the number_of_spad value is still used for division without checks :VL53L4CD_Error VL53L4CD_GetResult( Dev_t dev, VL53L4CD_ResultsData_t *p_result) { VL53L4CD_Error status = VL53L4CD_ERROR_NONE; uint16_t temp_16; uint8_t temp_8; uint16_t raw_spads; uint8_t status_rtn[24] = { 255, 255, 255, 5, 2, 4, 1, 7, 3, 0, 255, 255, 9, 13, 255, 255, 255, 255, 10, 6, 255, 255, 11, 12 }; status |= VL53L4CD_RdByte(dev, VL53L4CD_RESULT__RANGE_STATUS, &temp_8); temp_8 = temp_8 & (uint8_t)0x1F; if (temp_8 < (uint8_t)24) { temp_8 = status_rtn[temp_8]; } p_result->range_status = temp_8; status |= VL53L4CD_RdWord(dev, VL53L4CD_RESULT__SPAD_NB, &temp_16); raw_spads=temp_16; p_result->number_of_

Hi,I'm trying to write custom firmware for the MKI109D. I am currently using an MKI251A adapter board with it for evaluation. How do I set VDD_DUT and VDDIO_DUT to 3.3V on the MKI109D board without using MEMS Studio?   

Hi, In the datasheet of the gyroscope I3G4250D, page 21:CS: 0: SPI communication mode / I2C disabledMy question is: I have to configure the CS pin PE3 as Low at the beginning to make the gyroscope understands that I wants to use SPI? (PE3 is CS in the KIT STM32F411 Discovery)  Wating for your response,Thank you very much. 

Hi,i'm playing around with the VL53L4CX after putting it on my own pcb (yay).The user guide states that for the SPAD caliberation, NO target should be placed. The crosstalk requires a 600mm target.Do i understand correctly that the SPAD caliberation therefor is best performed outside and upwards to the sky? Or maybe in a room that is at least 6 meter long?It confuses me because i wonder how this is done in a factory where space is a premium :) Kind regards,        Ruben 

 LSM6DSVTR is marked V3,Does it change the DC format from YWW to Y or another format? What does "4" mean?Thank you.

Hello There  I have question regarding calibration of offset and cross talk for VL53L4CD / VL53L4ED.For my application i need to config Signal Threshold, Sigma Threshold, Timing Budget etc to other than sensor's default value,  So, my question is should i do xtalk & offset calibration with sensor's default config? or i need to do  calibration with my custom config?   Regards

The X-NUCLEO IKS4A1 cannot operate correctly in MEMS Studio with the default sensor selection on the board. I have the nucleo f401re.

Hi, I'm trying out the VL53 series to try to measure the height of liquids in a container. In my use case, we are measuring sauce in sauce cups - ranch dressing, hot sauce, etc. One issue we have noticed is that with oil or oily sauces such as olive oil. The sensor is not responding with the correct depth measurement. The sauce can be 4-6 inches from the sensor. Looking at the documentation, there could be some cross talk issue, however we don't what sauce will be used. (The user can provide different sauces) - Do you have recommendations on how to get better results with this sensor?

I designed a fsm Design for high G application. The odr of high G and fsm are same. The said functionality is generating interrupt when done on eval kit Nucleo board with iks4a1 kit in Mems studio. But when I converted it into header file and loaded in another sensor board with lsm6dsv320. It is not working. Earlier Free fall Fsm was done on same sensor, it worked both in mems and on this sensor board. I have called the fsm load function and enabled the embedded interrupt in MD2_CFG as I am generating interrupt on int 2. Odr and range settings of high G have been done seperately. What can be the reason of non functioning. 

Does anyone have access to documentation with an actual list of registers with addresses and functionality and a full description of the register bits for the VL53L0X?  All I have been able to find is documentation that refers to the questionable API driver package and some doxygen-generated document based on the comments in the API.  

For the same setup the distance values jump between a very high and a very low value. Setup 1: unit facing an open space(ceiling) Result 1 Result 2 Result 3 2514, 2483, 2466, 2407, 2752, 2799, 2808,   15,    0,    0,    0,    0,    0,    0,    0,    0 2474, 2461, 2475, 3021, 2839,   16, 2808,   15,    0,    0,    0,    0,    0,    0,    0,    0 2502, 2461, 2451, 2455, 2858, 2766,   15,   15,    0,    0,    0,    0,    0,    0,    0,    0 TOF Sensor does not seem to perform well when pointing into an open space(ceiling). &nbs

Hi，   vl53L0x goto sleep and wakeup to reduce power.  I used single_mode,program as follow:   I find add          sensor_init(dev,vl53_mode);            //activa  The measurement time was 600 mS. long more than not add  this function？  how  to reduce the time?      

The STAR1 laser beam scanning reference design was created as a technology demonstrator, and many of its original components are now outdated or no longer commercially available. To reproduce the design today, the focus should be on replicating the overall system architecture rather than sourcing identical parts.Modern MEMS or piezoelectric scanning mirrors can be used as replacements, along with updated mirror driver electronics built using current high-voltage amplifiers or dedicated MEMS driver ICs. STMicroelectronics and similar vendors may offer newer evaluation platforms or reference designs that serve the same purpose as the original STAR1 hardware. For piezo mirror evaluation kits, direct contact with manufacturers or authorized distributors is often required, as these kits are typically provided for development projects.Regarding optical waveguides, many commercial AR waveguide solutions exist today, though access may require NDAs. For prototyping, simpler optical combiners or

Hello, I am currently reading the ASM330LHH May 2020 DocID031239 Rev 4 datasheet and its Chinese version: ASM330LHH: Automotive Inertial Module Digital 3D Accelerometer and Digital 3D Gyroscope User Manual. During the design process, I have a few questions to confirm: Question 1: For CTRL9_XL (18h), when should DEVICE_CONF be set to 1 and when should it be set back to 0? Do I need to set DEVICE_CONF to 1 first before performing any write operation on any register of the ASM330LHH, and then set it back to 0 after all register write operations are completed? If DEVICE_CONF is never set to 1, what impact will this have? Will the written register values fail to take effect? Question 2: In the Chinese version of the ASM330LHH User Manual, Table 8. Accelerometer Samples to Discard, Table 12. Gyroscope Samples to Discard (LPF1 Disabled) and other tables all mention the term "number of samples to discard". What does this mean? How should I handle this—does it need to be implemented in the desi

I have an application that uses 10 VL53L0X sensors on an I2C bus.  I seem to have ended up damaging multiple STM32 dev boards trying to get this configuration to work reliably.  Any help to understand what I am doing wrong would be appreciated.So, there are 10 VL53L0X sensors on a single I2C bus connected to the I2C port on a Nucleo dev board.  There is a mechanism to enable each independently to set the I2C address, after which they all operate in continuous sampling mode and the MCU polls for results periodically.  This works fine, sort of, and the data comes in OK.  At some point everything stops and that's the end of it. I have found that the I2C port on the dev board seems to have been damaged and no longer works at all (probing with multi-channel scope).  There was nothing else connected to the dev board, just the I2C lines.The VL53L0X sensors have their own 3V power supply which is manually switched and is independent from the power t

Hi Team,In this post regarding VL6180x proximity sensor, the sensor is detecting the address(0x29) but the readings are receiving as 255 value even the object it detected in front of sensor. for reference purpose go through this code snippet wrote in arduino IDE for ESP32-WROVER-IE. What might be the problem?Regards, #include <Wire.h> #include "Adafruit_VL6180X.h" #define SDA 23 #define SCL 22 Adafruit_VL6180X vl; void setup() { Serial.begin(115200); delay(1000); Serial.println("Starting I2C..."); Wire.begin(SDA, SCL); delay(100); Serial.println("VL6180X test"); if (!vl.begin()) { Serial.println("Failed to find VL6180X"); while (1); } Serial.println("VL6180X found!"); } void loop() { //Serial.println("hi"); uint8_t range = vl.readRange(); uint8_t status = vl.readRangeStatus(); // if (status == VL6180X_ERROR_NONE) { Serial.print("Range: "); Serial.println(range); //} //delay(500); }Edited to apply source code formatting - please see How to

Hello,I intend to put LIS3DH and LSM6DSV32X on same SPI bus and use different CS lines to address them separately. But when the CS is desactivated, these components activate their I2C engine, therefore leading to possible conflicts of I2C interface on the SPI bus.For LSM6DSV32X, the datasheet states that I2C can be deactivated by setting to 1 the bit I2C_I3C_DISABLE of IF_CFG register.For LIS3DH, iy is said here (https://community.st.com/t5/mems-sensors/use-lis3dh-on-the-same-spi-bus-as-an-eeprom-is-it-possible/td-p/427285) to write 0x80 on address 0x17 to desactivate I2C on LIS3DH.Question 1: this method for LIS3DH is not officially documented in the datasheet, nevertheless, is it an official and safe way to deactivate the I2C bus ?Question 2 : If I deactivate I2C on LIS3DH and LSM6DSV32X, is it a safe way to make both components coexist on a same SPI bus ?Best regardsPierre Prot

On platforms like LCSC and Mouser, an IMU labeled "LSM6DSVQTR" is listed separately from the LSM6DSVTR. On JLCPCB, the LSM6DSVQTR has considerably more stock than the LSM6DSVTR and is eligible for the "economic" PCBA service, unlike the LSM6DSVTR.Do these IMUs have any meaningful differences, or can they be used interchangeably? If they do have differences, are they documented anywhere?

Hello everyone,I am interfacing ADXL345 in stm32f103c8t6 by using I2C connection. I have fixed the set up on a board. I would like to know if I can identify the movement of adxl by observing the changes in x, y, and z values if there is no vibration but the board is moving smoothly, that is, to the right or left. If not, how can I predict when the adxl will go forward or backward without relying on the sensor's tilt or vibration? I just want to create a basic activity detector where the logic would be :1. If the setup does not move, the output should be zero.2. If the setup is vibrating and moving, the output should be one.3. If it is simply vibrating (and not moving in space), the output should be 0.So, basically, I want to detect actual movement and not just vibration noise.I noticed that when the movement is smooth or constant ADXL345 values do not change much, so my logic is not detecting that as “motion.”STM32f103c8t6<-> ADXL345PB6<->SCL     PB

Hi，     1》In the dark，Place the white target 140mm from the sensor          call function         Status = VL53L0X_perform_offset_calibration(&vl53l0x_dev,0x8c0000,&pOffsetMicroMeter);     2》In indoor environments ，Place the black target  600mm from sensor         call function         Status = VL53L0X_perform_xtalk_calibration(&vl53l0x_dev, 0x2580000, &pXTalkCompensationRateMegaCps);    3》in main function               Status = VL53L0X_set_offset_calibration_data_micro_meter(&vl53l0x_dev,&pOffsetMicroMeter);          Status = VL53L0X_SetXTalkCompensationRateMegaCps(&vl53l0x_dev,pXTalkCompensationRateMegaCps);      Is the above process correct?         But           &n

Greetings,I am bring up a new HW design with the IIS2DLPC accelerometer integrated into the design.I am trying to bring up a Linux IIO device driver for this device, and the kernel does not currently have direct support for the IIS2DLPC, however it does support the LIS2DW12, which from looking at thedatasheet for both, they appear to be SW compatible.Can I just code the device tree node to specify the LIS2DW12?accelerometer@18 {compatible = "st,lis2dw12";reg = <0x18>;status = "okay";st,drdy-int-pin = <1>;interrupt-parent = <&sysfpga>;interrupts = <SYSFPGA_INT_ACCELEROMETER>;interrupt-names = "ACCELEROMETER-INT1";};Thanks,Ken