MEMS (sensors)

Posted on January 26, 2018 at 10:45Hi to all,We are usin this accel over i2c with this configuration:* Separate VDD and VDDIO (this one is attached to CS).* SDA and SCL are mounted with a external pull up resistor of 10K.* SDO/SA0 is left unconnected (it is supposed to have an internall pull up).Is there any power up sequence to ensure the i2c mode is properly configured/selected? Any delay between VDD and VDDIO?Powering up both lines to 3V, the VDDIO is not 3V, its in 1.9V or similar. If we disconnect CS from VDDIO. In CS we get a '0' and in VDDIO 3V. Is this normal? And the internall pull up resistor does not lift the pin to high?Is there any example of how to connect the accel for i2c communications? any keynote for the power up?Attached is an image of the mounted sensor were the marking is a dot, a datamatrix and a 'T'.Thanks in advance for your help.#lis2dw12 #i2c

Posted on January 20, 2018 at 05:15Hi, I have configured accelerometer's registers as follows. So, from the activity threshold value how I know that at which raw value of X, Y, and Z axis it will be interrupted on a specific pin?///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////response = LIS3DH_SetODR(LIS3DH_ODR_10Hz); if(response==1){ print('SET_ODR_OK\r\n'); } response = LIS3DH_SetMode(LIS3DH_LOW_POWER); if(response==1){ print('SET_MODE_OK\r\n'); } response = LIS3DH_SetFullScale(LIS3DH_FULLSCALE_2); if(response==1){ print('SET_FULLSCALE_OK\r\n'); } response = LIS3DH_SetAxis(LIS3DH_X_ENABLE | LIS3DH_Y_ENABLE | LIS3DH_Z_ENABLE); if(response==1){ print('SET_AXIS_OK\r\n'); } response = LIS3DH_SetFilterDataSel(MEMS_ENABLE); if(res

Posted on January 28, 2018 at 06:52Is the pin out diagram on page 6 which is labeled ''bottom view'' actually a view from the top? VCC is in the upper left corner (pin 1).  The top side view shows the pin 1 ''dot'' also in the top left corner. and finally the mech drawing shows another bottom side view which contradicts the figure 2 drawing..whats correct?thanks

Posted on January 22, 2018 at 09:27Hi I am using  LPS22HB with my custom made board based on STM32F777. I am reading LPS22HB using the same driver as ST is giving. I always read the same value of pressure i.e 1847. Temperature value is also incorrect as it is very small.  here is code snippet from the LPS22HB_Init()/* Make LPS22HB Reset and Reboot */ if(LPS22HB_SwResetAndMemoryBoot()) return LPS22HB_ERROR; pLPS22HBInit.PowerMode=LPS22HB_LowNoise; pLPS22HBInit.OutputDataRate=LPS22HB_ODR_25HZ; pLPS22HBInit.LowPassFilter=LPS22HB_DISABLE; pLPS22HBInit.LPF_Cutoff=LPS22HB_ODR_9; pLPS22HBInit.BDU=LPS22HB_BDU_NO_UPDATE; pLPS22HBInit.IfAddInc=LPS22HB_ENABLE; //default pLPS22HBInit.Sim= LPS22HB_SPI_4_WIRE;I have also tried by  disabling IfAddInc and reading one by one register.Could you please help me,

Posted on January 24, 2018 at 09:54Hi,I am working on LIS3DH accelerometer sensor, I have interfaced this sensor with STM32F103 series micro controller using SPI interface. When I read X, Y and Z acceleration values, I get some random readings and it too fluctuate lot. The sensor is placed horizontal on PCB, parallel to X , Y axis and perpendicular to Z axis. The reading for all three axes is fluctuate around 0.01 to -0.15. In initialization, all three axes has been enabled.As I am very new to accelerometer sensor, is my understanding that in the position mentioned above should I get g value for X and Y axis around 0g and for Z axis around 1g correct?OR it just shows fluctuations in X,Y and Z axis value when there is some movement of sensor and again it get stable value when the sensor is stationary?

Posted on January 28, 2018 at 00:34Hello,Is it mandatory that 100nF and 10uF to the VDD line has to be ceramic and aluminium respectively?Also, we had three custom boards built with IIS2DH. Surprisingly, all three were giving a different XYZ values when kept in the same orientation. Please give me some suggestions as to what I have done wrong or in what I could do to mitigate this problem.Thanks,Ranjith#iis2dh

