MEMS and sensors

Hello,I plan to use a cover glass on top of a VL53L8CX sensor. I understand that I need to perform a calibration to account for the crosstalk effect. According to the forum and datasheet, this calibration requires using an object with a known reflectance percentage. I have two questions about this process:Can I use a board covered with printing paper, setting the reflectance percentage to 88%, and place it approximately 1 meter away from the sensor for calibration, as suggested in the comments?The datasheet mentions measuring reflectance with "vl53l8 REFLECTANCE_PERCENT." Can I use the value obtained from measuring my detected object's reflectance to calibrate the sensor when the cover glass is applied?Thank you.

I am making my own wake up interrupt program based on P16 of the application note, and it is working fine. However, I noticed that I have to enable IIS3DWB to use the wake up function, which increases the overall standby current of the system by about 1.1mA. That is not what I was expecting, as I thought that the wake-up function would run at a very low current.So is there a way to reduce the current consumption of the IIS3DWB when using its wake-up function?

Hello, I am encountering strange samples in the raw data using the IIS3DWB accelerometer. I can make several requests for raw data without issues, but at a certain point, I receive data with incorrect values at specific sample positions. Whenever an error in the raw data is observed, strange behavior can also be seen in the RMS data. Even without vibration, the sensor maintains a DC level in the RMS values. This persists for a few minutes and sometimes a few hours before returning to normal. This error has a well-defined behavior in the raw data, with a value of 2560 observed every 32 samples for the gravitational axis, and a value of 0 in the raw data of the other axes also every 32 samples. The frequency and duration of this behavior are exactly the same as the behavior described for the RMS data. Sometimes I go several days without observing this problem, but sometimes it happens more than once a day. Is this behavior a known issue? Do you have any tips on where

Hi,We are using LSM6DSL for one of our products and in that we have noticed that the Z-axis Accelerometer deviates due to change in temperature for a stable orientation as shown below which is affecting pitch of the product  by -1 to -2 deg.    The IMU is placed near a LED driver which changes its brightness from 20% to 100%. The layout image shows the distance (7.5mm shown in thin silver line) between the thermal vias of the LED driver(which is in bottom layer) and IMU (in top layer). The entire board is potted with a thermally conductive epoxy material.As shown in the graph,1. Initially from 0 to 20 sec it is in 20% brightness (LED driver dissipates less heat) at 130 milliG.2. At 20sec, we switch the driver to 100%. We see that the due to sudden change in temperature by 1 deg the Z-axis accelerometer immediately shifts down by 30 milliGs (130mG to 100mG) and then slowly tend towards to its original value.3. At 225sec we switch the driver back to 20% and the Z-axis

Hello,I am designing a product based on VL53L4CDV0DH/1 ToF sensor,when purchased an evaluation board NUCLEO-53L4A1 It contains a small cover IR windowI want to use it in mass production,There is off the shelf such IR cover ?P/N ?Thanks,Eduard    

Hi,I am fighting with the offset calibration of multiple VL53L1X. I use the API ULD with Arduino.I build a device to have 4 sensor[4] at 140mm far from a same plan. 2 of them give a good measure, 2 of them do not.I have tried the following process to calibrate for each sensor[4] ({xx,xx,xx,xx} are the value during the debug):sensor[i].GetDistanceInMm(&distance[i]); // distances are {115, 142, 143, 118} uint16_t OffSetToF; sensor[i].GetOffsetInMm(&OffSetToF); // returned values are {0, 0, 0, 0} sensor[i].CalibrateOffset(140, &OffSetToF); //returned values are {26, 65533, 65532, 23} sensor[i].SetOffsetInMm(OffSetToF); //with previous values {26, 65533, 65532, 23} sensor[i].GetDistanceInMm(&distance[i]); // distances still are{115, 142, 143, 118}Whatever the API (ST Ultra Light Driver or native ST_API), is the VL53L1X_GetDistance function (or GetDistanceInMm) supposed to give the measure corrected of the offset value calculated with the VL53L1X_CalibrateOffset function and

Hello, I'm desparately trying to find a diagram that would explain how the different sensors (accelerometers, magnetometer, gyros...) are oriented on the IKS4A1. We can find individual axis information for each sensor on their specific datasheet, but I don't know how they are integrated into the IKS4A1. I could figure that it seems that the lsm6dsv16x is upside down (Z pointing down) but it's harder to figure it out for the magnetometer (LIS2MDLSensor).Also, another thing : it seems that the Quaternion values given by the lsm6dsv16x have their Z and X axis swapped. I think that a yaw rotation (Z axis) of the board gives a roll information on the output quaternion.Does anyone has any more information ? Thank you for the help.

