MEMS (sensors)

Hi,I want connect my SensorTile box with my Raspberry pi. For this, I use example_ble_1.py, but every time when i try to connect the devices then one of the given errors occur:guest@raspberrypi:~ $ sudo python3 example_ble_1.py##################BlueST Example##################Scanning Bluetooth devices...Discovery started.New device discovered: TB2 .Traceback (most recent call last):File "/usr/local/lib/python3.9/dist-packages/blue_st_sdk/manager.py", line 313, in discoverself._scanner.scan(timeout_s)File "/usr/local/lib/python3.9/dist-packages/bluepy/btle.py", line 854, in scanself.stop()File "/usr/local/lib/python3.9/dist-packages/bluepy/btle.py", line 803, in stopself._mgmtCmd(self._cmd()+"end")File "/usr/local/lib/python3.9/dist-packages/bluepy/btle.py", line 309, in _mgmtCmdrsp = self._waitResp('mgmt')File "/usr/local

I have a problem with identifying the sensor type from the marking on the housing. One is LSM6DSO32XTR and the other is ASM330LHHXTR. Unfortunately they came in a bag without a description on the label. One is marked T3 [QR code] 233 and the other LC [QR code] 307.Is there a way to identify them without attaching them to the board? Unfortunately the datasheet did not help.Thanks

