MEMS and sensors

Hello,I have the LIS2HH12 chip in two separate boards, same board, same firmware.  These devices have been working well, producing X,Y,Z data.  Until today, that is, after a firmware update.This device is the only thing on the I2C bus, 100KHz, 5.1K pullups, 3.3V, connected to an ESP32 S3.  Waveforms on the oscilloscope look clean.The CTRL1 register gets 0x3F and CTRL4 register gets 0x04 which I believe should provide initial functionality.WHOAMI returns 0x41, but STATUS returns 0x00 and all six OUT_ registers return 0, as illustrated below.I have a feeling I've overlooked something really simple.  I've read both datasheet and appnote, and looked through this community for hits on the LIS2HH12.  Thanks for any thoughts or ideas.WHOAMI and STATUSOUT regs

Hello, I am currently trying to write code for the I2C communication with the VL53L1-SATEL board. I was trying to confirm that the I2C was working by reading some registers mentioned in the VL53L1 Datasheet, those being 0xC0, 0xC1, 0xC2, 0x51, and 0x61. I was never able to get actual data from these registers. I have since found some example code that when I run I am able to read distance but when I try to read those registers in the example code I still am unable to get any of the data that is meant to be in those registers and some I get just zero while others I get the wrong values. I am wondering if the info in the datasheet about those registers is wrong or if I am doing something wrong along the way. A important note is that I am also reading from 0x010F using the same command which outputs 234, 0xEA in hex, but I am unable to see anywhere if that info is right or wrong.  Thanks, Carson

Hi,I would like to know what is the stop band attenuation of LPF1 and LPF2 for the sensors ISM330DLC & IIS2DLPC. Thank you!

AN5296Application noteASM330LHH: automotive inertial module digital 3-axis accelerometer and digital 3-axis gyroscope3 Operating modes”To guarantee proper power-off of the device, it is recommended to maintain the duration of the VDD line to GND for at least 100μs."About the statement:If the power is turned on before reaching the GND level, what will be the effect?

in interrupt read program as follow 

Hi,I would like to know if the STSW-IMG041 code that is flashed into the device is available somewhere. My goal would be to use the same code but on a custom board to verify that the sensor is working properly.Thank you! 

I wrote the i2c communication code for the vl53l1x ULD API in vl53l1_platform.c and i2c32.c, and called the API in tof.c to initialize vl53l1. The VL53L1X_GetSensorId function can correctly read 0xEACC, but the VL53L1X_CheckForDataReady function always shows that the distance measurement is not completed, and at the same time, the VL53L1X_GetDistance also cannot read the distance measurement result.

Hi, I am working on the LIS2DH12,  I have a problem to the appearance of acceleration data.  I'm using full scale of +/- 2g and ODR of 400Hz.  When the resolution is either 10-bit or 12-bit, only even number acceleration data is read(all x/y/z axis).  The acceleration data is generally correct(but only even number).  When resolution of 8-bit is selected, now both even and odd number acceleration data can be read.  It shows the same appearance for ODR from 1Hz to 400Hz.

Hello,I have a requirement to log the data from evaluation board STEVAL-STWINBX1 to cloud. I have created Azure IOT hub and while initiating the cloud logging from the app i was unable to successfully connect to the created IOT Device created in azure even though the connection string was pasted correctly. the application ST BLE Sensor classic automatically disconnects from the sensor once the cloud logging is enabled. do i need to install the SD card and log the data from card to cloud ? I got struck at this point, is there any specific firmware to be loaded, for now I'm just testing with the basic firmware that provides data from all the sensors to the app

Hello everyone, I would like to know if someone has ever tried to couple those two hardware components together?I am currently using the STM32C092RC board to build an FD-CAN network, and I would like to exchange some real data — or more explicitly, to simulate some real scenarios. Since the C092RC has an UNO shield connector, I thought I could easily use the VL53L8CX sensor on it.But the platform.h file, which normally communicates with the hardware, is made for the STM32F4xx family. So, is there any way to get the correct platform version for the STM32C0xx family? Has anyone ever tried this?  

Hi,ASM330LHH datasheet states that "compensation for high stability over temperature" are embedded in the device. Could you provide more information about the correction algorithms applied ?In particular, when we measure the bias at 0°/s of the ASM330LHH in a temperature chamber, we get strange non-linear behaviors that we suppose to be a consequence of these algorithms. For instance, in the following figure (filtered bias at 0°/s depending on temperature) some "steps" can be observed. Could you provide a description of the corrections applied / the reason of this behavior ? It would make the device more predictable for us.Furthermore, is there a way to disable these corrections ?Thank you a in advance.  

