MEMS (sensors)

We're using a LIS3DE in our project wired up to the MCU as following:So we're using I2C for communication and have access to both INT pins, but not to the reset line and neither is there a mechanism to hard-reset the accelerometer.During development I've often used breakpoints that would mess up I2C and the LIS3DE would stop answering, even after a CPU reset and thus reset of the I2C communication. Only after a power-on-reset of the whole device (VCC off/on) the LIS would start working normally again (no changes in SW).Since I don't have any access to the reset line I wanted to ask if there's any way to put the LIS in a known state, e.g., by pulling both SCL and SCA to

Posted on April 20, 2018 at 16:16Hello Experts,Recently I bought the STEVAL-WESU1 board and able to read the sensor data using android application.My requirement is to connect this wearable platform to other ARM board (raspberry pi board), raspberry pi should be able to read the data from wearable platform via BLE.Is it possible ? can you please provide us some code to do that ?Thanks for the help.Please let me know if need any information.#wearable #bluestsdk

Hi,This is my first question to the community so hello! :)I've recently started working with the LIS3DH accelerometer and I am experiencing some difficulty in interpreting the startup sequence for the device. Using the datasheet and AN3308 the startup sequence is described as the following for a generic configuration:Write Ctrl_Reg1Write Ctrl_Reg2Write Ctrl_Reg3Write Ctrl_Reg4Write Ctrl_Reg5Write Ctrl_Reg6Write REFERENCEWrite INTX_THSWrite INTX_DURWrite INTX_CFGWrite Ctrl_Reg5For my project I need to first write the configuration to the device in power-down mode and then when prompted set the correct power mode and begin sampling. However the above format seems to begin sampling after the first write to the device once the ODR has been set and axis enabled.Additionally for signal synchronisation on DRDY the I1_ZYXDA

When I first boot the board the accelerometer is not recognized in IIO. After a reboot it does or if I do a rmmod and then modprobe on the kernel modules.My kernel is based on the TI 4.4 kernel from the 3.02 automotive SDK. The accelerometer kernel module is from the ST website since it is not included in the TI Linux kernel.Michel CatudalACTIA Corp

Hi! I have a custom pcb with Lsm6dsl connect to mcu (nrf52832) via i2c. I can write and read regs of Lsm6dsl well (who I am also return 0x6a). But when I try to write ODR bits in CTRL1_XL (10h) reg (for example 0x10) then I can not work,because it alwaus return NACK (Negative Acknowledge).. like there is no i2c slave on this address. If I write other bits in CTRL1_XL (10h) reg (for example 0x0f) it work OK.Can anybody help me, what it is the problem?

https://www.st.com/content/ccc/resource/technical/document/application_note/group0/26/07/3f/bf/12/55/47/62/DM00402563/files/DM00402563.pdf/jcr:content/translations/en.DM00402563.pdfEquation:|Min(ST_X)| <= |OUTX_ST-OUTX_NOST| <= |Max(ST_X)|What is ST_X stand for? And OUTX_ST i OUTX_NOST? Is this right?Who can give me insight?

Posted on February 02, 2018 at 07:06My setup is very similar to my setup in previous question: https://community.st.com/message/182613-re-motionar-initialize-function-gets-stuck?commentID=182613&et=watches.email.thread#comment-182613 SensorTile + DataLogger sample project + SDCard + MotionARNow I'm trying to add MotionPM to the mix. I'm able to call the init function and get the version number of the library. I then proceed to call the Update function in a loop. It seem like it takes an update only 4 times before we jump into an error handler.I understand that this is not a lot to go by, but does this give anyone any clues as to what I may be missing?

I try to add mutex in the X-CUBE-53L1A1 SimpleRangingExamples I have defined #define VL53L1_GetI2cBus(...) CO_Mutex_get() in vl53l1_platform.c #define XNUCLEO53L1A1_GetI2cBus(...) CO_Mutex_get() inX-NUCLEO-53L1A1.cand also for PutI2cBusBut the drivers then hangs in VL53L1_WaitValueMaskEx has if it couldn't get the mutex.I have count, the number of release of mutex is OK.How can we integrate this example in FreeRTOS environement ?Best regardsthanks for any suport

The goal is to create the precise (and as cheap as possible) inclinometer, basing on the IMUs sensors. It should measure the angle change of the rotating wheel (speed up to 250 deg/s), with accuracy of 0.01 degree. I am not rejecting the fushion of few IMUs for getting better resluts.I was looking for the IMUs marked as "new", i.e. LSM6DSL, LSM6DS3TR-C, LSM6DSM trying to compare them. The only noticable difference I have noticed is power consumption, DSM is designed also for optical image stabilization, and TR-C has slightly higher output noise. I have a question for community: Which sensor should fit my expectations best?

