MEMS (sensors)

When I received the Sensortile chip, it had the mobile app code flashed on it.I was working on developing on the Sensortile chip, so I flashed my own .bin file onto the chip using ST-LINK Utility.Now I want to revert back to the mobile application code it originally had.Where could I find the .hex or .bin necessary for this?

We are able to retrieve microphone sensor data and view on Unicleo-GUI using serial port on STM32F446RE.While trying to port the microphone sensor data to USB virtual COM port the Unicleo-GUI is not responding.It is observed the data is not received on USB virtual COM port (i.e) interrupt is not generated on USB virtual COM port.Awaiting for support from forum.-Regards,Rajesh K.

VL53L1_GetRangingMeasurementData() ONLY returns data[0] buffer as result. It means that I will get just the result of ONLY one of the two sensor in the matrix. I'm trying to implement your "people counter" posted on youtube (https://www.youtube.com/watch?v=c91Ve-g0J2U) but by using abovementioned driver I'm not able or rather I have to "patch" the driver. Is there an already ready driver providing both data[0] and data[1]?Thanks a lot,Simone.

I'm using the lsm9ds1 as part of a bought module - the arduino nano 33 ble - which can achieve very low power (micro amps) in a power down mode. However, If I initialize and read accel and gyro data from the IMU, afterwards I can't find a way to get back to those low values and I get stuck in the milliamps. What sequence of writes should I send to the LSM registers in order to power it down as much as possible? I'm currently using this sequence for the power down:LSM9DS1_CTRL_REG3_M = 0x03LSM9DS1_CTRL_REG1_G = 0x00LSM9DS1_CTRL_REG6_XL = 0x00NOTE- the mcu communicates with the LSM using i2c.

HelloI had download the firmware FP-SNS-ALLMEMS2 on my STEVAL-MKSBOX1V1. From de app I can read the batery level, and I want to do the same with my raspberry and using bluepy. I have a script where I read the temperature and humidity values, so I wanted to know which uuid I should use for reading batery level characteristic as I do with enviromental values.Thanks

Hi,my name is Vincenzo.I would like to: perform the 3 calibrations ( RefSPAD, XTalk and Offset) for my three VL53L3CX ToF sensors (i have a P-NUCLEO-53L3A2);SAVE the calibration data and then APPLY them before to start the measurement. I have performed the three calibration following the user manual instructions, and I saw that all calibrations work correctly. But, I don't know how to save these calibration data in order to get and apply them with the functions GetCalibrationData and setCalibrationData(). In fact, when I use these functions, I see that the data applaied are different from the data I found with my calibration flow, I supposed that they are the data saved in the ToF's NVM.I wrote an application for the calibration flow and another application for the ranging flow. In the first application I perform the three calibrations, following the UM2267, and I print t

