MEMS (sensors)

I am using LSM6DS3. I got very strange values of gyroscope and accelerometer. I save some data of gyroscope at static position and figures of gyroscope data at static position is attached. Does LSM6DS3 needs calibration? Or we don't need to celebrate the LSMDS3? It is very difficult to arrange rotation table by calibration and sometime impossible?

Tried redoing the project several times - other labs seem to work

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.

Hello everybody. I just joined and would like advice on my problem. i have an IKS01A1 Multisensor board. i would like to connect it to a rasberry pi 3+ machine. I just can't find instructions anywhere. That is, how to make GPIO connections and where to get the necessary program for Rasberry (drivers etc), i.e. where to get the whole package. Are there any sensor programs encoded in Python. I am trying to build a sensor on the flexible fork of my bike.Thanks in advanceMika Aro

While measuring the distance of an obstacle using VL53L1X ( https://www.st.com/en/imaging-and-photonics-solutions/vl53l1x.html ) the result is fluctuating. This was tested with the breakout board ( https://www.st.com/en/evaluation-tools/vl53l1x-satel.html ). Example of the test conducted: We have set the fixed obstacle at a distance of 140 mm from the sensing unit. Case 1: Setting: Ranging: Autonomous , Distance Mode: Short , Timing Budget: 50ms , Inter measurement period: 50ms.Result: Varies in the range 138-144 mmCase 2: Setting: Ranging: Autonomous , Distance Mode: Short , Timing Budget: 500ms , Inter measurement period: 50ms.Result: Varies in the range 139-141 mmWhy the variation is observed for the tightly fixed obstacle (non varying distance) in these kind of sensors? What is the physics behind it (measurement fluctuation reason)? Please help me with the technical explanation.With regards,Bhaskar Ghosh

Hi,I modified the example program "Data Log Fusion" to calculate the position by integrating twice the linear acceleration. However, there is an error on linear acceleration that is very consistent both when the board is moving and the board is stationary. I read that ATime, MTime and FrTime are the parameters which most influence the behaviour of the MotionFX algorithm. Is there a method to set those parameters properly? I use Nucleo-L476RG with X-NUCLEO-IKS01A2.Waiting for a reply.Thanks,Marco Perciavalle

..

We use two types of sensors for our dev: lsm6dso and lsm6dsox. It is necessary to detect the type of sensor SW (without opening the device). And it's difficult, because adress (we use i2c) is the same, Device Identification (Who am I) is the same for LSM6DSO and LSM6DSOX... and i can't imagine how to easy to detect it

Free massive open online course (MOOC) with hands-on exercisesLearn to design with ST's newest and most advanced motion and environmental sensors with an easy-to-use STM32Cube development ecosystem.This free, self-paced video course features hands-on exercises designed to increase your knowledge of sensors and provide practical instruction on how to develop sensor applications using the STM32Cube hardware and software development ecosystem.Who should take this courseEngineers who wish to gain quick proficiency with motion and environmental sensors, and are looking for a user-friendly development toolset to accelerate and simplify their sensor designs. For more information visit the page click here. You will learnThe key features and capabilities of the most advanced motion and environmental sensors on the marketHow to start a new sensor project quickly and easily using the STM32Cube development ecosystemHow to use the ecosystem software to set up sensors, log sensor data, optimize sens

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 the data inside the structure VL53LX_CalibrationData_t, in particular inside its sub-structure VL53LX_customer_nvm_ma

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; } buf9[0] = WIA; ret9 = HAL_I2C_Master_Transmit(&hi2c1, ADDR, buf9, 1, HAL_MAX_DELAY); if (ret9 != HAL_OK) { strcpy((char*)buf9, "Error Tx\r\n"); } else{ ret9 = HAL_I2C_Master_Receive(&hi2c1, ADDR, buf9, 2, HAL_MAX_DELAY); if (ret9 != HAL_OK ) {&nbs

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 see that the cause of the interrupt was Wake-up event(W

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, whi

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.