MEMS (sensors)

the first interrupt is generated if the device is rotated by an angle greater than 35 degreesfrom the start position and remains in the blue zone for a period of time of at least 2 seconds1�?35 degrees. What is its principle calculation formula？At least how many axes changed I can think a Relative tilt happen？2�? When the chip is placed horizontally or vertically, The chip rotates 180 degrees along the central axis，this behavior is a  Relative tilt ?generate a interrupt ?

I accidentally connected 3.3v to the mki173v1 - could I damage it?

Hello everyone,I'm using lis2dh12 for acceleration measurement. In the datasheet, I find the typical zero-g offset accuracy is +/-40mg. When the device is placed horizontally, the reading of X-axis and Y-axis should be 0. For most of our devices, they work well, the reading is within 40mg when placed horizontally. But there is a device the X-axis reading is always about +100mg, no matter facing up or facing down. Is this a normal operation? Can you please help us analysis the reason?Sorry for my English, I hope my question is clear.Thanks.LiBing​Best regards

Hi,we are woeking on motion detection application using LIS3DH,we have done below registersettings but we are only getting interrupt on motion first time but after that we are not getting interrupt after reset also.once we are getting th einterrupt and checking the register INT1_SRC but its value we are getting is zero.can you please suggest register setting to detect motion,do we need to give some delay after any register setting.reg[0] = CTRL_REG1; /* 10Hz, normal power mode, ZXY enable */ reg[1] = 0x27; err_code = i2c_lis3dh_write_data(reg, 2); reg[0] = CTRL_REG2; /* HP filter for INT1 */ reg[1] = 0x01; err_code = i2c_lis3dh_write_data(reg, 2); reg[0] = CTRL_REG3; /* IA1 enable */ reg[1] = 0x40; err_code = i2c_lis3dh_write_data(reg, 2); reg[0] = CTRL_REG4; /* scale 4g */ reg[1] = 0x10; err_code = i2c_lis3dh_write_data(reg, 2); reg[0] = CTRL_REG5; /* interrupt 1 pin latched */ reg[1] = 0x08; err_code = i2c_lis3dh_write_data(reg, 2); reg[0] = CTRL_REG6;

Hello!I am an intern working on a project that should track the movement of multiple objects simultaneously. What I need is something compact and efficient. I came across your time of flight sensors and I was just fascinated by the way they work. I would like to use a VL53L3CX, which I am currently struggling to program.I saw a few demos which use the VL53L1X ToF sensor. One was a LIDAR and one was a counter for the number of people which were in a room. I tried to do some further research on how these sensors work. I found out that VL53L3CX and VL32L1X both share a multiple object detection feature which is based on a histogram. Also, from what I discovered, both modules are capable of capturing 13 datapoints. I found an Arduino API for the VL53L1X, but it does not do multiple object detection. I found a Nucleo32 F401 API as well, but I did not find a way to use it with my Nucleo32 F303.It would be amazing if I could understand how these sensors work and

HI everyone, I have this error message when I compile my main program with eclipse ... I'm using a P Nucleo 53L0A1 .. someone can tell me what's happening because I really don't understanderror message =>Open On-Chip Debugger 0.10.0+dev-00021-g524e8c8 (2019-04-12-08:48)Licensed under GNU GPL v2For bug reports, read http://openocd.org/doc/doxygen/bugs.htmlC:/Ac6/SystemWorkbench/plugins/fr.ac6.mcu.debug_2.5.0.201904120827/resources/openocd/scripts/st_board/nucleo_l476rg.cfg:15: Error: Can't find target/stm32l4.cfgin procedure 'script' at file "embedded:startup.tcl", line 60at file "C:/Ac6/SystemWorkbench/plugins/fr.ac6.mcu.debug_2.5.0.201904120827/resources/openocd/scripts/st_board/nucleo_l476rg.cfg", line 15

Hi.I'm testing pressure using LPS22HB IC.I connect GND SD0.But LPS22HB give me address nack.So I change address "Low" to "High", LPS22HB give me strange pressure value and not address nack.Why do LPS22HB address strange?Thank you.

HI, We used lsm6dsl sensor on mtk8735 platform (Android). We found that the low-pass filter is used in the high-frequency working mode which freq is greater than 26hz. the XYZ direction data range which obtained is not within +-4G, but 0x10h register value is 0x48 which ODR is LSM6DSL_REG_CTRL1_XL_ODR_104HZ and full-scale with +-4G. We kept turning the device and print the original value of accelerometer XYZ. We saw that the data is ranged in + - 1g which is abnormal as normal.we found tha sensor data is right only the ODR bellow LSM6DSL_REG_CTRL1_XL_ODR_26HZ without low-pass filter.Please give us a reasonable explanation and look forward to your reply. thanks

