MEMS and sensors

Posted on January 12, 2017 at 17:10Hello,I have troubles setting the H3LIS331DL accelerometer to trigger an interrupt when a programmed threshold is crossed. I can configure the device to trigger an interrupt when new data is ready on both INT1 and INT2 pad (confirmed with an oscilloscope). However, the threshold interrupt never fires.I used the following configuration :- Low power mode @ 10Hz, X/Y/Z axis enable : 0b1100 0111 written in CTRL_REG1- No high pass filter- No sleep to wake function- Threshold interrupt on INT2 pad, interrupt not latched -->CTRL_REG3 = 0- Full scale range +-100g, block data update : 0b1000 0000 written in CTRL_REG4- OR combination of interrupt on the 3 axis : 0b0010 1010 written in INT2_CFG- Threshold value set to ~2g (49mg/LSB @ +-100g) --> 0b0010 1000 written in INT2_THS- No minimum durationThe different parameters are well written to the sens

Posted on December 24, 2016 at 13:34Hi.I need an MEMS Angular accelerometer for my application (quatrotor).As i detected in http://www.st.com/content/st_com/en/products/mems-and-sensors/gyroscopes.html?querycriteria=productId=SC1288 , ST’s gyros measure angular acceleration.My question is how i can get this parameter from ST's Gyroscopes?Thanks

Posted on January 13, 2017 at 10:13Hi, I am considering mounting <LINK NO LONGER ACTIVE> on the edge of a PCB on a upcoming product to save space.This would result in PIN 6 and 12 not beeing soldered to GND, what implications would this have?

Posted on January 12, 2017 at 12:50I am using the magnetometer on this device, running at the max ODR of 220Hz. There are occasional (several times a minute) glitches which have the following charateristics:1. The interrupt is significantly delayed.2. The data read on that interrupt is (often) a big spike compared to values read before and after. It's just sitting on my desk.3. A shorter than expected delay before the next interrupt.4. The data read on the second interrupt is normal.5. Normal behaviour continues. No spikes occur except immediately after the long interrupt delay.6. The regular interrupts before and after the glitch do not fall onto integer multiples of the expected delay - there is an offset after the glitch.This trace shows interrupt, SCL and SDA:

Posted on January 11, 2017 at 12:27Hi, I am using a LSM9DS1TR, with accelerometer scale set to +-16G.With the device motionless on a table, I read a decimal value of 1360 for the Z axis, and if I flip the board over I read -1360 (give or take a few counts). So, this is obviously measuring gravity.I would however have expected gravity to be 1G, so I would have expected an output of 1/(16/32768) = 2048, not 1360.Can anyone explain why I do not see what I expect to see? I've obviously missed something!Thanks.

Posted on January 08, 2017 at 07:42I have got a strange problem with X-NUCLEO-CCA02M1 expansion board interfacing with NUCLEO-L476RG. I have followedhttps://my.st.com/content/ccc/resource/sales_and_marketing/presentation/product_presentation/d3/44/de/b9/33/a0/4e/25/x-nucleo-cca02m1_quick_start_guide.pdf/files/x-nucleo-cca02m1_quick_start_guide.pdf/jcr:content/translations/en.x-nucleo-cca02m1_quick_start_guide.pdf quick start guide to test the functionality of MEMS mic through the audacity(v2.1.2) software as mentioned in  doc. I have loaded the test binaries to the X-NUCLEO-L476RG and I am able to get the device reco

Posted on January 04, 2017 at 18:13Hi AllI am having some difficulties in configuring the Double Click Interrupt on the LIS2DH12.After power up, I am doing the following:TEMP_CFG_REG = 0xC0CTRL_REG4 = 0x80CTRL_REG1 = 0x77The above seems to work and provides sensible values for xyz axis when the PCB is at various angles. This suggests that the I2C bus is functioning correctly. Next I would like to enable click detection in the y- axis (any axis would do to start to prove the function works). I would like an interrupt on INT1 when a double click has occurred. INT1 is pulled up to 3.3 V via a 100 kOhm resistor.I am doing the following in order to configure the Double Click featureCTRL_REG3 = 0x80CLICK_CFG = 0x08CLICK_THS = 0x88TIME_LIMIT = 0xFF  //Not really sure the purpose of this, the datasheet is not really clearTIME_LATENCY = 0xFF

Posted on January 09, 2017 at 11:06oliverbeirne‌Where can I find drivers for LSM6DS3 which can be used with Android 6. Android requires both drivers and HAL. I could not find anything on this site. I had seen  a github repository with ST drivers, but that seems to be removed now. https://community.st.com/tags♯/?tags=lsm6ds3 https://community.st.com/tags♯/?tags=mems https://community.st.com/tags♯/?tags=sensors https://community.st.com/tags♯/?tags=accelerometer https://community.st.com/tags♯/?

