MEMS and sensors

When STHS34PF80 detects the human body for a period of time, TPRESENCE cannot fall back normally, and pres_flag is always 1。 code：

Hello,I intended to use VL53L4CDV0DH in my project.Could VL53L4CDV0DH measure reflective wafers material? ThanksChuong

Hi my name is Kevan Sherwood with Rayhawk Technologies, we develop an autonomous solution for opening and closing rails cars during the loading process. We have a toolhead that scans the gantry for a railcar to be opened and it then finds the latches opens them and opens the lid and moves on to the next. There are 2 feet on the bottom that do the opening and closing. We are testing with one of these VCSEL sensors (VL53L4ED) on the breakout boards to track the position of the feet on our tool when it is performing an opening and closing action. The goal is to see based on the foot position where in the process it is going wrong and have a data representation of what a good action looks like compared to a failed action. We have the sensor mounted at the end of the tool bar and it is pointed at a rod that moves with the feet. So it will measure the distance traveled when the feet are pressed. The distance being covered is 350mm total. Our main concern is dust and dust buildup on

I'm using LSM6DSV, and use it wake-up funciton, I will configure registers when wakeup, that time I got some invalid data such as "1.998665088 1.998665088 1.998665088", how to avoid it?

From theory, we define a Finite State Machine (FSM) as an abstract machine that can be in exactly one of a finite number of states at any given time, and is composed of a START state, a STOP state and a series of states, conditions and transitions. But how is this definition practically implemented in LSM6DSO sensor?For the LSM6DSO sensor, FSM is intended to detect a specific gesture: there are up to 16 independent state machines, both XL and G (and external MAG sensor) data can be used, and a number of interrupts and source registers for the event detection management are available.The activity recognition spans from Free Fall, to Glance, to Flip up and down, passing through Pickup, Shake and Wrist Tilt.If you are interested in a detailed explanation of the LSM6DSO FSM structure, that enables you to develop your own machine, please follow the next posts!Link: https://www.st.com/content/ccc/resource/technical/document/application_note/group0/56/95/d6/a1/34/4c/49/6d/DM005

Hi,I want to compensate for the temperature of the LPS22DF sensor.how does one go about programming for it? Is this formula correct?Pcorrected​=Pmeasured​−(TCF×(Tmeasured​−Treference​))If it is, should I use a temperature reference value of 25°C?Also, can you tell me the value of the Temperature Compensation Factor? Can I make a correction formula with TCO(Temperature coefficient offset) with a data sheet and program it?If possible, please let me know the formula that I can use TCO Thank you

Hello,    I am working on 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.The MotionFX library seems to work fine but the data from magnetometer are not correct since it requires calibration. On CubeMX even if I select the MotionMC software package, the MotionMC library is not added to the output.  I supposed this happen because the Magnetometer calibration functions are already available on the MotionFX library. The MX_MEMS_Process() is called from a FreeRTOS task, SensorReadRequest is set to 1 from a timer as done in the application demo. The problem is that MotionFX_MagCal_getParams(&mag_cal_data_out);does not update the mag_cal_data_out variable. All the hi_bias output values are 0, cal_quality always 0. During calibration I move the board with the typical "8" pattern but nothing happen.

Dear forum,We plan to assemble five LPS22DF sensors on the same I3C bus and (off course) to address them individually. According to the datasheet (7.4.1 MIPI I3CSM CCC supported commands) the answer to GETPID can only have two values, depending on SDO state. Beside that answer to GETBCR and GETDCR are fixed. As far as we understand Dynamic Address Assignment of the I3C protocol, there is an issue.We cannot use the I2C static address, because again it can have only two values, depending on SDO state.We cannot use Enter Test Mode (ENTTM) command, because it is not supported by the LPS22DF. (Even if we could, we might have 5 different random values in the Provisioned IDs, but it would not help so much to identify each sensor.)Thank you in advance

I am trying to use the VL53L4CD as a low power tamper sensor so that it interrupts when someone removes a lid.  I am using the ULP driver and I pulled in SetDetectionThresholds from the other driver.  I have been able to configure it to interrupt whenever the lid is outside of a threshold range (in case the lid is smashed in or removed), which seems to do exactly what I want.  However, if I quickly remove the lid completely so that the sensor detects nothing, it does not generate interrupts. Is there a configuration that tells it to interrupt when it sees nothing?

hi!I have a problem with the calibration of the IIS2ICLX-Accelerometer. I see there is happening a calibration but because I make a sensor fusion in the next step, I want to have the calibration fixed once its done. In the data-sheet and the forum I couldnt find a solution. Is there a possibility to manually control the background calibration process?Thanks!

I am working on a project using the LPS28DFW pressure sensor to monitor depth in water (~1000mBar / 10m), the sensor has a max operating range of up to 4096 mBar limited by its 24 bit 2s compliment output. As far as I can tell the negative half of the output range is never used unless autozero functionality is used, so I was hoping to use this to offset the pressure by a large value (ideally -4096) to better utilise the output range of the 2s compliment 24 bit output.  I have ran into 2 issues with this; first the REF_P (L and H) registers are read only, so I can't set a fixed offset, second the differential output is only put into the normal output registers and not into the FIFO. Is there any way around this? I see there is also a one time programable offset although ideally we would have control over when to offset for the extra range so the autozero function would be better.

