MEMS (sensors)

 In the document titled "STEVAL-MKI109V3 Professional MEMS Tool motherboard for MEMS adapter boards" UM2116, on p. 16 it is listed that the returned value from the *start command is: s t A_XH A_XL A_YH A_YL A_ZH A_ZL Int1 Int2 TL TH sw1|sw2 \r \n . This is incorrect as the device has a gyroscope and is returning 40 bytes. I need to know what these 40 bytes being returned actually are. Please advise. Thank you.

Hi,We notice IIS2MDC have single measurement mode which can be used for one shot operation. The datasheet also mention how to calculate current consumption for such mode.However we can not find if the sensor will go sleep immediately after measurement, or will it sleep after available data is being read?We might want to do something like this :MCU trigger the measurement, MCU go to sleep, ignore/disable DRDY interrupt, MCU wake up 1 second later, MCU read IIS2MDC output register, MCU trigger measurement, ..... (looping); thus creating 1 Hz measurement intervalWill such scenario able to decrease current consumption to expected value from datasheet's current consumption equation (page 16)? Or will there any leak current since the data is not read immediately?

Hello, I want to use a accelerometer which is LSM6DS3, and it's spec says that it's maximum ODR is 6600Hz.So I want to know is the ODR the same as sampling frequency?Or is it just out data rate? And is sampling frequency less than ODR? If so, what's the maximum sampling frequency is this sensor chip?Thanks!

What all interrupt registers do I need to setup for a specific amount of of shock for a specific duration?I specifically want to generate an interrupt when there is a vibration in any direction and should be able to tune the amount of vibration(threshold) to generate the interrupt. SpiTx(LIS2DH_INT1_CFG, 0xCF);   SpiTx(LIS2DH_INT1_THS, 0x01);  //1LSB*15.625mg/LSB=16mg SpiTx(LIS2DH_INT1_DURATION, 0x00);

Use 3-axis acceleration LIS2DS12page 10 figure 2 Pin description in datasheetThe z direction is reversed in the output, but I don't know why.ex) Gravity acceleration is displayed as + g.

when its chip select input is high, as it is supposed to operating in an I2C mode. Will the HTS221 data bus change into an output state and override the common SPI data?

I'm having some issues in trying to get valid data out of the LIS3DH. For some reason I am only receiving a constant value of -1 [0xffc0 10 bits left aligned] on all channels and FIFO slots. I can read/write all other registers just fine, it's just the sensor data that is not working. I'm sure it's something I'm missing in the config, but for the life of me I can't seem to find it.VCC and VCCIO is 3V3Communications is over I2C @ 400KHzI have repeated this failure mode on multiple devicesMy Init process is as follows:Read the Who_AM_I register and abort if it does not return the correct IDReset the device state by zeroing out all critical registers (TEMP_CFG, CTRL[1-6], REF, FIFO_CTRL, INT1_CFG, INT1_THS, INT1_DUR, INT2_CFG, INT2_THS, INT2_DUR, CLICK_CFG, CLICK_THS, TIME_LIMIT, TIME_LAT, TIME_WIN)Set BDU and 2g range in CTRL4Enable ZYXDA interrupt on INT1 in CTRL3Clear FIFOEN in CTRL5Se