Posted on January 25, 2018 at 18:52Hi,    My problem is I can not receive the interrupt signal of INT1 when I using FIFO mode with FIFO buffer full trigger. I find the cause is that the INT1 is always at high, but I expect it should be rise high when FIFO buffer is full.My HW is http://www.st.com/content/st_com/en/products/evaluation-tools/product-evaluation-tools/mems-motion-sensor-eval-boards/steval-mki179v1.html(LIS2DW12TR), I using the following pins for I2C  SCL, SDA, VDD, GND, SA0 (connect to GND)My Pin configuration for INT1 on MCU side is   PIN_GPIO_LOW | PIN_PUSHPULL| PIN_IRQ_POSEDGESW startup sequence:

Posted on January 25, 2018 at 11:16Hi, i am using this sensor for a while now ,and i have a problem when i use together accelerometer and gyroscope. When i use them seperately everything works great, but if use both of them and acquire data from the fifo buffer, accelerometer's data are not good at all. I save my data into an SD card using the SdFat library. I use teensy 3.6 and the ODRs for the sensors are really low 104Hz eatch. Does anyone know what might be the problem?Is this a sensor's problem or mine? Thank you

Posted on January 18, 2018 at 06:19Hello Miroslav, I have done following configuration for IIS2DH acceleromenter./////////////////////////// Sample Code ////////////////////////////////////////////////////response=LIS3DH_GetWHO_AM_I(&who_am_i); if(who_am_i==IC_READ_SUCCESS){ print('Who AM I %x\r\n',who_am_i);unsigned char response,status; AxesRaw_t data; response = LIS3DH_SetODR(LIS3DH_ODR_10Hz); if(response==1){ print('SET_ODR_OK\r\n'); } response = LIS3DH_SetMode(LIS3DH_LOW_POWER); if(response==1){ print('SET_MODE_OK\r\n'); } response = LIS3DH_SetFullScale(LIS3DH_FULLSCALE_2); if(response==1){ print('SET_FULLSCALE_OK\r\n'); } response = LIS3DH_SetAxis(LIS3DH_X_ENABLE | LIS3DH_Y_ENABLE | LIS3DH_Z_ENABLE); if(response==1){ print('SET_AXIS_OK\r\n'); } response = LIS3DH_SetFilterDataSel(MEM

Posted on January 24, 2018 at 11:39Hello,I have 2 questions about the microphone distance of the Bluecoin hardware.I have ordered this hardware to experiment with the microphones and the beam-forming algorithms and it works very impressive. I would like to alter some of the code but had some questions about this.According to UM2214 'Getting started with AcousticBF ...' the microphone distance need to be 21 mm? But the Bluecoin microphones are 40 and 57 mm (diagonal) apart, does this influence the beam-forming algorithm and what determines the distance to choose?I would like to pick-up speech further away from the Bluecoin using a beam-form what setting should I adjust to accomplish this?Marcel

Posted on January 20, 2018 at 00:04Hi everyone,I'm working with a LIS3DH accel and having trouble reading registers. I'm able to successfully read the value from any single register, but all subsequent reads return the same value. I.e. if I read WHO_AM_I register, and then read CTRL_REG1, both read commands return the value from the WHO_AM_I register.Has anyone encountered this before? I'm sure there's a small detail I'm missing.Below is the code for reading a register.uint8_t lis3dh_read_byte(const lis3dh_reg_addr_t addr) {   uint8_t cmd = 0;      cmd |= LIS3DH_SPI_READ_MASK;   cmd |= (LIS3DH_SPI_ADDRESS_MASK & addr);      HAL_StatusTypeDef status = HAL_ERROR;      while(status == HAL_ERROR)   {     status = HAL_SPI_TransmitReceive(spi, &cmd, rx_buf, 1, SPI_TIMEOUT);   }  &nb

Posted on January 22, 2018 at 17:39HelloI want to detect the movement for 10 min from an accelerometer LIS2DE12, I want to know if I can use the configuration of the interuption register or i must use a REal time counter Thanks