Hi Everyone, I am having issues configuring INT1. I have attached my current configuration.The init code looks like this: /* * Restore default configuration. */ lsm6dsm_reset_set(&accel_ctx, PROPERTY_ENABLE); do { lsm6dsm_reset_get(&accel_ctx, &rst); } while (rst); <snip> /* * Set interrupt routing */ lsm6dsm_int1_route_t intRouting = { .int1_fth = 1, .int1_drdy_xl = 1, };   lsm6dsm_pin_int1_route_set(&accel_ctx, intRouting);   /* * Set interrupt output to active low */ lsm6dsm_pin_polarity_set(&accel_ctx, LSM6DSM_ACTIVE_HIGH);At the end of the reset operation (line 8) the INT1 pin is LOW. At the completion ofsetting the pin routing (line17) INT1 is HIGH. At the completion of setting the pinpolarity (line 22) INT1 remains HIGH. Does that mean that data is already ready?At this point the data rate has not yet been set so I was not expecting data to be

Hi,I am trying to enable free-fall interrupt on INT1 and wake-up on INT2. However only free-fall on INT1 works. Here are the register settings:CTRL_REG1 = 0x6F // 200Hz ODR, enable XYZCTRL_REG2 = 0x00 // disbale HP filterCTRL_REG3 = 0x40 // IA1 Interrupt on INT1CTRL_REG4 = 0x30 // +- 16g FSCTRL_REG5 = 0x0A // latch both interruptsINT1_THS = 0x02 // 372mg threshold for free-fallINT1_DURATION = 0x03 INT1_CFG = 0x95 // setup free-fallCTRL_REG6 = 0x02 // IA2 Interrupt on INT2INT2_THS= 0x10 // wake-up threshold 3gINT2_DURATION = 0x00 INT2_CFG = 0x2A // setup wake-upI suspect it has to do with CTRL_REG6. I'm assuming "interrupt 2" refers to the interrupt selected in INT2_CFG, which in this case is wake-up? Regards,Kevin S

I am using STEVAL-MKI174V1 adapter board for LIS2DS12 evaluation. I checked the schematic of STEVAL-MKI174V1 and I have two questions:Can Vdd for STEVAL-MKI174V1 be 3.3V without damaging LIS2DS12 because it can handle only 2.2V (It seems answer to this will be yes because of regulator)Do I need to add external pull-ups to SDA, SCL line even after adapter board ?Thanks,Kiran

Hi,I am reading data out from two LIS3DHs. All works as expected until the full scale is set to +-16g.According to the data sheet, when FS is 11 and low power mode is enabled, each LSb in the data output registers represent 192mg. Low-power mode gives a 8 bit output in the OUT_X/Y/Z_H registers. The maximum value of a 8 bit 2's complement number is 127, and thus the data output registers can in theory show 127*192mg = 24g. This exceeds the +-16g threshold. Does this mean that in low-power mode and +-16g full scale, the number in the data output registers can never exceed 16000mg / 192mg = 83? I am getting values such as 127 and -128 from the data output registers, which don't make sense to me. I believe my register configurations are correct, as I was able to read (0, 0, 5) when the accelerometer is placed flat on the ground. 5*192mg = 960mg, which is close enough to 1g considering the limited resolution.Regards,

Hi, I need to get the FIFO contents prior to impact, to do this, I enable high pass, and go to stream to FIFO mode. But I get an interrupt as soon as I finish configuringI am configuring LIS2DH12 according to your application note:CTRL_REG1 = 0x37 // 25Hz, xyz enabledCTRL_REG2 = 0x0B // high pass data sent to FIFO and output regsCTRL_REG3 = 0x01 // IA1 interrupt on INT1 pinCTRL_REG4 = 0x48 // BDU, +-4g full scale readingCTRL_REG5 = 0x0A // latch both interrupt pinsCTRL_REG6 = 0x14 // interrupt 2 on INT2 pinINT1_THS = 0x0A // about 0.3gINT1_DUR = 0x03INT1_CFG = 0x2A // x high, or y high, or z highFIFO_CTRL = 0x20 // trigger event allows triggering on INT2CTRL_REG5 = 0x4A // enable FIFOFIFO_CTRL = 0xE0 // set mode to stream to FIFOCan you please take a look and tell me if I'm doing something wrong?

I am wondering if you could provide any sample code for testing the LIS2DW12 on Arduino if you have any? Thanks!

