MEMS and sensors

Hello,The LIS2DUX12 datasheet clearly states that "12.1.3 FSM_START_ADD_L (58h) and FSM_START_ADD_H (59h) FSM start address register (R/W). First available address is 0x35C.".The default address in MEMS-studio is 0x0200. In the FSM examples on GitHub, the address also is the same: 0x0200.Why are these addresses different and which one is correct?

I've tried to use VL53L0X API, but it is too confusing. The API package STSW-IMG005 lacks any proper guidelines how to use API. The source file vl53l0x_platform results in one or another error.i'm unable to my own code VL53L0X as register map is not properly available in datasheet. Tried to explore discussion forums but unable to find any relevant solution.The problem i'm experiencing with API is How to link I2C write and Read operations with API function callsKindly guide me.i'm using STM32F103 and IAR workbench.Regards

Hi,I created a new flow with the mobile app (Expert Mode) using the acceleration sensor and the RTC time.I adjusted the sample frequency of the acceleration sensor to 960Hz and choosed writing to SD card for output.I used a user defines output file name to verify if the new file is generated correct.After starting the logging with the app I had a look on the SD card.The file was generated properly and also the acceleration data was saved properly, but the sample frequency is always 50Hz (20ms). Anyway what sample frequency I set, the output data is always 50Hz.What do I need to adapt that the correct sample frequency is used?Thank you for help.Christian

I realize there's no footprint-compatible replacement for the LSM330DLC. Is the ISM330DLC a functional replacement? Will our software team have to make changes to our software if we swap from the LSM330DLC to the ISM330DLC? Is there a migration guide for making this change? Is there a different STMicro part that would be a more suitable replacement for the LSM330DLC?

Hi,I'm working on a driver for the ST ILPS28QSW.When I switch from Pressure to Qvar mode (using the CTRL_REG3.AH_QVAR_EN bit), I notice a brief transition problem: The first 3 samples read are invalid.    Please note that those incorrect samples are measured only when the STATUS.P_DA bit is set (therefore new pressure data should be generated).Is there a way to know when the data is stable?Is there a way to change between pressure and Qvar mode without reading those invalid samples?Regards,Gabriel

I have been trying to log data using LSMDSOX + Profimems, but it does not record any data. I have attached pictures of this. I have not updated the firmware, and I am using Ubuntu 22.04. I have exported the data to a file, and it is empty.   

I am using MEMS studio version 1.3. If I use an arbitrary timer when debugging the FSM, then according to the specification the timer value should change with each new incoming data sample. But will the value change after three or four samples? Does anyone have a similar problem? Is the error only during debugging?

Hello,     after experimenting MEMS sensors with the IKS4A1, I developed a custom board based on STM32F407 CPU with the LSM6DSV16XTR accelerometer+gyroscope and LIS2MDLTR magnetometer.The aim is to get board inclination and compass information with the maximum accuracy.On CUBE-MX I select the LIS2MDLTR on the "Board Part Mag" section, the LSM6DSV16XTR on the "AccGyrQVar" section. Then I selected the MotionFX, MotionTL, and MotionEC libraries. Finally I choose "CUSTOM_TiltSensing" on "MEMS1_Application". At this point the yellow warning message imposed me to add the "MOTION_SENSOR" on the "Board Support Custom" section. It is not clear to me the reason of this and what does it means. In any case after I had configured all the parameters the connection with MEMS Studio produces a "Board not identified" message. Does it has some sense to define the MEMS1_application on CubeMx with a custom board? Is it possible to use Mems Studio with cust

1.Shall ASM330LHB able to detect the sensor(Gyro and Accelerometer) fault in dynamic(not stationary) conditions and send the information to Host?. Self test will give fault information but it is applicable only in stationary conditions.2.If above is not possible ,can you please suggest any algorithms to detect the faults in IMU?

Hi All,I’ve been reading up on accelerometer calibration and noticed that many application notes suggest using an ODR (Output Data Rate) of 100 Hz, gathering 5-10 seconds of raw data, and then applying a least squares method for calibration. However, the IIS3DWB operates at 26 kHz, and storing raw data at this speed quickly depletes the available RAM.Is the method mentioned above also the preferred approach for calibrating the IIS3DWB, given its higher sampling rate? Could you recommend alternative techniques or tips for handling calibration with limited RAM?Any insights would be greatly appreciated.Best regards,Bob

