MEMS (sensors)

..

HelloI’m work on a project where it is necessary to detect if unit has moved and/or rotated. The unit (battery powered and wireless) is eg. placed on the floor and needs to be placed with same heading if it is picked up and put back up on floor within heading being +/-5-10 deg and in an upright position. The unit also have a PIR to detect movement in front of the unit. When repositioning and turning it to find the right heading, the unit will make a sound when the heading is found. In the unit is a LIS3DH accelerometer and a LIS2MDL magnetometer.From the accelerometer any movement will detected if the unit has been eg. picked up or pushed etc. When put back the magnetometer is used to find the heading.In test, it returns the correct heading each time, but can it be trusted over time? True north etc is not needed since the heading is set once for this unique placement of the unit – it is more like a relative heading.The accelerometer is always on, but magnetometer is off by default only

HiI am trying to make work the internal temperature sensor from a STM32G474RE and it seems to return a low value... 11.14 celsius degrees.This is the code I am using:#define TS_CAL1_ADDR ((uint16_t*) ((uint32_t)0x1FFF75A8)) #define TS_CAL2_ADDR ((uint16_t*) ((uint32_t)0x1FFF75CA)) #define TS_CAL1_TEMP 30.0 #define TS_CAL2_TEMP 130.0   double getTemperatureMCUPCB(void) { uint32_t TS_CAL1 = (int32_t) * TS_CAL1_ADDR; uint32_t TS_CAL2 = (int32_t) * TS_CAL2_ADDR; mcuPCBTempADCValue = global_adc1_val[1]; mcuPCBTemperature = ((TS_CAL2_TEMP - TS_CAL1_TEMP)/((double)TS_CAL2 - (double)TS_CAL1)) * ((double)mcuPCBTempADCValue*(3.3/3.0) - (double)TS_CAL1) + 30.0;   printf("MCU temp: %.2f\n", mcuPCBTemperature);   return mcuPCBTemperature; }And this is how is setup ADC1:​​Thanks in advance.

Can you tell me if there is an errata sheet for the LIS12DE?Is there perhaps something known that power consumption increases after long time of usage?

Trying to interface with the LSM303AH eCOM.

..

Hi MEMS experts,I am using LIS2DW12 to measure the movement with very rough distance.I tested it by measuring the X-axis only, but it seems to be biased to positive direction.I mean, Moving it to the positive direction : it starts having the + acceleration, it's stabilized, and gets - acceleration. : In this case, + acceleration occurred longer and - acceleration occurred less. I used these + / - acceleration to measure the rough distance, and I can see the quite accurate or bigger output than actual movement.Moving it to the negative direction : it starts having the - acceleration, its stabilized, and gets + acceleration. Interestingly, - acceleration occurred less and + acceleration occurred longer. So if the moving distance is short, + acceleration at the stop position take out the - movement as it's too much.In summary,I guess my accelerometer might be too sensitive to positive direction, but less sensitive to negative direction.I tried to find the calibration method for this bias,

I have the IIS2MDC along with LSM6DSL accel / gyro on a board with stm32L451 uC.Accel / gyro work fine. uC reads status byte then if any axis has new data ready it reads all from temp to accel (0x20-0x2d) in 1 ST hal fn call multi byte read: HAL_I2C_Mem_Read(). IIS2MDC seems to read X-Z fine using same fn that is read X Low to Temp high ( 0x68-0x6F) but the value for 6E-6F is a duplicate of X values (regs 0x68-0x69)I can read 6 bytes Y to temp and still get the X value for the temp. If I read X-Z in 1 fn call then temperature in another call, temp reads ok.I have read each register 0x45 - 0x6f one by one and compared to a read from 0x45-0x6f in 1 bulk read sequence. All matches except temperature or status (if no time for recalc).temp read alone: 0x6e - 0x1b, 0x6f = 0x00 - these make sense.temp read as part of axis or previous reads: 0x6e = 7d 0x6f = 0xff.This is on a board about 75 deg F so 0x001b is about correct. The IIS2MDC traffic has been verified with a logic anal

..

I am using lis2dw12 on congnitec board on linux. lis2dw12  is enumerated only as iio device as I do not configure spidev. I have to configure the interrupts 0x3F , CTL_1. How can I set this from sysfs interface ?

