MEMS and sensors

Hello!  First I would like to state my issue:  1. My software cannot connect to the LSM6DSO IMU sensor.   A little background on my project is that I am trying to use the IMU sensor to provide accelerometer readings in x, y, and z directions. I purchased a breakout board from Sparkfun that uses the LSM6DSO to test the sensor first with my Arduino-compatible controller via SPI communication. This proved that it works.  We then created our own design and referenced the way Sparkfun wired the LSM6DSO. Now when I run the program on the new board, the sensor doesn't work.  I looked into the library that Sparkfun uses for programming in Arduino and I see that it cannot connect to the IMU sensor. In the library I can see where it fails and it fails when checking the part ID. I keep getting a part ID of 255 which is 0xFF. I should be getting a part ID of 108 or 0x6C. Any ideas on what I can do to make it work?       uint8_t partID; re

I'm using the full API for the VL53L1 ToF sensor. The project is pretty simple as I'm using 4 sensor to measure distance connected on an I2C of an STM32F091.I'm optimizing the code and I'm come across the VL53L1X ULD API (Ultra Lite Driver Application Programming Interface) STSW-IMG009.From what I'm seeing most of the function I'm using:VL53L1_StartMeasurementVL53L1_GetMeasurementDataReadyVL53L1_GetRangingMeasurementDataVL53L1_ClearInterruptAndStartMeasurementXNUCLEO53L1A1_ResetIdVL53L1_SetDeviceAddressVL53L1_WaitDeviceBootedVL53L1_DataInitVL53L1_StaticInitVL53L1_SetDistanceModeVL53L1_SetMeasurementTimingBudgetMicroSecondsVL53L1_SetInterMeasurementPeriodMilliSecondsCould be replaced with the ones available in the ULD API.The only thing I can't understand is how to edit the Dev structure. I'm currently usingDev->I2cHandle = &hi2c2;Dev->comms_speed_khz = 100; //400Dev->comms_type = 1;Dev->I2cDevAddr = 0x52; // default ToF sensor I2C addressFrom what I'

Hi,We are working with the LPS22DF pressure sensor to be used in our device adapting a 3.3V system and have encountered issues related to the interaction between VDD_IO, VDD, and the I²C bus. When VDD_IO and VDD are connected to the same 3.3V supply:The I²C bus behaves as expected. (No issues here)However, when we disconnect VDD_IO and VDD, while I2C is active to be used for other sensors to communicate, the sensor seems to backfeed through VDD_IO's internal pull-up to VDD, interfering with the I²C bus (e.g., pulling lines to ~1.5–1.6V). (this is our theory at least)When VDD_IO is powered but VDD is not:I²C communication is disrupted.The sensor seems to partially power itself through internal pull-ups, potentially backfeeding into VDD.In addition, CS pin will sometimes influence the I2C bus if its connected to HIGH.We have tested it using the evaluation kit and also on a breadboard. What we did was add a diode between VDD and VDD_IO to temporarily eliminate the issue. However, the

Hi, I am using MotionFX with BlueCoin, for a solution that can detect vertical movement within 2 meter range with high precision.  I took the ALLMEMS2 example when I logged linear acceleration and gravity, it showed some unprecise values likelinear acceleration around 0.2 when the device wasn't moving. When I increased the full scale factor for ACC to 16.0f and Gyro to 2000dps, the linear acceleration value improved to the range of 0.05-0.1, which is still not as expected. Gravity value is strangely too high and stable 9.99, shouldn't it be closer to 9.81 max in the stale state?  NFO:__main__:Linear Acc -> x: 0.0290, y: -0.0090, z: 0.0190 INFO:__main__:Gravity -> x: 0.0590, y: 0.0310, z: 9.9990 INFO:__main__:Linear Acc -> x: 0.0090, y: -0.0180, z: 0.0490 INFO:__main__:Gravity -> x: 0.0580, y: 0.0300, z: 9.9990 INFO:__main__:Linear Acc -> x: -0.0110, y: -0.0190, z: 0.0390 INFO:__main__:Gravity -> x: 0.0580, y: 0.0310, z: 9.9990 INFO:__main

Hello community,I have an application where I want to implement STHS34PF80 for detecting people PRESENCE and MOTION with a range of 3 to 4 meters. In the Datasheet it is stated that it is possible without using extra lenses. Although, I am struggling to find the best config to have a good recognition with more than 1,5m.- What would be the step-by-step to make the sensor run in 4 meters range?- Could someone give me an example config for THRESHOLD, HYSTERESIS, LPF, ODR and AVG?