Hello, I am testing STEVAL-MKSBOX1V1 connected via USB to a Raspberry Pi4. On the SensorTile.Box I have installed the firmware version 3.4.6 or 3.4.7 (tried both these versions), since the last version 3.4.9 has a bug with the application I am running. The application is the classic "Vibration Monitor" app that is present by default on the SensorTile.Box, with some little modifications (expert mode): instead of sending data over BTLE interface, I have defined to send the output data of this application over the USB port, which is connected with the Raspberry PI4. After creating my custom application on my Android app, I click on PLAY and the custom firmware is flahed via BT on the SensorTile.Box. On Raspberry Pi Terminal interface the device is recognized from that moment on as "ST Virtual COM Port". All perfectly working, since the red led on the device starts flashing (i presume it

I've been trying to create a mesh for 2 weeks now and even just send data from a card to a pc via bluetooth but I'm completely stuck and I really need help. I have 3 sensortile cards. box (STEVAL-MKSBOX1V1) I saw that it had v5.2 BlueNRG-M2 and so normally I could make a mesh using function pack or even the application ios st ble mesh. but I'm totally blocked I wonder if this is even possible.Can anyone give me some pointers, particularly on how to integrate the function pack or something else?

helloI've been trying to use the LSM6DSV on it's steval-mki239a board with a nucleo board (nucleo-l476rg) via SPI and the lsm6dsv is not answering whatever the configuration of my SPI is.The sensor is fine since it work with the steval-mki109v3 board ans the MEMS studioI checked the SPI signal on the steval mki109v3 with a logical analyzer and found several odd things but the sensor is answeringI don't know if it is my analyzer but the MISO line is always stuck at 1 and the level of MOSI are strange but the sensor understand the message and answer with the right value (WHO_AM_I register:  MOSI should send

Hi,  I am using the LIS2DH12 to interrupt me on an inertial wake.  I am running in Low Power mode with a scale of 4G.  After verifying that the X axis produced the force that caused the interrupt I read the X_OUT_L and X_OUT_H registers to get the 2's complement value in the X_OUT register.   I want to calculate the actual force in mg that caused the wake.  Can someone verify that I am doing this correctly? OUT_X register contains 0xFC00I use these functions in my calculationint16_t twos_complement_to_decimal(int num_bits, int16_t num) {    // Create a mask to isolate the sign bit (most significant bit)    int sign_bit_mask = 1 << (num_bits - 1);    // If the sign bit is set (number is negative)    if (num & sign_bit_mask) {        // Invert all bits, add 1, and negate to get the decimal value  &nbs

Basic function is to calculate Heading 25 times per second. Using C++, STMCubeMX, and STM32L476IDE. Chip is the STM32L476RET.  Is this chip fast enpough? Need heading 25 times per second for main loop processing. Using timer 3. HAL is working, but is much to slow. Do not know how much faster LL would  be. Code below for the Mag. void Get_Mag (void); // Gets Mag, MagF, MagFG // 1. Reads Mag x,y,z // 2. Converts to 16 bits, // 3. Converts to floating Point, HAL_GPIO_WritePin(GPIOC,GPIO_PIN_5,GPIO_PIN_SET); // Sets Mag CS On HAL_GPIO_WritePin(GPIOC, GPIO_PIN_4,GPIO_PIN_RESET); // Sets XL CS Off TX[0] = (OUTX_L_REG_M | 0x80); Mag_Data[0] = 0;

I am using the HP filter and have the device configured for inertial detection using the HP filter.  I have the INT1_CFG register set to 0x2A so the device will interrupt when a HIGH event is detected on the X, Y, or Z axis.  The device does reliably interrupt me when I bang my board on my desk.  When the interrupt happens I read the INT1_SRC register to see what axis's the inertia was detected on that caused the interrupt.  I then wait a complete second before proceeding so I am sure the acceleration data has made it's way to the proper registers.  I then look at the XH, YH, and ZH bits to see which axis's caused the interrupt.  If the XH bit is set I read the OUT_XL and OUT_XH registers to get the acceleration value; I do the same for the YH and ZH bits reading the corresponding OUT_ registers.  The issue is that more often than not the OUT_X, OUT_Y, and OUT_Z registers are set to 0 when I read them.  I would expect the OUT_ registers to hol

I have recently brought a STEVAL-STLKT01V1 SensorTile kit in which LSM6DSM, LSM303AGR & LPS22HB are connected in 3 wire SPI on the SPI2 line of STM32L476. I pulled 4 CS lines to high at the beginning of the program and have set the SPI2 to Half duplex master mode with low data transfer rate. even though using the c command  lsm6dsm_spi_mode_set(&dev_ctx, LSM6DSM_AUX_SPI_3_WIRE); I'm getting no response on spi read, so the program is getting struck at lsm6dsm_reset_get(&dev_ctx, &rst). I was able to use 4 wire SPI with STM32F407 and LSM6DSM, but I still face issues with using 3 Wire mode with STM32F407 and LSM6DSM i have defined the CS Pin: #define CS_up_GPIO_Port CS_AG_GPIO_Port#define CS_up_Pin CS_AG_Pin my GPIO Configuration:   Sensor Initialization: /* Initialize mems driver interface */ stmdev_

HiWe are developing a project in which we are using LIS3DH to calculate the angle and based on that angle we stop/start an actuator.The sensor is mounted on a PCB which is aligned along x axis i.e. when stationary the acceleration in x axis is 1g * 9.98 and all other axis are zero (nearly). The movement of the PCB is along x axis.  Now our aim is to stop the movement of the actuator when the angle is 15 deg.The problem we are facing is that the reading of LIS3DH are not repeatable and not stable.For e.g. in the Initial Position I am getting the following acceleration values:

I use IIS3DWB with no LPF2 enabled, and I understand the Frequency response shown in Figure 13 at page 20 of the datasheet.I know that I can enable low-pass LPF2 filter, but from the same graph I don't understand if this filter can be enabled as a hardware anti-aliasing filter, or not.I mean, after I enable ODR/4 (as an example), is it safe decimating ODR by 4, or not?This decimation is safe if LPF2 is a hadrtware filter that "cuts away" every frequency above (ODR/2)/4.From the graph it doesn't seem so, but i't not 100% clear IMHO Thanks in advance for the clarification.

Anyone have any idea if the temperature can remain the same for long periods of time in a stable environment?

I followed 'STEVAL-MKI109D Professional MEMS Tool motherboard for MEMS adapter boards' and installed MEMS Studio.I then placed STEVAL-MKI250KA on STEVAL-MKI109D by following UM3420 and AN6173.  When I boot MEMS Studio, it just does not recognise the board either via bluetooth or serial.  I also installed https://www.st.com/en/development-tools/stsw-stm32102.htmlAny ideas what I am doing wrong?

I am working with the LSM6DSO16IS in MODE2 configuration with ISPU enabled. I have some questions regarding the MDRDY (Master Data Ready) signal:1. How is the MDRDY signal handled in MODE2 when using the master I2C interface with external sensors?2. Is there any specific configuration needed in DRDY_PULSED_REG (0x0B) for proper MDRDY operation in MODE2?3. Can you provide information about the timing relationship between MDRDY and the external sensor's data ready signal in MODE2?4. Are there any application notes or reference designs specifically addressing MDRDY usage in MODE2?Current configuration:- Like JP4 from X-NUCLEO-IKS4A1 SCH, the INT2 of LSM6DSO16IS is connected to the interrupt output of an external sensor- LSM6DSO16IS in MODE2- ISPU enabled- External sensor connected via master I2C- Using X-CUBE-ISPU framework

We are interfacing the IMP34DT05TR microphone with the STM32F423ZHJ6 microcontroller. I have attached the schematic for reference. However, we are unable to read the microphone data on our custom board, as we always get a NULL value in the output. Later, we connected the STM32F423ZHJ6 microcontroller (which we customized) to the IMP34DT05TR development board via wires. In this setup, we were able to successfully read the microphone data. However, once we mounted the microphone on our customized board, we only receive NULL values.    

I have lis2dwt12 sensor and nrf24l01+ sensor.Can i connect these devices on same spi line? i will select different CS pins.Thank you for now.

Hello, I have the sensortile box pro. I have used the algobuilder in the MEMS-studio to configure various data outputs (Acc, Gyr, RotationVector 6x). The sensortile isplugged in with USB. I can see those data coming into the MEMS-studio algobuilder evaluation, and I have no problem logging the data. I want to know how can I pull the same data into a Matlab. to perform a few real-time analysis. I cannot find documentation on how the communication works. I can connect to sensortile as a serial port object. I'm assuming the baudrate is 115200. However, I don't know what commands I need to send to it for it to return those data. Can anyone point me into the right direction? Thanks.  

I'm using ST MotionFX v2.7.1 and have encountered an issue with heading calculation.I'm following the sample code from the document:um2220-getting-started-with-motionfx-sensor-fusion-library-in-xcubemems1-expansion-for-stm32cube-stmicroelectronics #define STATE_SIZE (size_t)(2450) static uint8_t mfxstate[STATE_SIZE]; MFX_knobs_t iKnobs; MFX_input_t data_in_scale; void main() { /* Sensor Fusion API initialization function */ MotionFX_initialize((MFXState_t *)mfxstate); /* Modify knobs settings & set the knobs */ MotionFX_getKnobs((MFXState_t *)mfxstate, &iKnobs); iKnobs.LMode = 2; iKnobs.modx = 1; iKnobs.output_type = 1; iKnobs.start_automatic_gbias_calculation = 1; //orientation MotionFX_setKnobs((MFXState_t *)mfxstate, &iKnobs); MotionFX_enable_6X((MFXState_t *)mfxstate, MFX_ENGINE_DISABLE); MotionFX_enable_9X((MFXState_t *)mfxstate, MFX_ENGINE_DISABLE); /* E

Hi,I read the LSM6DSV on the STEVAL SMKI239AA using a Raspberry Pi Pico running Circuit Python. The CTRL1 register is set to 0x07 (240 Hz ODR, high performance). My output is converted to m/s^2 and looks like that when I move the sensor board slowly:Xacc: -8.6479 | Yacc: -1.3192 | Zacc: 5.5958 | sum: 10.38456 Xacc: -8.6479 | Yacc: -1.3120 | Zacc: 5.6042 | sum: 10.38817 Xacc: -9.1219 | Yacc: -2.3511 | Zacc: 6.3375 | sum: 11.35342 [snip]Xacc: -6.9216 | Yacc: -5.3630 | Zacc: 6.2219 | sum: 10.74166 Xacc: -9.1081 | Yacc: -6.2662 | Zacc: 6.7229 | sum: 12.93914 Xacc: -10.0293 | Yacc: -5.9400 | Zacc: 8.0236 | sum: 14.15091 Xacc: -6.5439 | Yacc:

Hello friends;I aim to develop FreeRTOS STM32 based flight control card software. First of all, I am trying to read data from my LIS2DH12 and LIS3MDL sensors in separate tasks and see them on my serial screen at usart1 921600 baudrate for debug purposes. However, I encounter a few problems. I present my project file in the attachment and I will explain the problems I encounter in detail below. Thank you in advance for your interest.These are ;1-) When I run the UART in normal mode, I can only read data from LIS2DH12.LIS3MDL only ends with a not found sensor 0xFF warning at startup, but the data flow of LIS2DH12 continues.2-)When I run the UART with DMA and semaphore, I can only read LIS3MDL data. This time I cannot see the LIS2DH12 sensor data on my serial screen.3-) However, sometimes the sensors sometimes interrupt the serial screen data flow, as if the sensor is locked and becomes inactive, but every time I reset the stm32, 10-20 data comes and go

