MEMS (sensors)

Posted on July 13, 2017 at 23:03I just downloaded the new STM32CubeFunctionPack_MOTENV1_V3.0.0 and going through what motion sensor library could do all at once.As I walk through the code in MEMSCallback(), all the W2ST_CHECK_HW_FEATURE checking is using 'if' and not 'else if'..... So is that meant all features can be detected all at once ?For instance, can W2ST_HWF_FREE_FALL and W2ST_HWF_PEDOMETER  be enabled at the same time ?? and get correct status ?Most specific to page 20 on 'en.FP-SNS-MOTENV1_quick_start_guide', it shows all individual Motion features.However, Mobile Apps would only able to show status one at a time.  Does, features actually running in parallel at firmware background ?Any doc list out how Application was implemented ?

Posted on July 09, 2017 at 11:47Hello sir,I meet a problem that I can present 6D positions now except (a) and (c) [both are related to left side] situations shown in LIS2DS12 application note. I can not find the problem. I output the 'position' exact data instead, for these two wrong situations, it is always shown 0, which should be shown 2 and 4 as expected. I'm thinking wether the x-axis is broken. Or are there any other reasons to cause this problem? (the 4th value after Get Acceleration shown the input interrupt value)WHO_AM_I_REG 0x43Get Acceleration: 38 897 -378 0Get Acceleration: 37 897 -378 0Get Acceleration: 39 900 -374 0Get Acceleration: 38 899 -377 0Get Acceleration: 110 937 -402 0Get Acceleration: 38 900 -373 0position change********** success 6D event function^_^ position = DW_RS  8Get Acceleration: -1884 611 -850 0position change**********

Posted on July 11, 2017 at 12:48Hi,I am trying to test my I2C connection with my STM32nucleoF411RE but I can't seems to have any response from my MKI142V1. I have tested the start condition and sending the address but it doesn't seem to retrieve the acknowledge bit that the sensor should send back. So my question is, can I really test the MKI142V1 without MKI109V2 that everyone recommends ?

Posted on July 09, 2017 at 14:40I posted in another forum but a fellow user suggested I post here.https://community.st.com/thread/41907-why-does-my-linear-sensor-array-not-scalenormalize?sr=inbox&ru=17270null

Posted on June 01, 2017 at 15:39I've got my LIS2DH12 configured as follows:TEMP_CFG_REGTEMP_EN0x11CTRL_REG1ODR1LPEN0ZEN1YEN1XEN1CTRL_REG2HPM0HPCF0FDS0HPCLICK0HP_IA10HP_IA20CTRL_REG3I1_CLICK0I1_IA10I1_IA20I1_ZYXDA0I1_WTM1I1_OVERRUN0CTRL_REG4BDU1BLE0FS0HR1ST0CTRL_REG5BOOT0FIFO_EN1LIR_INT10D4D_INT10LIR_INT20D4D_INT20CTRL_REG6I2_CLICK0I2_IA10I2_IA20I2_BOOT0I2_ACT0INT_POLARITY1REFERENCEREF0FIFO_CTRL_REGFM1TR0FTH1INT1_CFGAOI16D0ZHIE0ZLIE0YHIE0YLIE0XHIE0XLIE0INT1_THSTHS1INT1_DURATIOND0INT2_CFGAOI16D0ZHIE0ZLI

Posted on July 05, 2017 at 14:43STEVAL-MKI155V2 coupon board,cannot find exact pin number.On silk on the board, and no layout file on st site.And on en.DM0006727d.pdf, bottom view image seems to be mirrored.Please let me know where  I can  find the MKI155V2 pin map.

Posted on June 29, 2017 at 16:53Hi,I'm using X-NUCLEO-IKS01A1 with arduino uno,I'm getting the output for HTS221 with the codehttps://github.com/ControlEverythingCommunity/HTS221/blob/master/C/HTS221.c  ,the connections seem to be correct but when I'm trying to get the output for LPS25HB from the code https://github.com/ControlEverythingCommunity/LPS25HB/blob/master/Arduino/LPS25HB.ino I'm always getting the output as 0 hpa only.Even when I'm applying the pressure at the sensor.In the datasheet it is there that CS should be connected to VddIO ,I think it is internally connected as all the sensors in  X-NUC

Posted on July 04, 2017 at 15:39Hi,I'm using X-NUCLEO-IKS01A1 board for integrating the pressure sensor in my Atmel board SAM G55 series.I'm using the reference code of https://github.com/ControlEverythingCommunity/LPS25HB/blob/master/C/LPS25HB.c .I can able to get the correct output from WHO AM I register but the problem is that when I'm reading the output registers 0x28,0x29,0x2A ,the values are showing always as zero and they are not changing.Even If sometimes ,the registers are showing some value,the values are not changing even when the pressure is applied.I have configured the control registers too. 0x20 as 0x90 and 0x21 as 0x01.Can you please let me know any clue on why the output registers are not changing and always showing as zero.Please help me.Thanks and Regard