I am looking for information about iNemoEngine sensors in the latest STMicroelectronics HAL for Android.I successfully integrated the STMicroelectronics HAL framework into Android 11. I am using the LSM6DSOTR gyroscope/accelerometer and the LIS3MDLTR magnetometer. These sensors are correctly detected and can be accessed from an Android application. However, the STMicroelectronics HAL also creates iNemoEngine sensors, which do not return any values.The previous STMems_Android_Sensor_HAL_IIO framework used several proprietary STM libraries, including SENSOR_FUSION, GEOMAG_FUSION, GBIAS, MAGCALIB, and ACC_CALIB, to generate the game_rotation_vector, orientation, and rotation_vector sensors. Are these libraries still required for the latest STMicroelectronics HAL framework? What is needed to gain access to these libraries?What is required to make the fusion sensors work in the latest STMems_Android_Sensor_HAL_IIO?

Hello ST Community,I am currently working on integrating the LSM6DSV16X accelerometer with an STM32H7 series MCU over I²C. Our main goal is to detect the tilt angle of the system. Hardware SetupMCU: STM32H7Sensor: LSM6DSV16X (mounted on a custom board)Interface: I²CSA0 Pin: Pulled high → I²C address = 0x6BPower Supply: 3.3 VPull-ups: 4.7 kΩ on SDA and SCL linesI²C Speed: Tested at both 100 kHz and 400 kHz The setup is straightforward — the sensor is connected to the STM32H7’s I²C1 bus, and it can be successfully detected using an I²C scanner. I’m using the official STMicroelectronics driver from this repository:https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsv16x_STdC/examples/lsm6dsv16x_self_test.c  However, I’m facing an unusual issue during normal operation. Issue DescriptionWhen I try to read the WHO_AM_I register using the official LSM6DSV16X driver, I get inconsistent results. Case 1 – Normal Run (no breakp

hello , i am using lsmds0 sensor with nxp board below is the section of my code int main(void) { /* Write your code here */ Clock_Ip_StatusType clockStatus; clockStatus = Clock_Ip_Init(&Clock_Ip_aClockConfig[0]); Siul2_Port_Ip_Init(NUM_OF_CONFIGURED_PINS0, g_pin_mux_InitConfigArr0); Siul2_Dio_Ip_WritePin(MEMS_CS_DRIVE_ENABLE_PORT ,MEMS_CS_DRIVE_ENABLE_PIN,1); i2c_int(); //i2c_scan_bus(); i2c_bustest(); // I2C_ManualBusRecovery(); dev_ctx.write_reg = accelero_write;//assigning read and write pointers to ST driver context dev_ctx.read_reg = accelero_read; dev_ctx.handle = NULL; uint8_t who_am_i = 0; uint8_t ctrl1; int16_t raw_accel_data[3];// variable to store raw 16 bit accelerometer value volatile float acceleration_mg[3];// converted acceleration in milli-g lsm6dso_status_reg_t reg_status; // structure store the register flags lsm6dso_device_id_get(&dev_ctx, &who_am_i); lsm6dso_reset_set(&dev_ctx, PROPERTY_ENABLE);// starting resetting process uint8_t rst; uint

I have a question regarding the absolute maximum ratings of the ASM330LHH.In the datasheet, the Vin rating lists “(including CS, SCL/SPC, SDA/SDI/SDO, SDO/SA0)”.Does this voltage range also include any overshoot and undershoot on these pins?Additionally, if overshoot or undershoot exceeds the absolute maximum ratings,what potential issues could occur (e.g., malfunction, degradation, or damage to internal circuitry)? 

Hi everyone,I’m having issues with the VL53L7CHV0GC ToF sensor drivers on Linux. The kernel module loads fine, but I can’t read any data using the userspace part. When I try to use the driver completely in userspace mode, it reports that it can’t find the device on the bus, even though the device is physically present and visible on I²C.I use official sources from STMicroelectronics website.Has anyone encountered the same issue or maybe has a newer / fixed version of these drivers that works correctly?If not, at least a detailed datasheet with the I²C register description - which also doesn’t seem to be available online - would be really helpful, so we have a chance to write our own drivers.Thanks in advance!

Hello community,I'm new to using this sensor, but based on some initial testing I'm hoping it's a good fit for my application. I was hoping to get some general opinions/guidance on the approach I'm planning, so any tips/feedback are greatly appreciated!My application:Collect some reference data for a small (~1.5x1.5m) room, with the sensor mounted fixed in the middle of the ceiling, about 2.75m from the floor, looking straight down to the room. There are some stationary objects in the room that will be part of this reference 'scene' that is being captured. It is a fully enclosed room (expected to have no sunlight when the door is closed), and we can turn the lights off, so there should be little to no ambient light.I'd like to be able to periodically rescan the room and look for any differences to the reference 'scene' -- essentially looking for unexpected objects. It is not a very time sensitive application, so any filtering etc that might be helpful in making this determination is fi

I have broken the SATEL-VL53L8 into its small PCB form and have connected it with flying wires (about a foot in length) to the NUCLEO-53L8A1A breakout board. It is wired in the I2C configuration and the J9 connector is also set to I2C.When I open up the Smart Presence Detection software, I only get a sparce reading of different array values, which I believe are coming from the ToF located on the NUCLEO board and not the SATEL. This looks to me like some sort of comms issue, but I am not sure how to tackle it.Has anyone experienced this issue and know how to rectify it?Thanks in advance! 

Hi All, I've been using the VL53L1 sensor for drone height control, and the results have been quite good- however, the environment it is used in has plastic skylights with poor IR blocking. This causes unstable readings in direct sunlight. Some of the IR is blocked, and as such this is tolerable but undesirable. Would changing to the VL53L4CX improve this? Ranging up to 3m is required. Will the L4CX broadly outperform the L1CD in most situations?   Thanks!

I connected STEVAL-MKI236A and STEVAL-MKI109D and confirmed that the IMU information comes from Mems studio and Unico.My final goal is that this IMU value is output in serial communication.I want to read the output IMU 6-axis information through python and match it to ros2 topic.Please teach me the way.Thank you. Have a nice day

Hello, I am using the VD6283TX45/1 to develop a device and now have a question to consult. Due to my insufficiently careful reading of the data sheet during the initial design phase, I connected the I2C pins of this device to an I2C bus where the pull-up voltage of the bus is 3.3V. Later, when I checked the data sheet, I noticed that the reference design uses a 1.8V pull-up for the connection. However, the board with the device connected to the 3.3V pull-up has passed tests and the VD6283TX45/1 is operating normally for now. I am currently concerned about whether this connection method can ensure reliable operation in the long run. Or do I need to modify the circuit to implement level conversion for the I2C pull-up voltage?

Has anyone seen documentation or done optical power measurements for VL53L4CD? I’m trying to find the radiant energy or optical power output of this low power time-of-flight device. (I only succeed to find a graph showing the relative emitted power in their datasheet)

I could successfully operate the X- NUCLEO IKS4A1 in the MEMS Studio with the default sensor selection on the board. However, when I tried to select the LSM6DSV, which is connected on the DIL24 socket of the  X-NUCLEO IKS4A1 board, for the accelerometer and gyroscope sensor configuration in MEMS Studio, I get the following error window: The WHO AM I register value does not match the device selected I also connect two jumpers between 9-10 for the headers J4 and J5 on the X-NUCLEO IKS4A1 board and removed the two jumpers between 11-12 for the header J4 and J5. Do you have some recommendation, what I miss here?Many thanks in advance. Best regardsChristian

Hello,I am testing the LIS2MDL magnetometer in single-shot mode with offset cancellation enabled, according to the datasheet (DS12144 - Rev 6, page 22). The documentation states that in single-shot mode both bits OFF_CANC and OFF_CANC_ONE_SHOT in register CFG_REG_B must be set to 1.However, when these bits are both set (CFG_REG_B) and a single measurement is triggered by writing md = 01b in CFG_REG_A the measurement never completes — the ZYXDA flag in STATUS_REG remains 0 permanently.If only OFF_CANC_ONE_SHOT=1 is set, the measurement finishes normally and ZYXDA is asserted, but the output values look identical to normal single-shot measurements (no visible offset compensation effect).Test conditions:4WSPIBDU=1verified data readout sequence (reading all 6 output bytes resets ZYXDA properly)communication via SPI verified by WHO_AM_I = 0x40It appears that combining OFF_CANC=1 and OFF_CANC_ONE_SHOT=1 prevents the internal FSM from completing a single measurement.Questions:Is this a k

Could you please let me know at what point we can confirm that the ASM330LHH has successfully started up at the hardware level?If the WHO_AM_I register returns the expected response, can we consider that the device has initialized correctly?Additionally, after enabling the sensors via CTRL1_XL and CTRL2_G, is it possible to verify proper startup by checking whether the value of STATUS_REG changes?In a situation where the STATUS_REG value sometimes changes and sometimes does not, is it appropriate to judge that “no change” indicates the hardware has not successfully started?Thank you very much for your guidance.