MEMS and sensors

Further to this earlier post, any chance now is a BMA400 SPI library already ported to STM32CubeIDE?Many thanks

Hello, We've been developing a tank level monitoring system using these sensors: VL53L4CD (18° FoV)VL53L3CX (25° FoV, multitarget)VL53L4CX (18° FoV, multiobject, multitarget) First question is the definitions and distinctions between the terms multizone, multitarget, and multiobject. We couldn't get a clear information about these on the datasheets.Secondly, we are just using example libraries to get measurements. We are still discovering how to filter the readings that are not within the central zone. We've made a spreadsheet that we'll be happy to share privately. It shows the minimum tank diameter and the maximum tank depth that won't cause signal bouncing around the inner walls.Thank you. 

Hi there,   I read this document and it mentioned that the function "vl53l8cx_set_VHV_repeat_count" can be used to compensate for the ranging error caused by temperature. I would like to know the principle of VHV calibration compensation. Is it related to the signal power of VCSEL?   Does VHV calibration also apply to the compensation mechanism at low voltage (2.5~3V)? Or are there other functions that can compensate for voltage drift?  

I am using the STM driver to control the LIS2DH12TR accelerometer.The freeRTOS sensor task is as following (checks on return values and variables definitions are removed to simplify the code comprehension): void MEMS_task(void) { lis2dh12_self_test(&dev_ctx); result = lis2dh12_operating_mode_set(&dev_ctx, LIS2DH12_HR_12bit); result = lis2dh12_data_rate_set(&dev_ctx, LIS2DH12_ODR_100Hz); result = lis2dh12_fifo_mode_set(&dev_ctx, LIS2DH12_BYPASS_MODE); result = lis2dh12_block_data_update_set(&dev_ctx, PROPERTY_ENABLE); result = lis2dh12_temperature_meas_set(&dev_ctx, LIS2DH12_TEMP_ENABLE); for (;;) { result = lis2dh12_xl_data_ready_get(&dev_ctx, &acceleration_data_available); if (acceleration_data_available != 0) { /* Read accelerometer data */ memset(data_raw_acceleration, 0x00, sizeof(data_raw_acceleration)); lis2dh12_acceleration_raw_get(&dev_ctx, data_raw_acceleration); acceleration_mg[0] = lis2dh12_from_fs2_hr_to_mg(data_raw_

I have a project where I'm using the BLE whitelist.In order to do that I'm using the aci_gap_set_undirected_connectable API.However, the BLE beacon does not seems to advertised, only the scan response seems to be shown by my phone.When I tried to use the aci_gap_set_discoverable, beacon was shown as expected.Am I missing something?Any help will be appreciated.  The project runs on STM32WB55.I used both ST BLE toolbox and nRF connect applications on my android phone to view the advertise data.The code that does not advertise the beacon:    uint8_t AdvertiseBeacon[] = {ADVERTISE_BEACON};    uint8_t ScanResponse[] = {SCAN_RESPONSE};    hci_le_set_advertising_data(beaconSize, (uint8_t*)&AdvertiseBeacon);    hci_le_set_scan_response_data(sizeof(ScanResponse), ScanResponse);    aci_gap_set_undirected_connectable(advertiseInterval_min,         advertiseInterval_max,        GAP_RESOLVABLE_PR

Hi! I've got a product that we've just made a load of and while building out the firmware I realised that the INT pin on the LIS3MDLTR doesn't (at least according to the datasheet) appear to be able to be configured to show when new data is ready. The DRDY pin seems to be required for that, and it hasn't been connected in our design.Is there any magic way of using INT as a DRDY pin, like a hidden register value that could be changed?Failing that, are INT/DRDY open drain outputs? We have very limited IO on our MCU, but could we short them together in a revised design?thanks,Gordon

Guys, I ran into a strange problem while debugging LIS2DH12, someone help me. I configured the high-precision mode, using 12 bits, with a range of +-4g, that is, when I placed the table (the chip with the sign facing up, the positive direction described in the instructions) it should have been subject to neutral acceleration and the converted value should have been -1g, but the result I got was +1g, I verified the other two axes, The resulting acceleration value is the opposite of the direction indicated in the manual, that is, when I always accelerate in the opposite direction of each axis, the resulting conversion value is indeed positive   Moreover, I read out the register value directly using lis2dh12_from_fs4_hr_to_mg function for conversion, and the size is close to 1g, but its direction is reverse, at this time I am the chip marked up, the acceleration value should be gravity acceleration downward is negative, it is positive.

@John E KVAMI ported the gesture recognition example (STSW-IMG035_F401) from the STM32F401RE to the NUCLEO-U575ZI-Q with the X-NUCLEO-53L8A1 and the gesture library (STSW-IMG035_M33).  If I used the VL53LMZ_ULD_API driver included with the GestureKit it seemed to work fine; all gestures were recognized. If I used the VL53L8CX_ULD_API driver (STSW-IMG040), it worked poorly; only the TAP gesture was recognized (and even that was inconsistent).  This was repeatable on the same hardware;  I could load and calibrate the MZ based project and it worked fine, then I could load and calibrate the 8CX based project and it would only recognize the TAP gesture.  I was surprised that the driver intended for the specific part performed worse than the generic one.I've attached the two ported projects (one using the MZ driver and one using the 8CX driver) for comparison.Have I missed something? Note: One significant difference I just found was that If I held a book at about 20c

I use accelerometer LIS2DH12 to wake up the device by motion detection. It's working correctly for long time but currently I found a trouble with interrupt. It's rarely happen and hard to reproduce.Here is my initialization: INT1_CFG = 0010 1010INT1_THS = 0000 0010INT1_DURATION = 0000 00010CTRL_REG2 = 0000 0101CTRL_REG3 = 0100 0000CTRL_REG5 = 0000 1010 (LIR_INT1 = 1)read to clear INT1_SRCI start up my device and wait device go to sleep, then I lightly touch on my device to wake up, The INT1 signal and I read INT1_SRC register before continue proccess. After that, the INT1 still signals again and again eventhough I leave my device stable on the table.I have checked LIR_INT1 at CTRL_REG5 that INT1_SRC cleared by reading INT1_SRC but when INT1 signal, I read INT1_SRC (= 0110 1000 for example) then second read INT1_SRC (still = 0110 1000). To stop INT1, I have to clear INT1_CFG in my code. Note that, The whole process I make sure

Hi, I am trying to configure interrupt on LSM6DSLTR module but I am not able to get any interrupt on the pin INT1.I am using nrf52 dk for setting interrupt on pin. err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_INT1_CTRL, 0x03);if(err_code != NRF_SUCCESS) return err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_TAP_CFG1, 0x90);if(err_code != NRF_SUCCESS) return err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_WAKE_UP_DUR, 0x00);if(err_code != NRF_SUCCESS) return err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_WAKE_UP_THS, 0x02);if(err_code != NRF_SUCCESS) return err_code;err_code = nrf_drv_mpu_write_single_register(LSM6DSL_ACC_GYRO_MD1_CFG, 0x20);if(err_code != NRF_SUCCESS) return err_code;After configuring interrupt my values becomes repeated or same<info> app: 251781.25, 231621.25, 231621.25, 1755.82, 1755.82, 1755.82<info> app: 33643.75, 13483.75, 13483.75, 235.09, 235.09, 235.09Ca

I have a question about the FIFO_Pattern.If I have only configured the accelerometer and set the watermark to 1536 samples, meaning 1536/3, which is equivalent to 512 samples (16 bits each sample) for each x, y, and z. And one sample is reading from 8 bit FIFO_DATA_OUT_L & FIFO_DATA_OUT_H.Will I have to skip the first 3 samples for the gyro, or will the samples be only for the accelerometer? For example, if the IF_INT bit in CTRL3_C (12h) is set to 1, and I am reading 6 bytes from register FIFO_DATA_OUT_L, do the first two bytes correspond to Ax, the next two to Ay, and the other two to Az?

Currently I connected the X-NUCLEO-53L8A1 to F401RE, and I notice that on the web page of VL53L8CH, the sensor can get the data with 64 zones with 18 bins at 15 Hz. But when I use the VL53L8CH with the Example_12_cnh_data which use VL53LMZ_ULD_API, I found that when I set the cnh config to get the data with 64 resolution, 16 bins, and 15Hz, the fps I get from the serial port is only 3.6Hz, not 15Hz. Is there any way to improve the FPS of the code?

HiI saw that the CS and I2C enable are on the same pin and also the SPI and I2C CLK and data.Does it means that this component can not be with other SPI IC on the same line? (because when the CS is 1 while talking to other ICs it will be in I2C mode and will transmit junk to the bus)? if so, its intended use in SPI mode is to be single component on the bus?regarding Lis2MDL it has I2C_DIS (h62 bit 3). this is also not 100% clear to me. If I connect 2 ICs on same bus in the moment I will start to config the first IC to disable I2C the other will interfere because it CS will be on 1... please help me understand how can I do it? maybe the I2C_DIS bit is the default (it is missing in the datasheet)?please help me understand this issue.thanks

Hello,I'm currently using VL53L8CX with an STM32U535 on a custom PCB.I'm using X-CUBE-TOF1 package.I'm able to identify the sensor with SPI at 2MHz using vl53l8cx_is_alive function.I was able to successfully init and use VL53L8 on U-585I-IOT02A dev board with the same code.there is my function to send data throught SPI :And to receive data  : The problem is in function vl53l8cx_init.There is timeout in various function depending on SPI frequency and apb frequencytimeout can come from this line (325) or from _vl53l8cx_poll_for_mcu_boot function.Often timeout appear at the third occurrence of _vl53l8cx_poll_for_mcu_boot function.I'm clearly lost in the search for the causes of this problem. I tried to increase or decrease the SPI frequency but this only change the line where the timeout occurs. I remain available for any further information.Thx for every kind of help ! 

Hello,I am looking for sensors for an upcoming research experiment looking at helmet-mounted motion and environmental sensing and found this article: MEMS Accelerometer Integral To New Helmet-Mounted Impact Sensor | Electronic Design. I am not looking to study collision; this will be used in an aerospace environment where I will be looking at acceleration, vibration, and head angle, as well as multiple other environmental factors (temp, pressure, etc.). This led me to the x-nucleo-IKS4A1, which appears to have all (or most) of the capabilities I am looking for, but I am pretty new to all this and would like to understand: 1) if there may be a better product, 2) what would need to be purchased alongside this product, and 3) average time of set up for implementation especially for someone unfamiliar with these systems. Thank you!