I am using the FIFO to read both the ACC & GYRO data using the FIFO_DATA_OUT_H and FIFO_DATA_OUT_L at 52Hz ODR.But once every 1~2 hours, the FIFO data seems corrupted. Debugging it shows the FIFO Pattern number (FIFO_STATUS3 & FIFO_STATUS4) return a huge number like (0x1D8).The normal case, Pattern should be 0~5 for GYRO-ACC.Anyone experience this issue before ?

Hi,I looking for ideal parameter for sound source localization for 2 microphones on-board, maybe someone testing this ? I tried to set different parameters for different algorithms and each time the angle print on the console was poorly reflected correct source sound location.Maybe I should pay attention to the settings of other parameters if so which ?libSoundSourceLoc_Handler_Instance.channel_number = 2;   libSoundSourceLoc_Handler_Instance.M12_distance = ???; //side or diagonal ?   libSoundSourceLoc_Handler_Instance.M34_distance = ???;   libSoundSourceLoc_Handler_Instance.sampling_frequency =   AUDIO_SAMPLING_FREQUENCY; //how value is the best ?   libSoundSourceLoc_Handler_Instance.algorithm = ACOUSTIC_SL_ALGORITHM_BMPH; //which algoritm better and why ?   libSoundSourceLoc_

I have been using the fast ODR setting to reach magnetometer data rates higher than 80hz. I have noticed that there are spikes of about +/- 250 in the data at higher frequencies. After some research, it seems this is caused by reading registers while the device is also updating those values.My question is are there any undocumented side effects of this fast ODR setting? I am wondering this because setting these higher data rates is not documented in the LSM9DS1 datasheet, but rather in the LIS3MDL datasheet.

I want to get gps information using p nucleo lrwan1. Can I get an open source that can help? I'll use the uart port.(gps)

Posted on July 15, 2018 at 05:18Hi I am working with the LPS22HB eval board from ST and trying to generate an interrupt when the pressure drops suddenly.  So according to the data sheet this would be a PLE event (2nd bit of 0x0B register) Below are my register settings - reg 0x10 - 0x50reg 0x12 - 0x03reg 0x0B - 0x0AI set the threshold registers 0x0C and 0x0D to the current value of pressure reading. I would expect that the int pin to change state from low to high after creating an external low pressure event but there is no change. Even the interrupt flag IA or PL from reg 0x25 is not set. Now to make sure I did not have a bad device, I set the LPS22HB for generating an interrupt for a high pressure event. So I set bit PHE (1st bit in 0x0B reg) and the interrupt IS generated when I create a high pressure event. So everything works fine for a high pressure event interrupt.

Hi,I am trying to get lsm303c output an "active low" interrupt on pin INT_XL.here is my init code:void LSM303C_AccInit(void){    uint8_t result = 0;    ACCELERO_IO_Write(LSM303C_CTRL_REG1_A, 0b00100101);  // disable y axis to avoid mg     ACCELERO_IO_Write(LSM303C_CTRL_REG2_A, 0b00000000);      ACCELERO_IO_Write(LSM303C_CTRL_REG3_A, 0b00001000);      ACCELERO_IO_Write(LSM303C_CTRL_REG4_A, 0b00000000);      ACCELERO_IO_Write(LSM303C_CTRL_REG5_A, 0b00000011);  //interrupt active low, open-drain    ACCELERO_IO_Write(LSM303C_FIFO_CTRL, 0b01000000);  //stream mode,    ACCELERO_IO_Write(LSM303C_IG_CFG1_

I'm trying to apply the VL53L0X to an project that require extra air gap between module and cover window. I just saw a video from YT: https://www.youtube.com/watch?v=puRvRsrfpTs that appear to be "official".There is 3d gasket model. It is available to download? Thanks!

Posted on June 22, 2018 at 14:23I am looking for a successful setup for a VL53L1X in outside conditions any type of help to get more then 30 cm in sunny weather #vl53l1x

Posted on July 09, 2018 at 13:01I'm tryong to set my ROI with the P-NUCLEO-53L1A1 and i can't find the function ( VL53L1_SetUserROI() ) in the SimpleRangingExamples Project , i'm using the IAR workbench , anyone have a clue ?

Posted on February 07, 2014 at 09:25Hello,For a project we are using the LSM330DLC 3D accelerometer and 3D gyroscope module. Chapter 4.1. of the datasheet (Doc ID 022162 Rev 2) mentions self-test functionality, which can be enabled by setting the self-test bit. However none of the registers mentioned in Chapter 8 have a reference to this self-test bit. Could you please indicate in which register this self-test bit is located. #lsm330dlc-self-test