Hi Team,We are working on BHI160B BOSCH IMU sensor using STM32L053R8 board. We can read the Quaternions, calculate RPY. But now we are finding a Yaw drift issue with that IMU. Could an expert from ST help us solve this technical issue?Also, Is there any IMU sensor related to ST that is better than BHI160B and doesn't get the Yaw drift issue? If yes, we will be happy to go with ST IMU sensors that is better than BHI160B.Any technical expert help would be very thankful.Regards,Vamshi.

I plan to purchase NUCLEO-F767ZI & X-NUCLEO-IKS4A1 for my project. I just wonder whether the Unicleo-GUI works with the combination of  NUCLEO-F767ZI + X-NUCLEO-IKS4A1.Your advice is highly appreciated. Qingshan

I want the tap detection to work only in x axis, so I have set the TAP_Y_EN and TAP_Z_EN to 0.But still im able to see in the logs like interrupt from z and y. I'm using the api lsm6dso_tap_detection_on_y_set, lsm6dso_tap_detection_on_z_set and passing 0. 

Hi, When I input 32000 (32 kHz) into the AUDIO_IN_SMAPLE_FREQUENCY macro within cca02m2_conf.h The advanced tab within microphone properties is lost, not allowing me to select 32 kHz, 16 bit input. I have noted that when entering 48 kHz and 16 kHz as the AUDIO_IN_SMAPLE_FREQUENCY, the advanced tab is available, allowing me to select the correct sample rate, and stream audio in Audacity.  Has anyone encountered this issue in the past and has a work around? Using X-NUCLEO-CCA02M2 shield with the Nucleo F401RE board and Windows 11 OS.

I need to reduce the RAM requirement to use the VL53L8CX with a STM32WL55 application.  I am working with STM32duino implementation and need an example of how to implement disabling some of the data output by the VL53L8CX (e.g. motion indication, multi-targets) as discussed in section 5.2 of UM3109 (A guide to using the VL53L8CX, low-power, high-performance Time-of-Flight multizone ranging sensor). An example "platform_config_custom.h" file or modified "platform.h" file and code snippets to include in STM32duino VL53L8CX example "VL53L8CX_HelloWorld_I2C" would be much appreciated and can permit me to proceed with our evaluation of the VL53L8CX for our use case.Thanks!Jim

Hello everyone, I am using MPU6050 with STM32F44VET7 When I read the values of MPU6050 its seems normal. I checked my codes twice nothing wrong its standart MPU6050 library.  Az is = 1.1but when I quickly raise the card in the +Z direction, I expect Az to increase but instead I see it decreasewhen I quickly raise the card in the -Z direction, I expect Az to decrease but instead I see it increaseCan u explain me the logic of this?

I'm trying to extract the data Game Rotation Data from the ism330bx sensor. I'm just not quite sure, which setting to use for that. What I did so far:Setting the sensor for an ODR of 480Hz with a range of 4000dps and 8g.(ism330bx_reset(NULL)) (ism330bx_auto_inc(NULL)) // set auto increment register (ism330bx_set_odr_g(NULL)) // 480Hz (ism330bx_set_range_g(NULL)) // 8g (ism330bx_set_odr_xl(NULL)) // 480Hz (ism330bx_set_range_xl(NULL)) // 8g After that I can extract the sensor data from the registers 0x22 to 0x2D.Now I'm trying to configure the SFLP function in the embedded functions: I2C_WRITE_PARAM writeParam = { .Address = ISM330BX_ADDRESS, .Data = 0b10000000, .Register = FUNC_CFG_ACCESS }; i2cWriteSuccess = i2c_write(&writeParam); // switches to embedded fuunctions writeParam.Register = EMB_FUNC_EN_A; writeParam.Data = 0b00000010; i2cWriteSuccess = i2c_write(&writeParam); // activation of SFLP writeParam.Register = SFLP_ODR; writeParam.Data = 0b01101011;

Hi Team,Good day!We are using LSM303D accelerometer chip in our tracker device. We are mainly using accelerometer data for any crash detection. We have around more than 5000 devices in field and many of them reporting sudden spikes in accelerometer axis data without any actual disturbance. We have configured our LSM303D chip with below configuration:Initial write CTRL0 (1Fh) to CTRL7 (26h) : data[1] 0 (0x00)              data[2] 111 (0x6F)         data[3] 24 (0x18)            data[4] 2 (0x02)              data[5] 8 (0x08)              data[6] 136 (0x88)         data[7] 0 (0x00)      &nbsp