Posted on January 05, 2017 at 00:51Are there any spice or cadence files to simulate the lps22h/25h/331ap pressure sensors to co-simulate them with an ASIC?If yes, how does one access them?Thanks

Posted on December 23, 2016 at 04:42I am a new user of ST’s LIS2DH12. I am confused about the sentence 'Leave “Pin 1 Indicator� unconnected during soldering'. It was in chapter 4.1 Soldering information in datasheet of LIS2DH12. What this sentence mean? And why does Pin1 need disconnect? And how can I achieve Leaving “Pin 1 Indicator� unconnected during soldering?

Posted on December 29, 2016 at 15:42I'm trying to connect SPH0641LU4H-1 microphone to STM32F411RE Nucleo board.According to the Wikipedia https://en.wikipedia.org/wiki/Pulse-density_modulation format should represent lowest and highest amplitude as 0b0000...(all 0) and 0b1111...(all 1) accordingly.When I connect microphone pin to the ground ->  0b0000... PDM data is transferred to PDM_Filter_XX_XX and output sound is silence. But when I connect it to 3.3v source to emulate PDM 0b1111... ->  the output I get is 1KHz noise. (mailto:16bit@16KHz PCM). PDM_Filter_128_LSB function outputs big(depends on micGain) int16_t values with + or - sign.B

Posted on December 21, 2016 at 11:26Hi, I am trying to configure osxmotion library in Juma Canon. I was able to successfully import motionar,motionfx,motioncp,motiongr library in the project but was unable to properly execute the license manager. I am attaching the video link- https://www.youtube.com/watch?v=v35_pLUQQlU . Please help me out.#stm32f401 #library #arm #compile-license

Posted on December 30, 2016 at 08:14Here's my configuration:set(CTRL_REG1, 0x00); set(CTRL_REG2, 0x80); set(CTRL_REG3, 0x00); set(FIFO_CTRL, 0x00); //Flush FIFO set(CTRL_REG1, 0x3A); //3A was 3E set(CTRL_REG2, 0x50); //50 set(CTRL_REG3, 0x00); set(FIFO_CTRL, 0x40);In my code, I wait 2 seconds and read 32 values from FIFO and average them.Then I wait 1 second and read 16 values from FIFO and average them.I do the above in a loop.Pressure data looks find for about 33 seconds, and then, I get junk back.If I restart my device (power down and back up again) it will work fine again, for about 33 seconds.The problem is consistent.  What is going wrong here?To read a single pressure value, I just request 5 bytes from 0x28 and read them in.  I use the first 3 to calculate pressure and discard the last 2 as they are temperature and not necessary for

Posted on December 28, 2016 at 08:23I am designing circuit using LIS2DH12. I want to use the I2c, so I connect Cs to high level, and SA0 to GND. I am not sure if CS should be connected to Vdd, or Vdd_IO. As I understand it, Cs should be connected to Vdd_IO. But I am not sure, so I ask this question, and I need help.

Posted on December 05, 2016 at 20:44Hi.Sorry for my English.specified in the datasheet If a slave receiver does not acknowledge the slave address (i.e. it is not able to receive because it is performing some real-time function) the data line must be kept HIGH by the slave. The master can then abort the transfer. A LOW to HIGH transition on the SDA line while the SCL line is HIGH is defined as a STOP condition. Each data transfer must be terminated by the generation of a STOP (SP) condition.Sensor sets the data line in high. The microcontroller by sending an address sensor receives NACK, and stops communication.After that, registers AV_CONF, CTRL _REG1, CTRL _REG2, CTRL_REG3 reset to its default state (All read operations read the default values).This situation occurs if the ODR> 0. (1 Hz 7 Hz 12,5 Hz)Why is this happening?How do I check the conversion is complete without R

Posted on December 23, 2016 at 07:27Hi, I am new to LSM6DS3 inertial module, I am trying to use it with my arduino mega 2560, in SPI mode ,but in trouble with  Z & Y axis output of the accelero meter. X axis output respond well.Already tried to read the output raw registers with and without reading the STATUS Register, but the result remains same.  I bought the breakout board from Sparkfun and made necessary changes for using this in SPI mode. Attaching my arduino code with this post.

Posted on December 21, 2016 at 20:32Hi,I have connected an FPGA to an LPS331ap, and I can retrieve good data as seen in the oscilloscope, but only if the supply voltage is above 2.4V (I have Vdd and Vdd_io shorted together), rather than the 1.71V quoted in the data sheet. The logic signals from the fpga are 1.8V, however. I am also using SPI.For my application, I would like to minimize power consumption and thus minimize the supply voltage.Has anyone else observed observed this higher-than-spec necessary supply voltage, and found a way to get it to work with supply as low as Vdd=1.8V?Thanks

