MEMS (sensors)

Posted on August 11, 2017 at 10:20Dear，all：      ST companies have used for vibration measuring acceleration sensor? Requirements are as follows:Frequency response： more than 1khRange: 0-40 gPower：Low power consumptionUsed in water pump, fan and other industrial sites     if ST companies have not these sensor,Can you introduce other company sensor?

Posted on December 05, 2017 at 23:07Hello ST Community,I have an application using the IIS2DH MEMS accelerometer. I was running into some issues, so to troubleshoot, I bought the STEVAL-MKI168V1 daughter board and SEVAL-MKI109V2 mother board. Using these kits, and by using the STSW-MKI109W software package, I was able to troubleshoot the majority of my issues.I have one issue that remains. The multibyte read does not work in 4 wire SPI mode. Here are some details.1. I have the /MS bit in the command byte set to 1.2. My command sequence appears to be no different than SPI_Read_MultiData in spi_mems.c of the sample code.3. When reading out the registers (0x20 to 0x3F), I get correct data if I read each register using the single-byte read mode. If I use the multi-byte read mode, I will get data that doesn't make sense. For example, I might read INT1_SRC (0x31) and get a 1 in the most significant bit (supposed to

Posted on December 05, 2017 at 13:15hi,I'm trying to program a LIS2DH via I2C, with a stm32l151rb. I'm interested in the activity mode, in order to wake up the stm32l1 using the INT2 pin connected to one micro's wake-up pin.my configuration is:/*CTRL_REG1*/ 0x29, //0b0010 1001 ODR@10Hz, LowPower mode enabled, Z disabled, Y disabled, X enabled, should drain 3uA /*CTRL_REG2*/ 0x00,  /*CTRL_REG3*/ 0x00, //disable all INT1 interrupts /*CTRL_REG4*/ 0x10, //0b0001 0000 FS = +/- 4G, self test disabled /*CTRL_REG5*/ 0x00, //do not latch /*CTRL_REG6*/ 0x08, //0b0000 1000 enable activity interrupt on INT2 /*REFERENCE*/ 0x00, //was 0x1e/*INT2_CFG*/ 0x02, //0b0000 0010 enable INT2 interrupt generation on X high events/*INT2_THS*/ 0x20, /*INT2_DUR*/ 0x10, /*ACT_THS*/ 0x21, //0x1e = 1000mG (9.81 m/s^2)@4G FS refer to table 84 (pg.48) of datasheet /*ACT_DUR*/ 0x14

Posted on December 07, 2017 at 04:03Hi,Is that possible to replace LSM6DS3 with LSM6DS3US?Thanks,#lsm6ds3us #lsm6ds3

Posted on December 08, 2017 at 19:04Can someone explain how to calculate the mg, dps, and temperature for the data read from the corresponding registers?  I'm trying to understand how to determine the scaling.  The datasheet eludes to using the rate and FS settings to determine this. 

Posted on December 05, 2017 at 16:41Hello,We have added LSM9DS1 to our design. We used linux 4.4.19 and we have added drivers got from https://github.com/STMicroelectronics/STMems_Linux_IIO_driversWe use SPI, modules are loaded fine and LSM9DS1 is detected (both accel/gyro and magnetometer chip selects).My questions is, is there any public API or example program for linux user space, for reading data or changing LSM9DS1 configuration?Thanks a lot for your help.Best regardsAngel

Posted on November 24, 2017 at 03:23hi,i can get the value of three-axis acceleration sensor,but how to calculate the angle?who can help?

Posted on December 08, 2017 at 17:31I'm unclear about the the different types of interrupts generated by LIS2DE12 and similar devices.In CTRL_REG3 (22h), the following interrupts can be enabled: I1_CLICKI1_IA1I1_IA2I1_ZYXDAI1_WTMI1_OVERRUNI understand what CLICK, WTM, and OVERRUN do, but I'm not completely sure about IA1, IA2, and ZYXDA. It appears that IA2 can be used for wake up interrupts defined by a threshold and duration, is that the same for IA1? What about ZYXDA?I looked for app notes or other documentation that explain these interrupts, but I haven't found much so far.Can someone point me to the appropriate document?Thanks!

Posted on November 29, 2017 at 11:10LSM9DS1 magnetometer in FAST_ODR mode is said to give output data at greater than 80 Hz. But can we specify this ODR ? What should I do if I want an ODR of 100 Hz ?#magnetometer #odr #lsm9ds1

Posted on December 04, 2017 at 17:07HelloWhat is the rule for the marking of the part LIS2DH12TR ?Please see attached. What the meaning of the characters 650 ou 703 ?Is it the date code ?Thanks for your help.#device-marking

