MEMS (sensors)

I'm using the temperature sensor in LSM6DSRX.In page 12 (4.3 Temperature sensor characteristics) of the Datasheet (see the image), what is "Toff" (Temperature Offset)?The Table 4 gives a range of -15 to +15 C for Toff, what is this range for? The Table also gives the operating range of -40 to +85 C. I was wondering how to use "Toff" in calculating the temperature ?Thanks for any help!

The STEVAL-MKI197V1 has standard breadboard pins on it. The muRata dk (WSM-BL241-ADA-008DK) has available connection points in position JP4 - looks like the right place to attach. Is there a ribbon cable or adapter to connect these two boards together?? thank you! (see photos)

I've used a number of times LSM6DSL IMU sensors and I never had any problem with them: they are in general very precise and straightforward to use. However, in a recernt pre-production run, some accelerometers provided strange values on one or two axes compared to the usual values. In these conditions (stationary board in horizontal position) the expected values on two axes should be close to 0 g, i.e. raw values in the range of about +-200 for a full scale of 16 g. This happen with most units, but on some others (identical firmware, identical boards) we get much greater values, something like >5000 or even >16000, that, by the way, are normally sensitive to the self test stimuli. The problem seems to be only in the accelerometer values: other functions work correclty.My question is: are these values something "normal", that can/must be corrected through calibration (with the offset registers or in firmware)? Or have I to assume that these devices have been simpl

Question is if I can use LIS3DH with VDD only (3.3v) , and VDD_IO (1.8v) supply only during configuration ? And in this case, what power use INT1 and INT2 pins ? If possible to run on VDD only with having them working (at least as OD ?).Datasheet is not clear about that....

hi, I am trying to debug the bootloader which comes with sensortile.box to change it for my requirements. In doing so I want to inspect how it works using debug session. But unfortunately, when starting to debug the session the curser doesn't even recognize the main.c func. how to debug a bootloader successfully. I tried with user applications and I can debug...

Hello,When configuring the LSM6DSL ( STEVAL-MKI178V1 ) to sample Data at 6664 HZ ( without any digital Filters active, FS= +- 16g, +- 250deg/s ) there seems to be an consistent 1deg/s @ 800Hz noise on some gyro axis. The same signal but stronger ( > 10deg/s @ 800Hz ) is also apparent on a proprietary board. What causes this noise ( it seems to come from the LSM6DSL itself ) and why is it stronger in some modules than in others?Doesn't this signal violate the specified noise density of 4mdps/sqrt(Hz)? STEVAL-MKI178V1: proprietary Board:

Is it stored in the FIFO when the threshold of the INT1_THS register is exceeded?Or is it stored regardless of the threshold of the INT1_THS register?

I have an application with a LSM9DS1 that is powered up for a few minutes at a time and then shutoff. It might be powered up again for a few minutes within the same day, or be used only the day after or a few days later. The purpose is to get angular speed information from the gyro.During testing, I noticed that each time I turn it on, I might get an initial reading that differs progressively from the last time I turned it on. Specifically, during a period of 2 weeks, the speed reported varied progressively up to 0.1 rpm or about 0.6 dps. This was measured against a reference source, that was calibrated with other means (laser tach).This seems too high a drift to me, especially as is not "continuous" drift while measuring. Is this expected or normal ? Any clue on what might be causing this ?Thanks

I am trying to get the LIS2DE12 to generate an interrupt when shaken. I have connected the INT1 pin to an open drain I/O pin of my MCU. I an get it to generate the desired interrupt with some reliability. However, when it is just sitting still, it generates interrupts randomly. The ODR is 10 Hz. How might I stop this?Thanks in advance,Rob

I am trying to set up a self test process for an assembly including an LIS2DE12. The device works normally when I tilt and invert it. When I try to put it in to self-test mode by writing either 02h or 04h to CTRL_REG4 the readings are the same as with 00h written to CTRL_REG4.I initially tried using the process for the LIS3DH on Page 57 of AN3308 but that says to write 80h to CTRL_REG4, which does not seem to be valid because that would set the BDU bit to 1, not valid for an 8 bit part, and not set either of the self test bits.Can someone please shed some light on whether the self-test function is available with the LIS2DE12 and what I can expect from it.Thanks in advance,Rob

Hello,I can succesfully have ready (DRDY) under interrupt (INT1) at low or normal power vfrequencies. Cool.BUT I do not success in using threshold and duration.Can anyone, can give me the correct configuration to do this:Get an INT1 interrupt each time the sensor as over pass a threshold for more than 50 samples at 10Hz low power. And then do necessary process in the interrupt to renew this indefinitly.The threshold can be 0 for now to ensure that the sensor will create an interrupt periodically each 5 sIn advance many thanks