Helloin the data sheet of LPS22HH the absolute accuracy is  ±0.5 in which range of pressure ? ( 800 hPa to 1100 hPa) ? because i tested some samples in 0.3 bar and 0.5 bar, there big difference between the mesure of LPS22HH and reference (exactly values).Thanks

I want to use the motionfx library in the x cube mems1 package for my flight control card and ahrs project, my aim is to obtain roll pitch and yaw values with sensor fusion, but I have not come across an example code for using motionfx. Can anyone help?

Hello,in the datasheet of LPS22HBTR the absolute pressure accuracy is between 0. and 1 mBar in the range of 0°C and 65°C .Please have more information about the absolute pressure accuracy in negative temperature ? because i will use it betwen -20°C and 0°Cthanks 

I have asm330lhh acceleration and gyro sensor. I have a problem with communication with spi, when I try my other mems sensors (lis3mdl, lis2dh12) with the same connection line, I get the correct whoiam code, while with the asm330llh sensor I sometimes get random values or 0xff.

HelloI ordered 10 samples of the LPS22HH pressure sensor evaluation board (STEVAL-MKI192V1). Upon receipt, I noticed that each board was packaged in a cardboard box but without an anti-static bag.I then began taking measurements by varying the pressure inside a test chamber. Out of the 10 samples, only 5 function correctly and measure the expected pressure, while the remaining 5 consistently read only 1 bar.Could this be due to the high sensitivity of the board and the sensor itself, or could it be a delivery issue? I find this particularly concerning as I ordered from three different distributors and encountered the same issue. This leads me to wonder if the sensor is particularly fragile. Could you provide any insights on this? thanks