Posted on June 05, 2017 at 11:40I am trying to measure a machine's vibration using LIS3DH sensor. I set the LIS3DH in low power mode and 5.376 kHz sampling frequency which outputs 8 bit output. I use spi to get the data from the sensor. I changed this raw output into �g' using the sensitivity value given in the datasheet.My problem is: The sensor shows a fluctuation in its output of Z axis even when there is no vibration applied and the sensor is fitted on a horizontal surface. The range of this fluctuation is approximately from 0.6g to 1.2g. I have attached a image that shows such output. (X axis is time and Y axis is vibration in terms of g)Can someone please help me to interpret why this is happening ? Is there a method to somehow remove this noise from the output ?Please help.

Posted on July 02, 2017 at 14:49Hi everyone, we are working the the LSM6DS0 from ST interfacing through SPI with a CC2650 microcontroller. We have been able to test our custom PCB, read some data from the accelerometer, but we are not able to configure the interrupt generation (neither from OUTPUT data available neither from threshold high event detected)We have a couple of doubts, since there are no resources online about the PCB electrical connection. Should the interrupt pin be connected directly to the input GPIO of the uC? Should we use some pull up, pull down?Here we report the dump of all the registers we read on our debugger together with a synthetic description of all our configurations.ALL REGS DUMP (obtained through SPI, after some time): [0] '\x00'[1] '\x00'[2] '\x00'[3] '\x00'[4] '\x00'[5] '\x00'[6] '\6a'[7] '\x32'[8] '\x32'[9] '\x32'

Posted on June 30, 2017 at 19:28Hey guys I have been working with VL53L0X and Stm32F7  at my company so the problem is that it can identify the chip ID well but get a ERROR_CONTROL_INTERFACE at the first api callVL53L0X_DataInit(&MyDevice);After further debugging HAL_I2C_Master_Receive gives an timeout error but HAL_I2C_MASTER_TRANSMIT goes through fine.The device address for read is set to 0x53 while for write is 0x52 

Posted on June 22, 2017 at 18:21Hi,I have X-NUCLEO-IKS01A1 having 4 MEM sensors ,I have seen that this board is compatible with arduino UNO,I have connected the board same as like the ST nucleio board,but I couldn't find the sensors giving output with arduino UNO code . I have also connected the board with Intel edison,but I couldn't detect the addresses of the sensors.Can you please let me know the hardware connection of X-NUCLEO-IKS01A1 with arduino UNO .I'm providing 5V as input (Vin) and added pullup resisters too.Thanks and Regards,Radhika

Posted on June 28, 2017 at 12:38Hi, I'm having some problem using the LSM9DS1 FIFO...My objective is to continuously acquire, without loosing samples, the Gyro and Accelleration data. (The magnetometer is turned off)This is what I do:- I set the watermark threshold to 21 samples (IMU_FIFO_samples = 21 (IMU_FIFO_samples = FlashBuffer_Initialize(IMU_6);)- I configure the interrupt to be sent to pin INT1_A/G (LSM9DS1_configInt(XG_INT1, INT_FTH, INT_ACTIVE_HIGH, INT_PUSH_PULL);)- I configure the FIFO in Bypass Mode (LSM9DS1_setFIFO(FIFO_OFF, IMU_FIFO_samples);)-- In order to start the data acquisition I configure the FIFO in Continous Mode (LSM9DS1_setFIFO(FIFO_CONT, IMU_FIFO_samples);)(I did try to set the IMU_SAMPLE_RATE to 14Hz and 900+Hz but the results are the same)v

Posted on May 19, 2016 at 04:45 Hi guys, I new to STM32, was mostly use PIC32 for USB audio application but due to cost decided to switch to STM Now I have STM32F0 discovery board with STM32F072RBT6. I tried to setup USB audio with CubeMX and compile with out no issue. Now I would like to change the Audio Sampling rate to 48KHz instead of 1KHz (code default value). Once change to 48KHz, the code will run into Hard Fault exception. So I take a look into the code and sort of does not understand below part (summarize from various .h and .c) #define USBD_malloc (uint32_t *)USBD_static_malloc #define USBD_AUDIO_FREQ 22100 #define AUDIO_OUT_PACKET (uint32_t)(((USBD_AUDIO_FREQ * 2 * 2) /1000)) //=4=88bytes /* Number of sub-packets in the audio transfer buffer. You can modify this value but always make sure that it is an even number and higher than 3 */ #define AUDIO_OUT_PACKET_NUM 80 /* Total size of the audio transfer buffer = 88*80=7040 byte