FIFO_CTRL4 is 00A1 in hex , 10100001 in binary FIFO_CTRL3 is 00AA in hex , 10101010 in binary fifo_status1 is 00000000 fifo_status2 is 00100010 FIFO DATA OUT TAG IS 00100001   I have already set LSM6DSO like this but no data is inside the FIFO Must I open and close embedded function?  I saw someone 's reply in the community  riteRegister ( LSM6DSOX_FUNC_CFG_ACCESS, 0x80 ); //Open Embedded Functions WriteRegisterBit( LSM6DSOX_EMB_FUNC_EN_A, 3, true ); //Enable Pedometer sensor in Adv Func WriteRegister ( LSM6DSOX_EMB_FUNC_EN_B, 0x10); //Enable false positive rejection WriteRegisterBit( LSM6DSOX_EMB_FUNC_FIFO_CFG, 6, true ); //Enable Step Counter Batching WriteRegister ( LSM6DSOX_FUNC_CFG_ACCESS, 0x00); //Close Embedded Functions  

Hello,I am using MotionFX on STM32BlueCoin device. I tested values of linear_acceleration and gravity from MotionFX library, and I have very strange bias on produced values, although I try to feed perfect hardcoded data to the library.For example I always send MotionFX 6X input data as following, Accelerometer x=0, y=0,z=-9.81, Gyro x=y=z=0In return, I have strange values on the gravity axis. INFO:__main__:Gravity -> x: 0.0000, y: 0.0000, z: -10.0000 INFO:__main__:Linear Acc -> x: 0.0000, y: 0.0000, z: -0.1890 INFO:__main__:Gravity -> x: 0.0000, y: 0.0000, z: -10.0000 INFO:__main__:Linear Acc -> x: 0.0000, y: 0.0000, z: -0.1890 INFO:__main__:Gravity -> x: 0.0000, y: 0.0000, z: -10.0000 INFO:__main__:Linear Acc -> x: 0.0000, y: 0.0000, z: -0.1890  Why is gravity Z always 10? Shouldn't it be 9.81 in perfect condition? Why linear_acceleration have this strange value of -0.189?I tried to change many knobs parameters, but I couldn't even change it a bit.

Hi,I am developing a product that can be installed in either a horizontal or vertical orientation and uses the LIS3MDL as the source for a compass..The PCB is common so the LIS3MDL will be in one of 2 orientations.In a horizontal position everything is fine and I get the readings expected.In vertical orientation it is not working.My assumption was that the axes X,Y,Z were just names and that the data from each axis was relevant to that axis and that the data obtained would relate to the plane that axis was on.It seems this is incorrect. I have run a test and see that the range of values (max-min) on each axis is very different, particularly on the Z axis.Moving the sensor through 360 degrees on each axis I am getting X -59 to 25, Y -36 to 46, Z -86 to 0I assumed I would get the same min to max for each axis.So can the sensor be used in a vertical orientation? I need the Z axis facing forward (to replace X) and X axis facing left (to replace Y).

Hi,  I want to detect a shock  with the H3LIS331DL and its interrupt on threshold level. I used it in normal mode and an ODR of 1000Hz. The shock in my testbanch is : I want to know what is the minimum of time when the duration is setup to 0 with my ODR to set interrupt signal.What is the answer of the sensor when the shock is an high frequency one...There is few information about the bandwidth of the sensor or about its transfer function in its datasheet or application note.Thanks for your help   

Hello, I'm using the LIS2DW12 on my own board.Consumption seems a little high to me. In the datasheet I found a value around 5.5µA and I obtained rather 45µA.The configuration is as follows:- ODR 50Hz- FIFO in continious mode with INT1 enabled- Full-scale 4g- 14 bits resolution in LP2.I did not find any information regarding consumption in FIFO mode. Can you give me some information?Thanks

Hi ST,Using the vl53l1x in our devices we are finding some cases of unexplained sensor distance changes.  Large changes. We use the sensor in a contained/controlled environment.  A bin -- the sensor is used to measure distance to items contained in the bin.We have seen some cases where the sensor behaves normally and then,  unexplained,  it spikes way up.  From 100mm to 2meters  measurements for instance. Powering off and powering on brings it back to normal.We are unsure where to start looking here so wanted to ask first here.  What might be possible causes of this?Thanks,Will  

The device does not output the data in a sudden. And it has no effect to press the RESET button. When I try to re-flash the board, the available memory of the flash only remains 8KB. Even the total memory is only shown as 32KB on PC, much less than the normal size which is 512KB. So I cannot copy the BIN to the flash according to the USER-MANUAL as usual. How to fix this?

Hello,I am using STEVAL-STWINKT1B development board and I can write and read sd card using setting to SD 4 bits Wide Bus and FATFS.If I add on STM32CUBEMX as middleware FREERTOS I can't read the SD in fact I get back FR_NOT_READY when I execute the f_open method.How can I solve this problem?

Hi, I'm trying to decipher the inner workings of the fsm configuration on this sensor. While the an5904 application note features an example of configuration on page 42, things take a turn after the 21st step. The following step selects page 2, and I can't find a description of the page contents anywhere. The only available description of the embedded advanced features pages is for page 0 in the data sheet. 