Hi everyone, I am currently using the VL53L8CX for people counting. However, I have encountered an issue where occasionally, changing the data acquisition rate during the data collection process causes a disruption and prevents further data acquisition.1. How can I dynamically change the acquisition rate during the data collection process?2. How can I dynamically change the integeration time during the data collection process? 

HiI refer to the VL53L0X Datasheet DoclD029104 rev5 page 15 article 2.10 Ranging Sequence.There not a lot descritption in your documentI need to understant how GPIO1 stay down before the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 1/ GPIO1 is not pulled up, the sensor pull it down, then the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 2/ GPIO1 is pulled up by 10k ohms, the sensor pull it down, then the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 3/ GPIO1 is not pulled down, the sensor pull it up when , then the sensor pull it up when init/ranging/housekeeping phase is finish.hypothesys 4/ the API pull the GPIO1 down and wait that the sensor pull it up when init/ranging/housekeeping phase is finish. Thanks in advance for answers

As far as I know, dToF has two illumination modes. One is spot dToF (iPhone) and the other is flood illumination. Which one is VL53L8CH? Thanks.

Hello, Im trying to set up Act/Inactivity INT1 at high ODR (1.66khz / 2000dps / 4g). Its threshold is too high so it resets or goes in/out of active/inactive state too often. Is there any way to lower the activity threshold so it really needs to be at rest to enter an inactivity state? Regards, 

