MEMS and sensors

Hello,the VL53L5CX and L7CX ULD guides mention that a target status of 6 and 9 should be considered with a confidence of 50 %, while a comment in the api.h file says that  "5 & 9 means ranging OK", which gives the impression of a higher confidence ration than 50 %. Therefore, my question is: how to exactly deal with measurements with the status 9?

Hi, i'm trying to enable the tilt feature in an LSM6DSO on INT1 or INT2 but isn´t been possible until now. I´ve read the datasheet and used the example as template but for some reason the interrupt is not working. Looks like the embedded functions are not being activated correctly.  These are the registers that I'm using to configure it. First hex is the register direction and the second one is the value to write.   ConfigRegisters(IMU,0x01,0x80);ConfigRegisters(IMU,0x04,0x10);ConfigRegisters(IMU,0x0A,0x10);ConfigRegisters(IMU,0x17,0x80); //RW registerConfigRegisters(IMU,0x01,0x00);ConfigRegisters(IMU,0x5E,0x02); Am i missing some register to configure?  Thanks,

Hello,I'm currently working with the ICM-20602 IMU sensor and the LSM6DSV16X IMU sensor in an STM32-based project using STM32CubeIDE for stm32f446re. I've successfully interfaced with the ICM-20602 sensor and am able to read the WHO_AM_I register after ensuring that the sensor is out of sleep mode by configuring the POWER MANAGEMENT 1 register. Here is the relevant code I used for the ICM-20602 sensor: /* Function to read a register from the ICM-20602 via SPI */uint8_t spi_read_register(uint8_t reg_addr) {uint8_t tx_buf[2] = { reg_addr | 0x80, 0 }; // MSB set for read operationuint8_t rx_buf[2] = { 0, 0 }; HAL_GPIO_WritePin(GPIOD, GPIO_PIN_2, GPIO_PIN_RESET); // Set CS lowHAL_SPI_TransmitReceive(&hspi3, tx_buf, rx_buf, 2, HAL_MAX_DELAY);HAL_GPIO_WritePin(GPIOD, GPIO_PIN_2, GPIO_PIN_SET); // Set CS highreturn rx_buf[1];} /* Function to write to a register over SPI */void spi_write_register(uint8_t reg_addr, uint8_t value) {uint8_t tx_buf[2] = { reg_addr & 0x7

Hello! I didn't find Driver of MPL115A2 for STM32, I tried to create a simple oneI'm not able to get dynamic data from the sensor.I connected it as below:VDD > STM32 3.3VGND > STM32 GNDSCL > PB8SDA > PB9HSR > not connectedSDWN > not connectedThis is the code i'm trying    // MPL115A2 registers with bit shifts for I2C communication #define MPL115A2_REG_PRESSURE_MSB 0x00 // Padc_MSB #define MPL115A2_REG_PRESSURE_LSB 0x01 // Padc_LSB #define MPL115A2_REG_TEMP_MSB 0x02 // Tadc_MSB #define MPL115A2_REG_TEMP_LSB 0x03 // Tadc_LSB #define MPL115A2_REG_A0_MSB 0x04 // a0_MSB #define MPL115A2_REG_A0_LSB 0x05 // a0_LSB #define MPL115A2_REG_B1_MSB 0x06 // b1_MSB #define MPL115A2_REG_B1_LSB 0x07 // b1_LSB #define MPL115A2_REG_B2_MSB 0x08 // b2_MSB #define MPL115A2_REG_B2_LSB 0x09 // b2_LSB #define MPL115A2_REG_C12_MSB 0x0A // c12_MSB #define MPL115A2_REG_C12_LSB 0x0B // c12_LSB #define MPL115A2_REG_CONVERT 0x12 // CONVERT // Perform a memory read to read

Hi everyone!!!i am working on motionEC library and there i have observed that it need sensor orientation. can anyone explain me what exactly is this orientation meaning and how it effects the library??reagards,regards,ANIL.

HELLO,Can someone tell me the time accuracy of the output rate of II3DHHC?ThanksTakenari otawa

I am using LSM6DSOX with Unico Gui, how can i plot external data in Unico Gui? Is that possible? The data is in the attachement

I DEVELOP A  STEP COUNTER USING lis2dux12 CHIP.I WANT TO KNOW I HOW I SETUP INTERRUPT IN STEP COUNTER

Hello. We know that lis3mdl is temperature sensitive, i.e. there is a scale shift. From what we have read, this cannot be compensated for with software ( Or maybe it's possible? ). Therefore, can this be prevented physically, e.g. by using some thermal paste? The idea is to prevent lis3mdl from heating up too much. Our operating temperature range is 10-35 degrees Celsius. Thanks.

Hi Team, We purchased the LIS2DW12TR MEMS sensor and we found there is a QR code + T marking on the body of the IC. In the datasheet, there is no mention of body marking. Please confirm that this is the correct part we purchased.Thanks,Abishek

Hi, I am considering IMUs from ST and ADI - ADIS16505. I found that ADI provide their IMUs with "in-run bias stability" and "angular random walk", but ST does not. I also checkout the community about this, and ST only test IMUs in characterization. I find LSM6DSR characterization can be shared. I am looking at the LSM6DSV16BX IMUs characterization for the two parameters. Could you please provide that for my final decision? Thank you very much

Hello everyone, I'm looking for an application note (similar to AN5063 but for the LPS27HHTW sensor) to get an idea of the mechanical integration and any necessary tolerances. Additionally, I wanted to ask the community if anyone has installed two sensors on the same side of the board and what the mechanical implications are in this case.

I use LIS2DS12 This is my init function   void LIS2DS12_Init(void) { uint8_t ctrl_1 = 0x72; //0111 for 6.4kHz ODR [7:4], 00 for 2g [3:2], 1 for high frequency available[1], 0 for BDU not activated [0] uint8_t ctrl_2; // [6] for soft_reset, [1] for disable I2C, [0] for 4 wires SPI HAL_StatusTypeDef ret; ret = spi_read_LIS2DS12(CTRL2_ADDR, &ctrl_2); ctrl_2 |= 0x42; // [6] for soft_reset, [1] = 1 for disable I2C, [0] = 0 for 4 wires SPI ret = spi_write_LIS2DS12(CTRL2_ADDR, &ctrl_2); //reset the accelerometer ret = spi_write_LIS2DS12(CTRL1_ADDR, &ctrl_1); //set the accelerometer to measurement mode spi_read_LIS2DS12(CTRL1_ADDR, &ctrl_1); spi_read_LIS2DS12(CTRL2_ADDR, &ctrl_2); }   with read and write :    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(G

Hello,I am working with the LSM6DSV16X IMU sensor and interfacing it using SPI mode 3 on an STM32 microcontroller(STM32F446RE) with STM32CubeIDE. My SPI configuration is set with CPOL = High and CPHA = 2nd edge, and I have set the baud rate prescaler to 4, resulting in a baud rate of 10 MBits/s.Before reading the WHO_AM_I register, I configure certain registers as follows:if (spi_write_register(CTRL3_REG, 0x45) != SUCCESS) return ERROR;if (spi_write_register(FUNC_CFG_ACCESS_REG, 0x00) != SUCCESS) return ERROR;However, when I attempt to read the WHO_AM_I register, I consistently receive 0x80 instead of the expected 0x70.Here is a summary of my setup and the issue:SPI mode: Mode 3 (CPOL = High, CPHA = 2nd edge)Baud rate: 10 MBits/s (prescaler = 4)Initial register configurations:CTRL3_REG = 0x05FUNC_CFG_ACCESS_REG = 0x00Could anyone suggest potential reasons for this discrepancy or any troubleshooting steps I should take?Thank you!      

Hello Community, I am new here and new to this field as well. I am currently using the VL53L8CH Lidar Sensor which has a MZAI some GUI tool to access and save data logs along with some visualizations of the data.I am currently doing some experimentation with the sensor and trying to understand the output data. I have the excel file through which I am accessing the CNH data.1. What does the CNH data even mean, why are some values -ve in it, the CNH plot provided by the BUI doesnt show any -ve values but the graph there is all in the +ve axes? My Experiment: Placing a flat white reflective square object at around 5 feet along with another larger flat white square object at 2 bins apart behind object 1 (considering the bin width to be around 222mm as the sensor is in 8x8 mode and the number of bins is 18 over the 4000mm range of the sensor). My Findings: When I drew histograms/bar graphs of these CNH values for the zones that were illuminated for Object 1 (the smaller objec

Calibration of ToF sensors requires a target which is '17% reflective'. Can I take it this means a simple peice of paper or card printed on a laser printer at 83% black (greyscale)?Thanks

Dear ST technical support.Please can you advise the pin configuration and bus timing (period between active devices) to allow me to connect three of your LPS22HB pressure sensors in parallel on the same SPI bus?The CS pin is used to enable the SPI function on one device but it is not clear if the other SPI pins can be common with other devices.Thanks and regardsDuncan

I was using the sensor until now on an Raspberry Pi with direct access to the I2C bus without problems.Now I use an FT260 USB-I2C interface to communicate to the sensor from a PC via USB. In principle the communication is working, e.g. vl53l5cx_is_alive() works as expected.But the initialization fails. On the poll for sensor booted status I now always get a 9 as the answer instead of the expected 1 until the timeout is reached.In the documentation I haven't found any hint what the value of 9 at this point means.This is the place where vl53l5cx_init() fails:  /* Wait for sensor booted (several ms required to get sensor ready ) */ status |= WrByte(&(p_dev->platform), 0x7fff, 0x00); status |= _vl53l5cx_poll_for_answer(p_dev, 1, 0, 0x06, 0xff, 1); if(status != (uint8_t)0){ printf("vl53l5cx_init(): Wait for sensor booted failed\n"); goto exit; } And inside _vl53l5cx_poll_for_answer() I see that the returned value is 9. Because the expected value is 1 _vl53l5cx_poll_f

Hi there,  I am using multiple VL53L4CX sensors and the target is a person's hand within a 60cm range. I am wondering if there is a specific calibration method for a hand within a shorter range (60cm), to improve readings. Right now I am just using the default settings and using the STM32H755zi Any help is appreciated, thanks.  Isaac

I was able to run the vl53l5cx demo, however when calling 53l5cx_check_data_ready, I see that it reported a 'GO2'error. The code is C5.The content of the (relevant?) config.tempbuffer is 0, 5, C5, 81.How to figure out what is wrong here, is there an list of error codes of the GO2 error(s)?

Posted on June 05, 2017 at 20:31Hi,We're using LIS3MDL to detect changes in the earth magnetic field due to various metallic objects flowing in the sensor proximity. So, we are not interested in the correctness of the absolute values in order to properly detect the magnitude of the field or the North direction, we only need to compare the magnitude of the field between consecutive measurements. That being said, I don't see any reason to calibrate the readings.The problem we are facing is that for unknown reason, the readings (mostly on Z axis, but I've seen also for Y) on some of our sensors are sometimes evolve from initial 'right after boot & install', normal values to really unexpected and different values. The external conditions are the same, the magnetic field is the normal earth field.Please have a look on this table, it's basically a log with recordings (x1, y1, z1 is the first measurement, x2, y2, z2 - second measurement, typically after two minutes):Id  &n

Hi, I'm trying to use the VL53L0X sensor driver with zephyr and nRF52833, but I'm getting errors when the driver is trying to calibrate. Below are the errors returned by the log system: My question, how could I solve this, it seems to be a software problem right?    

I want to use the VD55g1 camera on widows but i am not able to find the right driver 

We embed lis3mdl on our board that we produce, most of them are perfect, unfortunately there are single pieces where the magnetic north is wrong, the heading is wrong by up to 60-100 degrees. What could be the reason ? Regards. 

Hello, I am developing a sensor board using the Raspberry Pi Zero 2W with the VL53L5CX IC by itself, not a breakout board. However, I am running into a problem when trying to read in the sensor data using a simple test script offered by Pimorini. I also have the VL53L5CX breakout board from Pimorini which I connect to the same pins and run the same script and it works just fine.    Here is the error:             Uploading firmware, please wait... Exception ignored on calling ctypes callback function: <function VL53L5CX.__init__.<locals>._i2c_write at 0x7fac3ca0c0> Traceback (most recent call last): File "/home/pi/dronepi/env/lib/python3.11/site-packages/vl53l5cx_ctypes/__init__.py", line 125, in _i2c_write self._i2c.i2c_rdwr(msg_w) File "/home/pi/dronepi/env/lib/python3.11/site-packages/smbus2/smbus2.py", line 658, in i2c_rdwr ioctl(self.fd, I2C_RDWR, ioctl_data) OSError: [Errno 121] Remote I/O error Exception ignored on call