I have followed the description in <an5296-asm330lhh-automotive-inertial-module-digital-3d-accelerometer-and-digital-3d-gyroscope-stmicroelectronics.pdf> to write self-test code, but the Accelerometer and Gyroscope's data is still not in the correct range which is defined in <asm330lhh.pdf> .Could ST provide an e-mail address, so I can send my test code to you?

X-nucleo-VL53L8A1 not working with nucleo-f401re and GUI,when i connect vl53l8 expansion on Nucleo-f401re ---LD1 blinks red and green...also com port shows in device manager but vl53l8 GUI does not show/detect com port

..

I tried to get XL and gyro data by data-ready interrupt mode,​1. Configuartion registers sequence and values are as follows Use Bypass mode, XL data-ready rounted to INT1; gyro data-ready rounted to INT22. In ISR1 reads the STATUS_REG, if XLDA bit is set, read XL data3. In ISR2 reads the STATUS_REG, if GDA bit is set, read gyro datais that correct to get XL and gyro by data-ready interrupt mode?My questions areIf read STATUS_REG on ISR, the INTx will keep on high, only do a XL read or gyro read from LSM6DSR, the INTx pin change to low?If I put the read XL and read gyro on background while(1), it is likely to cause the INTx pin high and system hangsOnly read XL and gyro inside ISR can keep system stable​​setup sequence​read back reg = 0x12, val = 0x 4read back reg = 0x14, val = 0x60read back reg = 0x16, val = 0x 0read back reg = 0x a, val = 0x 0read back reg = 0x 9, val = 0x 0read back reg = 0x5e, val = 0x 0read back reg = 0x56, val = 0x41read back reg = 0x17, val = 0x 0read back reg =

Hi! I'm using the VL6180X with several libraries for a specific application. However, I have noticed that most of them configure some registers that are not detailed in the manufacturer's datasheet. Therefore, I would like to know what these registers refer to within the sensor and their functionality, in order to fully understand its operation. The registers in question are the following. write8bit(0x0207, 0x01); write8bit(0x0208, 0x01); write8bit(0x0096, 0x00); write8bit(0x0097, 0xfd); write8bit(0x00e3, 0x00); write8bit(0x00e4, 0x04); write8bit(0x00e5, 0x02); write8bit(0x00e6, 0x01); write8bit(0x00e7, 0x03); write8bit(0x00f5, 0x02); write8bit(0x00d9, 0x05); write8bit(0x00db, 0xce); write8bit(0x00dc, 0x03); write8bit(0x00dd, 0xf8); write8bit(0x009f, 0x00); write8bit(0x00a3, 0x3c); write8bit(0x00b7, 0x00); write8bit(0x00bb, 0x3c); write8bit(0x00b2, 0x09); write8bit(0x00ca, 0x09); write8bit(0x0198, 0x01); write8bit(0x01b0, 0x17); write8bit(0x01ad, 0x00); write8bit(0x00ff, 0x05); write8b

Dear Sir,In datasheet, it says that Angular rate zero-rate level is +/- 1dps,does it means that when the chip soldered on PCB and in flat stationary state, the expected value is +/- 1dps or close to +/- 15 counts for +/-2000dps scale?What is the min and max G_TyOff? Not found in datasheet.Thanks.

I'm currently investigating mechanisms for synchronization of disparate IIS3DWB units in a given system. The current thought is that signal alignment between two disparate IIS3DWB units can be achieved without a traditional SYNC signal by aligning to a common "flag" or indicator time base. In the context of our system, we can use the XLDA or FIFO_WTM_IA flag. The XLDA or FIFO_WTM_IA flag will go high when there is either data ready to be consumed, or when a watermark has been hit once data has filled the FIFO enough. Assuming that the time for the processor to consume the accelerometer buffer over SPI is deterministic and consistent, we only need to ensure, then, that the time propagation between data coming in and a flag being risen high is deterministic and fixed. We also want to ensure that the time between the flag being risen and the routed output INT signal going high is also deterministic and fixed. Is there a timing diagram that shows exactly on which clock pulses do flags get

We got from two different suppliers some LSM6DSOXTR and we expect to get 0x6C as fixed value in register 0x0F. ON the contrary we got 0x68 that looks to be the ID code of the oldest and obsolete LSM6D0. Is that possible? Is possible that I got wrong chips from the distributors? Is 0x68 actually the ID of the oldest LSM6DS0? Thanks!