Hi, We have a board featuring 5 VL6180X sensors and I noticed some oddities regarding the initial offset and scale in the latest production run:Some sensors are unable to measure any distance below 15mmThe ranging linearity between different sensors is +/- 10mm (taken as the delta between a 20mm and a 68mm measurement to a matte aluminium plate).Initial offset is varying +/- 10mm The initial offset appears to be roughly in spec with the datasheet (Table 18. Ranging specification), although we have quite a few sensors at the maximum offset (and in the datasheet this is after 3 reflow cycles, we only have 1).The linearity is far worse than what I see in "Figure 6. Typical ranging performance".The largest issue for us is the inability to measure below 15mm. Some sensors simply register 0mm (4 boards out of a batch of 30 had this issue).I was wondering if this is the expected behavior of the sensors, or if we're doing something wrong in our design/production?Regards,SytseFYI, our

Hello,  How many mechanical shock support the LSM303AH please ? and if uou have others reference of inclinometers thanks to give me informations. Thank you

Dear, Could you tell me if FS signal have internally pull up or pull down?   Regards

Hi!I've since given up on utilizing VL53L1X for liquid level measurement. @John E KVAM had previously reccomended me to use instead the VL53L4CD sensor for this sort of application (small recipients with water), and I plan to ship it next week. But I've also read about VL53L5CX which has the advantage of reading liquid level even when angled at about 15° due to its wider FoV.Is there any other ToF sensor that should perform well for this kind of scenario that I'm not aware of? Even if being overall worse but having an specific advantage like VL53L5CX.Thanks in advance!Edit: I've noticed now that the VL53L4CD is out of stock on both stores I could ship from, but VL53L4CX is available. From this forum post, I gathered that I can run the ...CD software on the ...CX, but do they have any other difference besides processing power?

Hello ST team.I am operating the VL53L1CB sensor with zephyrRTOS, I reach distances to four meters without problems, in addition to measure distance above them (eight meters top in ideal conditions), all this in ROI.I am working with the manual UM2133 and I have doubts about the calibration, I have a crystal covers (bought by aliexpress) and I did the calibration proposed by the manual, it has some crosstalk interference, it works with intermediate accuracy and precision.Do you have any manual that explains in more detail about the calibration (refSPAD, crosstalk, offset)? especially the point “6.2.6 Setting crosstalk calibration data” that makes in detail the parameters and how it affects the sensor.The purpose is to improve accuracy and precisionBest regardsThanks!

Hello, I'm currently working on a project with a VL53L8X sensor.When I installed this product on the ceiling, the data of adults passing by is well observed, but the data of children passing by is not. I understand that this is a physical limitation that comes from the 8by8 array.Is there a software solution to this?Thank you

I have 5 VL53L8CX on the same I2C bus.I need to set the LPn pin HIGH of the sensor I want to change address.But the problem is that I can also change the address when LPn pin is low as well.Also I also don't know how to scan I2C addresses in only one sensor when all other also reply as well even though only one sensor has LPn pin set to HIGH.Can I not disable I2C with the LPn pin or am I missing something?LPn pin datasheet:Enables communication. Drive this pin to logic 0to disable the I²C communication. Drive this pinto logic 1 to enable the I²C communication. Thispin is typically used when you need to changethe I²C address in multidevice systems. 

I am trying to use Satel VL53L8 Cx over Arduino due . The library I am using is stm32duino VL53l8cx but I never get any result .Connections were as per the expamples but it did not work.Is there a library I can use for this . I have earlier used VL53l5 but that never created an issue

Hi Everyone,I'm using STM32L4 with LSM6DSM on IAR IDE and using motion AC library to calibrate the accelerometer data. Code flow is like in first position when it has got the 500 samples for one position then it will wait till you rotate the position and when it is in next position again it will take sample for that position. The problem is, If I kept the device for longer time in one position only then lets say 2 min then sensors doesn't get calibrate, not able to understand what can be the reason.Because I'm not able to find out is there any timeout or any buffer overflow is happening. 

I hope someone can help me with the accuracy of my VL53L1 sensor. I can’t get the sensor working accurately above 40cm. I am working on a hobby project and want to use the sensor to avoid obstacles. The board I use is not an VL53L1-SATEL. It’s from an other manufacturer. I tried different api’s. The most recent full api and the ULD from ST. I even tried the Adafruit api for this sensor. All the api’s are producing more or less the same results. Is there something I could test to figure out what’s going on? 

Does anybody know where do I get the .a library for LSM303AGR on ambiq apollo4blue plus platform which contains following feature.Acc Data + Mag Data -> AzimuthMag Data Calibrationnote:I am currently using this two library, but it doesnt work well and I have been tring to find the referrence about this two lib but I can not find any as well.