MEMS (sensors)

Posted on January 17, 2017 at 19:16Hi.I am using the LSM9DS0, and have observed a lot of noise on the z-Axis of the Accelerometer Data. The attached picture is a plot showing the noise while operating at 100Hz in the +-2g range. Is this a normal level of noise for this device, or am I doing something wrong, or is the device defective?kind regards.Erich Neumann#lsm9ds0 #accelerometer #noise

Posted on March 26, 2015 at 14:53 Hey there, I recently installed a new LSM303D (accelerometer + compass) on my board and I am having some issues with it. I can read the data from the accelerometer fine, but the ones from the compass seem ''locked'', I read a total of 3 pairs of MSB-LSB, of which only the LSB change over time. Here is an exemple of reading (LSB on the left): Mag X: -125 -1 Y: -93 -1 Z: -22 -1 Mag X: -115 -1 Y: -101 -1 Z: -26 -1 Mag X: -119 -1 Y: -78 -1 Z: -34 -1 The LSBs change erratically regardless of the orientation of the sensor. Here is the config I'm using: ST_CTRL_REG 1 , 0 x 67 ST_CTRL_REG 5 , 0 x 60 ST_CTRL_REG 6 , 0 x 00 ST_CTRL_REG 7 , 0 x 80 I am using SPI. I don't really get how I am not getting the values right. Any help or lead would help me a lot :) Thanks !

Posted on October 26, 2016 at 16:43Hi , I have STEVAL WESU module  and logged acelerometer data using android app. (plz see attached file)My settings are: Timer: 512 Hz, 10Hz, 1HzMEMS Accelerometer output data rate: 416 Hz , 833 Hz, 100HzIn the logged data host time stamps and node time stamps are available. My  observation:All the time stamps are in milliseconds.Host, stamp time on data at 100Hz if Timer value > 100Hz otherwise at Timer value. Node, stamp time on data at 1000Hz irrespective of ''MEMS Accelerometer output data rate'' settings. If Host time stamp rate  lower than node time stamp,  then are we losing data? What is allowable max. data rate at which we can log accelerometer data considering BLE protocol? As per sensor data sheet 1Hz- few kHz data rate is allowed. thank you,  #steval-wesu

Posted on January 31, 2017 at 06:12hi,     I am Reading the Accelerometer and Gyroscope sensor values by checking the XLDA and GDA bits as follows             if((readReg(STATUS_REG)&0x01)==0x01)     // checking XLDA        {              Ax = (int16_t) readReg(OUT_X_H_A) <<8 | readReg(OUT_X_L_A);              Ay = (int16_t) readReg(OUT_Y_H_A) <<8 | readReg(OUT_Y_L_A);             Az = (int16_t) readReg(OUT_Z_H_A) <<8 | readReg(OUT_Z_L_A);       }if((readReg(STATUS_REG)&0x02)==0x02)        // checking GDA { Gx = (int16_t) readReg(OUT_X_H_G) <<8 | readReg(OUT_X_L_G); // typecast as Gy = (int16_t) readReg(

Posted on January 27, 2017 at 15:04Hello, sorry for me level in EnglishI have to carry out an end of year project of electronic bts, and I am stuck at this levelI need your help to understand a lack of reading in the following code I use this soft : 'Sensors_Reader', it is a program provided on the page of the site MBEDI have this board NUCLEO_L476RG and this shield sensors 'X-NUCLEO-IKS01A1'I receive this information in return on 'un moniteur serie' :--- Starting new run ---Humidity | Temperature Sensor ID = HTS221 (0xbc | 0xbc)Gyroscope | Motion Sensor ID = UNKNOWN (0x0 | 0x0)===I2C [errors]: 0x00       X                Y                ZMAG [mgauss]:     &

Posted on January 27, 2017 at 00:19We were looking at using the LSM6DS3 in a new design, but I noticed the LSM6DSL uses half the power.  The two parts look to be pin compatible and probably software compatible (at least for most features).  Is that correct? More specifically: is it valid to use the AN4650 Application note to work with the LSM6DSL (at least until there is a similar application note for that part available)?  Is it likely that code written for LSM6DS3 would work if the part were swapped with the LSM6DSL?Any ETA on a usage application note for the LSM6DSL?#lsm6ds3 #lsm6dsl