Is "Duration" for wakeup based on the "LOW power freq" (ie the selected value from 0,5 to 10Hz) or from the "NORMAL ODR" mode (ie; the selected value from 50 to 1000) ?Is possible to manage to have the interrupt (INT1) only when Threshold/duration is passed ?

Hello Community,I am working on the LIS2DE12 accelerometer. using the example code by STM.https://github.com/STMicroelectronics/STMems_Standard_C_driversI am making a test case with the lis2de12_filter_hp_rst_on_int.c example.I have placed a module on the ground. still getting invalid results on the output. pi@raspberrypi:~/test/lis2de12_STdC $ ./main.bin tx_com : Acceleration [mg]: 15.60 -46.80 904.80 25 tx_com : Acceleration [mg]: 0.00 0.00 0.00 15 tx_com : Acceleration [mg]: 0.00 0.00 15.60 15 tx_com : Acceleration [mg]: 0.00 0.00 0.00 15 tx_com : Acceleration [mg]: 0.00 0.00 0.00 15 tx_com : Acceleration [mg]: 0.00 0.00 0.00 15 tx_com : Acceleration [mg]: 0.00 0.00 0.00 15 tx_com : Acceleration [mg]: 0.00 0.00 0.00 15 tx_com : Acceler

Hi !I am trying to do what I feel is a rather simple thing, which is doing the exact same thing as the demo firmware provided as an STM32CubeExpansion for testing the CCA02M1 MEMS microphones on a Nucleo L476RG.So far, I have gotten to the point where the USB descriptor are properly initialized and I can the board as a microphone as Audacity. There is absolutely no sound coming out of it when I hit the record button however.I have checked that the microphone works with the demo binary, so I know by solder bridge configuration is good.I am trying to use a 48kHz sampling rate, with USB driven acquisition being disabled. I also noticed a few oddities alongside the "no sound in Audacity" bit:The record speed in Audacity is a bit slower than with the demo firmware. Meaning a recording a second of "audio" in Audacity actually takes more than a second.When examining the USB frames with an USB analyzer I noticed ap

Hi everyone,I try to implement range measurement using the VL53L3CX sensor with the VL53L3CX_API_1.1.4. I can get distance measurement and talk with the sensor properly using the basic patent :Status = VL53LX_WaitDeviceBooted(Dev); Status = VL53LX_DataInit(Dev); Status = VL53LX_StartMeasurement(Dev);   for(;;) { Status = VL53LX_WaitMeasurementDataReady(Dev); Status = VL53LX_GetMultiRangingData(Dev, pMultiRangingData); printf("d= %5dmm",pMultiRangingData->RangeData[j].RangeMilliMeter); }The issue is : I have FLASH memory overflowed with .data and user data when it comes to add my applicaction! (by 17kB!!) :fearful_face: I don't need to detect more than 1 object, and I don't need precision nor any calculation feature but the ones strictly needed to have distance. Is there any functions or c files I could get rid of? I tried to mess around with the API but there are quite a lot o

In my application I read out the sensor values (register 0x20-0x2D) with an interrupt every 20ms. After a software reset I have the strange behaviour that the acceleration value of the X-axis stops at a certain value (somewhere in the range of the current acceleration). The Logic Analyzer shows that the sensor value of the X-axis read via SPI is always the same, while the values of the Y- and Z-axis always change slightly. Since this is a safety-relevant application, a static value over a certain period of time is considered a sensor defect and an error is registered. With a software reset, the power supply to the sensor remains and the application is reinitialised. I have tried to solve the problem in different ways (reload boot register, CR1 power down/on, axis desable/enable, the mentioned options in combination and different order) but nothing has helped. If the sensor axes are deactivated and reactivated (CR1) after the software reset, valid values come from the s

What is the difference between the marking "SH" and "S2" for the part number LSM6DS3?Please advise if the correct top marking SH" and "S2" are both valid. Thanks

Hello everyone, I am new to STM32 and to Keil. I would like to change the accelerometer resolution from 2G to 16G, but due to my inexperience, I don't know how. My teacher didn't help my and said that I need to figure it out by myself, but I really don't know what to do. Can somebody help me what to do a what to change? Here is code that teacher provided: I will be very thankful is someone can help me. //-----------------------------NASTAVENI AKCELEROMETRU ( Setting)------------------------- //Defaultne je rozlišení +-2g //SPI Komunikace HAL_GPIO_WritePin(GPIOE, ACC_CS_Pin, GPIO_PIN_RESET); //Chip select adresaRegistru = 0x20; //CTRL_REG4 HAL_SPI_Transmit(&hspi1, &adresaRegistru, 1, 50); data = 0x37; //povol osy, 12,5Hz na vystupu HAL_SPI_Transmit(&hspi1, &data, 1, 50); HAL_GPIO_WritePin(GPIOE, ACC_CS_Pin, GPIO_PIN_SET); //Chip select HAL_Delay(20);