I would like the ability to generate an interrupt be programmed into the embedded flash so that I can use STHS34PF80 without a microcontroller. Is this possible?

Dear ST- Community, we are currently implementing a new function to our existing device with the following function: We want to detect, when the device is tilted. This function is not time critical at all. The most important fact is energy consumption. We do have a LIS2DS12 accelerometer, connected via I2C. We want to collect ACC data with 12,5 Hz / LP for the max. time before we readout the FIFO. At the moment, we readout the FIFO every 20 sec. This get us ~250 samples. The problem is, that if the time between readouts is longer than 9 sec., we can not read all samples (we take the FIFO_SRC reg. resp. the FIFO_Samples reg.). Our time delay is 10 sec., we expect 125 samples, the first time we get 125 samples, after the next readout only 17 samples afterwards again 125 samples and so on. If the time gets even longer, it looks like this:  FIFO Size: 113 Status Reg (0x27): 1 // readout FIFO SAMPLES (0x30): 4 // check remaining samples // delay 10 sec.FIFO Size: 123 Status Reg (0

I am trying to connect two VL53L8CX time of flight sensors to STM32F401RET6. I need one I2C bus for both sensors but unable to assign slave address dynamically. I need to know where to modify the program in stm32cube IDE

Hi all,I'm working on a product that uses a TOF sensor (exact type# TBD) to identify if someone(s face) who is sitting in a chair is present within a certain distance and angle (around 20 degrees). If the right conditions are met the product should be switched on. I'm looking for ways to prevent the product from switching on based on false positives that the sensor receives from static objects when no on is actually present, such as wall, chairs etc. Appreciate your thoughts! 

I am currently trying to perform the Cross-talk calibration procedure, but I am confused because the procedures mentioned in the documents "Proximity and ambient light sensing (ALS) module" and "VL6180X cross talk compensation implementation" are somewhat different.The document "Proximity and ambient light sensing (ALS) module" mentions that the offset needs to be written before performing the measurement, but this is not mentioned in the document "VL6180X cross talk compensation implementation."Additionally, the "VL6180X cross talk compensation implementation" document uses RESULT__RANGE_RAW. Could you please advise which one I should follow? Thank you. 

Hello -I have an Accel 28 board made by Mikroe that has the LIS2HH12 device. As per the Mikroe data sheet I set J1,J2,J3 to positions 2-3. I have removed J5 so that line isn't pulled up.I've got the first 6 pins on the lower left up connected to my NUCLEO-L476RG development board.GND, 3V3, SDI, SDO, CLK and CS. I have confirmed CS, CLK and SDI have normal and good signals. Yet, SDO is distorted, almost non-existent, but does return the correct value occasionally. Please see scope pix attached. Top is SDI/MOSI, bottom is SDO/MISO. I've also tried unplugging SDO pin from Accel 28 to STM32 to confirm it's not a loading issue. On this test the function did return the correct value of 0x41 to "Who am I" (0xF) command.It's clear to see this is a peculiar signal and not normal at all. Also attached is Accel 28 schematic.Could you please offer any suggestion as to what the problem might be? Have you seen this before?Thanks! 

hi anyone can please help me for the integrating vl53l0 sensor with rx71m mcu,because i am not getting specific document for communicating it with rx71m over i2c please support

Hi, I am using the LIS2DW12 on my board communicating over I2C with the nRF52840.  I have not yet been able to communicate with the accelerometer at all, and all attempts to read or write end the same way (see screenshot)I have the CS and SA0 lines both pulled up to VDD, and VDDIO is tied to VDD because they are the same voltage, 1.8V.  Could there be an issue with VDD and VDDIO being the same rail? 

Hi,i am using both the VL53L5 and L7 in a quite limited space, where the sensor need to run in the 8x8 continuous mode. Therefore, the thermal design is quite challenging.  So, my question is: what temperature does the sensor specifically deliver with the parameter "silicon_temp_degc"? Can it be assumed to be its junction temperature? If not, can a delta between silicon temperature and junction temperature be estimated?

I have configured the activity/inactivity function, but I only get the interrupt raised on inactivity, not on activity. Is this function supposed to be able to alert me to both activity and inactivity? Or is it just inactivity that raises the interrupt?

