MEMS and sensors

Hi folks,I am currently testing the VL53L0X sensor and reading the datasheet. Is the current consumption of the sensor 19 mA in the single ranging scenario, or is it calculated for continuous ranging? I'm not clear on this point.Thanks!

Hello experts,I am using rock chip board with android 12 on it along with the sensor lsm6dsox connected on i2c2.I have added the driver and compile the Linux and then build android images.After booting I can see device is detected on i2c and probed successfully, now when I tried to get the same sensors list at android level I get 0 sensor device listed.below are the probe logsrk3568_s:/ # logcat | grep lsm01-01 12:00:00.830 0 0 I st_lsm6dsox_i2c 2-006b: Linked as a consumer to regulator.1701-01 12:00:00.831 0 0 I st_lsm6dsox_i2c 2-006b: Freq Fine -262 (ts 25262)01-01 12:00:03.552 0 0 I st_lsm6dsox_i2c 2-006b: MLC loaded (1) MLC 1 FSM 0001-01 12:00:03.556 0 0 I st_lsm6dsox_i2c 2-006b: Device probedAfter checking online I get below link from support teamhttps://github.com/STMicroelectronics/st-mems-android-linux-sensors-halI followed the same link with multi-hal configuration as well as with HIDL configuration but no sensor is listed in dumsys sensorservicerk3568_s:/ # dumpsys sensorserv

My project makes progress, see here:https://youtu.be/ah19fWodqg8 https://youtu.be/svEeEQ9jmDc My question:When I set LPn low - is just the I2C disabled? Or would also an initiated ranging stop?In order to save power: is there a need to set via I2C the mode, or would LPn low already bring the sensor into low power mode? (I am not convinced based on what I have studied in the datasheet).Another question:The RES signal on ToF sensor: does it reset the entire chip? As I understand, just the I2C is reset. In order to reset the entire chip, I had to toggle also both VDDs.I have realized: when the chip is messed up (e.g. still running a range scan configured), just toggling RES is not enough. I need a power cycle of entire setup. Is this expected as "reset behavior"?

Question 1: What is the minimum measuring distance of the VL53L4CD? The official manual states it as 1mm, but in my actual tests, it fails to measure accurately when getting closer than about 1cm. At closer distances, the data becomes erroneous. Why is this happening?Question 2: After modifying the I2C address of the VL53L4CD, can the change be retained even after power loss? In my current tests, every time the device powers up, I need to manipulate Pin X to change the address. However, upon the next power cycle, the address isn't saved and I have to reconfigure the device address again.

Hi, may I ask you? Is it any difference between STSW-IMG003 (api for VL6180X) and STSW-IMG011 (api for VL6180V1)? Is it working both sensor on same API ? Thank you for replay? Best regards Loring. 

I am working with a vl53l8cx and following the instructions exactly to initialize the sensor but it always generates a hard fault error.  I tried debugging , the hard fault is generated once the function Wrbyte is being called and it writes to the address 0x0777. As no register map probably exist I am stuck with this . Need Help

I have a P-NUCLEO-53L8A1 development kit, which consists of an X-NUCLEO-53L8A1 connected to NUCLEO-F401RE. When I am using the GUI program STSW-IMG041, it can correctly get data. However, I am using the X-CUBE-TOF1 kit from this website link: https://www.st.com/en/ecosystems/x-cube-tof1.html. I compiled the example '53L8A1_SimpleRanging' located in 'en.X-CUBE-TOF1\Projects\NUCLEO-F401RE\Examples\53L8A1', but I encountered an error while running it: 'VL53L8A1_RANGING_SENSOR_Init failed. Check you're using ONLY the center device soldered on the shield, NO satellite shall be connected!' I debugged my code and found that it fails when trying to read the ID:if (VL53L8CX_ReadID(&(VL53L8CXObj[Instance]), &id) != VL53L8CX_OK){ret = BSP_ERROR_COMPONENT_FAILURE;}Since using the GUI program gives me data successfully, I believe the module itself should be fine. However, I can't initialize it using the code.I look forward to receiving help from all the experts. Thank you very much.

Hi,we have designed a custom board that includes a STHS34PF80 but after triggering a one-shot acquisition, the DRDY bit is never set and reading from the TOBJECT_x and TAMBIENT_x registers without waiting for DRDY only returns 0. We are interfacing the sensor using I2C from an nRF52 SoC.Implemented procedure:Powering up the sensor (+ wait for 500 ms)Enabling block data update (Reg: 0x20, Data: 0x10)Triggering Acquisition (Reg: 0x21, Data: 0x01)Waiting for DRDY bit to be set (Reg: 0x23), Alternatively: Wait 25 ms and reading registers 0x26-0x29 directlyThe sensor ACKs the data transfers so I assume that in terms of the hardware everything is fine, WHO_AM_I (0x0F) correctly returns 0xD3.Am I missing something?Thank you very much in advance!   