Posted on January 25, 2017 at 05:13x = ?y= ?z = ?

Posted on January 24, 2017 at 14:28

Posted on January 04, 2017 at 00:05I am interested in viewing compass heading ( from north) out of the WeSU1 dev kit. Is this merely a setting within sensor fusion to obtain this?Thanks!

Posted on January 23, 2017 at 18:13The spec for the LIS3DSH quotes +-16g, yet the sensitivity at full scale is 0.73mg/LSB, giving a full scale range of +-24g. Can the sensor be used effectively at +-24g? What kind of non-linearities or other errors might arise at these higher levels?

Posted on January 23, 2017 at 13:03Hi,     I am using STEVAL-MKI160V1 evaluation module of LSM6DS3 in arduino platform with 8g scale.  When I turn this 1g to -1g , it suddenly fall to 89 , 86 , 89.......etc ,  from 4173  (1g reading, that i got)  with a tilt of less than 5 degree from initial position , ie the g value varies not sinusoidally. it gives some valid values in some other positions between a rotation of 1g to -1g, and again falls to invalid values mentioned above,  Due to this my Madgewick filter give me , error output. Attaching my codes , Please help to solve this problem

Posted on January 16, 2017 at 18:26I am trying to configure the iNemo to assert INT1 when significant motion is detected. I have followed AN4650 closely (the configuration matches that given in AN4650 Section 6.2 at the end of the section), but no interrupt is ever generated. I am using a STEVAL-MKI160V1 plugged into another board. I'm probing INT1 on the STEVAL while shaking the board and otherwise trying to simulate walking, running or other motion. I have tried reducing the threshold, including DEB_STEP, but nothing has worked.Does this mode actually work as documented? Do other registers need to be written to make this work? I have the FIFO turned on, and it accumulates data at 26Hz as expected.Thanks.

Posted on July 27, 2016 at 20:51I'm just getting started with the CCA02M1 expansion board, Nucleo '476RG and X-CUBE-MEMSMIC1 software.I've got the software compiling in Kiel, and the USB-audio interface works well.(44.1kHz sampling doesn't seem to work properly, though 16 and 48kHz are fine. The documentation is a bit ambiguous regarding support for 44.1kHz, but that's not a big deal at the moment.)My question is that the demo software uses 1 millisecond buffers and this is pretty hardcoded - with many instances of (samplerate/1000) and variations of that in the codebase.I'm interested in performing signal-analysis on buffers of exactly 256 or 512 samples (which will be around -but not exactly- 10ms in duration).Is there any special reason why the buffers have been kept so small, and/or the buffer size isn't more parameterised?(I don't require USB streaming for this application, although it migh

Posted on December 13, 2016 at 04:27hi, allI want to enable STEVAL-MKI119V1 on Windows platform, but without an available software. I contacted the STMicroelectronics Support team, but they told me that product STEVAL-MKI119V1 is obsolete, they do not retain any information or data on obsolete products. Fortunately, they also told me that there are also online distributors that still have in-stock inventory, so some will still have access to information and documentation concerning this product. That's why I come here. If someone could help would be very appreciated.  BTW, if someone could help propose an alternative product that have the he same capabilities with STEVAL-MKI119V1 would be great. My purpose is to find an available device which has the ability to access sensors(Ambient Light, Gyroscope, Ac

Posted on January 14, 2017 at 07:28My suppliers in Australia say it is obsolete and Mouser quote 20 weeks delivery. Digikey show no stock and I cannot get an availability. ST website says it is active. Can someone recommend an equivalent to this. I need to get hold of 25 of these now and a further 150 in 3-4 weeks time. 

Posted on January 09, 2017 at 10:41I would like to use an iNemo with an external magnetometer (i.e. Sensor Hub mode) to gather data and place acc, gyr and mag readings in the FIFO. Is it possible to have the mag drive the ODR of the iNemo with its data ready line?The mag data is the most important, and it would be nice to collect data at its max ODR of 220Hz. The iNemo supports rates of 208Hz, 416Hz, and so on. I would prefer to avoid rates where I get duplicates or dropouts in the mag data.Thanks.

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