Posted on December 20, 2016 at 17:32I am using the LSM6DS3 component in a design. I've used the component in the past (and always liked it), but never in this capacity. I am using I2C for communication with 10k pull up resistors and am powering on/off the sensor with a separate power bus than my micro controller. I have the interrupt pins connected to my micro controller, although they are not in use. The issue I am experiencing is that when the power for the sensor is turned off, the I2C lines are being pulled low. When the power for the sensor is pulled high, the I2C lines are high as expected and I can communicate to other peripherals on the I2C bus. In effect, powering down the sensor is pulling down the entire I2C line, drawing extra current in my system and preventing other I2C communication. Is this a problem you can provide insight on? I wasn't sure if the module supported this mode of operation, where

Posted on December 17, 2016 at 06:48Hi, i searched for the exact principle of the time of flight technology in internet but the answer i got was different in different websites. I bought VL53l0X sensor recently and i need the exact principle of TOF of ST's product.

Posted on November 04, 2016 at 15:57Hi,I would like to use IIS2DH accelerometer as main accelerometer in a custom board for my project. For this reason I've bought the STEVAL-MK1168V1 to make some tests. I would like to ask you some questions about this product, since they are not well specified in the datasheet I've downloaded from the product page site.1) I usually program with Atmel microcontrollers, so I've made the same this time. What I've done is to link both i2c pins, Vdd and Vdd_io to Vcc=3v3, GND and both INT1 and INT2 pins. i2c communication works fine but i can't handle interrupts generated through INT pins.I set the Int1_cfg register to binary 00111111 (OR combination of all axis events), the I1_A01 bit on ctrl_reg3 to 1 and, after moving the board, I cheked the int1_src register I've seen that IA, ZH, YH, XH bits are set, so what I've expected was an interrupt on INT1 pin, but the corresponding callbac

Posted on December 15, 2016 at 10:23Hi there,   According to the datasheet of LSM303D, I could find the self-test function of the accelerometer, but could not find the same function of the magnetometer.   How to test the magnetometer if no build-in self-test function provided?Best Regards,Cheng#lsm303d-self-test #lsm303d

Posted on December 15, 2016 at 16:25Hi Everybody, I want to test the interrupt of the LSM6DS3 sensor without any movement. Do you know if it is possible to generate an interrupt with the sensor self test ?If I program a low interrupt threshold and I launch the self test of the sensor, is it possible to see the interruption ?Thanks a lot for your help.

Posted on November 28, 2016 at 17:59Hi everybody,We are using LIS3DS0 on the ISK01A1 board monted on a Nucleo F103-RB...Our software is based on HAL drivers (got in the cube).We met this strange issue in some of our boards (we confirmed the test with many students and dozens of boards):1- we plug the board2- the accelerometer failed to initialize. (due to the WHO_AM_I register which is 0xD4 instead of 0x68).We can reset again and again our STM32, without any change.Then we program a flush of registers of the LIS3DS0.We confirm the registers seems to correspond to another component (L3G3200D) !(WHO_AM_I of 0xD4, )But, when we do the following steps, the component run well :1- plug the board2- -> fail to initialize3- get off the JP2 jumper4- ensure temporarly 0V on the Vcc of sensor (with wire) (to avoid a 2V power by

Posted on November 02, 2016 at 23:14Hello Everyone,I am having trouble talking to the LSM6DS3 using 4 wire SPI. I have verified the signals to the device as being correct per the datasheet. I am commanding 0x8F to do a WHO_AM_I command but am not seeing anything coming back on MISO. The only problem I can think of is the SCx and SDx pin is left open. I did not tie them to VCC or ground. Could this be the problem? Due to the package, I can't modify it on board. 

Posted on August 10, 2016 at 06:08I brought STEVAL-MKI160V1 MEMS sensor board. Bulk ID Z5T42380E024. While working with the sensor I got an issue like I enabled interrupt generation to interrupt pin INT1 for 6D orientation detection. So when ever I change the orientation, interrupt is generated and interrupt pin INT1 is going from low to high state. But it is not going back to low state for detecting the next interrupt detection. INT1 pin is maintaining high state even if I again change the orientation to first or previous state. My doubt is, is there any register or bit in a register to be programmed to make the interrupt pin INT1 becomes low and be ready automatically to serve next interrupt detection? Is this feature available in LSM6DS3 sensor? #interrupt-lsm6d3s