Hello Everyone!!!I am using ISM303DAC in my project E-Compass, I am facing an issue regarding hard iron calibration. in datasheet it is mentioned that we have do hard iron calibration using external processor  and has to store those values in the internal registers of sensor.  here i don't know how to do the hard iron compensation can anyone please let me know the procedure/steps to do the hard iron calibration if any example is available with you please provide me.Thank you,regards,ANIL.

Hi, I am using MKI239A and MKI109V3 with LSM6DSV (IMU). Knowing the full scale of accelerometer and gyroscope, I still need resolution information to calculate the exact readings. I did not find relevant resolution info on data sheet... Could you please provide some information? thanks for your help! @Federica Bossi 

Hello, I am using STM32H745 to setup and communicate with LIS2DS12 accelerometer via SPI 4-wires. I am trying to setup the accelerometer and I started with reading the WHO_AM_I register. It's default value is (43h) and I changed the value of the first bit to '1' so that my STM32 can read the value. The SPI communication is setup as follows: With the read and write fucntions set like this: HAL_StatusTypeDef spi_write_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret; uint8_t address = regAddr & 0x7F; uint8_t sendData[2] = {address, *pData}; //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 0); ret = HAL_SPI_Transmit(&hspi2, sendData, 2, 20); //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 1); return ret; } HAL_StatusTypeDef spi_read_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret = 0x01; uint8_t address = regAddr | 0x80; // Set the Read/Write bit to 1 for read operation uint8_t sendData[2]= {address,0}; uint8_t receiveData[2] = {

Hello I I'm using the -> GitHub - STMicroelectronics/STMems_Standard_C_drivers, for presence and motion detect with a NUCLEO-F401RE directly connected with STEVAL-MKI231KA, i can read the sensor ID and setup the other paramethers, but my question is related to wakeup_thread, i to setup an external interrupt connected to INT1 from the board sensor to toogle this variable? without this i think that i will not start to read the sensor properly. the example is: https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/sths34pf80_STdC/examples/sths34pf80_tmos_presence_detection.c   /* handle event in a "thread" alike code */            if (wakeup_thread) {              wakeup_thread = 0;              motion = 0;              presence = 0;

Hello,I want to enter the decimal part of a number in to filed "Float" (Advanced Features -> FSM -> Converter).The Decimal Separator in the Regional Settings of the system I use (KDE/plasma) is a comma.It seems that the "Float" field only accepts a decimal point as decimal separator, but I cannot enter the decimal point character in this field: after pressing "." key nothing appears in this field.I can enter the "," character as decimal separator, but after conversion I get the wrong result in the field "Float16".Am I missing a some option in MEMS-studio settings to solve this problem?Additional info: if the "Float" field already contains a decimal point, I can enter "." character, but if the field was initially empty, then I can't enter "." character.P.S. I remember I had the same problem on Windows and in the previous version of MEMS-studio. MEMS-studio v1.3.0My system: Operating System: Arch Linux KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6

Hello, I am using STM32H745 to setup and communicate with LIS2DW12 accelerometer via SPI 4-wires. I am trying to setup the accelerometer and I started with reading the WHO_AM_I register. It's default value is (43h) and I changed the value of the first bit to '1' so that my STM32 can read the value. The SPI communication is setup as follows: With the read and write fucntions set like this:     HAL_StatusTypeDef spi_write_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret; uint8_t address = regAddr & 0x7F; uint8_t sendData[2] = {address, *pData}; //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 0); ret = HAL_SPI_Transmit(&hspi2, sendData, 2, 20); //HAL_GPIO_WritePin(GPIOB, GPIO_PIN_4, 1); return ret; } HAL_StatusTypeDef spi_read_LIS2DS12(uint8_t regAddr, uint8_t *pData) { HAL_StatusTypeDef ret = 0x01; uint8_t address = regAddr | 0x80; // Set the Read/Write bit to 1 for read operation uint8_t sendData[2]= {address,0}; ui

In the guide to using the VL53L5CX multizone Time-of-Flight ranging sensor it's described that for periodic temperature compensation the function vl53l5cx_set_VHV_repeat_count has to be called.I can't find the function in any header or c file.

How can I permanently write values into the registers of the VL6180x? I tried modifying the loadSettings() in begin(), such as changing the value at 0x0041 to 0x60 and then marking it. However, after repowering, the value at 0x0041 in the VL6180x reverts to 0. Does this mean that the register is volatile memory? Or how should I modify the NVM to write the values I want?Thanks in advance.