I'm using lis2dw12 accelerometer, while using INT1 pin to route interrupts, it's working good, how ever when I route it to INT2 pin, it doesnt work, the configuration I set:in ctrl reg 5: I set INT2_DRDY to 1 in ctrl reg 7: INT2_ON_INT1 to 1, INTERRUPTS _ENABLE to 1are there any configuration/conflict with other configuration?Thanks

Dear Sir\MadamI have been using steval-mki190v1 (LIS2DTW12 IC), Trying to communicate through I2C with STM32F103RCT6  microcontroller in LIS2DTW12 IC by default how does it act SPI or I2C. Let me know how to configure the I2C pin configuration of LIS2DTW12 communication with the STM32F103RCT6 microcontroller.   Best regards,Gagan GowdaEmbedded Engineer

Hello,I'm trying to set up the two interrupts on the LSM6DSOX, INT1 and INT2 to indicate Single and Double Tap events, respectively.I'm able to make both events trigger their respective interrupt, but would like them to be completely separate.I think I need to implement a delay on the Single Tap, to ensure it doesn't operate under double tap condition - it currently operates twice for a double tap!Is there a way I can do this inside the LSM6DSO, or must I differentiate the interrupts in my microcontroller?  WriteRegister( LSM6DSOX_CTRL1_XL, B01100000 ); //Set ODR to 417Hz? WriteRegister( LSM6DSOX_CTRL4_C, B00100000 ); //Enable Tap on X,Y,Z WriteRegister( LSM6DSOX_TAP_CFG0, B00001110 ); //Enable Tap on X,Y,Z WriteRegister( LSM6DSOX_TAP_CFG1, B00001000 ); //Set X Threshold WriteRegister( LSM6DSOX_TAP_CFG2, B10001000 ); //Set Y Threshold + Enable Interrupts WriteRegister( LSM6DSOX_TAP_THS_6D, B10001000 ); //Set Z Threshold WriteRegister( LSM6DSOX_INT_DUR2, B01111111 ); //S

Hi everybody and thanks in advance for the support.I have a ST SensorTile and I'm starting with the DataLog project to output data through USB port. I have correctly integrated MotionFX libraries and they seem to run, except there are just a bit of problems.What are the right units for time in MotionFX_propagate and MotionFX_update (param eml_deltatime). It seems it has to be expressed in seconds but in some samples you use a 20 constant defined. For instance: 20ms are 0.02f?What is the param eml_q_update in MotionFX_update? Should I put a float of something or it should remain NULL as stated in example/doc?What is the correct sequence for magnetometer calibration?MotionFX_MagCal_init at start (using sampleTime expressed in milliseconds?)MotionFX_MagCal_run in the loop, before the MotionFX_propagate/_update and until the MFX_MAGCALGOOD is reached?Can the MotionFX_MagCal_run be called every loop independently of the quality reached? What is the drawback?Is possible to know when to call

Good afternoon,I would like to use the Sensor tile on which is running the en.fp-sns-allmems1 fw to directly record sensor measurements on the SD card. The idea is to power on the sensor tile, then dobletapping on the sensor tile to start recording directly on the SD card; once I dobletapping on the sensor tile, it stops recording on SD. In a nutshel, I want en.fp-sns-allmems1 to work like en.stsw-stlkt01 on the sensor tile without interacting with the BLE app, because I am interested in having quaternions recorded in csv and en.stsw-stlkt01 does not support quaternions. Should I try to (a) adapt en.fp-sns-allmems1 to do as I said above or should I try to include a library for computing and recording quaternions in en.stsw-stlkt01? If it is better to do (b) what library do you suggest ? Since I am new to programming at these level could you provide me some hints and examples, please ?

I am working on a project which has 2 board revisions A and B.(A was the old revision and B is new). Board A has the accelerometer chip lsm6dso and board B has the accelerometer chip ism330dlc. The driver used is drivers/iio/imu/st_lsm6dsx/. If I use the compatible string in dts as compatible   = "st,ism330dlc" and only the accelerometer in REV B is working and not in board A. But if I add compatible   = "st,lsm6dso", the accelerometer in board A is only working and not in board B. What changes can I make in the dts or in the driver so that the same driver can be compatible with both boards and the accelerometer is working on both boards?