While flashing the LIS3DH I accidentally commented out a block of code causing read/writes of unintended registers. Below is the code which caused it. static void read_accel(void){ uint16_t MOSI = 0xA9; uint32_t MISO; int8_t dataRec; uint8_t i = 0; float accel_data[3]; while(1){ USART1->CMD = USART_CMD_RXBLOCKDIS; // disable block USART1->CMD = USART_CMD_CLEARRX; while (!(USART1->STATUS & USART_STATUS_TXBL)); USART1->TXDOUBLE = (uint32_t)MOSI; while(!(USART1->STATUS & USART_STATUS_TXC)); MISO = USART1->RXDOUBLE; printf("%x\n", MISO); dataRec = MISO>>8; USART1->CMD = USART_CMD_RXBLOCKEN; accel_data[i] = ((float)dataRec*4/256);// if(MOSI==0xAD)// break; MOSI=MOSI+2; i=i+1; } float noGravAndDirAccelData = sqrt(accel_data[0]*accel_data[0]*9.8*9.8 + acc

I really need your help!It is happening something strange here!I have installed the "VCP_V1.3.1_Setup_x64" in the last two months to connect with my hardware. and my PC easily was detecting my sensor and everything was working very fine. But on 19th November, after automatically my windows has been updated then, unfortunately, this driver isn't working at all. During the last two days I have reinstalled the driver and .... but it isn't working at all and I am completely confused. 

I am designing a sensor to measure vibration from industrial equipment. The main characteristics of the accelerometer are listed below:- Acceleration Range - up to 8g- Type - Digital- Output Type - I²C, SPI- Axis - X / Y / Z- Bandwidth - minimum of 1.6KHz (as higher the better)- Resolution - 16 bitsI found a lot of accelerometer that meet the specifications above, although I am not being able to understand how can I guarantee a good resolution in high frequencies of the accelerometer. I already tested the MPU9250 in a shaker and the results in low frequency (until 150Hz) is reasonable, although in high frequencies (from 150Hz until 1kHz) it is horrible as shown below:

I have the VL6180X doing continuous range measuring, which is working awesome, but after 60 seconds or so of the same reading I get an error in register 0x004D for VCSEL Watchdog Test. It says to replace the part, but I have had this with multiple Satel boards now. What could be the ACTUAL cause for this?

From Pololu's Arduino adaptation of the "heavy" driver =) (STSW-IMG007) I gather that the functions in vl53l1_platform.c should return 0 if they succeed and 1 if they fail, so that's what I've done in the ultralight driver. However, some of the other functions in the ultralight driver don't appear to be handling the status return values correctly. For instance, the function VL53L1X_SensorInit in VL53L1X_api.c mostly ignores the status return until the final call to WL53L1_WrByte, which it then returns as the status for VL53L1X_SensorInit. VL53L1X_ERROR VL53L1X_SensorInit(uint16_t dev) { VL53L1X_ERROR status = 0; uint8_t Addr = 0x00, tmp;   for (Addr = 0x2D; Addr <= 0x87; Addr++){ status = VL53L1_WrByte(dev, Addr, VL51L1X_DEFAULT_CONFIGURATION[Addr - 0x2D]); } status = VL53L1X_StartRanging(dev); tmp = 0; while(tmp==0){ status = VL53L1X_CheckForDataReady(dev, &tmp); } status = VL53L1X_ClearInterrupt(dev); status = VL53L1X_StopRanging(dev

I Unzipped the supplied demo software package and opened the tilebox project in Keil Microvision. After it autoinstalled all the support packages required I attempted to compile the code as per the readme.txt instruction. It failed due to not being able to fine the arm_math.h file which is clearly included in the folder structure. Any ideas why? In the readme it claims to have successfully compiled with Microvision 5.22 with no problems.

I’m trying to read 6 memory addresses I series. They represent appropriate X, Y, Z Accelerations levels. At low speed – up to 50kbps all good and working correctly. However if I increase I2C speed – up to 400 kbps, then I see wrong data being sent from Accelerometer chips. This was verified on multiple prototypes. Communication lines quality is good and signals are clean on Oscilloscope. See attached picture. It seems like on higher speeds (400 kbps) chip is missing to send very first byte (low byte of X acceleration).Do you know what can be issue here and how to solve it.

Hi, I need help in SPI communication between an acclerometr and my board, Is there any how someone can do it for me, I will be willing to pay them or does STM supports any forums for help this way.Thanks

I want to detect the difference between two objects like flat surface and little projected surface so that i need accuracy in mm.Could we improve the accuracy level of vl53l0x?

will con-formal & epoxy coating effect the functionality of sensor ?

I did the temperature test and get the below graph. The Axis data always jumps at some temperature between 10-30 ℃.Settings: 2g scale, high resolution mode and ODR is 100Hz.​Did anyone else have encounter such problem? The sensitivity stated on datasheet is 0x01%/℃.

We are approaching the end of this long basic tutorial on the ST.box (the #13 number is just a case...) with the presentation of the DataLogExtended sample application. This pro-mode firmware pack implements the dialog (via USBD Virtual Com Port) with the Unicleo-GUI running on a PC connected via USB to the ST.box eval board, visualizing all the sensor data streamed from the board.In these way all the Unicleo-GUI features described in this past post apply also to SensorTile.box platforms, allowing the user to go deep to ST.box feature. For example, it is possible to exploit all the DSOX features such as the FSM and the

About which bits is the CRC for AIS1120sx formed? 8 to 31?

how to make mems data and mic data combine

I configured the device and I am able to read XYZ data by polling the status register 0x27 and reading data when it is ready. I read more than 32 samples of each. Here are my steps to read data that works:Read register 0x0F - 0x33Write Control register 1 - 0x07 // I can enable interrupts in register 3 before setting ODRWrite Control register 2 - 0x00Write Control register 3 - 0x00 // Interrupts need to be set before ODRWrite Control register 4 - 0x00Write Control register 5 - 0x00 Write Control register 1 - 0x3F // Lpen and ODR.Loop: Poll Status register and read 6 bytes with with 0xA8 (0x28|0x80)Now I want to use the DRDY interrupt and it is not working. I have confirmed that my interrupt code does work by externally pulling the line high. I enable my interrupt code before setting I1_ZYXDA bit in Control register 3. And per AN3308 I am setting I1_ZYXDA bit in control register 3 before

I'm working with the VL53L1X as part of my bachelors projekt. In that regard I'd like to explain to the reader how the sensor works. As far as I've read, the sensor solely relies on timing the interval between pulsing the diode until the SPADs generate a current from the light hitting them. My calculations tells me that if the sensor measures its maximum range (400cm), the interval would be on around 13,3 nano seconds. This raises a couple of questions for me:1) How fast is the clock in the sensor? I cant find this info in the datasheet, and I imagine it would be very fast to be able to measure these small time intervals.2) What's the minimum distance that VL53L1X can measure? Is the clock fast enough to measure 20cm distance for example, which would give an interval on around 0,66 nano seconds?Thanks a lot in advance.

when hand held device is flat i get roll and pitch degree -2 and +2. during pitch measurement :moving upwards from a flat level front , and then i get -90 degree.moving flat level from upward i get -2 degree. moving downward from a flat level, and then i get 90 degree.moving flat level from upward i get +2 degree.during roll measurement :moving downward from a flat level right side, and then i get -90 degree.moving flat level from downward i get 2 degree.moving upwards from a flat level at left , and then i get 90 degree.moving flat level from upward i get 2 degree.means i get pitch and roll degree with range +90 to -90. with out roll and pitch i get the correct degree and direction but when i tilt the hand held device i not get correct degree and direction . so i use roll and pitch in below code but i not get correct degree and directioni use below code      &nbs