MEMS (sensors)

Is it possible to run any of the ST PDM mic sensors with a spread spectrum clock input? What implication does that have on audio quality? For example, is it possible to run any of the sensors with a clock input of 3.075MHz PDMCLK with 0.5% center spread frequency deviation at a modulation rate of 33kHz?Best Regards,Casey

..

Hi there,The spec for the LIS3MDL doesn't include I/O voltage thresholds like Voh, Vol, Vih, Vil. Can anyone point me to a reference for these? Seems like basic info that should be included in the spec. Maybe I missed it, but I've checked a couple times.Thanks!Steve

In my project i am using LSM6SOX sensor to generate the interrupt for every 10 degree incrementation on X axis. I found this link...https://github.com/STMicroelectronics/STMems_Standard_C_drivers/blob/master/lsm6dsox_STdC/examples/lsm6dsox_fsm_raw.c it worked well! Similar way of "/Program: glance/" static const uint8_t lsm6so_prg_glance[] = { 0xb2, 0x10, 0x24, 0x20, 0x17, 0x17, 0x66, 0x32, 0x66, 0x3c, 0x20, 0x20, 0x02, 0x02, 0x08, 0x08, 0x00, 0x04, 0x0c, 0x00, 0xc7, 0x66, 0x33, 0x73, 0x77, 0x64, 0x88, 0x75, 0x99, 0x66, 0x33, 0x53, 0x44, 0xf5, 0x22, 0x00, };I am try to generate .ucf.. using this link... https://github.com/STMicroelectronics/STMems_Finite_State_Machine/tree/master/configuration_examples/example_0_fsm`const ucf_line_t Free_fall[] = { {.address = 0x10, .data = 0x00,}, {.address = 0x11, .data = 0x00,}, {.address = 0x01, .data = 0x80,}, {.address = 0x04, .data = 0x00,}, {.address = 0x05, .data = 0x00,}, {.address = 0x5F, .data = 0x4B,}, {.address = 0x46, .data = 0

We have commercial product based on the LSM6DS3 and are now moving to the IIS3DWB (in combo with the STM32L412). One of the cases we often encounter with customers is the observation of "slow" phenomena (like large machines moving slowly). This was relatively easy with the LSM6DS3 by setting a low ODR (with associated anti-aliasing) filter. Now with the IIS3DWB the ODR is fixed. LPF1 is fixed too. HPF (from the composite filter) is used to eliminate gravity and LF noise. So if, I understand correctly, to achieve the above we need to implement our own downsampling consisting of an anti-aliasing LPF + decimation, all running at 26.7k, to achieve sampling rates of say 26 or 52Hz? This looks like at step back from the LSM6DS3. Or am I misunderstanding the capabilities of the IIS3DWB ? Thanks for advice.

..

On loading the firmware to the MKI 109, the ST Cube Programmer yielded a unique serial number for each of the 109 devices. However, I can not get the ST Cube programmer to reopen the connection once the firmware is updated. This is a problem because we are using two MKI210 devices with a single NUC. If the NUC reboots the devices can swap Port numbers, so I cannot use the Port Number as a unique identifier. Is there a way to read the serial number from the MKI210 device with C# code at the time I boot the computer? I enclose a results set, which are good.

I have question regarding the accelerometer LIS2DH12.I'm trying to configure the interrupt, to trigger when e.g. the x-axis goes above a threshold value. Not sure what to put in the INT1_THS register?and, in the output registers (OUT_X_L and OUT_X_H) what's the value/unit? is it in g, mg or m/s2?Looked in the datasheet and looks like when the sensor is configured in Normal Mode with +-2g sensitivity, each digit is equal to 4mg?So if I read out for example the raw value '2000' from x-axis, this should be:2000x4 = 8000mg = 8g?How can it be 8g when the measurement range is +-2g?

Hi ST engineers, my project use LSM6SDLTR connect with TI chip by I2C. I already get the orginal data and trying to trans them into quaternions or eulerian angles. Here is some issues.1.accelerometer original data have some noise.How to deal with them?2.Are there any quatenions transfer demo or lib?3.My eulerian angles data is not correct , pitch is always the same value and it rotated automaticly while there are not movement of my board.