Hi,I am designing Obstacle Detection Sensor for AGVs. I have following requirements:Ranging Distance : 5-8mRanging Frequency: 30HzFoV: 135 degree with multiple sensorsI have gone through Vl53L1X and Vl53L1CB sensor, i found that ranging distance of 8m is possible with Vl53L1CB sensor in Ranging Mode. Is it possible in indoor environment?Along with this what will be output of Vl53L1CB sensor? Will that be distance of detected object?What will be affect of ambient light on ranging distance?Vl53L1CB GUI is accessible through F411RE Nucleo Board or not?Please resolve my queries so that i can proceed furtherRegardsAkansha Verma

I am having trouble evaluating a custom PCB with a LIS25BA accelerometer fitted.The circuit is exactly the same as ST evaluation board for the same part (STEVAL-MKI211V1 + MKIGIBV3).When connecting to the motherboard using the ST evaluation board, UNICO is able to connect to the device and all the data and registers are there as they should be (i.e who_am_i = 20h).When using my own PCB connected to the same pins as the evaluation board the connection fails:"ERROR: The adapter board has not been recognized.The WHO_AM_I register value does not match the device selected"Am I missing a software configuration step over I2C? Is the evaluation board configured to anything other than factory default?Have I translated the interconnections incorrectly?I would be grateful for some support on this matter.Thank you.Regards,Robin

Hello. I just start to work with vg6640 image sensor. According to the datasheet all what i need to do make it start streaming is to make sensor into STREAMING state. I have done that, the SystemFsm register shows that i'm in the SENSOR_STREAM state and TempSensorTop/Bot register shows that sensor start heating, but Frame_Count value is not increasing and there is no frames it seems. Can you give me any advises on the sensor start sequence? What is the approximate sensor temperature in the streaming state?Can you also explain how Test Pattern works? It seems like after i write into TestPatternControl register Frame_Count value becomes 0x00000032 and then 0x00000000 on the next read.P.S. For some reasons Frame_Count register gives me 0x000000FF in Idle state, but datasheet says that it should be 0xFFFFFFFF.Thanks.

Hi, I have purchased several three-axis acceleration chips, but I mixed them together by mistaken. The chip is too small, and I can’t see if there is any text on them to distinguish them. After comparing the chip manuals of both , It seems to be indistinguishable from the software function, so what should I do? This is a very urgent matter. Thank you in advance for your reply.

I've got erratic behavior of access to H3LIS331DL sensor from my MCU when STOP2 mode is set. It seems that sometimes, the Interrupt ( INT1 on DRDY) received from theH3LIS331 is not, or very lately processed (maybe after wake up from other reason). I can see that when the H3LIS331DL interrupt is processed very late (about 7ms after the INT1 signal), sometimes the I2C Data reading (that I can see with digital signal analizer) does not reset the DRDY interrupt from the H3LIS331DL, and then the acquisition process is no more ongoing.By the way if I set HSI clock either than MSI before entering STOP2 mode the processing seems as fast as if i was not in STOP2 mode... and then every thing is ok ?Any clues ?

I am trying to build a project 'GPS aided INS' in college. I have tried many options for interfacing  "MKI196V1 (ASM330LLH)" IMU, but couldn't get the results. I tried interfacing the sensor with STM32 (maple mini) using sduino, also with nano and uno. If anyone has any resources related to the above-listed issues, kindly help.

I have tried to work with LIS3DSH sensor using I2C protocol. I applied procedures on STM32f manual. But it didn't work. I wanna just receive x axis value. According to this, The GPIOD-12 will be on if it is less than 20. Maybe ı could not realise its failure. Anyone help me about that ? ahead of time, thanks.#include "stm32f4xx.h" // Device header #include "string.h" #include "stdio.h" #include "stdlib.h"   #define SLAVE_ADRESS 0x1E // LIS3DSH SENSOR ADDRESS   /*Prototype Functions*/ void I2C_START(I2C_TypeDef*,uint8_t,uint8_t ); void I2C_WRITE(I2C_TypeDef*,uint8_t); void I2C_STOP(I2C_TypeDef*); uint8_t I2C_READ_NACK(I2C_TypeDef*); uint8_t I2C_READ_ACK(I2C_TypeDef*);   // Valuables int8_t x=0,y=0,z=0; uint8_t r_data=0;   int main() { // Definitions GPIO_InitTypeDef GPIO_InitStructure; I2C_InitTypeDef I2C_InitStructure; // Clock Buses Configurations RCC_AHB1PeriphClockCmd(RCC_AHB1Periph_GPIOE| RCC_AHB1Periph_GPIOD |RCC_AHB1Periph_GPIOB,