Posted on January 22, 2018 at 08:51Hi ,I am using LSM9ds1 in one of my project. The main reason for using this chip is,  it is THE one recommended for IMU feature, where all 3 sensors are in one chip.In Android 6.0 , I am getting all 3 sensors data , Accelerormeter , Gyro and Magnetic sensor.My question is :1: How do I validate the IMU feature? 2: Is there any specified calibration process to test and validate IMU on LSM9DS1?Please configmThanks,Dayananda

Posted on January 17, 2018 at 02:13I believe I've configured my system (LSM6DSMTR connected to Nordic nRF52382 via I2C) to interrupt on INT2 when the FIFO threshold is reached.  What is happening, is that I get an interrupt when data first appears in the FIFO (status shows 3 samples), then after a while, I get the FTH interrupt with the status showing the FTH number of samples.  I suspect that the first interrupt is the wakeup interrupt I've configured in the MD2 register.  I've configured that so that the FIFO will transition to bypass-to-FIFO  Any suggestions how to eliminate that first interrupt at the processor? By the way, I do want INT1 to assert on wakeup.  Not INT2.  Here's a readback of my registers:0x1: 0x00x2: 0x00x3: 0x00x4: 0x00x5: 0x00x6: 0x4E0x7: 0x00x8: 0x10x9: 0x800xA: 0x240xB: 0x00xC: 0x00x

Posted on January 16, 2018 at 11:10In the datasheet say that this pin must be work(indicate moment of magnetometer new data avalaible ) automatically(without need of configuration), but it doesn't work. Why? In the http://www.st.com/resource/en/datasheet/iis2mdc.pdf said that M_XYZ_DA status bit must be connected with DRDY_M output pin(page 32, CFG_REG_C (62h) 0 bit). Does not LSM9DS1 datasheet contain complete information?This question(https://community.st.com/0D50X00009XkhX7SAJ ) has proved this  assumptionnull

Posted on January 19, 2018 at 11:22hi everyone,i'm trying to debug my program on the iNEMO M1 but when i press the reset button to start the program the iNEMO is disconnected from the debugger and i can't talk to it anymore, so i can't see where the problem is.hardware situation:i'm using the iNEMO M1 mounted on a home-made board, programmed by the STlink of a nucleo stm32f0 discovery.Vdd is supplied by the USB of nucleo.the reset button used is the one of nucleo, linked through the board.software situation:cubeMX is used to set the iNEMO configuration.TrueStudio is used to program the iNEMO.working aspects:the simple programs i wrote worked just fine (toggle led with timer countdown, external button inputs or delay functions)when i ask for the accelerometer data it does not work, but maybe the problem is in the code.the problem is that when i compile and then start the p

Posted on December 05, 2017 at 22:19I want to access the LSM6DSL via SPI. And I ´m always recieving 0x40, when I read the WHO AM I register. I expect 0x6A. I am sending 0x8F to read the WHO AM I register.. Any Idea why I am not recieving the right value?

Posted on January 16, 2018 at 21:24   Here is their initialization code:    i2c_LIS2MDL_Read_8Bit(LIS2MDL_WHO_AM_I, &b);       i2c_LIS2MDL_Write_8Bit(LIS2MDL_OFFSET_X_REG_L,0x00);    i2c_LIS2MDL_Write_8Bit(LIS2MDL_OFFSET_X_REG_H,0x00);    i2c_LIS2MDL_Write_8Bit(LIS2MDL_OFFSET_Y_REG_L,0x00);    i2c_LIS2MDL_Write_8Bit(LIS2MDL_OFFSET_Y_REG_H,0x00);    i2c_LIS2MDL_Write_8Bit(LIS2MDL_OFFSET_Z_REG_L,0x00);    i2c_LIS2MDL_Write_8Bit(LIS2MDL_OFFSET_Z_REG_H,0x00);       i2c_LIS2MDL_Write_8Bit(LIS2MDL_CFG_REG_A,0b10001100);// temp comp, continuous 100hz data rate    i2c_LIS2MDL_Write_8Bit(LIS2MDL_CFG_REG_B,0b00000010);// offset cancellation enabled    i2c_LIS2MDL_Write_8Bit(LIS2MDL