For the test of 'Vibration monitor' in the SensorTile.box example apps, I made data with 'Vibration monitor Training' and tried to test 'Vibration monitor Comare', but an error message 'SDfile needed for the app not found' appears and I can't run the app.​ ​in USB virtual disk, There are files logged by the App 'Vibration monitor Training'​​​

Is the sampling rate of the X,Y axis different from the Z axis? I am trying to sample at 1kHz and I noticed that the Z-axis is sampling slower than X,Y when reading the status register.

I want to detect both single and double tap and distinguish between them. For example, if I tap the device once, the device knows it is a single tap. If I tap the device twice, the device knows it is a double tap. But the current register configuration can only detect double tap event, not single tap event. Single tap event does trigger INT1, but it is not latched and cannot be detected in TAP_SRC and STATUS pins. Could you please let me know which register configuration I am missing?+) If it is impossible to detect both single and double tap in INT1 and distinguish between them, is it possible to separate them so that INT1 detects single tap and INT2 detects double tap? Register Configuration:Image attached Test Steps :Single tap on the LIS2DS12 boardExpected output :1. Interrupt 1 triggered and latched.2. The value of "STATUS (27h)" pin is 49 (WU_IA, SINGLE_TAP, and DRDY turned ON)3. The value of "TAP_SRC (38h)" pin is 6* (TAP_IA and SINGLE_TAP turned ON).  Actual Obse

Hello, I'm trying to enable the MLC option for the MKI197V1 and I'm having some trouble.The DatalogFusion runs fine when configured for the WL55JC, but what I want is the MLC option that can be seen on the DataLogExtended sample. Any guidance is appreciated.

Hi I recently bought a IKS01A3 and want to do research related to human activities. I already have a nucleo-wb55 with me so basically I just connect them via arduino uno V3 ports and willing to set up I2C communication between those two boards. I know there are higher-level drivers and software packs for IKS01A3 board together with fancy UI, but is there a way that we can directly retrieve data according to each sensor unit's datasheet?I've connected the board's outside connection I2C SCL and SDA (Arduino connector CN10 pin 10 and pin 9) to IC2_1 on IKS01A3 (DIL24 socket pin 20 and pin 21 respectively), and since I2C bus routing are connected as 1-2/3-4(default setting), which means I2C_1=I2C_2 with all devices are on the same bus.#define I2C_SLAVE_ADDR 0x94 << 1 #define CODY_MAX_TRIAL 50I define the slave address of the STTS temperature sensor on IKS01A3, and since it's given by the datasheet as 0x94, which mean 0b'10010100, I believe we need to shift leftwise 1-bit (act

..

Hello,I'm using an STM32 M4 for recording short audio signals through the I2S interface and I write the PCM to an SD card. To check that everything is fine I have recorded pure tones (1kHz or 2kHz). By doing that I noticed in some recordings (not all of them) some glitches in the audio signal. Can someone help understand why those glitches appear?The reference manual reports that I2SxCLK frequency should be higher than the APB bus. In my case the APB is 16MHz and the I2SxCLK is 48MHz. Here is attached one of the 2s audio tracks recorded. Sometimes the glitch appears at the beginning of the track, some others later.What else can generate this issue?

..

As you can see in the picture, the higher part of the sinusoid signal is getting wrecked in the highest part, but it appears in the lower part (so the information is still there).This happens when the magnetic field is strong enough (We are putting a coil next to it generating the magnetic field)The problem is that I (and any of the people I work with) do not think this is a big enough magnetic field for it to overflow, so that is why we are wondering if there is another problem we did not think about.As the manufacturer suggests, the data aquired by the magnetometer should be processed as following: and what I am doing to process it in the code is exactly that:uint8_t y_low = 0; uint8_t y_high = 0;   //y_L HAL_I2C_Mem_Read(&hi2c1,slave_address << 1, OUTY_L_REG, I2C_MEMADD_SIZE_8BIT, &y_low, size, HAL_MAX_DELAY);   //y_H HAL_I2C_Mem_Read(&hi2c1,slave_address << 1, OUTY_H_REG, I2C_MEMADD_SIZE_8BIT, &y_high, size, HAL_MAX_DELAY);   y_val

..

..

..

..

..

..

..