MEMS (sensors)

We are planning to use 9DoF sensor LSM9DS1 with STM32L4 controller.We tried to find sensor library on web but not able to get one, can you pl provide us supported library including sensor fusion for STM controller?

We have an LIS2DE12 accessed via i2c. We set:0x20 to 0x1f0x1f to 0xc00x23 to 0x80Then we read 0x07 until TDA is set.Finally, we read temperature data.Example 1:0x0c = 0x000x0d = 0x13Example 2:0x0c = 0x800x0d = 0xdfHow do we convert these values to degrees?

Hi,We are using gyroscope calibration library for linux in order to get more accurate gyroscope values. Can u please tell me what value need to be set for the various parameters in the iNemoEngine_gbias_setKnobs() API .Thank you,Best Regards,Sharmila

I am going to use STM32L4R5 series controller.

Arduino IDE currently has these files for the above MCU + LSM6DS33. I need to replace this sensor with the ISM330DLC, avoiding starting from scratch if possible.

I was wondering about the format of the data from the H3LIS331DL accelerometer. At +/-400 scaling, 0.195 is listed as the scaling factor (in G). However, the data appears to be only 12-bit, left justified, since the lower 4 bits are always zero. After multiplying the result by 0.195, does it also need to be right-shifted 4 bits? If this isn't done, the stock G values at rest are quite high, anywhere from 5-10 G.

Posted on July 03, 2018 at 03:35LSM6DS3 Continuous FIFO interruptsFor this discussion 1 sample = 6 bytes of 3d accelerometer data.I want to use FIFO to save power on CPU.As long as all sample data fits in the FIFO, all is straight-forward.I'm unable to figure out how to use Continuous mode to read more samplesthan fit in the FIFO.Example:I want's to read 2048 samples x 6 bytes.Because FIFO is 8k I intend to read 2 x 1024 samples. I have tried many combinationsof fifo status bits, but no approach works. Here's one attempt:setup-----FIFO_CTRL3.DEC_FIFO_XL = 1CTRL4.DRDY_MASK = 1FIFO_CTRL1/2.FTH = 3093 // (1024 samples + 7 discards (my setting)) *3INT1_CTRL.INT1_FTH = 1FIFO_CTRL5.FIFO_MODE = 6 // Continuous modeisr---if (FIFO_STATUS2.FIFO_FULL == 0)   // first read    // discard i

