MEMS (sensors)

Setup- Mikroe LSM6DSL Click on Microchip PIC24F Curiosity Board, Salaea Logic I2C protocol analyzer. Yes I use a wrist strap, ESD mat, and grounded Weller soldering iron. Why didn't ST use rounding in their Accel Self-Test? Should I?

Hello, in 2021 I developed a Zephyr 2.6.0 based app which interfaces with STMicro's IIS2DH accelerometer. During development stages I was able to talk more directly to this sensor through Zephyr's I2C API, by passing the following member of a valid IIS2DH device pointer: device->data->bus. This reflects STMicro's Zephyr driver code, as found in `zephyr/drivers/sensor/iis2dh/iis2dh.h`, both in Zephyr 2.6.0 and more recently released Zephyr 3.1.0. New features and bug fixes as of 2022 compel my team to move forward to use Zephyr 3.2.0, where I have recently encountered non-trivial rewrite of the IIS2DH sensor data structures in `zephyr/drivers/sensor/iis2dh/iis2dh.h`. I've adjusted my app side code accordingly, but have run into a subtle issue where, as soon as I make a reference to compile iis2dh.h and related sources, the test h t t p s ://github.com/zephyrproject-rtos/zephyr/blob/main/drivers/sensor/iis2dh/iis2dh.h#L49 returns false, and my device pointer thus lacks an i2c data

..

..

Facing an issue with respect to 6D orientation detections on LIS3DH. Both, 6D position and 6D movement gets triggered only at 1G. Threshold register doesn't seem to have any influence on the 6D orientation. For, 4D the detection happens exactly at the set threshold.The following are the settings used for 6D position detectionINT1_CFG is 0xEA % AOI - 1; 6D -1; X,Y and Z enabledINT1_THS is 0xA %1.5m/s^2 as thresholdINT1_DUR is 0x78 %0.3 seconds duration for ODR 400Hz CTRL5 is 0x00 %Disable 4DAs a hack, I enabled 4D bit of CTRL5 so that X and Y detections of 6D happens at the set threshold. But, the Z-axis is still not affected by this hack. Z-axis 6d position detection gets triggered only at 1g and -1g.Any suggestions how to solve this?

We read the temperature from the sensor in LIS2DH12. We tried two devices and both read 5..6degC lower than the actual temperature. The offset seems quite consistent in the range of our interest (between 0 and 50degC). The supply voltage is 3.3V.Obviously, we want a better temperature accuracy: +/-1degC is the maxBecause of that, we'd like to ask you a few questions:The datasheet says that the temperature sensor is calibrated in the factory at 2.5V. Can that inaccuracy be the result of a different voltage supply?Can we calibrate this offset in a separate micro?Can we expect that once we calibrate this offset in production, this offset stays unchanged over time?Is it a chance that if we calibrate the temperature sensor at 20degC, the offset at other temperatures will be different? So we have to calibrate it using more than one point?Can you offer another accelerometer that has a more accurate temperature sensor in a similar package?Best regards,Alexey

Hi,I am using a XIAO BLE Sense Board that uses an nRF52840 MCU and an LSM6DS3TC-R connected via I2C. The original bootloader from Seeed works fine with their library for the gyro sensor and I am now trying to develop my own with the nRF5 SDK.At the moment I have issues with the I2C connection, so the sensor works fine when powering the device on most of the time, but in some cases it is unpredictably not answering on the I2C bus when reading/writing to the sensor (read WHO_AM_I as the first transmission). I think no ACK is sent after the adress or after the first byte of data (the subaddress), but I cannot confirm that because the Pins of neither the MCU nor the gyro sensor are accessible on the breakout board for an oscilloscope.Is it possible that the gyro sensor needs some kind of I2C reset or some kind of SDA/SCL push pull sequence that it starts responding again? Or do I need to unpower it for a few ms to reset everything maybe?Thanks in advance and best regards!

..

Im getting the roll and pitch changed. The correct direction of the roll is the x-axis and the pitch is the y-axis? 