Posted on January 18, 2018 at 09:07I have configured the Wake-Up interrupt (with highpass filter) as described in the application note: 1. Write 60h to CTRL1_XL // Turn on the accelerometer // ODR_XL = 416 Hz, FS_XL = 2 g2.Write 90h to TAP_CFG // Enable interrupts and apply high-pass digital filter; latched mode disabled3.Write 00h to WAKE_UP_DUR  // No duration4.Write 02h to WAKE_UP_THS // Set wake-up threshold5.Write 20h to MD1_CFG // Wake-up interrupt driven to INT1 pinAll other registers are used with default values.After 2.6 ms of writing the MD1_CFG register the INT1 pin gets high and remains high 50 ms. I would expect, that the pin gets hight after a wake-up event occurs.. This case happens independently of the sampling frequency, wakeup trheshold or wakeup duration. After the 50 ms it seems to  work fine.I expect that the signal on INT1 is low until an wake-up event.  Is this

Posted on January 18, 2018 at 14:42Hi, I want to test IMU Sensor callibration and it's functionality. I have all sensors available Accelerometer + Gyroscope + LSM9DS1_mag. Could you please tell me the procedure to callibrate sensor values as IMU unit.

Posted on January 12, 2018 at 04:25when i use lis3dsh , i test the power waste is 1.7mA, is more big than the discription in datasheet. the way i use it: the circuit board use STM32F4discovery , i init the gpio ,and then measure the Electric current.when i measure the Electric current i haven't init the reg of lis3dsh .question:1)How much is the lis3dsh current2）How to configure lis3dsh to get it into low power

Posted on January 04, 2018 at 13:18the following code i have written for STM32F103C8T6 for interfacing with AIS3624DQ accelerometer. But while checking , when i read register WHO_AM_I (0x0F) it should return me 0X32 default but it is returning me 0XFF. for any output register it is returning me the same value as 0xFF. please help in this. i know some thing is wrong but i am not getting it. thanks in advance. the code is as follows.////////unsigned int x=0;void main(){GPIO_Digital_Output(&GPIOA_BASE, _GPIO_PINMASK_4); //chip select CSSPI1_Init_Advanced(_SPI_FPCLK_DIV2, _SPI_MASTER | _SPI_16_BIT | _SPI_CLK_IDLE_HIGH | _SPI_FIRST_CLK_EDGE_TRANSITION | _SPI_MSB_FIRST | _SPI_SS_ENABLE | _SPI_SSM_ENABLE | _SPI_SSI_1, &_GPIO_MODULE_SPI1_PA567);Delay_ms(100);while(1) { GPIOA_ODR.B4=0; //chip select low x=SPI1_Read(0X0F); Delay_ms(10); GPIOA_ODR

Posted on January 16, 2018 at 09:17Hello,I'm using LSM6DSL in sensor hub mode with LIS2MDL, using the example in IKS01A2 I have managed to activate the LIS2MDL and read data from it.My current issue is that I can't put the LIS2MDL in low power mode, I tried using 'LSM6DSL_ACC_GYRO_SH0_WriteByte' function but it get stuck in the while loop waiting for 'LSM6DSL_ACC_GYRO_SENS_HUB_END_OP_COMPLETED'Can you please assist?Thank you,Michael

Posted on January 12, 2018 at 13:07Hi, I got a problem in LIS3DH ADC function, we use LIS3DH ADC1 to detect the battery power in our product, but now we found that ADC can't work in the new lot of LIS3DH, the date cod is 8734. And the lot of data code 8518 is the last lot we used and it works fine in our product. Can anyone help me to find if any change in LIS3DH ADC function after the data cod 8518?  And please refer my attached pictures to show the I2C waveform, the data always is 0 when we read out from ADC1 register of date code 8734 chip. The waveform of date code 8518 chip can show the right data of ADC1.#lis3dh-adc-function-problem

Posted on January 16, 2018 at 17:08Hi everyone. I'm trying to use VL53L0X satellites with my nucleo32 (STM32L031K6) but i'm having a lot of problems to integrate the API. I'm generating the initial code with STM32CubeMX and importing the project to Atollic trueSTUDIO. Tried to add a folder with all .c and .h files but didn't work.Is there an easier way to make it work?Thanks in advance.