Posted on November 30, 2017 at 18:09AxisMeasurement values (mg)Self-Test Values (LSb)xyzxyzZ-46.920-1047.8853204-31.2893.841000.96715185Y78.2969.38-218.921418741-46.92-969.68203.32818343X938.4125.1249.621812324-985.32-172.0493.841904311Above are the results of a self-test done on an IIS2DH accelerometer. The acceptable spec for the self test on all axes is between 17 and 360 LSb, so in all of the above orientations the sel

Posted on November 30, 2017 at 11:19Given that the LIS3DH FIFO is only 10 bit wide, is it actually possible to run the accelerometer with 12 bit resolution? #12-bit #lis3dh #fifo

Posted on December 01, 2017 at 11:20Hello,I would like to ask what is 'RES' pin in LIS3DH and LIS3DE? The only informtion is that it should be connected to the ground. Is it hardware reset which is activated with high state?

Posted on November 29, 2017 at 17:59I am currently using the LIS3DH to obtain some acceleration data. Currently my mode of operation is to first initialise the device in Bypass mode and to configure the remainder of the parameters, then when required the device is re-configured into FIFO mode where I poll the DRDY signal until my total number of samples have been taken, then I put the device back into Bypass mode. I have noticed that when I follow the above process for a single read and then return at some point later to perform another single read I obtain a repeated value. This has led me to re-evaluate my method of operation.Going back to AN3308 I have noticed that I can instead switch the power mode to power down. This brings about the following, if I am using the I1_ZYXDA bit (which is supposed to be set before configuring the ODR) to set the DRDY signal should I be disabling FIFO_EN (CTRL_REG5) prior to