Hi, I am working on Anomaly Detection in motor using ISM330ISN. As soon as I am choosing the Buffer Size of 256 in the datalogger and adding the signal, I am getting this warning of minimum RAM required is 9KB. However upto 128 buffer size, it is working fine. What is the reason that I am getting warning as I am going above 128 buffer size ? @Denise SANFILIPPO @Eleon BORLINI   

As mentioned in the datasheet of ISM330IS, we can go to accelerometer ODR of 6667 Hz but in the NanoEdge AI Studio, it is showing only upto 833 Hz. Can you tell how can we go above ODR of 833 and the. Also how can we go above Sample per axis i.e. buffer size of 256 ? @Denise SANFILIPPO @Eleon BORLINI    

Are formulas 1-4 correct in AN5894?Segment [AC] is the hypotenuse of triangle ACE, and the angle between segments [AC] and [CE] is half the dihedral angle HFOV. Then formula 1 should have a sine instead of a tangent.If I am right, in the example the angle between the segment [CB] and the opposite segment of the pyramid should be [DFoV] = 2*ASin(Sqrt(2*(Sin(60/2))^2)/Sqrt((Sin(60/2) )^2+1)) = 78.5 degrees. This value agrees with measurements made on the 3D model.

Hello,VL53L8CA is active product on your product list but i couldn't find a datasheet and sample.I have contacted with my local reseller buying termin is 22 weeks. Before buying i would like to have a datasheet and sample. What is the last situation of VL53L8CA?  Thanks in advance,  

Hi there, In the app, my steval-mki197v1 with LSM6dsox gets recognized as LAM6DSO32.Is this normal behaviour?luika

Hi!I’d like to know if the Vl53L8xx product series support “SPI daisy-chaining” ?For a project, I’ll need few of those, either “straight” along a line segment ( +/- like Neonode’s ZForce sensor bar ), as a “grid”, or as an “arc section” ( that is, a curved line segment ), and I’d like to maximize speed while minimize the needed pins to control the whole set of n sensors.Regarding my choice among the whole “VL53L” product lineup, it seems it’s the only one that supports SPI, which is one of the main needs for the project, the others being the smallest amount of processing needed on the “controller” uC, and a precise-enough detection of multiplemfingers up to 10cm from the sensor in a reliable manner.From what I can read in the datasheet, it does some “auto-incrementing” stuff when begin given more than the expected 15+8 bits, which may get in the way or even prevent some tricks I had in mind totally ( I guess, wrongly ? )This being said, I could also be cool repurposing the GPIO1 of oth