Hi,I would like to read data from FIFO at a stretch in ISM330DLC. Elaborately, I have set an Water Mark Interrupt to 0x3FC in FIFO mode and i would like to read total number of bytes at a time.Is it possible to read?If i Read like that will the WMI happens again or not?if so how the WMI wil work in such case?Thanks & Regards,Jhansi P

 while (1) {  /* USER CODE END WHILE */ for (int i=0; i<11; i++) { buf1[i]=0x0; } for (int i=0; i<11; i++) { buf1[i]=0x0; } for (int i=0; i<11; i++) { buf2[i]=0x0; } for (int i=0; i<11; i++) { buf3[i]=0x0; } for (int i=0; i<11; i++) { buf4[i]=0x0; } for (int i=0; i<11; i++) { buf5[i]=0x0; } for (int i=0; i<11; i++) { buf6[i]=0x0; } for (int i=0; i<11; i++) { buf7[i]=0x0; } for (int i=0; i<11; i++) { buf8[i]=0x0; } for (int i=0; i<11; i++) { buf9[i]=0x0;&

Hello, I am trying to use the LSM to detect taps . I use the default configuration which suggested in the application notes : 1. Write 60h to CTRL1_XL // Turn on the accelerometer   // ODR_XL = 417 Hz, FS_XL = ±2 g   2. Write 0Eh to TAP_CFG0 // Enable tap detection on X, Y, Z-axis   3. Write 0Ch to TAP_CFG1 // Set X-axis threshold and axes priority   4. Write 8Ch to TAP_CFG2 // Set Y-axis threshold and enable interrupt   5. Write 0Ch to TAP_THS_6D // Set Z-axis threshold   6. Write 7Fh to INT_DUR2 // Set Duration, Quiet and Shock time windows   7. Write 80h to WAKE_UP_THS // Single-tap and double-tap enabled (SINGLE_DOUBLE_TAP = 1)   8. Write 08h to MD1_CFG // Double-tap interrupt driven to INT1 pin With this configuration i am able to get interrupts. My problem starts when i try to check the cause of the interrupt by reading TAP_SRC or ALL_INT_SRC. When i read ALL_INT_SRC register i

I have been experimenting with the X-NUCLEO-53L3A2 and have grabbed some quick measurements to see what the accuracy looks like. I am using it the range of 100mm-1000mm indoors. I have callibrated it using a white box with white computer paper taped to it for the offset and a random dark black box for the cross-talk. Using those same object I have measured the following: My question is, are there any ways to improve the accuracy?

https://www.st.com/resource/en/datasheet/lsm9ds1.pdfsee figure 8

Hi, I'm relatively new to microprocessors and everything ST. I've recently been assigned to a project that is supposed to use the LSM6DSOX to track movement within a 3D space. I have the SensorTile.box and a STM32Nucleo-L476RG board. I've been having a lot of trouble trying to use the sensor within the SensorTile.box. I tried using Unico GUI, but it won't detect my sensor when I connect it to my computer. I confirmed the SensorTile.box is on, and my computer detects its presence (I'm able to see it in the File Explorer and access the contents of the board). I have STM32CUBEIDE installed, I installed the X-CUBE-MEMS1 Additional Software Pack, I tried downloading the STM Virtual COM Port drivers, but I still can't seem to get this to work. I am running Windows 10, and have tried the most recent versions of all the above mentioned software. Can anybody help me get started, or at least steer me in the right direction? The online videos I've found have people seamlessly using Unico GUI,

I am using a sensortile board. Using the starter firmware I get the accelerometer (LSM6DSM) values with a resolution of 1mg least significant bit resolution in the csv file on the sdcard. According to the data sheet of LSM6DSM we can get upto 0.061 mg resolution. The ACC values are stored as integers, unlike pressure, temp and humidity. How do we get float values for other LSM6DSM accelerometer as well?Thanks in advance.

I am using LIS2DH and LIS2DH12 with the same register setting and system. However, I got different performance. LIS2DH had the worse performance, compared with LIS2DH12. That is, LIS2DH12 could reach around 150Hz but LIS2DH only reach 110Hz, when I set them to DR 200Hz. What's the difference between LIS2DH and LIS2DH12? Any possible reason for the gap (150Hz vs 110Hz)?

Can someone please help me with upgrading the firmware in my SensorTile.box (STEVAL-MKSBOX1V1). I am successfully being able to connect to the device using the Android application "ST BLE Sensor v4.4.3", and I get a notification saying that there is a new firmware available, but nothing is happening when I select to "Start firmware upgrade". Can I download the file "SENSORTILE.BOX_v3018.bin" from somewhere and manually upgrade the firmware instead?

My call back code looks like this:char MotionMC_SaveCalInNVM(unsigned short int datasize, unsigned int *data) { // This function is called when a call to MothionMC_Initialize(sampletime,0) is made with // data set to zero. uint8_t i; unsigned int *data_local; data_local = data; for(i = 0; i < datasize; i++) { otter_mag_cal_nvm[i] = *data_local; data_local++; } return (char)0; }...in debug, this code hard faults when the loop reaches 106. Far short of the st.com's MotionMC passed "datasize" of 184. The code has been tested to make sure the array otter_mag_cal_nvm[] is not at fault. For this testing the line "otter_mag_cal_nvm[0] = *data_local;" was used instead and the hard faults still occurred on the 106th iteration.

Using the MotionMC and MotionEC libraries to implement a tilt compass. After the Motion libraries report good compass calibration I save the calibration data using the MotionMC_SaveCalInNVM() call back. Then I re-boot the device and load in this calibration data using the MotionMC_LoadCalFromNVM() call back.But the Motion libraries does not report good-compass-calibration. I still have to spend time rotating the magnetometer and accelerometer before the Motion libraries report good-compass-calibration. I will concede, I think I only have to spend about 1/2 the time rotating the magnetometer and accelerometer before the Motion libraries report good-compass-calibration. But I had hoped that I would see good-compass-calibration immediately after loading in the calibration values.-thanks

Have been working with magnetometers for the car parking application. the previous sensors used has not satisfied the range for the application required. Does LSM303 detect at a range of 30cms?

LIS3DE (DocID023719 Rev 3) and LIS3DH (DocID17530 Rev 2) datasheets show the same code ($33) for the WHO_AM_I command? Is this correct? I would expect a different code given one is only 8-bit and the other 8/12-bit.

For information only, I don't consider this a big problem, for me. When the sensortile.box is connected to any USB port to charge the battery, it apparently sets the system into a loop while trying to identify the unit. Logs show 'device descriptor read error....' and 'failed to get pattern....' messages . This loop not only prevents udev access to the USB system but also prevents applications that use USB from starting. Unplugging the sensortile.box breaks the loop and the system returns to normal.

We are using the LSM9DS1 to track orientation and measure the surrounding magnetic field. However, in our application the field being measured also includes the magnetic field from a permanent magnet. When briefly exposing the sensor to the magnet, the offset bias of the sensor is changing. This makes our previously calibrated parameters for the magnetometer unusable.The screenshot below shows raw magnetometer output from our program. After we introduce a permanent magnet (within the full-scale range) and remove it from its vicinity, the magnetometer bias changes. For this screenshot, the change in magnetic field norm was approximately 1051 LSB, or 0.51 gauss at +/- 16 gauss. This gets much worse with stronger magnetic fields (>16 gauss) but nowhere near the 50 gauss indicated in the datasheet where a degrading offset would be noticeable. Is there any way to prevent this? I also found that

I am working on a project/proof of concept that requires measuring the distance to a person relative to the VL53L1X sensor. I did a little digging on the data sheet, and wanted to verify my findings and propose a couple questions to see if this product is the right answer.The sensor is to be placed outdoors in a partially shaded area, pointing towards a person that is also partially shaded. Based on the product sheet, I looked at a 50 kcps/SPAD case and estimated Caucasian skin as 60-65% reluctance based on data online. Given these factors, it said I could expect between 154-166cm. Does this sound correct? I am trying to stretch the effective range for my application, and am hoping to get in the 10ft range if possible.Along these lines, what would I be able to do to increase performance in these conditions? Would a shroud that covers the perimeter of the sensor prevent ambient light from obscuring the data? Also, the measurements would be taken parallel t

Hello. I use lsm303agr. It have mag and acc. Mag works well, but acc data always read wrong.

Hi, for a project, I have designed a PCB with the component LPS25HBT. We want to know if there are some technical recommendations about the sensor's boundary conditions.Will we have to design the cover with some distance between the sensor and the boundary? Some distance or relative distance between the sensor and the cover?If the PCB is embedded in resin must have a minimum distance between the sensor and the resin.Thanks in advance!

We have a project using the H3LIS331DL in a remote control to determine whether it has been dropped. One of the versions uses both INT1 and INT2 connections. The INT2 connection is used to turn a power supply on, which wakes up the micro (if it's not already awake because of the direct INT1 connection).I've chosen to use the ST driver code.Both INTs are configured identically.The problem is that when I put the unit in low-power mode and set the accelerometer into Wake-To-Sleep mode, the accelerometer will wait for a period and then start putting out pulses of about 60 microseconds, spaced about 750 microseconds apart.There's quite a bit of variation (about 0.4G) in the reported values on each axis while it's sitting on my desk, but I only really care about peaks.Here's my initialisation code (note that bIntThreshold is set to the equivalent of 10G, and seems to work correctly:// Make sure the accele