I'm using the STEVAL-MKI245KA development kit, trying to get the IMU readings with an AT-Mega through I2C. The I2C communication between the adapter board of the kit is working, but the IMU values recieved by the arduino are not updating. When I run the code to get the accelerometer and gyroscope values, the value is always 0 for all axes acc and gyro. (the reason I know the I2C is working is because when it wasn't working, the values were all -1, but when it does 'work' the values at all 0). Here is a screenshot from the datasheet of the IMU with the registers of all the parameters:And here is the code that I am using to access the values at these registers:#include <Wire.h> #define IMU_ADDRESS 0x6B // Address of the IMU device void setup() { Wire.begin(); // Initialize I2C communication Serial.begin(9600); // Initialize serial communication } void loop() { // Read STATUS_REG register Wire.beginTransmission(IMU_ADDRESS); Wire.write(0x1E); // Address of the ST

Hello, I am working on integrating IMP23ABSU into my hardware. Hence, I reviewed the evaluation schematic (steval-stwinkt1b) to understand its setup. I have a few questions regarding the schematic, in addition to what has been answered here, it would be great if you could answer them.1. There are three MREF in the schematic for steval-stwinkt1b, part of which is attached to this message as an image below. I understand what the ones circled in green correspond to, but what does the MREF circled in red correspond to?2. In the response here, it was mentioned that the amplification factor of 1 + R6/R7 = 2.34 is to take advantage of the microcontroller's 3.3V. But isn't the Opamp's VCC+ and microcontroller's VREF+ tied to 2.7V? Meaning the analog voltage range will be from 0 to 2.7V and the output M1P can only range from 0 to 2.7V, am I correct in interpreting the setup?Thank you. 

Hi, We recently purchased few VD55G1 camera sensors along with Camera EVK kit and breakout board for Raspberry Pi. I intend to use it with Ambig Microcontroller. I downloaded Brighsense EVK software kit to figure out settings. I am referring to file attached below to figure out the settings intended for proper operation. Following these instructions in section 5.3 on page 6 and section 9 (FW_PATCH section) on page 10, it recommends, to send PATCH_AND_BOOT command followed by BOOT Command. When I send these instructions it times out with logs attached as below.  It would be really helpful if you could help us with newest version of driver code which help us get started. Regards, Karthik

I put a object at about 1100mm, and another object at about 50mm. And use example5 to test vl53l7ch (4x4 resolution, max 2 objects per zone), but found that it does not recognise the closest object. For example, zone 13 output:[Zone13] (found 1 object), object 1 ==> ( range status: 5, distance:1043, signal_per_spad:3, sigma:26)object 2 ==> ( range status: 14, , distance:32, signal_per_spad:1674, sigma:1) My questions are:1. What is status code 14? I can not find it in UM31832.Why the driver does not put object 2 in the first position after I have called vl53lmz_set_target_order to set target order to VL53LMZ_TARGET_ORDER_STRONGEST3.why the sensor does not recognise object at "distance:32" (that is object2)  even its signal is more larger than object at "distance:1043"(that is object1) 

We use STM32F103RG to driver ism330dhcx, and use MotionDI to calculate the pitch and roll angle.Parameters:Frequency: 100HzScale: accelero =2gyro = 250AccKnod Caltype:OneTimeGyrKnod CalType:ContinuousSFKnod output type: ENUWhen the object roll angle is close to 90°, MotionDI calculate value is 150°。When the the object roll angle is less than 84°，MotionDI calculate value is normal。How to solve this problem?

Hello,I am developing an application that uses 8 ILPS22QS in 3-wire mode and a microcontroller that does not support this mode natively. A shift register is used to control the CS lines and it is working as expected.I tried to go around this problem by wiring the SPI as per the diagram attached.I am using the Arduino IDE and the SPI library.After enabling the SPI at a speed of 100000Hz (and set to MODE 3), I pull the first sensor CS pin low and immediately write to address 0x0E the value 0x60.After that I try to read back the same register (SPI.trasfer(0x8E)) and register 0x0F, but the chip does not respond. During the "reading back" part of the transaction, I tried sending either 0xFF or 0x00 on the MOSI, but the result is the same, on the MISO I just get a copy of whatever the MOSI is sending.I have also tried changing the 2.7k resistor between the MOSI and MISO pin for a 5k, but nothing changed.I have attached the full arduino code too, just in case (to test it, remove .txt extensio

Good Afternoon,I've been working on migrating from the LSM6DSO32 to the LSM6DSV32X and I notice that neither part specifies ODR Accuracy for normal or low power modes.  Is this information available? Thank you