I was wondering if it is possible to do it with the SensorTile and if so, what are some helpful documents or example programs (preferably in Python). I have been looking through the design tips for example DT0106 (Residual linear acceleration by gravity subtraction to enable dead-reckoning). The document is great however, I have some confusions regarding the complete steps as it starts of assuming that we already have a rotational matrix. I was wondering if I could get some tips on how to calculate 3D displacement using the SensorTile.

In Design Tip DT0106, is it mentioned that:Another technique which can be of help in controlling the integration error is known as Zero-Velocity-Update (ZVU): when the modulus of the acceleration is 1g and the output of the gyroscope is near 0, then it is assumed that the velocity is zero, and the corresponding integrator is reset to 0. If all the conditions are met in the above code, this instruction is executed: velhp(i,:)=[0,0,0]. What does it mean for the "modulus of the acceleration is 1g"? How could I determine this from the accelerometer data? Furthermore, does the output of the gyroscope being near 0 mean that the gyroscope data in all x,y,z axes be 0? I am quite new to these sensors, so I hope that I could get some clarification on these. Thank you!

I want to access PDM_OUT data from the MP45DT02 and output this on the CS43L22. For this I want to use the I2S protocol but I have difficulties connecting the MP45DT02 to the I2S mode and using the HAL_I2S_Receive function. How do you initialize the I2S mode?

Hello, I am writing this message to you because I need help, if it is possible I would be grateful to you .. Ok, I am working on a project in which we will use the VL53L0X as a sensor in an access control device , we will use it as a proximity sensor to trigger the opening of a door .. For this I bought a P-NUCLEO- 53L0A1 board to perform tests with the his VL53L0X sensor, I performed distance tests, air gap tests manually and read the values.However in the UM2039 manual I saw that there are several calibration tests to be performed except that I did not do very well in software I downloaded the eclipse software import the VL53L0X file from the API but I don't know where to start or how to start my calibrations, what code to use etc if you have any leads it would really help me to move forward .. Thanks .

Hi,my name is Vincenzo.Trying to make some simple applications with ToF VL53L3CX the following doubt arose:Can several ToFs, close to each other, work at the same time without the risk of the measurements being disturbed?In other words, if different ToF VL53L3CX, set in the same way, start the measurement at the same time, is it possible that the laser generated by a ToF is received by the collector of a different ToF?Thanks in advance for your support

I'm using an array of VL53L0X for a robotics application, and I'm struggling with the problem of offset calibration. I have looked through the API, but I get lost pretty quickly. Can you point me at any working tutorials and/or examples showing how to do this?TIA,Frank

Hi, i want to use VL53L1X and VL53L3CX  to detect a small size target (e.g finger,rope) at 1 meter away. i am wandering what's the minimum target size for VL53L1X and VL53L3CX ?Thanks.

I am trying to log acceleration values, time and date over a longer period of time. (8 hours)After an undefined time (often after about 1h) the green LED will no longer flash. If the SensorTile.box is supplied by a power supply, you can see that the SensorTile.box consumes about 40mA continuously in this state.In this state the app can also no longer connect to the SensorTile.box. The following settings were used in expert mode:Firmware: 3.4.1Low power acceleration sensor: Acquisition time (minutes) = 480- Low Power Mode 1- 12.5Hz- no LP Filter- no HP Filter- full scale 2gRTC dateRTC timeFile to SD card (buffer 10k)Streaming on BLE shows the same behaviour.Streaming to USB works over the hole periodDoes anyone have any idea what could be causing this?Thanks in advance

I'm trying to use the X-NUCLEO-53L1A1 board for measuring curren of an isolated VL53L1X sensor. I connected the mini PCB over flying connectors VL53L1X to the X-NUCLEO-53L1A1 board and can use it over the VL53L1X_gui successfully. When I diconnect the GND and VDD cabels from the X-NUCLEO-53L1A1 board and connect them to an external power supply. The VL53L1X_gui shows an ERROR as soon as I select that sensor in the drop down menu.The ERROR is:VL53L1_SERIAL_COMMS_DLL.setActiveSensor():: RetVal:-1

I have been using it already for a couple of weeks, today I plugged it in and I get that error. I tried to flash it again with the .bin file provided to update the firmware, but of course it's the same as previous version. I also checked the port number, set it to manually identify it, but still get the same error. Can you please help me? thanks!