Hello,We want to use LSM6DSV IMU sensor with external 3-axis 18-bit high-precision magnetometer sensor through IMU sensor hub function also with its FIFO function. We refer to following LSM6DSV sensor hub example:https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsv_STdC/examples/lsm6dsv_sensor_hub.cWe found that we can't get 3-axis 18-bit (3 x 3 = 9 bytes) mag sensor data from above example. It seemed that we can only get 3-axis 16-bit (3 x 2 = 6 bytes) through sensor hub with FIFO function. Because our total sensor data size has 9 bytes more than 6 bytes, we don't know how to use sensor hub to get 9 bytes mag sensor data with LSM6DSV. Could you give us some suggestion to acquire 9 bytes data from sensor hub or workaround method? Thank you very much.Nan

Hi,I'm designing a flight controller pcb using several ST mems sensors, (LSM6DSO, LIS3MDL, LPS22HH) and interfacing them to an STM32H743IIT6 microcontroller over a shared SPI bus. I'm on the second iteration of this board, all sensors worked on the first version except the LIS3MDL, this was consistent across multiple boards, which leads me to believe its either a hardware design or a software issue in how I was trying to communicate with it. The behavior I experience with the LIS3MDL is no response at all when any communication is attempted, this is confirmed by scoping the SPI lines.Below are screenshots from my oscilloscope of an SPI read of register 0x0F. Excuse the poor aliasing on the SCK lines, this was right at the limits of my cheap scope lol. Its not shown here but I also confirmed the CS line goes low before the clock starts and return to high after the read is complete.Yellow: MOSI, Blue: MISOYellow: MOSI, Blue SCKSoftware Version 1I used CubeMX to configure the project, as

Hello ST guys:We want to use LSM6DSV(IMU) with an external magnetometer(LIS2MDL) through Sensor Hub mode to gather data and place acc, gyr and mag readings in the FIFO. We want to make INT2 into an input signal which triggers the sensor hub. And we configure following registers to make START _CONFIG = 1 according to following documentation: sh_cfg_read.slv_add = (LIS2MDL_I2C_ADD & 0xFEU) >> 1; /* 7bit I2C address */ sh_cfg_read.slv_subadd = LIS2MDL_OUTX_L_REG; sh_cfg_read.slv_len = 6; lsm6dsv_sh_slv_cfg_read(&dev_ctx, 0, &sh_cfg_read); lsm6dsv_fifo_sh_batch_slave_set(&dev_ctx, 0, PROPERTY_ENABLE); lsm6dsv_sh_syncro_mode_set(&dev_ctx, LSM6DSV_SH_TRIG_INT2); lsm6dsv_sh_data_rate_set(&dev_ctx, LSM6DSV_SH_120Hz); lsm6dsv_sh_slave_connected_set(&dev_ctx, LSM6DSV_SLV_0_1); lsm6dsv_sh_master_set(&dev_ctx, PROPERTY_ENABLE); We also configure data ready signal on LIS2MDL: lis2mdl_drdy_on_pin_set(&lis2mdl_ctx, PROPERTY_ENABLE);

Hello ST Community,Test EnvironmentHW:STEVAL-MKI227KASTEVAL-MKI109V3 SW:Unico-GUI or MEMS-Studio PhenomenonThe pitch/roll angle generated by LSM6DSV16X SFLP is heavily influenced by longitudinal / lateral acceleration. E.g., if I mount the MEMS board in a car, the pitch angle can varied more than ±15° while the car is accelerating or decelerating. The problem is quite similar with this post: Solved: Re: Seeking Assistance: Overcoming Linear Accelera... - STMicroelectronics Community I tried adjusting the ODR and FS parameters but it didn't help. Disabling the gyro will make the situation even worse (pitch angle varied more than ±30°). AnalysisMy goal is to measure the pitch / roll angle on a moving vehicle. However, the sensor fusion output of LSM6DSV16X SFLP does not seem to be able to support this kind of dynamic inclinometer application. And I do not know whether and how can I adjust SFLP configurations to make the algorithm rely more on the gyro i

Hi,I managed to get the sensor working with firmware VL53L5CX_1.3.11. It works even if I reduce the data load and disable everything except distance.My problem is, that I do not receive any data if I switch the resolution to 8x8 - the sensor is only delivering data in 4x4 resolution. This happens for all data and for only distance data.I tried several different chips. The error code is 167 = 0xa7 in check_data_ready (GO2 error status). I got no error before neither when switching the resolution nor when starting ranging.Thanks

