MEMS (sensors)

Hi all,I wanted to get information on the lifecycle of the ISM330DLC device? Is there a certain date when the sensor values will drift outside of the allowable tolerances? Thank you,Imran

Hello, I'm using a STEVAL-STLKT01V1 demo board to perform voice streaming over BLE using allmems 1 v4.2.0 (since versione 4.3.0 dropped support for my demo board). My setup is:Steval demo board with allmems v4.2.0Python script using Bleak library to manage BLE connectionI'm having trouble connecting the board to the script. I've managed to connect the board to my pc using Windows 10 built-in BLE device managemente. I've inserted the default pin and the computer notify me that the device is connected. When I try to connect to the STEVAL board the script hangs on the connect method until it sends a timetout error. I know that the library is working because I've used the same script in the past to connect to other devices.What am I missing? Is there some configuration to add/to remove?My goal is to connect the STEVAL board with allmems 1 v4.2.0 to my python script - without any pin - and subscribe to it's characteristic. I'm planning to add some custom characteristic in the future, b

I WANT TO TEST THE FSM FOR THIS LSM6DSO, WHICH IS EMBEDDED ON ONE OF PORTABE DEVICE TO DETECT ITS ACTIVITIES.THE MAIN POINT IS TO DETECT IT HAS NO MOTION IN A PERIOD OF 20 MINUTES TO ACTIVATE AN EVENT, FOR EXAMPLE, TURN ON AN ALARM.PLEASE HELP IN FSM !THANKS

Hi,I am using the setup with LSM6DSL + LIS2MDL. All works fine, with the exception that once started the conversion to FIFO with sensor fusion, at 104 sps, I observe significant periodical (around 22 samples cycles) noise on the last acceleration axis (Z). With LIS2MDL stopped there is no noise. More, if I disable the internal pull-up resistors, the noise disappears as well. Any advice on this?Many thanks,Florin

im using the ism330dhcx in an application where POSE (position + orientation) estimation are required.the accelerometer and gyroscope data are written to an SD card @ 100Hz and will be post processed to keep things simple, however, if anyone has a real-time algorithm that would be amazing! 

Posted on November 28, 2017 at 14:27Hi all! I am trying to read temperature and pressure values (then, convert pressure to altitude) from MS5611 barometer using I2C interface with STM32F4. So far, I managed to read both temperature and pressure values. I can read the sensor calibration values, do the digital conversion (long enough delay for conversion to be completed) and second order temperature compensation. Hence, I get very good, responsive temperature readings.The problem is pressure value is not as stable as temperature value. When I try to calculate the relative altitude using barometric formula, I get weird results. Such that, relative altitude value changes from 0 to 5-6 meters even if barometer is still. Moreover, when I move barometer up, pressure value increases (hence, relative altitude decreases), which is not possible  . So, what could be the reason for this problem? Should I apply some sort of digital filter? My pseudo-code to is as follows: p

My STM32 can only correctly retrieve data from LSM6DSL when debugging. The code remains unchanged. When debugging, I get the correct data; without debugging, I get incorrect data.My SPI frequency is limited to 8 MHz, and there is a delay of more than 200 microseconds inserted between each SPI send and receive call to ensure sufficient preparation time for the sensor.I have removed all irrelevant code.The problem seems absurd but has been troubling me for a long time.It's worth noting that even without debugging, I can correctly read the 'WHO AM I' register. This is what's causing me great confusion since the communication seems to be fineIn non-debug mode, the data register can only be read as 0 and 255 as logIf I start debugging mode, I don't need to perform any operations on the microcontroller. I just need to reset it and run at full speed. With the same code, I can obtain the correct data. void LSM6D_Write_Reg(uint8_t reg, uint8_t data) { IMU_CS_CLR; LSM6D_DELAY; LL_SPI_Tra

lsm6dsox sensor generates significant motion interrupt when a change in user location is detected. It generates an interrupt when the difference between the number of steps counted from its initialization/reset is higher than 10 steps. So it uses step counter. I need to detect the difference the user location by significant motion on 3 steps. please help me how i should change the significant motion feature to detect the user location on 3 steps. Thanks,

What is the maximum time-limit in minutes that can be set in the register LSM6DSO_WAKE_UP_DUR, for inactivity detection. I want to rise an interrupt after 20minutes. How is it possible? 

HiI'm currently using your LPS22DFmodule to measure pressure and I saw in the datasheet that the temperature accuracy is  ±1.5 °C (T = 0 to 80°C). My working range is between -15°C and 60°C. Could you please give me the accuracy of this sensor in the range -15 to 65°C?

Hi everyone,I'm working with the STEVAL-STWINKT1B and have a question about powering it with a 3.7V battery. The board uses the STBC02 PMIC, which operates between 4.5V and 5.4V according to its datasheet.The datasheet suggests the STBC02 charges a battery using a 5V input from USB or an external source. However, it also mentions a "Sys net" input for the internal LDO of the STBC02. This LDO output feeds another DCDC buck converter powering the MCU and peripherals, along with an analog LDO for the MCU VREF.My question: Can the STEVAL-STWINKT1B function directly from a 3.7V battery when there is not USB or external input, even though the PMIC datasheet specifies a higher voltage range?