Hello,actually I am want to read data from fifo of the lis3dh sensor. I follow the datasheet and application note:write 00000000 in TEMP_CRG_REGwrite 00100111 in CTRL_REG1write 10001000 in CTRL_REG4write 01011110 in FIFO_CTRL_REGwrite 10000000 in CTRL_REG5clear fifo in while loop until FIFO_SRC_REG&0x20 == 0 (check for empty flag)write 01011110 in FIFO_CTRL_REGwait until watermark flag is activated (i.e. FIFO_SCR_REG&0x80==0)read values since empty flag stays 0 (i.e. FIFO_SRC_REG&0x20==0)Unfortunately it works exactly once. Than the watermark will never be reached again (I was waiting appr. 1h). Also there seems to be no change at the FSS bits of the FIFO_SCR_REG. Has anybody a hint for me what can be the root cause and how to overcome that issue? Thanks a lot.Kind regards,Philipp

I have enabled the conditions needed to turn on the 6D orientation, and tried to read the registers according to these files: https://os.mbed.com/teams/ST/code/LSM6DSL//file/77ec4781b110/LSM6DSL_acc_gyro_driver.c/ and https://os.mbed.com/teams/ST/code/LSM6DSL//file/77ec4781b110/LSM6DSL_acc_gyro_driver.h/Can anyone help me?

Hello ST-Community!When I'm using the LIS2DW12 at ODR=1.6kHz, the Interrupt for reaching the FIFO-Threshold is jittering with 1/ODR, but only if the threshold is greater than 12. If it's less or equal, everything is working fine.The buffer-Mode is set to FIFO-Mode, but this behaviour also occurs in Continous-Mode.The Power-Mode is set to High-Performance/Low-Noise.The Interrupt is routed to the INT1-PinThe two images show the rising edge on the pin INT1. The time between the two cursors "a" and "b" is 624us (almost 625us), which would equal to 1/ODR (1/1600 = 625E-6)

Hello,I am currently trying to implement offset calibration to VL53L0X sensor. I placed sensor in front of white paper with 100mm distance as datasheet suggest. When I get sensor measurement before offset calibration, I get 135mm which is fine because i placed glass in front of the sensor. However, when I calibrate sensor, I get 0mm as a result from same distance. So, I move sensor to 200mm, I am getting 100mm for measurement. I think of offset calibration as it will add or subtract offset value from the measurement value not set 0mm when the offset calibration has made. I am using VL53L0X_perform_offset_calibration function from api. I followed UM2039 documentation as referance. So, what could be the possibble reason for that or is it the way offset calibration work?Regards,Taha

Hello,I am using LIS2DH12 with SPI connection. I am able to read back Device ID which is 51. Also, I can write a to the reference register and read back successfully. However, I cannot set registers. I am writing value on it and read back. The value on the register does not change.uint8_t dev_id;   ret = lis2dh12_device_id_get(&dev_id); printf("Device ID %d\n", dev_id);   uint8_t data= 0xAA; uint8_t data2=0; lis2dh12_filter_reference_set(&data); TMR_Delay(MXC_TMR0, MSEC(10)); lis2dh12_filter_reference_get(&data2);   int result = 0;   result = 0; lis2dh12_op_md_t op; lis2dh12_op_md_t op_set = LIS2DH12_NM_10bit; result = lis2dh12_operating_mode_get(&op); printf("GET| Func result %d Mode %d\n", result, op); result = lis2dh12_operating_mode_set(op_set); TMR_Delay(MXC_TMR0, MSEC(10)); printf("SET| Func result %d Mode %d\n", result, op_set); result = lis2dh12_operating_mode_get(&a

Hi,I am having uncertainties when calculating displacement and change of angle effected by random walk.I want to know proportion of failure in measurement caused by random walk.In the datasheet of ISM330DLC random walk (ug/sqrt(h) is declared as noise density (ug/sqrt(Hz)).I found different approaches in calculating effect of random walk effecting displacement and got confused.Example: noise density: 75 ug/sqrt(Hz) -> converted to ARW: 1.25 ug/sqrt(h)displaceent after 1 minApproach one (which I can imagine is correct): s = 0.5*9.82(ARW * sqrt(t(h)))*t^2= 0.5*9.81(1,25 ug/sqrt(h)*sqrt(1/60))*60^2 = 2.85 mmApproach two I found: s = 9.81* noise density *sqrt(t) *ts = 9.81*(75 ug/sqrt(Hz) * sqrt(60))*60 = 0.341 mCan anyone help and/or does have some sources with useful information?Thanks a lot!!!

I'm wondering if there are any concerns with acceleration measurement offsets and extra noise due to strain on the package from encapsulating it or potting it. I'm specifically looking at the LIS2DS12 if different packages have different answers to this question.