Posted on June 23, 2017 at 15:24Hello,I am interfacing SPI based LSM6DS3 accelerometer to imx7 based board. I got LSM6DS3 driver from  'https://github.com/STMicroelectronics/STMems_Linux_Input_drivers '. Added device tree for this (kernel-4.1.15) as below.        lsm6ds3@0{                compatible = 'st,lsm6ds3';                reg = <0>;                spi-cpha;                spi-cpol;      

Posted on June 22, 2017 at 14:51We have two prototype boards each equipped with a LIS331HH.One of the sensors seems completely broken because the Z axis shows values around 2.3g while laying flat on the table. Because of that we were now looking into self tests to check all sensors in production.We query all the axis and divide each value by 16. The data sheet tells us that 1digit is 3mg so we expect 333 on the Z axis and 0 on X and Y. We measure X:20, Y: 35 and Z: 373, which is an offset we expect [1].Now we start the self test in plus mode and measure X: 177, Y: 131 and Z: 828.The self test values differ by X: 157, Y: 96 and Z: 455 from the non self test values.In the data sheet there are values for 'self-test output change'. Those mean, that X and Y are supposed to differ by a max of 180 and that Z may only differ by 370?So this sensor passes the test on X and Y and fails on Z and therefore we have t

Posted on December 29, 2016 at 08:41Hello,I am using VL53L0X to perform range measurement. I knew there are C APIs and examples that provided by ST already. However, due to I am developing my project by other language, I think I should access to registers to achieving measurement.My problem is I don't know the definition and valid value of all registers. I tried to find relevant information on my.st.com and some technical forums, and got some useful clues. For example, I knew the address of VL53L0X_REG_SYSRANGE_START is 0x00 and I can configure different modes of range measurement by setting different values. Sadly, I cannot find a Spec that guides me to learn whole registers. So I will not achieve more functionalities by reading/writing registers.So could you please provide me some relevant information or Spec which describes all register

Posted on June 21, 2017 at 12:34Hi,I'm having trouble with HTS221 device driver integration (for a FreeRTOS app). ST provides a platform independent driver (see http://www.st.com/en/mems-and-sensors/hts221.html ). But those drivers have functions which need to be remapped :         // the user must redefine the proper HTS221_WriteReg         #define HTS221_WriteReg(RegAddr, NumByteToWrite, Data)  HAL_WriteReg(HTS221_I2C_ADDRESS, RegAddr,      NumByteToWrite, Data)I want to use this driver with I2C but I don't find how, since I'm not use to play with drivers.Did someone already do this ? Or use another similary driver with an imx6 board ?QD

Posted on June 12, 2017 at 01:50Hello:What kind of problem would be caused if pins 2 and 3, marked as NC in the data sheet, were grounded? Would it cause the device to not function?Thanks...

Posted on June 21, 2017 at 10:25Hi, I am using LSM9DS1 IMU for one of our android-6.0 based product. As referred in below links,HAL Layer :  https://github.com/STMicroelectronics/STMems_Android_Sensor_HAL_Input Drivers:https://github.com/STMicroelectronics/STMems_Linux_Input_drivers After integrating above stacks, we are seeing some of the CTS failures.Please suggest us correct stack.Note: we are not using interrupts. Driver polls for events for every 1msThank YouBabu#accelerometer #lsm9ds1 #imu #gyroscope #i2c

Posted on June 19, 2017 at 17:41Hi at all,I am trying to implement gesture recognition with a SensorTile, to develope my firmware I started studying the BlueMicrosystem2 example, and so I was able to detect simple gestures as the wrist's orientation.Now I would like to recognize some gestures a few more complex, as draw a letter in the air or a symbol, what could be the way to implement this?I know that the open.mems library encodes a limited number of gesture in a code, as could I to recognize custom gestures and map them?Should I sample the data sensors by the SensorTile with regularity and compute them to recogize the gestures? or the Open.MEMS library can help me in this operation?Best RegardsTommasohttps://community.st.com/tags♯/?tags=sensortile%20bluenrg-ms%20firmware‌#sensort

Posted on December 12, 2016 at 14:48We need Linux device drivers of lsm6ds3 for kernel 3.7.6.Can somebody provide drivers

Posted on June 24, 2014 at 09:43Dear, What is the linearity error rate with VL6180X ? Tks and regards. A. #proximity-sensor #vl6180x

Posted on January 20, 2017 at 06:43I wonder that ST has plan to make another enhanced version of VL53L0x.VL53L0x's I2C speed and output rate is slow.If a spi interfaced device is made, I hope that it would support the daisy chain.Currently multiple sensor interface is very complex.And I hope that the API library is more simple and light.Additionally, a right angle mounted sensor is needed.

Posted on June 13, 2017 at 02:32Hi, I'm having some difficulty clearing the interrupt pin on the H3LIS100. I have it set to generate and interrupt on data ready. I am also using the LIS2D chip, which has a somewhat similar interface, and I can clear that interrupt by reading the INT1_SRC register (for an over threshold interrupt), but neither reading the INT1_SRC nor the actual data registers seems to clear the interrupt pin for the data ready interrupt condition on the H3LIS3100 chip. Going to power down state does clear the interrupt but that is not too useful when taking repeated data samples.