I'm having problems to be able to establish the connection between STEVAL STWINBX1 and ST MEMS Studio software, with either of the two available ways (BLE or Serial port). In the first case, mainly the board won't be shown to select. In case it does, after trying to connect it, an error message appears: "Can't open the board". In  the second case, the board always appears to be selected but once I try it, an error message is shown which says "Board not identified". I'm not able to connect it no matter what I try. As said in the user manual relative to the software, this board can only work for the AlgoBuilder functionality, not for a full or partial sensor evaluation. It has to be said that the board works perfectly through BLE on the IOS App. Am I missing something? Sound strange to me. Maybe is just non-compatible or maybe it's a firmware issue (which I think it's not the case). Any suggestion will be very helpful.

I searched all available documentation, community and haven't found answer.AN5983 says nothing about motion and presence units.Code base (https://github.com/STMicroelectronics/sths34pf80-pid) and datasheet also say nothing about motion and presence units.I just would like to know, whether register values TPRESENCE_L(3Ah), TPRESENCE_H(3Bh), TMOTION_L(3Ch) and TMOTION_H(3Dh) correspond to any physical units like. mm, cm, inch, etc?Am I able to get distance from object to sensor?

Hello,I have been battling with getting an LSM303AGR to pass the self test. The accelerometer is passing the self test and the values look reasonable (Z-axis ~1g), but the magnetometer will not pass. I have 2 STEVAL-MKI172V1 boards, both are showing the same symptoms. I am testing with a Nucleo-U5A5ZJ-Q with I2C at fast mode (400KHz).Initially, I wrote my own self test based on the procedures in the datasheet (Version 11.0, Aug 2022). I was able to get the accelerometer to pass, but not the magnetometer. After debugging ad infinitum, I decided to try using the test provided from the STMems_Standard_C_driver repo contained in lsm303agr_self_test.c. I found a few posts here and this was what everyone was directed to.It is worth noting there are several bugs in this test: using uninitialized data, using previous data from the accelerometer test for the mag test without clearing, etc. Once I had these bugs sorted, I reran the tests to get the exact same outcome I was getting from

Hi,does someone know the diffenences between MP34DT05 and MP34DT05-A?The MP34DT05 is not in prodiction. Cant find other differences, what does the -A means?Thanks for helping me out.

Accroding to https://community.st.com/t5/mems-and-sensors/how-lsm6dsv16x-enables-sensor-fusion-low-power-sflp-algorithm/ta-p/585084LSM6DSV also have SFLP, do it change the factory calibration values? and which registers will be changed?

I am using an imu sensor ( ism330dhcx ) which I am working on to accelerometer and gyroscope data and I get the raw data from ims330dhcx and convert the raw data into actual angles by using the motionFX library. Still, there is some deviation between the imu sensor ( ism330dhcx ) and the standard reference device, so I need to calibrate the data for the standard output angle. so, please let me know if there is any software application tool to calibrate the imu sensor to the standard angle.

I designed a card that uses Stm32f446 and many sensors, but although the other sensor on the I2C line works, I cannot even get an I2C OK response from the LSM6SDL. I don't think there is a mistake in the design, but I am sharing it with you anyway, thank you in advance for your help. 

Hi everyone, Building a predictive maintenance device with a MEMS accelerometer. Using STEVAL-STWINKT1B as reference, but missing Altium design files. Anyone have them to share? Thanks!

Last year it was in STM32CubeIDE under X-CUBE-MEMS1... now it's no longer there. The only board extensions are IKS01A3, IKS02A1 and IKS4A1. What about IKS01A2?Pietro

Hi,I am working on a project to detect human presence. While testing I found that the TMOS sensor latches to a hot/cold body nearby and fails to detect humans. My measuring distance is only 6" - 10". Below is the debug of the issue I am facing with hot water. I have tested it with multiple permutations of ODR, AVG_TAMB, AVG_TMOS. I face the same issue in every scenario. The latching problem remains the same with cold water.  Ideally, the tpresence should come back to zero after the hot or cold object has been removed from FOV, but the sensor continues to stay on the new value (i.e. 1000) and treats it as the new normal. Please suggest what mechanism can be used to mitigate this problem.  Regards,Lovelesh Patel

I am a bit confused about changing the Gyroscope Full-Scale range during operation (dynamically).  Do I only need to change register CTRL2_G, or anything else too, to trigger a change to the Full-Scale range? What happens once I change the sensitivity? Lets say I sample the value sitting in the Gyroscope. Then I change the sensitivity. Will the next value from the gyroscope be based on the new sensitivity? Putting aside the settling time associated with changing sensitivity. How long before the new sensitivity takes effect? Is the next sample at the new sensitivity, or if that sample has already started conversion will it be the sample after that? If there is a time to take effect, how can I make this time to take effect consistent?     

If I am trying to use INT1 to indicate a "data-ready" event, does that result in a Low to High transition on the INT1 pin? Or a High to Low transition on the INT1 pin?  Does the line stay high indefinitely, until the data is read? What happens when new data overwrites the old data? Does the INT1 line change state, and then back again?   

Hi all,I'm trying to use the LIS3DH to detect if the object is in a non-safe position, i.e. standing on a slope (tilted) or in the upside down position and generates an interrupt if it's one of these. Setup:Y-axis pointing downwards in the stable position (y-axis reads +1G)ZH & XH whenever the threshold exceeds 480 mg for longer than 0.5 secondsODR on 100 HzRange +- 2gLPM enabledI've tried the postition detection function for this, but to my experience this only generates an interrupt when it's mostly in the known axis regardless of the set threshold. Maybe I've misinterpreted the datasheet.For now I've got the tilt interrupt working, but whenever I want to detect upside down it generates an interrupt when it's in the stable position. I know this is due to the inertial interrupt triggering whenever the absolute value of the axis is above the threshold, so gravity triggers this interrupt. I'd rather have the remaining interrupt detect a free-fall so I want all of this in t

How consistent is the LSM6 sampling clock? I didn't see any details regarding clock variation at different temperatures, etc in the manual. However, I may have missed it.