MEMS (sensors)

Hi team,i'm using STEVAL-MKBOXPRO and want to reprogram its BlueNRG-LP chip.ST provides the original.bin files in STSW-MKBOXPRO-FS.Two .bin files provided in this SW are, SensorTile.boxPRO.bin for the MCU and dtm.bin for the BlueNRG-LP.My question is simple: where can i found the c/c++ code (projects) of these 2 bin files ?So as to change some configurations ...I'll appreciate some help from STM team.Regards, Christian

we are using LSM6DSV16x sensor with nrf5340 dk board , wea are getting values like this ACC[mg]:x:-157.50,y:-30.74,z:981.00GYRO[mdps]:x:-700.00,y:-140.00,z:420.00,please help in calbration to get accurate values of  sensor .

Hi, I understand IKS01A2 is not supported anymore in the current AlgoBuilder software versionIs it still possible to download the last AlgoBuilder version that supports this board ?I can only download the latest version from the website (no older versions).Thanks

Hii, I am using the LSM6DSM imu sensor module . To integrate the driver i followed the link:-https://github.com/STMicroelectronics/st-mems-android-linux-drivers-iiomy device tree modifications looks like this: &i2c3 {     clock-frequency = <400000>;     pinctrl-names = "default", "gpio";     pinctrl-0 = <&pinctrl_i2c3>;     //pinctrl-1 = <&pinctrl_i2c3_gpio>;     sda-gpios = <&gpio5 19 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;     scl-gpios = <&gpi

I am using IIS3DWB for machine condition monitoring product development project.I am using the below integration for velocity conversion as per MotionSP but unable to estimate speed RMS (not even 50% closer to the reference values).----------------------MotionSP_TD_SpeedEvalFromCircBuff - perform a speed estimation using a numerical integration method (Trapezoidal Rule) on the acceleration values Formula used:           /* vi = vi-1 +[(1-GAMMA)*DELTA_T]*ai-1 + (GAMMA*DELTA_T)*ai (in mm/s) */---------------------What's best and accurate way to calculate speed from acceleration considering industrial application?ST's timely support would be much appreciated.

I've been trying to interface the STM32F407VET6 with the NRF24L01 modules, however after trying multiple boards modules and library's it still fails to work. im not sure the issue is with hardware as ive tried multiple modules and the black board has a slot designed for this type of module, moving the spi1 pins to SCK(PB3), MISO(PB4), MOSI(PB5) and CE(PB6) CS(PB7) IRQ(PB8), according to the schematics. Trying over the regular pins makes no difference either.  The two main library's i tried were found on github. i tried following the controllerstech tutorial for writing the library and tried the one on github but neither worked using. for the controllerstech lib i tried transmitting to a dummy address which kept returning 0..https://github.com/controllerstech/NRF24L01.git the baud ra