Posted on November 30, 2017 at 18:41I have an STEVAL-MKI109V2 board for evaluating MEMS accelerometers.I downloaded the Unico software for Windows (I'm running Windows 7) from the ST website and installed it.I didn't realize the USB driver install was separate, so when I plugged in the device into my computer it wasn't recognized.So I unplugged the eval board, installed version 1.04 (current version) of the USB driver.The install was successful, but when I plug in the board, the driver does not load, device manager reports Code 28, which means the driver was not found.I tried rebooting, uninstalling, reinstalling, nothing worked. I found the registry entry for the ST USB device and tried to delete it, but Windows would not allow me to do that. This has become really painful.I went to another Windows computer and installed the driver and Unico app before pluggi

Posted on November 27, 2017 at 09:10Hello All,I configured ODR to 1600Hz at CTRL4 register on LIS3DSH.It works perfectly except for update frequency.INT1 pulse outputs with 600us interval! I attached Oscilloscpe at INT1 pin.It should be 625us(1s/1600 = 625us).Could anyone kindly help me what is wrong with my setting, hardware...?

Posted on January 02, 2017 at 16:15 I've been trying to understand how to interpret and format the data I'm getting from the accelerometer. First, my setup: Low power, 5.376KHz ODR, 16G full scale, normalresolution mode, ZHIE enabled, ZLOW disabled, THSset to 30 (First I need to understand how to interpret and format the data with the above configuration, then I can work on tuning things for my application). I am using an Arduino to interface to the IIS2DH and getting AOI interrupts on INT1. All of this is working in my Arduino and code. This is a Z probe for a 3D printer, so when the probe (accelerometer) strikes a solid surface, it generates an interrupt for the Z axis event (X and Y are not enabled). This all works. I get the interrupt and then fetch the OUT_Z_L and OUT_Z_H registers as 8 bit integers. It is from here that I need help understanding what I am getting and how to interpret it.

Posted on November 22, 2017 at 18:47Hi everyone!I'm working with the LIS2DS12 accelerometer chip with STM32F4xx via SPI. I could make the sensor alive, configure it (configuration is checked by an SPI read back) to operate in FIFO mode with threshold interrupt on INT1 pin which works properly (checked on scope). My problem is that somehow the read values are not correct. During the configuration I have set the IF_ADD_INC bit in CTRL2  register, so if I make a read request onto the OUT_X_L (0x28), then I could read out the all the bytes from the FIFO (256x6 bytes) in one read sequence in the repeating order of X_LSB;X_MSB;Y_LSB;Y_MSB;Z_LSB;Z_MSB. Then I have made the scaling onto [mg], which showed good results at the Y and Z axis. I could measure the Earth's 1g 'force' correctly. But all of my x axis values are corrupted. They show ~10.000 mg values. Also on oscilloscope I have tracked the communication and I could see they are all wrong. As

Posted on November 21, 2017 at 23:34I like to use the Sleep-to-wake and Return-to-sleep feature of the LIS2DE12. I am wondering what axis value is compared with the threshold value (ACT_THS). Can I select the axis? The http://www.st.com/content/ccc/resource/technical/document/datasheet/group0/72/cb/80/a7/5e/fe/46/9d/DM00153214/files/DM00153214.pdf/jcr:content/translations/en.DM00153214.pdf doesn't say much! #sleep #accelerometer #mems

Posted on May 11, 2017 at 08:24HiI apologize if this is a stupid question but I would appreciate it if someone can clear it for me.In LIS3DH, based on the mode selected, there are different Output Data rates (ODR) available for choice. What is this output data rate ? Is it similar to sampling rate ?For instance,If I select a normal mode output at 1.344 KHz, does that mean I should read the OUT registers of the axes every (1/1.344k) seconds ?Please help.

Posted on November 24, 2017 at 14:39Hi, we are using your expansion board X-NUCLEO-KS01A2 with motion MEMS with the Nucleo STM32F401. We see in the schematic of the board X-NUCLEO-KS01A2 that the supply voltage of the four sensor is Vdd=1,8V.To adapt the voltages from the sensors to the microcontroller you use two level translator ST2378E.We are doing the hardware design with the four sensor (LSM303AGR, LSM6DSL, HTS221 and LPS22HB) and the microcontroller STM32F40re. We see in the sensors datasheet that it is possible to use Vdd=3,3V for all of them. It is in the operating range for Vdd and Vdd_IO.Our question is whether it is possible to do a hardware design without the level translator ST2378E. We supply the sensors with 3,3V and connect the signals directly to the microcontroller that it is supplied with 3,3V.We attach the schematic of the board X-NUCLEO-KS01A2.

Posted on November 23, 2017 at 13:07 Hi, we are upgrading our product from a LSM9DS0 to a LSM9DS1. During testing, we are unable to get tilt compensation working with the compass on the LSM9DS1. We have calibrated the compass. When using the code below, this works perfectly on the LSM9DS0. When using on the LSM9DS1, it doesn't compensate. Is there a difference between the LSM9DS0 and LSM9DS1 which would break this? E.g. Accel and Mag are orientated differently? //Normalize accelerometer raw values. accXnorm = accRawX/sqrt(accRawX * accRawX + accRawY * accRawY + accRawZ * accRawZ); accYnorm = accRawY/sqrt(accRawX * accRawX + accRawY * accRawY + accRawZ * accRawZ); //Calculate pitch and roll pitch = asin(accXnorm); roll = -asin(accYnorm/cos(pitch)); //Calculate the new tilt compensated values magXcomp = magRawX*cos(pitch)+magRawZ*sin(pitch); magYcomp = magRawX*sin(roll)*sin(pitch)+magRawY*cos(roll)-magRawZ*si

Posted on November 22, 2017 at 17:48I try to use the lis3dh in FIFO_STREAM mode and HighRes mode. But when I read the values they seem to only be 10bit values.(I am setting CTRL_REG4 = 0x08, CTRL_REG5=0x40 and ODR=100Hz.)According to AN3308 16-bits values are stored in the FIFO. In the LIS3DH datasheet, on the front page it says '16-bit data output FIFO'. But further down in section 3.6 I read 'The LIS3DH contains a 10-bit, 32-level FIFO.'.Has any one managed to get 12-bit values from the FIFO?BR/Tomas

Posted on November 03, 2017 at 09:55Hello,I implemented a DMA with my LIS2HH12 to avoid losing datas.The problem is that my DMA is too fast, I am able to read at 1.8kHz (1800 (x,y,z) datas in 1 second) thanks to my DMA but the max ODR that I can choose on my accelerometer is 800Hz.So I am wasting a lot of memory with my DMA cause if I choose a 400Hz ODR if have a new data available each 4 or 5 sample.As I understood, it is not possible to change the DMA speep. Did I miss something on the datasheet that could help me to solve my problem ? FIFO is interesting but while reading all the registers to get (x,y,z) datas, I will loose some datas ?Note : I don't want an interrupt when new data available cause it will stop my program everytime

Posted on November 22, 2017 at 06:19   We are working with STPM10 to measure the Voltage,current,Active energy,Reactive energy and apparent energy. we are using 10W to 1KW load.with current calibration as +12% and Voltage calibration as +9%. Upto 400W load the readings are proper.but when we connect load above 400W the active energy register (DAP),reactive energy register (DRP) is reverse counting for some case of load.kindly provide when the register is starts countdown and how can we solve this issuethanks #stpm10