My goal is to implement the VL53L3CX TOF sensor on a Quanser Qdrone as a sensor for height control. As an inbetween I am trying to get the VL53L3CX working with my Raspberry PI3 first to better understand how the sensor and API work. So far I have not been able to find any premade PI3 libraries for communicating with the VL53L3CX. I believe this means that I have to use either the en.VL53L3CX_LinuxDriver_v1.0.5 or the EN.EN.bare_driver_VL53L3CX_v1.2.4. I have the sensor wired to the raspberry pi and using i2cdetect -y 1 I can see the sensor at address 0x29. From what I have read on other threads, the sensor does not send a stream of distance but instead sends a histogram of distance that needs to be decoded by the API/driver. This means that I will have to implement one of the drivers, right?What is the difference between the two drivers? Is there an advantage to one over the other or are they roughly equivalent?I am very new to Linux and am not sure how to install the drivers. Coul

Hello,in the datasheet for the L8, the power consumption for a low power mode such as autonomous 4x4, 1Hz frequency and 5 ms integration time is given to be 1.6 mW . I tried measuring the power consumption for a similar mode which is autonomous 4x4 @ 1Hz and 2 ms integration time, which should be the mode with the absolute minimal power consumption. However, I measure important currents on both CORE_1V8 and AVDD pins of the chip. For CORE_1V8, the average current is 16.87 mA and for AVDD I get 7.08 mA average. These currents lead to a power consumption of around 68 mW which is far from the datasheet and I was wondering if I was doing something wrong. Here are the measurements for the currents As you can see, the period between pulses is 1000 ms which validates that ranging frequency was set to 1 Hz. Also, there is only one laser pulse with a period (integration time) of 2ms, which validates that we are indeed in 4x4 (else we would have 4 pulses) and that we are not

I am using a LIS2DE12 to detect when a mechanical shock occurs to my device. The datasheet provides only nominal values for the sample rate and the sensitivity.What is the tolerance on the sample frequency, I am using the ODR nominal rate of 5376 Hz?What is the tolerance on the sensitive, I am using the +/-16 g range, which has a typical sensitivity of 187.5 mg/digit.What is the worst case temperature sensitivity?What is the worst case offset?If worst case values are not available is there some characterization data which could provide some guidance?Thank you.

Hi All, From ST website we unable find on the datasheet or more info on LSM6DSLUSTR this part and what is the current status of this part. Besides that, whether both of the part able replace each other.

HI,I am working on VL53L1 sensor using X CUBE TOF1 software. I want to change the I2C speed to 1MHz. Can somebody guide me how to do it?Thank you

Hi All I am running Unicon GUI on Windows 10 and using it to communicate with STHS34PF80 sensor plugged onto STEVAL-MKI109V dev board.I can fully interact with the senor via the GUI app. Meaning reading and writing all registers of interest.I however want see what registers are being written and read by the GUI so I attached my logic analyzer to the I2C pins but unable to read any sensible data. So I am assuming that the motherboard is communicating over SPI. I want to be able to sniff the interaction between the GUI app and the  senor over I2C.So what do I have to do to make the GUI change communication protocol.Ola

Hi all,For the last several days I have been battling this API for the VL53L5CX and finally reached the point where the initialisation passes every time. I proceed to set some of the configuration parameters (mostly resetting to the default values suggested in the application note). These functions also return status = 0. Then I start a ranging session. The problem is that checking the status/error output shows me that the function is failing with a 255 error. Further investigation with a debugger has yielded that the final if() check in the function sets the status too 255. This means that the data_read_size check has failed. see screenshot below for reference.I should note that, every single function and I2C transaction passes with no error. In other words, status = 0, the whole time, until this if statement. It is the physical value of the variables that does not match. Has anyone else had this error? or can offer some suggestions as to what is happening and how to fix it?Thanks

Hi, I am currently evaluating the LSM6DSV16X IMU and I have a few questions regarding the sensor fusion functionalities, particularly the gyroscope bias.It is not very clear to me when to enable the gyroscope bias, and how to use the data it provides.Here is my reasoning: at rest, the gyroscope data has a little offset from 0. In order to compensate from that offset, one can average the data received, and subtract that from the gyroscope data.Am I correct in thinking that the gyroscope bias generated by the SFLP block is an estimation of this offset ?I intend to record IMU data of a moving object. When the device is moving, does enabling the gyroscope bias functionality automatically correct the output gyroscope data ? Or should I first enable gyroscope bias at rest, save the value it gives me, and then subtract the offset from gyroscope data ?I believe the latter answer to be correct, could you confirm this please ?I am basing my code off of the provided examples : https://github.com/

Hi all,we have a customer hardware with ISM330IS sensor on .We want to implement a pedometer on it like in the ISM330DHCX. Is it possible ?I followed the repo ism330is-pid/ism330is_reg.c at 413acfb51fd6f81a7449980a1caf286e37c909fe · STMicroelectronics/ism330is-pid (github.com) but it seems to not include it !Instead I see it for ISM330DHCX (STMicroelectronics/ism330dhcx-pid: ism303dhcx platform independent driver based on Standard C language and compliant with MISRA standard (github.com))  Can I use that code too ?