Hi, I am curretly using a Nucleo H503RB and the IKS02A1 expansion board in order to use the ISM330DHCX.I tried several way to use via STM32Cube IDE which is my goal as i want to use C language without success to see any sign of an i2c adress with an i2c scan code. When i used the Arduino ide with STM32Duino and the ISM330DHCX library it worked immediatly with the wire library i2c default instance. What am i doing wrong in stm32cube ide ? int main(void){  HAL_Init(); /* USER CODE BEGIN Init */ /* USER CODE END Init */ /* Configure the system clock */SystemClock_Config(); /* USER CODE BEGIN

Hi,I am trying to use the BLE (SPBTLE-1S chip) on my STEVAL-STWINKT1 board. The idea was to use a project example from X-Cube-BLE2 with the following configuration :HCI_TL : BasicHCI_TL_Interface : UserBoardApplication : SampleAppI used the SPI2 to communicate with SPBTLE-1S.However, I can't communicate with the BLE, the void MX_BlueNRG_MS_Init(void) fails. The function tBleStatus aci_hal_read_config_data(uint8_t offset, uint16_t data_len, uint8_t *data_len_out_p, uint8_t *data) returns BLE_STATUS_TIMEOUT.Maybe an issue with the clock or/and the spi configurations? Or something else?I would really appreciate your help.Thanks.

I am thinking of powering the IIS2DLPCTR accelerometer VDD rail from a buck converter and wanted to understand if this part uses an internal LDO to step the VDD voltage down to power the internal MEMS block and ADC? Or does it use the supplied VDD directly for this? Trying to decide if it’s necessary to use an external LDO on the VDD rail or if a buck with its ripple voltage will not impact performance. 

When I connnect sensorTile.box from App.the followign msg poped ip continuously. and no fucntion work properlywhat is the reason. I upgraded the FW on FOTA  at the first connection.what is the suggestion ?Thanks!Forest  

Can anyone provide a documentation over integration custom ml algorithm in ISPU.If I have a machine learning model like tflite or onnx how can I deploy it in ISPU

Trying to get the lowest power out of this device, but it seems to draw at least 900uA of current when even the accel and gyro are disabled. Any suggestions on how to get the current draw of this device lower? Here's my setup:Custom PCBnormal current draw without IMU 0.1mAnormal current draw with IMU and below settings: 1mAConnections4-wire SPI bus w/ CS (shared with other IC with separate CS)pins 2, 3, 6, 7 GNDpins 5, 8 to 3.3Vall others NCFirmwareIMU gets turned on with ODR 12.5 for accelerometer and gyroI2C gets disabled for SPI onlyAccel and Gyro power mode set to 1 (HP off)a few samples are readIMU ODR set to 0 for accel and gyroread accel and gyro values onceGo to sleep (1mA current draw)I can confirm that by removing the IMU the current drops to the expected 0.1mA. Any ideas as to why it's co

I'm trying to make a demo with the ispu chip ism330is and the STEVAL-MKBOXPRO the issue is I can't find a suitable firmware for the tilebox pro that is compatible with the ispu and allows me upload the compiled UCF program into the chip. Below is a screenshot of the current firmware I'm using FPSNS DATALOG 2 in which it shows the ispu as unknown and if I try to upload the UCF it's just gets stuck! 

Hi, I noticed that, on MEMS Studio, whenever a block is repeated inside a subdesign it gives an error when building. As an example to represent this, I've created a subdesign "A" where I input the acceleration sensor of a X-NUCLEO IKS01A3 and i output the results in a graph as shown in the next image.The subdesign "A" uses a demux, adds to every output its current value with the previous one and mux it back again.

Hello, I'm learning how to use stm32 hardware and how to program it and today i connect the X-NUCLEO-IKO1A2 to my board (Nucleo-GO71RB) and installed the inucleo software,  i did everythink like te st video said, but for some reason the software doesn't detect the sensors board, someone have some advices or warnings to give me?

Hi all,Could you show me the temperature accuracy of LIS3MDL ?Thanks all,

Hello experts,I am using rock chip board with android 12 on it along with the sensor lsm6dsox connected on i2c2.I have added the driver and compile the Linux and then build android images.After booting I can see device is detected on i2c and probed successfully, now when I tried to get the same sensors list at android level I get 0 sensor device listed.below are the probe logsrk3568_s:/ # logcat | grep lsm01-01 12:00:00.830 0 0 I st_lsm6dsox_i2c 2-006b: Linked as a consumer to regulator.1701-01 12:00:00.831 0 0 I st_lsm6dsox_i2c 2-006b: Freq Fine -262 (ts 25262)01-01 12:00:03.552 0 0 I st_lsm6dsox_i2c 2-006b: MLC loaded (1) MLC 1 FSM 0001-01 12:00:03.556 0 0 I st_lsm6dsox_i2c 2-006b: Device probedAfter checking online I get below link from support team

Hi,we have designed a custom board that includes a STHS34PF80 but after triggering a one-shot acquisition, the DRDY bit is never set and reading from the TOBJECT_x and TAMBIENT_x registers without waiting for DRDY only returns 0. We are interfacing the sensor using I2C from an nRF52 SoC.Implemented procedure:Powering up the sensor (+ wait for 500 ms)Enabling block data update (Reg: 0x20, Data: 0x10)Triggering Acquisition (Reg: 0x21, Data: 0x01)Waiting for DRDY bit to be set (Reg: 0x23), Alternatively: Wait 25 ms and reading registers 0x26-0x29 directlyThe sensor ACKs the data transfers so I assume that in terms of the hardware everything is fine, WHO_AM_I (0x0F) correctly returns 0xD3.Am I missing something?Thank you very much in advance!   

Hello,First forum post so I apologise if I miss any key information. I'm trying to use NUCLEO-G474RE to test out the functionality of MotionAC using CubeMX to generate the program structure and Clion to edit it. All I am doing right now is trying to call:MotionAC_Initialize(1); However I get back that:undefined reference to `MotionAC_Initialize'This lead me to add the following to the CMake file, which I feel like I should not have to, is the CMake file generated by Clion or CubeMX? (a very basic question I know but I'm new to this) It's also of note that I enabled hardware floating point in the make file as well.target_link_libraries(${PROJECT_NAME}.elf ${CMAKE_SOURCE_DIR}/Middlewares/ST/STM32_MotionAC_Library/Lib/MotionAC_CM4F_wc32_ot_hard.a)  After adding that line it pulls in the .a file (I'm working on macOS) it sea

我想知道LIS3DH的三种工作模式是什么？我收到了两份文件，一份是高分辨率模式、正常模式和低功耗模式，另一份是关机模式、正常模式和低功耗模式。我比较了两种模式的寄存器配置。低功耗模式相同，第一个数据中的高分辨率模式与第二个数据中的正常模式相对应。你能给我一个关于这个问题的具体解释吗？

Hi @Federica Bossi , I have a question about timestamp and the external sensor event.According to the application note of LSM6DSO (image above), timestamp's register is written when main sensor or external sensor event occurs. I have no problem with main sensor event because it seems like the timestamp register is written when the new data from accelerometer and gyroscope is ready to be read. However, I am unclear about the external sensor event since I wouldn't directly be polling data from the external sensor but through LSM6DSO's sensor hub.My questio

Hello,I am using a I3G4250D gyroscope and would like read the temperature. Currently, I read 246 (in decimal) in my register 0x26.In two's complement, it is equivalent to -9.   Then I have to multiply by -1 so -9 * -1 = 9°C (I am not sure)But It is the summer, and 9°C for a measure of tempe

I have added Digital Inclinometer application of X-Cube-MEMS1(9.6.0) on stm32f777zit6 wherein I want to read the rotation(angle) from LSM6DSL device. I have added all the required component files and Motion_DI library to the workspace.Reference taken from: X-Cube-MEMS1>>9.6.0>>Projects>>Nucleo_F401RE>>Application>>IKS01A2>>DigitalInclinometer I am successfully able to configure the LSM6DSL with i2c1 of stm32f777zit6 and able to read the "who am i".But my MotionDI library is not getting initialised. During debug, my code gets stuck at function MotionDI_manager_init((int)ALGO_FREQ);.  Code is not working after this.Kindly suggest what can be the issue?? RegardsALPS  

would you please help to review the attached log and give some advice to customer?Thanks.Attached is the test log data, test conditions:1. The device is fixed on the desktop without moving or shaking. 2.2. The CPU reads the X/Y/Z data of the Sensor via I2C, and found that the X-axis data is decreasing, but the Y/Z data does not change in a wide range. 3.3. CPU platform: RV11264. Kernel version: linux 4.19, the kernel is a little change: linux is used in version 4.19, because in the L4.19 kernel to read the data also has anomalies, the customer ported the L5.10 version of the lsm6ds3tr-c driver.[root@RV1126_RV1109:/userdata]# . /test.sh[0] accel: -714 -1780 -16310 anglvel: 83 -438 -118[1] accel: -718 -1781 -16323 anglvel: 84 -437 -121[2] accel: -719 -1781 -16317 anglvel: 85 -437 -118[3] accel: -727 -1783 -16320 anglvel: 80 -438 -116[4] accel: -727 -1783 -16317 anglvel: 83 -437 -119[5] accel: -732 -1786 -16

I am measuring pressure using the LPS28DFW under conditions where the gas flow is approximately 70°C with a relative humidity of 80-100%. During measurement under these conditions, I encountered an issue where the sensor stops working. However, the sensor resumes normal operation once it is sufficiently dried. According to the datasheet, the sensor is expected to function under these conditions, but it currently does not. I would like to inquire about the possible reasons for this issue.Even in the presence of liquid droplets, the gel should prevent these droplets from reaching the MEMS, allowing it to function normally, but this is not happening. Could it be that the protective gel on the MEMS is leaking or detaching under these conditions?