Hello,First forum post so I apologise if I miss any key information. I'm trying to use NUCLEO-G474RE to test out the functionality of MotionAC using CubeMX to generate the program structure and Clion to edit it. All I am doing right now is trying to call:MotionAC_Initialize(1); However I get back that:undefined reference to `MotionAC_Initialize'This lead me to add the following to the CMake file, which I feel like I should not have to, is the CMake file generated by Clion or CubeMX? (a very basic question I know but I'm new to this) It's also of note that I enabled hardware floating point in the make file as well.target_link_libraries(${PROJECT_NAME}.elf ${CMAKE_SOURCE_DIR}/Middlewares/ST/STM32_MotionAC_Library/Lib/MotionAC_CM4F_wc32_ot_hard.a)  After adding that line it pulls in the .a file (I'm working on macOS) it seams to throw an error inside the library. in function `MotionAC_Initialize':motion_ac.c:(.text.MotionAC_Initialize+0xbc): undefined reference to `Mot

We are using a VL53L8CX to detect seat occupancy from above in an environment which can have quite high levels of ambient light through adjacent windows.  We are wondering whether using a 940nm bandpass window in front of our sensor can help improve perfromance with high ambient light. If this idea has wings, I suppose something like this could do the job: https://midopt.com/filters/bn940/ Phil54  

My three ToF sensors on a finger ring are working (using a Portenta C33).https://youtu.be/qL_alTQpko0Next steps: train and realize gestures (and maybe visualize in Unity). So far, my sensors mounted on a finger ring (for RingGesture) is working (just to consider the power consumption and to do an active ranging in a sequence, just one sensor at a time). 

我想知道LIS3DH的三种工作模式是什么？我收到了两份文件，一份是高分辨率模式、正常模式和低功耗模式，另一份是关机模式、正常模式和低功耗模式。我比较了两种模式的寄存器配置。低功耗模式相同，第一个数据中的高分辨率模式与第二个数据中的正常模式相对应。你能给我一个关于这个问题的具体解释吗？

Hello,I'm trying to get a VL6180X sensor to work.I've downloaded the latest API: en.VL6180_API_V1.3.0.zipMy goal is to make the sensor work in I2c on a Raspberry PI in the c or c++ language.But I can't compile my code, or rather compile the api into a library.Where can I find an example of a makefile or command to do this?Thanks for your help.

Hi @Federica Bossi , I have a question about timestamp and the external sensor event.According to the application note of LSM6DSO (image above), timestamp's register is written when main sensor or external sensor event occurs. I have no problem with main sensor event because it seems like the timestamp register is written when the new data from accelerometer and gyroscope is ready to be read. However, I am unclear about the external sensor event since I wouldn't directly be polling data from the external sensor but through LSM6DSO's sensor hub.My questions is, for instance, assuming I will be reading timestamp data directly from the timestamp register on LSM6DSO, if I have LIS2MDL connected to LSM6DSO as sensor hub slave, does it mean that the timestamp register will be filled with data when the data from LIS2MDL arrives at LSM6DSO's FIFO through sensor hub operation?Thank you,

Hello,I am using a I3G4250D gyroscope and would like read the temperature. Currently, I read 246 (in decimal) in my register 0x26.In two's complement, it is equivalent to -9.   Then I have to multiply by -1 so -9 * -1 = 9°C (I am not sure)But It is the summer, and 9°C for a measure of temperature is not possible. I read 10 times the datasheet but no one information to convert the data from register into °C.Can you help me please ? It will be great to edit the datasheet to give a formule to transform the raw data in °C.ThanksTom

I have added Digital Inclinometer application of X-Cube-MEMS1(9.6.0) on stm32f777zit6 wherein I want to read the rotation(angle) from LSM6DSL device. I have added all the required component files and Motion_DI library to the workspace.Reference taken from: X-Cube-MEMS1>>9.6.0>>Projects>>Nucleo_F401RE>>Application>>IKS01A2>>DigitalInclinometer I am successfully able to configure the LSM6DSL with i2c1 of stm32f777zit6 and able to read the "who am i".But my MotionDI library is not getting initialised. During debug, my code gets stuck at function MotionDI_manager_init((int)ALGO_FREQ);.  Code is not working after this.Kindly suggest what can be the issue?? RegardsALPS  

would you please help to review the attached log and give some advice to customer?Thanks.Attached is the test log data, test conditions:1. The device is fixed on the desktop without moving or shaking. 2.2. The CPU reads the X/Y/Z data of the Sensor via I2C, and found that the X-axis data is decreasing, but the Y/Z data does not change in a wide range. 3.3. CPU platform: RV11264. Kernel version: linux 4.19, the kernel is a little change: linux is used in version 4.19, because in the L4.19 kernel to read the data also has anomalies, the customer ported the L5.10 version of the lsm6ds3tr-c driver.[root@RV1126_RV1109:/userdata]# . /test.sh[0] accel: -714 -1780 -16310 anglvel: 83 -438 -118[1] accel: -718 -1781 -16323 anglvel: 84 -437 -121[2] accel: -719 -1781 -16317 anglvel: 85 -437 -118[3] accel: -727 -1783 -16320 anglvel: 80 -438 -116[4] accel: -727 -1783 -16317 anglvel: 83 -437 -119[5] accel: -732 -1786 -16311 anglvel: 86 -438 -117[6] accel: -738 -1782 -16309 anglvel: 79 -437 -117[7] acc

I am measuring pressure using the LPS28DFW under conditions where the gas flow is approximately 70°C with a relative humidity of 80-100%. During measurement under these conditions, I encountered an issue where the sensor stops working. However, the sensor resumes normal operation once it is sufficiently dried. According to the datasheet, the sensor is expected to function under these conditions, but it currently does not. I would like to inquire about the possible reasons for this issue.Even in the presence of liquid droplets, the gel should prevent these droplets from reaching the MEMS, allowing it to function normally, but this is not happening. Could it be that the protective gel on the MEMS is leaking or detaching under these conditions?

Hi,I want to know the best solution to read accelerometer and gyroscope data using the STEVAL-MKI182V2 board with the STEVAL-MKI109V3. At this moment, I can use Unico-GUI to read live all the data from the sensor, but I want to make a AI model to read directly from the sensor and to predict certain movement from the sensor like standing up or seating on a chair for example.Is there a way by using the STM32CubeIDE or the MEMS studio? After opening the MEMS studio, the STEVAL-MKI182V2 doesn't look to be compatible with this program, why ?In STM32CubeIDE there's the module XCUBE.AI but can I feed through the model I'm giving him the data that the mcu is reading from the sensor live?I'm not very familiar with AI stuff so be gentle with me please :)

Hi,I'm unable to connect my STEVAL MKBOXPROA  (SensorTile.Box Pro) to Mems Studio, here's what I get:"board not identified" I tried uploading the DataLogExtended.bin, and it says it programs successfully, but I noticed there's a quick "verification failed" in there, and I still get the same problem as above.Any help on what I'm doing wrong would be greatly appreciated.Cheers,Keith.  

Hi everyone.I'm trying to use a NUCLEO-F401RE, a X-NUCLEO-IKS02A1, and a STEVAL-MKI197v1 and the following software: v3.2.0.4544 AlgoBuilder, v1.25.1.11665 Unicleo-GUI, v1.15.0 STM32CubeIDE, v6.11.0 STM32CubeMX and the X-CUBE-ALGOBUILD and x-CUBE-MEMS1 software packages (everything running on windows 11). First I didnt use AlgoBuiderI selected every sensor each board has on the x-cube-mems1 (package) and build it using CubeIDE (no error or warnings), but the Unicleo-GUI shows only the X-NUCLEO sensors, being unable to switch between (for example) the different Gyr/Acc sensors.If i dont select the board extension IKS02A1 CubeIDE gives no trouble (0 error and warnings) but the Unicleo-GUI doesnt recognice my board and i get stuck here:(note: If i select to list all coms it appears, but shows nothing and cannot start) When I try to create a custom firmware for AlgoBuilder, if I select the Algo custom aplication option without the MEMS IKS board extension. I copy the project

we are using the early version 1x in a vertical detection mode.  it has a 23 degree fov. in some of our testing we determined we need more.. FOV currently we tilt the board holding the TOF sensor to eliminate wasted FOV where the sensor would be projecting on a wall.  tof mounted 8ft high on the wall, projecting down, so we have tilted the FOV out, so that the back edge of the FOV is parallel to the wall its mounted on.  the newer 5x/8x have bigger FOV.. 63 and 90 degrees.. we don't need that much, BUT  I would like to detect on the outer edge, vs a smaller square 4x4 with edge against the exclusion zone. or 6x4 with the 4 edge against the exclusion zone. pic attached, box mounted on wal, tof pointing down,  zoom in on box, pad layout and detection zoneis this possible?  we need 6-10ft of detection in a narrow band. maybe 20-24 inches wide.  

How can I find the CE Certificate for the VL53L0X?

I can't find any information about status 9, how can I resolve this status?

Hi I have 4 sensors in configuration all have separate address and initialize ok. when first sensor start ranging I check the state vl53l8cx_get_power_mode wake it up and it ganges with no errors. but then I want to put it to sleep, so I again check the state  vl53l8cx_get_power_mode and sensor gives me 0x05 value instead of 0x04 expecting for wakeup state. Any reason for that behaviour or what does state 0x05 mean?