Porting the VL53L0X API (https://my.st.com/content/my_st_com/en/products/embedded-software/proximity-sensors-software/stsw-img005.license=1533144599665.html) to a particular platform requires implementation of a set of functions abstracting I2C access:VL53L0X_LockSequenceAccessVL53L0X_UnlockSequenceAccessVL53L0X_WriteMultiVL53L0X_ReadMultiVL53L0X_WrByteVL53L0X_WrWordVL53L0X_WrDWordVL53L0X_RdByteVL53L0X_RdWordVL53L0X_RdDWordVL53L0X_UpdateByteVL53L0X_PollingDelayHowever, all of the VL53L0X_{Rd,Wr} functions can be written in terms of VL53L0X_RdMulti or VL53L0X_WrMulti. Furthermore, VL53L0X_UpdateByte can be written in terms of WrByte, WrByte, and the Lock/Unlock functions.These implementations should be added to the core API, reducing the necessary platform functions to:VL53L0X_LockSequenceAccessVL53L0X_UnlockSequenceAcce

Hello,We are developing a board for sound processing based on the the bluecoin(STEVAL-BCNKT01V1) demo board, we have several questions concerning the way we can implement this technology on our board. On the board we develop we want to test stereo sound localization with on board microphones and microphone external to the board.1-   The microphone used on the bluecoin (MP34DB04) is not commercialed any more can you recommend us same replacement component? 2-   On the boards STEVAL-BCNKT01V1 there are 4 microphone, 1 microphone is clocked by the signal MIC_CLK which is generated by the microcontroller, the 3 other microphones are clocked by a signal MIC_CLK_234 which can be disabled by the microcontroller through a switch. Could you clarify what is the use of this architecture? 3-   In our solution we want to test the possibility to use 4 external microphones. These external microphones would be on small da

Posted on July 12, 2018 at 06:09今�RUNNESAS製R5F100FCを使��VL53L0X�ら�離データを�得�よ�������。���データシートを見る��レジスタ情報���困�����。スレーブアドレス�0x52��る�����り����データレジスタやconfig�レジスタ�全�分�ら��������助������。

Posted on July 05, 2018 at 05:48Where can I find VL53L1X mbed driver? Thank you so much.

hai , iam using ii2328dq for reading the accelerometer values so here from sensor i got continues data how to know that frequency of data and could you pkease tell me how tocontrol that sensor data frequency.

Hello Experts,I have STEVAL-WESU1 board and able to run given demo example, now I would like to enable the UART debug port to see whats going on in code.This is the example I am using to run on the smart STEVAL-WESU1 board.~\STSW-WESU1\Projects\STEVAL-WESU1\Demonstrations\WESU_DEMO\SW4STM32I referred the following user guide(page no 19) and shorted the 2nd & 3rd position of J1 & J2 jumpers. And connected 6th pin(RX232) of J5 connector to RXD of "TTL to USB" converter, and USB is connected to my PC, no output seen in serial terminal.Please correct if me I am missing anything.https://www.st.com/resource/en/user_manual/dm00279614.pdfCan you please help on this ?Any help greatly appreciated.Thanks for the help.

Helloi tried to integrate SimpleRangingExamples of  X-CUBE-53L1A1 in a multi-thread FreeRTOS environement (4 threads also access the I2C)The SimpleRangingExamples of X-CUBE-53L1A1 running alone in a thread is OK. I want to add this thread to the 4 other thread accessing the I2C.I have protected the i2c with semaphore : the 4 threads share well the I2C. to add the SimpleRangingExamples in a new thread , i have the following definitions :define VL53L1_GetI2cBus(...) CO_Mutex_get() osMutexWait(i2c_mutex_id, osWaitForever)define VL53L1_PutI2cBus(...) CO_Mutex_put() //(void)0 //CTT osMutexRelease(i2c_mutex_id)the thread is the following :void PY_TASK(void const * argument){   int status;   Dev->I2cHandle = &hi2c1;   Dev->I2cDevAddr = 0x52;//CO_Mutex_get(); status = VL53L1_WaitDevic

I have recently purchased an STM32F767ZIT6 Nucleo kit, as well as an X-Nucleo-IKS01A2 MEMS expansion board. I installed Unicleo-GUI, and downloaded the X-CUBE-MEMS1 software. I can't figure out how to get firmware to run on the board though. I dropped a couple of .bin files into the appropriate location (although all of the folders in the Projects/Multi/Applications directory seem to only have folders for STM32F401RE-Nucleo, STM32L152RE-Nucleo, and STM32L476RG-Nucleo...). When I click on "Program", the LEDs on the board cycle, but when the program gets to the "Waiting for firmware response" section, it never gets a response.I don't care what firmware I even run, I'd just like to see the Unicleo GUI talk to my board. Right now all I have is "Firmware Description: Unknown".

Posted on July 16, 2018 at 09:02Hi All,I need device driver for LIS35DE MEMS motion sensor.CPU is I.MX6Q and linux platform kernel 4.4.0-130-generic.Could you give me a this driver?Thanks & BR,#lis35de

Base assumptions:1.    Testing equipment – X-NUCLEO-L053R8 base board with X-NUCLEO-IKS01A1 and X-NUCLEO-IKS01A2 expansion boards.2.    Magnetometer devices under consideration - LIS3MDL on X-NUCLEO-IKS01A1 and LSM303AGR on X-NUCLEO-IKS01A2.3.    Magnetometer initialization parameters – 50 Hz sampling rate, random parameter set (applies to any combination of parameters – low and high output data rate and/or full scale, different operating modes, etc.).4.    Magnetometer (and expansion board) positioning – completely static (the device is being tested with the expansion board being positionally fixed).5.    Magnetometer calibration – Completely static positioning before testing implies no need of explicit calibration.Testing data1.    Four (4) tests performed by placing monolithic me

I use LSM9DS1 with STM32L433 and get strange data.Initialization code:HAL_GPIO_WritePin(CS_A_G_GPIO_Port, CS_A_G_Pin, GPIO_PIN_RESET);   address = CTRL_REG4;   data = 0x38; //0b00111000   HAL_SPI_Transmit(&hspi1, &address, sizeof(address), 0x1000);   HAL_SPI_Transmit(&hspi1, &data, sizeof(address), 0x1000);   HAL_GPIO_WritePin(CS_A_G_GPIO_Port, CS_A_G_Pin, GPIO_PIN_SET);     HAL_GPIO_WritePin(CS_A_G_GPIO_Port, CS_A_G_Pin, GPIO_PIN_RESET);   address = CTRL_REG5_XL;   data = 0x38; //0b00111000   HAL_SPI_Transmit(&hspi1, &address, sizeof(address), 0x1000);   HAL_SPI_Transmit(&hspi1, &data, sizeof(address), 0x1000);

Prior to the forums being migrated, I saw a post linking to sites to obtain reflectance targets for calibrating and testing the VL53L1X or VL53L0X. I.e. Grey 17% N4.74, Grey 54%, and White 88% N9.5. I'm moving from breadboard development with the satellite boards to a PCB with the VL53L1Xs sensors populated on them and calibration will become a necessity. I've attempted searching the new forums for this post without much luck. Could anyone direct me to where to obtaining these reflectance targets?

It appears that the functionality is written into the code but I can't figure out how to get it to work. I am using the SW4STM32 IDE to build and compile and I know that in main.h there is #define ENABLE_MEMS 0 which can be changed to a 1 but the .h doesn't recompile and build when I rebuild the project. Only the .c files build. 

I have confusion about I2C address for magnetometer.As in the datasheet at page 11:SDO_M: I2C least significant bit of the device address (SA0) for the magnetometerBut in the table 20 page 30:See picture enclosedIt looks like the SDO_M pin is used for SAD[1] since the SAD[0] is not change.Please help me in this case, is it correct?

Posted on July 12, 2018 at 08:16Dear all - especially STM developers,I recently integrated an LIS331HH sensor. It seams to be very nice sensor! But anyway while reading LIS331 Datasheet, I found that information required for proper MCU driver implementation (especially interrupt-related information) missing.Even though some information become clear during repeated reading of Datasheet, something remains unclear. Even though I was able to find proper settings experimentally, it took some time...Some points: The two's complement output (OUT_X_L, OUT_X_H, ...) range is not explicitely given (it is clear after repeated Datasheet reading, but implicitly hidden) - is it full range (16bit two's complement used? or there are limits? e.g. -4096 to 4096?) - I found, that full range is used for LIS331HH, but other family members are be different (I have no experience, but I saw code here:

The VL53L0X API (https://my.st.com/content/my_st_com/en/products/embedded-software/proximity-sensors-software/stsw-img005.license=1533144599665.html) requires definition of a platform-dependent structure of type VL53L0X_DevData_t. This structure must contain a field of type VL53L0X_DevData_t, where the API stores all portable state data.API functions primarily access this embedded field through a pair of (again, platform dependent) macros -- PALDevDataGet and PALDevDataSet. However, there are portions of the API which don't follow this convention -- instead, they directly access a struct field named Data.This forces platform implementations to declare the device structure in a precise way, while also forcing the declaration of that macro. This is non-ideal, and the problematic areas of the code should be fixed to be consistent. Specifically, there are direct field accesses at:vl53l0x_api_core.c: 419vl53l0x_api_calibration.c: 73

Hi all,I am designing an application which would tell me, if a ping pong ball lands on a particular area of a table or not. Below is a sketch that illustrates:Sensors would be placed on left side of the table, facing the other side as shown in the above image.Minimum and maximum distance range for the sensors to track the ball, would be 2cm to 153 cm respectivelyMore importantly , if a ball would fall within the area of 153 x 137, the sensors should be able to detectMy questions:After going researching on different sensors available., i have narrowed down to VL53L1X. Do you think this is the right choice?If one VL

When I use the breakout board included in the dev kit, the precision is at most 2 mm, but when I use the VL53L1X soldered on one of my board, the precision is really different. Is there a particular calibration or setting that are input to the breakout board that would make it this way?