Hi,Because of internal pullups on several st accs I changed it with this acc and, now I have a problem with sleep-state or sleep-state-ia bits in wake_up_src or state or state_dup regisers. This bits after the sleep duration doesn't give a response or gives unstable response which I couldn't understand. I tried directly same codes on github also on application note and also with my settings but results are the same. Example init sequence is below.void acc_init_sequence(void) { lis2ds12_pin_int1_route_t int1_route; dev_ctx.write_reg = platform_write; dev_ctx.read_reg = platform_read; dev_ctx.handle = SPI1; systick_delay_ms(k_BOOT_TIME); lis2ds12_device_id_get(&dev_ctx, &whoamI); if (whoamI != LIS2DS12_ID) while (1);   /* Restore default configuration */ lis2ds12_reset_set(&dev_ctx, PROPERTY_ENABLE);   do { lis2ds12_reset_get(&dev_ctx, &rst); } while (rst); // /* Start device configuration. */ // lis2ds12_i2c_interface_set(&dev_ctx,

(LSM6DSL) I want to know why raw data(angular rate) is multiplied by sensitivity.Multiply the angular velocity(gyro raw data) by sensitivity and it becomes mdps, what exactly is mdps?float_t lsm6dsl_from_fs500dps_to_mdps(int16_t lsb){  return ((float_t)lsb * 17.50f);}

Hello,I am working with STEVAL-MKI197V1 to evaluate the steps detected by the pedometer.By looking at the documentation, I found out that the pedometer can be better configured by using the UNICO GUI. At the moment, I do not have the STEVAL-MKI109V3 motherboard, but I read that the Regression Tool can be used offline with custom data written in a specific format.Therefore, I tried to use the regression tool with a simple txt file ('test_steps50.txt') containing the following data:A_X [mg] A_Y [mg] A_Z [mg] 251 900 -119 259 907 -132 271 907 -145 276 904 -162 280 915 -166 263 908 -163 260 882 -171 225 869 -165 224 863 -181 228 860 -210   *Data are spaced with tabsIf I choose the folder containing this file and the output directory, after running the tool I do not get any configuration file (.ucf). The only file I get is the 'regression_tool.config' file in a different path with respect to the output directory defined in the UNICO GUI. However, this file is just telling me some d

Hi community,I'm using a LIS3DH MEMS on our propriety board with a ST32L476 MCU.When trying to read x, y, z, channels I get correct data for y and z, but x (Registers 0x28 and 0x29) always return 0x80 0x80.Sometimes after power up the board, all three channels work as expected!The behaviour is the same with SPI or I2C interface.I made a dump of all registers to see the configuration:SELFTEST OK, all channels are readable.Reg: 0x7 = 0xFFReg: 0x8 = 0x0Reg: 0x9 = 0x0Reg: 0xA = 0x0Reg: 0xB = 0x0Reg: 0xC = 0x0Reg: 0xD = 0x0Reg: 0xE = 0x0Reg: 0xF = 0x33Reg: 0x10 = 0x9CReg: 0x11 = 0xBReg: 0x12 = 0x90Reg: 0x13 = 0x31Reg: 0x14 = 0xB1Reg: 0x15 = 0x33Reg: 0x16 = 0x1CReg: 0x17 = 0x24Reg: 0x18 = 0x28Reg: 0x19 = 0x9EReg: 0x1A = 0x70Reg: 0x1B = 0x75Reg: 0x1C = 0xC0Reg: 0x1D = 0x0Reg: 0x1E = 0x10Reg: 0x1F = 0x0Reg: 0x20 = 0x27Reg: 0x21 = 0x0Reg: 0x22 = 0x0Reg: 0x23 = 0x0Reg: 0x24 = 0x0Reg: 0x25 = 0x0Reg: 0x26 = 0x0Reg: 0x27 = 0xFFReg: 0x28 = 0x0Reg: 0x29 = 0x3Reg: 0x2A = 0x80Reg: 0x2B = 0xFFReg: 0x2C

Hi, I'm currently trying to determine the bandwidth which should be used for different output data rate setting for the gyroscopes on this IMU.The datasheet specifies the exact bandwidth for the accelerometer for different settings as ODR/2, ODR/4 ect. But unfortunately, the same table isn't available for the gyroscope.Please let me know if I'm missing something obvious.Thank you for your help.Jacob

Questions for the IIS3DWBTR:But as I mentioned in my other post and repeated here, I don't care about getting the data out at high sample rates. I'm just using the interrupts for thresholds and want to use this part because it has a higher bandwidth for detection.In I2C mode for the IIS3DWB device the datasheet says it only support single axis mode because I2C is too slow to get the data. I want to use I2C mode to configure either wake up or activity thresholds for all 3 axis and then configure the interrupts to tell me those thresholds were exceeded. I don't need the data.So the questions are In I2C mode:Are all the axes still active?Can I access all the registers in I2C mode to configure the thresholds for all axes of the device for the interrupts?Can I effectively get two thresholds for each axis if I use one set of thresholds for wake up configured on INT1 pin and another set of thresholds for activity configured on INT2 pin?What is the max rate of the I2C interface?

i would like to output my sensor data by USB, it seems that is it places into a .dat file but how is it encoded ? or it is possible to get the value directly?

Do I need to install any application on my PC? Right now I am using STBle on my android phone.

For my thesis, I need a pressure sensor for air with water vapor and scattered water droplet. The pressure ranges from 100 to 300kPa.abs and the temperature from -30 to 70℃.After searching your website, I find two potential pressure sensors, namely LPS28DFW and LPS22QS.My question is as follows:1. The LPS28DFW uses water-resistant package. What is the depth from the surface of the gel-filled through hole to the surface of the inlet of the through hole? The depth determines the available gas volume of the through hole and this is what I actually care about. In my situation, the smaller the available gas volume, the better. It would be better if you can tell me the amount of the available gas volume.2. Whether the LPS22QS is applicable to the situation of air with water vapor and scattered water droplet? I find that in the datasheet, the LPS22QS is applicable to gas and water metering. I am confused with this.

Could I get a value of Thermal Resistance for the sensor ISM330DLCTR?

When I connect the sensortile.box to the ST BLE Sensor App, it automatically prompts me to upgrade the sensortile.box's firmware to v349.bin.As I asked before, if the firmware of the sensor tile.box is upgraded to v3.4.9, the data from the accelerometer cannot be read properly. Vibration monitor demo app does not run properly also..As a result of inquiring on the ST community site, ST saids that the firmware of the sensor tile.box will be upgraded to v3.4.10 soon.I hope that all these problems will be cleared if I upgrade the firmware of the sensor tile.box FW to v3.4.10.By the way, when will the firmware v3.4.10 will be released?

Dear Sir, After performing IMU MLC training process by UNICO GUI and coming out training data, .ucf, please advise us where to add the training data, .ucf into our ST IMU sensor driver and where to add detection flow into our IMU sensor once the gesture is detected. We will apply ST IMU sensor, LSM6DSOX which is support MLC.Thanks.Mike / mike.sun@quantatw.com

..

When testing the ST BLE SENSOR app and SensorTile.box pairing, can I disable the SensorTile.box firmware upgrade message popup in the ST BLE Sensor app?

helloi use STEVAL-MKI178V2 (adapter board) + STEVAL-MKI109V3 (motherboard) with UNICO-GUI ver9.13.i try "Absolute wrist tilt" example as it described in "AN5040 - Rev 3".The questions are:- in "A_WRIST_TILT_Mask (59h)" register, each bit by itself works fine. but if i use more than 1 axis (x and y, or y and z) - i got continuous interrupts (interrupt than latency time than interrupt ...). see attached picture- in "A_WRIST_TILT_Mask (59h)" register, for each axis i got absolutely same behavior for positive and negative tilt.please adviceAlexander